Finofo connects natively to Oracle NetSuite, which stays your system of record: Finofo syncs the vendors, accounts and segments your coding needs, then sends approved, line-coded bills and payment records back.
Settle a few NetSuite decisions during setup, such as which subsidiaries are in scope, which segments are required, which tax engine you use and whether the invoice file is attached.
Finofo can match POs and receipts it captures itself, so AP does not wait for NetSuite data to be complete.
From NetSuite, 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, and the departments, classes, locations, subsidiaries and custom segments your coding requires. Each invoice line in Finofo is coded with those values, so a bill that reaches NetSuite needs no recoding.
In Finofo, invoices are captured, read, coded, matched and approved. When an invoice is approved, Finofo sends it to NetSuite with its line coding. Posting follows approval, and how payment records go back is agreed with your Finofo team during setup.
NetSuite stays the ledger for financial reporting and close. The source document, approval history, comments and exceptions stay with each invoice in Finofo.
1. Confirm the setup with your Finofo team. NetSuite uses Finofo's native integration.
2. In NetSuite, create a GL account for each Finofo currency account, for example one in CAD and one in USD, under Setup > Accounting > Chart of Accounts. They give payment records an account for each currency.
3. Your Finofo team sets up the NetSuite connection with you. The route depends on your NetSuite version and what data needs to flow in each direction.
4. If your connection uses the integration bundle, your NetSuite administrator installs it from the link provided during setup and enables the required features on the SuiteCloud tab of Setup > Company > Enable Features.
5. 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.
6. Check that each vendor profile in Finofo holds its ERP mapping, and agree with your Finofo team how payment records are sent back.
Ask your NetSuite administrator to use a dedicated integration role rather than a personal login. It keeps access auditable and survives staff changes.
These are the areas where NetSuite accounts differ most. Agree each one with your Finofo team before go-live.
Each area below shows the question to settle, followed by why it matters.
1. Post a simple, single-line invoice from an existing vendor.
2. Post a multi-line invoice with different accounts, segments and tax on different lines.
3. Run an invoice with a price or quantity mismatch against its PO, and check that Finofo flags it before approval.
4. Post a credit note against an earlier invoice.
5. If you use OneWorld, post an invoice for a second subsidiary.
6. Pay a small batch and check the payment entries in NetSuite.
Open each record in NetSuite and confirm it is something your controller would accept at close without edits.
Finofo codes invoice lines by company, GL account, operating unit and department, plus optional dimensions, with required fields and valid combinations. How your subsidiaries map to those, and which subsidiaries are in scope, 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 custom segments during setup so your Finofo team can map them and set required fields and valid combinations.
Plan tax mapping with your Finofo team before the change, because enabling SuiteTax in NetSuite cannot be reversed.
Yes. Finofo captures POs and receipts directly and matches them at line level, then posts clean entries to NetSuite.
Talk to your Finofo team during setup. Whether open bills already in NetSuite come into Finofo for payment is part of the integration design, and approved bills can then be paid individually or in a batch.
Yes. Coding is set per line, so each line can carry its own account, department, class, location and other segments.
