Finofo connects natively to Sage Intacct, which stays your system of record: Finofo syncs the vendors, accounts, entities and dimensions your coding needs, then sends approved, line-coded bills and payment records back.
Settle the Sage Intacct decisions during setup: which entities are in scope, which dimensions are required, how bill approvals run and how tax is handled.
From Sage Intacct, Finofo uses vendors and the reference data your team codes with, brought in through the connection, a CSV import or manual upkeep: the chart of accounts, entities, and dimensions such as location, department, class and project, plus any user-defined dimensions your coding requires. Each invoice line in Finofo is coded with those values.
Invoices are captured, read, coded, matched and approved in Finofo. Approved invoices go to Sage Intacct as bills with their line coding. Posting follows approval, and how payment records go back is agreed with your Finofo team during setup.
Sage Intacct keeps the ledger, consolidation and financial reporting. The source document, approval history, comments and exceptions stay with each invoice in Finofo.
1. Confirm the setup and the entities in scope with your Finofo team.
2. Prepare Sage Intacct access with your administrator. A dedicated integration user, rather than a personal login, keeps access auditable and survives staff changes.
3. Your Finofo team sets up the Sage Intacct connection with you. The route depends on your Sage Intacct version and what data needs to flow in each direction.
4. Agree the coding dimensions with your Finofo team: which ones each line needs, which are required and which combinations are valid. Reference data comes from your ERP through the connection, a CSV import or manual upkeep.
5. Check that each vendor profile in Finofo holds its ERP mapping, and agree with your Finofo team how payment records are sent back.
6. Test with real invoices before go-live (see below).
Each area below shows the question to settle, followed by why it matters.
1. Post a single-line invoice from an existing vendor.
2. Post a multi-line invoice with different accounts, departments, locations and tax on different lines.
3. If you are multi-entity, post an invoice for each entity in scope.
4. Post a credit note against an earlier invoice.
5. Pay a small batch and check the payment entries in Sage Intacct.
Open each bill in Sage Intacct and confirm the dimensions, entity and tax are what your controller expects.
Finofo codes invoice lines by company, GL account, operating unit and department, plus optional dimensions. How your entities map to those, and the entities in scope, and whether bills post at the top level or at each entity,, is settled with your Finofo team during setup.
Finofo supports optional coding dimensions, such as project, alongside company, GL account, operating unit and department. List your user-defined dimensions during setup so your Finofo team can map them and set required fields and valid combinations.
No. They are different Sage products with different integrations. Sage 300 has its own article.
Approvals happen in Finofo, including on mobile, so approvers review and approve there rather than in Sage Intacct.
Talk to your Finofo team during setup. Whether open bills already in Sage Intacct come into Finofo for payment is part of the integration design, and approved bills can then be paid individually or in a batch.
