Key takeaways
- Vergo proposes invoice coding by inference from your own Sage 300 history — no rule library to build, no keyword lists to maintain — and shows why it chose each account.
- In a multi-company Sage 300 install, the first coding decision is which company the invoice belongs to; the Web API addresses each company by its own org ID.
- Coding reaches the full account — GL accounts built from your segment codes — plus the optional fields your AP invoices carry.
- Approvals route by GL account, by amount or by project, and are optional — policy flags can catch only what breaks a rule.
- Approved invoices post into Sage 300 through the Web API's APInvoiceBatches endpoint as open batches, so your posting routine stays in control.
Where should you go next?
- Learn more about Vergo AP Invoice Automation
- Learn more about Vergo Expense Management
- Learn more about Vergo Employee Reimbursements
- See the Sage 300 integration spec
What is the step-by-step approach to automating invoice coding and approvals in Sage 300?
Start with one intake point per company or one shared inbox for all of them. Vergo reads each invoice as a document, line by line: vendor, invoice number, date, amounts and what was actually bought. It first decides which Sage 300 company the invoice belongs to, then matches the vendor in that company's APVendors list and proposes a GL account for every line from your own history with that supplier — the whole account, built from your segment codes, not just the natural account. Where your AP invoice details carry optional fields, Vergo proposes those values too. A new supplier nobody has set up is coded on first sight from what the invoice says, not queued for a rule someone has not written yet.
How does approval routing work?
Approval is optional and follows the authority you already use. Route by GL account, by amount (over a threshold you choose needs a second approver), by project, or by company; or skip routing and let policy flags stop only what breaks a rule. Approvers work from their phone, see the invoice image beside the proposed coding and the reason for it, and confirm or change it in one step. Every decision is time-stamped against the invoice. Once approved, Vergo posts the invoice through the Sage 300 Web API into APInvoiceBatches for that company, where it waits as an open batch for your team's normal posting — the same place a manually keyed invoice would sit.
What makes Sage 300 invoice processing different?
Sage 300 — the ERP sold as Accpac until 2012 — is chosen for multi-company and multi-currency work, and that is where generic tools fall down. An invoice coded to the right account in the wrong company is still wrong, and a tool built around one flat chart ends up with someone rekeying intercompany costs. Sage 300 accounts are built from segments, so the department or location segment decides where the cost reports. Optional fields carry the extra detail your reporting depends on, and they are easy to drop in an import. An integration that addresses each company directly, reads its own accounts and segment codes, and carries optional fields through keeps that structure intact. Sage 300 is also a different product from Sage 300 CRE (formerly Timberline) — if you run the construction system, see the Sage 300 CRE guide below.
What does a practical example look like?
A group with a US and a Canadian company in Sage 300 receives a software invoice billed to the Canadian entity. Vergo reads the lines, assigns the invoice to the Canadian company, matches the vendor in that company's vendor list, and proposes the software account with the IT department segment and the optional field your reporting uses, from how that vendor has been coded before. The amount is over the threshold, so it routes to the controller, who approves from a phone after seeing the reason for each line. The invoice posts through the Web API into that company's AP invoice batch, and AP posts the batch on its usual schedule — no keying, no re-coding, nothing in the wrong entity.
What should you look for in Sage 300 AP automation tools?
Look for a tool that reads your Sage 300 structure rather than asking you to rebuild it: companies, vendors, GL accounts, segment codes and optional fields. Ask how it decides which company an invoice belongs to, and whether it writes through the Sage 300 Web API or hands you a file to import. Check that invoices arrive as open batches so your posting routine and controls stay in place, that approvals follow your existing authority without an IT change, that approvers can act from a phone, and that every coding decision shows its reason. Finally, ask whether the same tool handles card spend and reimbursements, because three tools means three reconciliations.
How does Vergo handle this?
Vergo is an AI-native, card-agnostic spend platform that runs card spend, employee reimbursements and AP invoices through one coding model. It proposes coding by inference from your own accounting structure and history — no rule library to build, and new vendors coded on first sight. Every coding shows why it was chosen, so a reviewer confirms instead of re-coding. Approvals are optional and fit how you already control spend. Vergo captures, codes and approves invoices and hands them to Sage 300; it does not pay them, so payment stays on the rails you already use.
Related questions
Frequently Asked Questions
Can Sage 300 route invoice approvals natively?
Sage 300 records invoices in batches and controls posting; configurable multi-step approval routing with mobile approval and AI-proposed coding happens upstream of it. Vergo does that work before the invoice reaches the AP invoice batch.
How does Vergo handle multiple Sage 300 companies?
The Sage 300 Web API addresses each company by its org ID. Vergo assigns each invoice to a company, reads that company's vendors, accounts and segment codes, and posts into that company's AP invoice batch.
Does Vergo post into Sage 300 or produce an import file?
Vergo posts through the Sage 300 Web API: invoices into APInvoiceBatches and card spend into GLJournalBatches. Batches arrive open, so your team still controls posting.
Does Vergo pay the invoice?
No. Vergo captures, codes and approves invoices; payment stays on your existing Sage 300 payment batches, bank or payment provider.
Is this the same as Sage 300 CRE?
No. Sage 300 (formerly Accpac) is Sage's multi-company ERP; Sage 300 CRE, formerly Timberline, is a separate construction and real estate product with its own job cost structure.
