Finofo works alongside your ERP: it uses the vendors, accounts and coding dimensions your team works with, does the capture, coding, matching and approval, then sends approved invoices and payment records back.
Native integrations cover NetSuite, Sage Intacct, QuickBooks Online, Xero, Microsoft Dynamics 365, SAP Business One, Odoo, Sage 300, Acumatica, DualEntry, Campfire and PBS, and any system can connect through a pre-built integration, an API, secure files or scheduled exports.
You can start using Finofo before your ERP is connected.
Your ERP stays the system of record for the ledger and financial reporting. Finofo does the accounts payable work before an entry reaches it. Documents are captured, read, coded, matched and approved in Finofo, and the comments, exceptions, approval history and original attachments stay with each one.
Every connection has the same shape. Reference data comes into Finofo, so coding uses the same vendors, accounts and dimensions as your ledger. Finished work goes back, so your ledger receives coded, approved entries with no rekeying. Posting always follows approval.
Invoice lines are coded by company, GL account, operating unit and department, plus optional dimensions such as project, with the required fields and valid combinations your organization sets. Reference data comes from your ERP through the connection, a CSV import or is maintained manually. Each ERP names its dimensions differently: classes and locations in QuickBooks Online, segments in NetSuite, dimensions in Sage Intacct and Business Central, tracking categories in Xero, subaccounts in Acumatica, analytic accounts in Odoo.
Each direction below shows what moves, followed by why it matters.
These systems have native Finofo integrations. The middle column shows how each one usually structures coding, which is what you plan around during setup.
Each system below shows how coding is usually structured, followed by what to plan around.
The right route depends on your ERP version and what data needs to flow in each direction. Your Finofo team confirms it with you before implementation begins. If your system is not listed, it is still worth the conversation: the path is scoped around your entities, vendors, coding rules and export formats.
1. Scope the rollout with your Finofo team: the entities in scope, the coding dimensions, the approval rules and a set of test documents.
2. Agree the connection path, and what data flows in each direction.
3. Clean up the vendor list in your ERP: merge duplicates and make inactive vendors inactive. A clean vendor file makes the first import and vendor mapping much faster.
4. Check Settings > Members and roles to see what each role can do, and decide who looks after the integration.
5. Post the test documents and check each one in your ERP before go-live.
With a pre-built connector, customers have gone live in as little as two weeks.
1. Open Settings > Integrations. With a pre-built connector such as QuickBooks Online, the integration card shows the connected system, a Connected chip, a Last sync line with the date and time of the most recent sync, and a Sync button.
2. On the GL properties tab, review each property brought in from your ERP. Used for sets where it is offered when coding: invoices, expenses, both or neither. Required for sets which coding cannot be completed until it is filled in.
3. Click a property to open its records. Click Describe on a record to say what it is for in your own words. Automatic coding uses these descriptions when no rule covers an invoice.
4. In Coding settings, use Add rule to code recurring vendors automatically. Rules are evaluated top-down, and the first match wins for each property.
The connection method, ERP version and objects supported vary by installation, so what this page lists for your ERP is agreed during setup.
Each vendor profile in Finofo holds its ERP mapping, so bills post to the right vendor. Vendor reference data can come from your ERP, a CSV import or manual entry.
1. Where your connection lists ERP vendors, open Settings > Integrations, then GL properties, and click Vendors. On ERP Vendors, the Unmapped tab lists vendors from your ERP that are not yet linked to a Finofo vendor.
2. For each row, click Select & match and pick the matching Finofo vendor.
3. To bring in every unmapped ERP vendor at once, click Import All ERP Vendors.
1. Open Settings > Documents, Invoices tab, and go to Approval and posting.
2. Choose Automatic posting to check the vendor, invoice number, dates, line items and coding before an invoice goes to approval. The final approval posts the bill to your ERP.
3. Or choose Manual posting. Invoices go to approval, and a reviewer posts each approved invoice with Post to ERP.
4. Click Save.
With Manual posting, the Post to ERP drawer checks each invoice and shows whether it is ready or blocked, and why, before anything is sent. A posted invoice shows a Synced with ERP chip, and its ERP section shows the destination and a link to the record in your ERP.
How payment records reach your ERP is settled with your Finofo team during setup. With QuickBooks Online, you map them on Payment entries:
1. In your ERP, make sure there is a GL account for each Finofo currency account, for example one for CAD and one for USD.
2. In Settings > Integrations, open Payment entries. Under Finofo currency accounts, map each Finofo currency account to its ERP GL account. Finofo posts payment entries with these accounts when batches are paid out.
3. Under External Payments, you can limit which GL accounts can be chosen for Cheque, Bank Payment, Credit Card and Vendor Credit, and mark one as the default. Leave a method empty to keep all accounts available.
You do not need a live connection to start. Documents can be captured, matched, approved and paid from day one, and clean, coded invoices posted once the ERP is connected. This helps during an ERP migration, for a newly acquired entity or while a connection is being scoped. Purchase orders, contracts and blanket POs can also be tracked in Finofo before they exist in the ERP. POs do not have to be created in Finofo: they can be brought in from an existing system, and the path for PO and receiving data is scoped for your ERP.
No. Finofo works with or without an ERP. You can capture, match, approve and pay first, then connect your ERP and post clean, coded invoices when you are ready.
Native integrations cover NetSuite, Sage Intacct, QuickBooks Online, Xero, Microsoft Dynamics 365, SAP Business One, Odoo, Sage 300, Acumatica, DualEntry, Campfire and PBS. Any system can also connect through an API, secure files, scheduled exports or custom workflow tools.
No. Your ERP stays the system of record. Finofo handles the AP work before entries reach it.
Rollout is scoped with your Finofo team around your entities, coding dimensions, approvals and test documents. With a pre-built connector, customers have gone live in as little as two weeks.
It depends on the connector and the design agreed with your Finofo team during setup. The integration card shows the date and time of the Last sync.
Yes. Invoice lines can be coded by company, GL account, operating unit and department, plus optional dimensions such as project, with required fields and valid combinations.
Yes. Finofo keeps the original attachments, including Word, Excel and Outlook files, and you can download them. Whether the file is also attached to the record in your ERP is confirmed for your system during setup.
Duplicate detection works within one organization. If you run separate organizations, a shared AP inbox can help triage documents before they are routed to the right entity.
Yes. POs can be brought in from an existing system and used for invoice matching, and the path for PO and receiving data is scoped for your ERP. You can also create POs in Finofo.
