EzzyBills
EzzyBills is an invoice data scanning application which automatically extracts invoice data, including line items. Invoices can be uploaded to EzzyBills via email, direct file upload, and via the EzzyBills scanning app. This saves time and reduces errors compared to manual data entry, provides a built in digital paper trail, and allows for paperless automation of common processes such as reconciliation, invoice approval and expense claims.
See the EzzyBills documentation for further information.
Prerequisites
Setup an EzzyBills trial account, make sure to choose Integrate with Cin7 Core
Users will need the Settings: Cin7 Core API Setup permission to generate API keys from Cin7 Core.
EzzyBills requires an API license to connect. Cin7 Core API licenses can be added to your subscription from the My subscription page.
Connect EzzyBills and Cin7 Core
You will need to create an API application in Cin7 Core and copy the details to EzzyBills in order to integrate the two.
NOTE: Two free external integrations are available under Cin7 Core's standard subscription plan. If you already have two integrations, you may first need to purchase licenses for the additional external integrations under the My Subscription page.
In Cin7 Core, navigate to Integrations → Cin7 Core API.
On the API Integration page, click the + icon on the top right, enter a name for the API (for easy identification, you might want to use EzzyBills as the API name), and click Create button to generate an API channel.
Cin7 Core then creates the API Account ID and Key under the Setup tab of the API Integration page. You will need both pieces of information to connect Cin7 Core to Pencil.
Click Save.
Login to EzzyBills, and click the top menu Apps. Click the icon for Cin7 Core.
Add the Cin7 Core Application ID and Cin7 Core Key in the text boxes.
Click Save.
Now you have connected EzzyBills to Cin7 Core. Congratulations!
Import Supplier Invoices into Cin7 Core
After the connection has been set up, you can start to upload supplier’s invoices to EzzyBills via file upload, or email, or EzzyBills phone app.
-
EzzyBills will extract the PO number from the invoice, and look for the PO in Cin7 Core with the matching PO number. If a match PO is not found in Cin7 Core, please follow this linkhere to rectify.
You will receive an automatic email notification if a PO match has not been found.
-
After the match PO is found in Cin7 Core for the invoice, and the PO is Authorized, EzzyBills try to match each bill line with a PO line.
If a Bill line does not exist on the PO (such as a freight charge), then the line be added as an Additional Cost.
The source document will then be attached to the PO.
Next, Authorize the invoice in Cin7 Core
Once you receive the stocks in your warehouse, you then click Add Stock Receiving, then Copy From Invoice. Edit the lines to verify the received items and click Authorize.
If all stocks are received, then the PO status will change to Received by Cin7 Core automatically. Steps 4-6 can be automated by EzzyBills. If you need this, please contact us at support@ezzydoc.com.
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB