What makes AP automation AI-native?
AI-native AP automation reads an invoice as a document, not a template. Vergo reads every line of a supplier invoice bound for Xero and infers the coding from the line descriptions and from how your team has coded that supplier and similar purchases before. An invoice in a layout nobody has mapped, from a supplier nobody has set up in Xero, is coded on first sight instead of falling into an exception queue, and the approver sees why each line was coded the way it was.
How does Vergo work with Xero?
Vergo connects directly through Xero's public API — self-serve, with nothing needed from your team or from Xero — and reads your chart of accounts, contacts and tracking categories. Confirmed invoices are created in Xero as bills (accounts payable invoices) against the supplier contact, coded line by line with the PDF attached, ready for the payment run you already make. New vendors, accounts and tracking values appear in Vergo as they are created in Xero, so nobody codes against a stale list. The full specification lives on the Xero integration page.
What does Xero need on each supplier invoice?
- Contact: the supplier, matched to your existing contacts.
- Account and tracking: for every invoice line.
- Invoice number and due date: read from the document.
- Attachment: the supplier's PDF, attached to the bill.
What does this look like day to day?
A printing supplier emails an invoice with two jobs on it for two different clients. Vergo reads both lines, matches the supplier contact, proposes the cost of sales account and a different client tracking value on each line, and routes it for approval. Once approved, the bill with its PDF is waiting in Xero for the next payment run.
Does Vergo pay the invoice too?
No. Vergo captures, codes and routes each invoice for approval, then hands it to Xero; it does not pay suppliers. Payment stays on the rails your business already uses — your bank, your existing payment run, your current payment provider. Approvals are optional and fit how you already control spend: route by GL account, by amount or by project, or skip approval flows and let policy flags catch only what breaks a rule before it reaches Xero.
What changes at month end in Xero?
The work moves from the end of the month to the moment of spend. Because coding happens when the receipt or invoice arrives, close in Xero becomes a review of exceptions rather than a pile of unkeyed supplier invoices. Card spend, employee reimbursements and AP invoices run through one coding model — same coding, same review, one reconciliation against the Xero structure — and payment stays on the rails you already use.
Where should you go next?
- Vergo's Xero integration
- AP automation for landscape companies on Xero
- See Vergo run AP automation with Xero
Who runs Xero?
Xero is cloud accounting software run by small and growing businesses and the advisers who keep their books. It codes spend to an account plus tracking categories — up to four can exist, two active at a time — so choosing the right two values is most of the coding work. If your finance team lives in Xero, the AP automation layer should adapt to it, not the other way round.
Does Vergo do AP automation for Xero?
Yes. Vergo captures, codes and routes supplier invoices, then creates them in Xero as bills.
Does Vergo replace Xero?
No. Xero stays the system of record. Vergo sits in front of it, capturing, coding and reviewing spend before it reaches the ledger.
How is Xero connected?
Vergo connects directly through Xero's public API — self-serve, with nothing needed from your team or from Xero — and reads your chart of accounts, contacts and tracking categories.
Does Vergo pay suppliers?
No. Vergo captures, codes, approves and syncs invoices; payment stays on the rails the business already uses.
