Finofo and Acumatica: How the Integration Works

How It Works

From Acumatica, Finofo uses vendors and the reference data your team codes with, brought in through the connection, a CSV import or manual upkeep: accounts, subaccounts, branches, and the projects, tasks and cost codes 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 Acumatica as AP bills with their line coding. Posting follows approval, and how payment records go back is agreed with your Finofo team during setup.

Acumatica keeps the ledger, inventory and financial reporting. The source document, approval history, comments and exceptions stay with each invoice in Finofo.

What Syncs Between Finofo and Acumatica

• Acumatica to Finofo: Vendors, each mapped on its Finofo vendor profile.
• Acumatica to Finofo: Accounts, subaccounts, branches, and the projects, tasks and cost codes your coding requires.
• Finofo to Acumatica: Approved invoices with account, subaccount, branch and project detail on each line.
• Finofo to Acumatica: Payment records, in the form agreed with your Finofo team during setup.
• Stays in Finofo: The source document, approval history, comments and exceptions.

Set Up the Connection

1. Confirm the version, deployment, companies and branches in scope with your Finofo team.

2. Prepare Acumatica access with your administrator or partner. A dedicated integration user, rather than a personal login, keeps access auditable.

3. 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.

4. Check that each vendor profile in Finofo holds its ERP mapping, and agree with your Finofo team how payment records are sent back.

5. Test with real invoices before go-live.

Acumatica Decisions to Settle During Setup

Each area below shows the question to settle, followed by why it matters.

• Companies and branches: Which companies, tenants and branches does AP cover?
  Bills must post to the right branch with valid accounts.
• Subaccounts: Which subaccount segments carry department, location or product line, and are any filled in automatically?
  Acumatica builds much of its coding into the subaccount.
• Projects: Do bills need project, task or cost code on each line?
  Project cost reports depend on them.
• Bill status: Should bills arrive on hold for review, or ready to release?
  Keeps release under accounting's control.
• Approvals: Do approval maps run on AP bills in Acumatica?
  Avoids approving the same bill twice.
• Tax: Which tax zones and tax categories cover your vendors, including GST, HST, PST and QST where they apply?
  Each line needs the right tax treatment.
• Purchase orders: Are POs and purchase receipts raised in Acumatica, in Finofo or both?
  Decides where Finofo reads POs from for matching.

Fix Common Acumatica Sync Issues

• A subaccount or project is missing from coding options: Check that it is active in Acumatica and set up as a coding dimension in Finofo.
• An approved invoice is not in Acumatica: With Manual posting, open Post to ERP: the drawer shows whether the invoice is ready or blocked, and why. Check that the vendor profile holds its ERP mapping. Then check for a closed financial period or an inactive account, subaccount or vendor.
• A bill is rejected for its branch: Check the branch coded on the invoice, and that the account and subaccount are valid for that branch.

Tips

• Write down what each subaccount segment means before setup. It makes required-field decisions much quicker.
• If subaccounts are built automatically in Acumatica, agree with your partner which segments Finofo should code and which Acumatica fills in.
• Test one bill per branch in scope, and one with a project and cost code.
• Acumatica remains the system of record for the ledger, inventory and financial reporting.

Frequently Asked Questions

Does Finofo support multiple Acumatica companies and branches?

Finofo codes invoice lines by company, GL account, operating unit and department, plus optional dimensions. How your entities map to those, and the companies and branches in scope, is settled with your Finofo team during setup.

Can Finofo code projects, tasks and cost codes?

Finofo supports optional coding dimensions, such as project, alongside company, GL account, operating unit and department. List your project fields during setup so your Finofo team can map them and set required fields and valid combinations.

Does it matter whether Acumatica is SaaS or on premises?

Share your deployment with your Finofo team. The connection path is confirmed for your installation before implementation begins.

Can AP start before POs and receipts are in Acumatica?

Yes. Finofo captures POs and receipts directly and matches them at line level, then posts clean entries to Acumatica.