Key takeaways
- Business Central reports cost by G/L account and dimensions, so each purchase invoice line needs the right dimension values, such as project or department, as well as an account.
- Vergo reads accounts, dimensions and vendors through the Business Central v2.0 API, so proposed coding uses values that exist in your company.
- Coding is proposed by inference from your own history, with the reason shown, and approvals route by GL account, by amount or by project.
- Approved invoices post as purchaseInvoice records with purchaseInvoiceLines and attachments. New suppliers are created as vendors.
- The connection is self-serve through Business Central's public API, so nothing is needed from your team to start.
Where should you go next?
- Learn more about Vergo AP Invoice Automation
- Vergo's Dynamics 365 Business Central integration
- AP automation that works with Dynamics 365 Business Central
How do you automate invoice coding and approvals in Business Central, step by step?
- Connect Business Central. Vergo connects through the public v2.0 API and reads your chart of accounts, dimensions and vendor list.
- Collect invoices in one inbox. Vendors email invoices to your AP inbox and staff drag and drop scans. Vergo extracts vendor, invoice number, dates, amounts and lines, and flags likely duplicates.
- Code each line. Vergo proposes the G/L account and dimension values for every line from how your team coded similar invoices, and shows why it chose each value.
- Route for approval. Route by project so the owner of the budget approves, add an approver above a set amount, or let recurring bills pass on policy flags.
- Post to Business Central. Approved invoices post as purchase invoices with their lines and the invoice document attached, ready for your normal payment process.
What does a Business Central purchase invoice line need?
Business Central keeps its chart of accounts short and uses dimensions for analysis. That makes dimension values on each line as important as the account:
- G/L account for what the cost is.
- Global and shortcut dimensions, such as department, project, location or cost center, as your company defines them.
- Vendor, matched to an existing vendor or created when the supplier is new.
- Attachment of the invoice document, so auditors and approvers see the source.
An invoice that posts with the account but no project dimension still reaches the ledger, but it disappears from project and department reports. Companies that run jobs through dimensions find these gaps at month-end. Coding the dimensions on each line when the invoice arrives prevents them.
How should approvals be routed for Business Central?
Vergo routes by GL account, by amount or by project, and approvers review the invoice, the proposed account and dimensions, and the reason from a phone, without a Business Central licence. Typical rules:
- Invoices carrying a project dimension go to that project's manager.
- Invoices above a set amount add a finance approver.
- Recurring overhead bills skip approval and rely on policy flags.
What syncs between Vergo and Business Central?
Vergo reads accounts, dimensions and vendors, and posts purchaseInvoice and purchaseInvoiceLines records, vendors, attachments, and journals with journalLine entries to a G/L or bank account, through the Business Central API. Microsoft documents these endpoints in the Business Central API v2.0 reference. The connection is self-serve. The specification is on the Business Central integration page.
A practical example
A contractor that tracks jobs with a project dimension in Business Central receives an equipment rental invoice for two projects. Vergo proposes the rental G/L account and splits the lines across the two project dimension values, following how earlier invoices from the same rental company were coded. The invoice routes to one project manager, who confirms both lines from his phone. It posts as a purchase invoice with two lines, each with its own project dimension and the PDF attached, and both project reports show the rental cost that day.
How Vergo handles this
Vergo is an AI-native, card-agnostic spend platform that runs AP invoices, card spend and employee reimbursements through one coding model against your Business Central accounts and dimensions. Proposals come from your own history, with the reason shown, and new vendors are coded on first sight. Approval flows are optional, and payment stays on the rails you already use.
Related questions
Frequently Asked Questions
Does Vergo post purchase invoices directly into Business Central?
Yes. Vergo posts approved invoices as purchaseInvoice records with purchaseInvoiceLines and the invoice attachment through the Business Central v2.0 API.
Can Vergo code Business Central dimensions, not just G/L accounts?
Yes. Vergo reads your dimensions through the API and proposes dimension values on each line, such as project or department, alongside the G/L account.
Does connecting Business Central need IT work?
No. The connection is self-serve through Business Central's public v2.0 API, so nothing is needed from your team to start.
How are new suppliers handled?
Vergo reads your vendor list and can create a new vendor through the API when a supplier invoices you for the first time, so the invoice does not wait on vendor setup.
Can card transactions post to Business Central as well?
Yes. Card spend and reimbursements are coded with the same model and post as journals with journalLine entries to a G/L or bank account.
