Finofo and Sage 300: How the Integration Works

How It Works

From Sage 300, Finofo uses vendors and the reference data your team codes with, brought in through the connection, a CSV import or manual upkeep: GL accounts, and the departments, locations, entities and optional fields 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 300 with their coding. Posting follows approval, and how payment records go back is agreed with your Finofo team during setup.

Sage 300 is often installed on your own servers or hosted by a partner, so the connection is planned with your Finofo team and your Sage partner. Sage 300 keeps the ledger and financial reporting.

Check Which Sage You Run

Each product below shows its former name, followed by whether it is covered here.

• Sage 300: Sage Accpac.
  Yes.
• Sage 300 CRE: Timberline Office.
  No. It is a separate construction and real estate product.
• Sage Intacct: Intacct.
  No. Sage Intacct has its own article.
• Sage 50 (Canada): Simply Accounting.
  No.

Check the product name and version on the Sage 300 About screen, and share both with your Finofo team.

What Syncs Between Finofo and Sage 300

• Sage 300 to Finofo: Vendors, each mapped on its Finofo vendor profile.
• Sage 300 to Finofo: GL accounts, and the departments, locations, entities, optional fields and other dimensions your coding requires.
• Finofo to Sage 300: Approved invoices with GL and coding detail.
• Finofo to Sage 300: 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 and connection path with your Finofo team. An on-premises installation may need something set up on or near the Sage 300 server, so involve your IT team or Sage partner early.

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

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

4. Test with real invoices, including ones that use optional fields and mixed tax.

Sage 300 Decisions to Settle During Setup

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

• Batches: Should invoices arrive in an AP invoice batch for your team to post, or post automatically?
  Many controllers keep posting under accounting's control.
• Account structure: Which GL account segments carry department, location or division?
  In Sage 300, much of the coding sits inside the account number itself.
• Optional fields: Which header and detail optional fields must carry through?
  Optional fields often drive management reporting.
• Tax: Which tax groups and tax classes cover your vendors, including Quebec and multi-province suppliers?
  GST, HST, PST and QST need the right tax group for each line.
• Multicurrency: Are CAD and USD vendors both in scope?
  USD invoices must post in USD with the expected rate treatment.
• Project and Job Costing: Do invoices need contract, project, category or cost codes?
  Job cost reports depend on them.

Fix Common Sage 300 Sync Issues

• An optional field value is not available for coding: Check that the value is active in Sage 300 and that the optional field is set up as a coding dimension in Finofo. If it is not, raise it with your Finofo team.
• Invoices are not appearing in Sage 300: With Manual posting, open Post to ERP: the drawer shows whether the invoice is ready or blocked, and why. Then check whether entries are waiting in an unposted batch.
• Tax on a line maps to the wrong tax group: Correct the tax on the line in Finofo, and review the vendor's tax group and class in Sage 300.
• An account is rejected: Check that the full account, including every segment, is active in Sage 300 and allowed for the fiscal period.

Tips

• Bring your Sage partner into the first setup call if Sage 300 is on premises.
• Write down which account segments mean what before setup. It makes required-field decisions much quicker.
• Test at least one Quebec supplier with GST and QST, and one supplier from a PST province, before go-live.
• This article does not cover Sage 300 CRE or Sage 50. Sage 300 remains the system of record for the ledger and financial reporting.

Frequently Asked Questions

Is Sage 300 the same as Sage 300 CRE?

No. Sage 300 descends from Accpac. Sage 300 CRE descends from Timberline and is built for construction and real estate.

Can invoices arrive as a batch for review in Sage 300?

Discuss posting during setup. Many teams prefer invoices to arrive for review, so posting stays with accounting.

Does Finofo handle Canadian sales tax for Sage 300?

Finofo reads tax on each line, including GST, HST, PST and QST, and flags tax that does not add up before anything posts. Mapping to your Sage 300 tax groups is confirmed during setup.

Our Sage 300 is on premises. Can we still connect?

Talk to your Finofo team. The connection path for on-premises and hosted installations is confirmed before implementation begins, and an API, secure file or scheduled export path can be scoped where it fits better.

Do we have to use optional fields?

Only if your reporting relies on them. List the ones that must carry through, and Finofo can require them on the lines where they apply.