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 Plex 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 Plex, 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 Plex?
Plex issues API keys per customer tenant, so your administrator enables access once; Vergo then reads your GL accounts and departments and writes through the journal entries API Plex publishes for developers. Confirmed invoices post into Plex as journal entries coded to account and department, so the cost is on the ledger the day it is approved; payment stays with the process your team already runs. New vendors, accounts and departments appear in Vergo as they are created in Plex, so nobody codes against a stale list. The full specification lives on the Plex integration page.
What does Plex need on each supplier invoice?
- GL account: for each invoice line, not one account for the whole document.
- Department: the plant, line or function the purchase supports.
- Invoice document: kept with the coded entry in Vergo, so an auditor can trace the journal line back to the supplier's invoice.
What does this look like day to day?
A tooling supplier emails an invoice with a regrind charge for one plant and new inserts for another. Vergo reads the two lines, proposes the tooling account for both with a different department on each, and routes it to the plant manager who owns the larger line. Once approved, one journal entry with two coded lines posts to Plex.
Does Vergo pay the invoice too?
No. Vergo captures, codes and routes each invoice for approval, then hands it to Plex; 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 Plex.
What changes at month end in Plex?
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 Plex 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 Plex structure — and payment stays on the rails you already use.
Where should you go next?
- Vergo's Plex integration
- AP automation for manufacturers on Plex
- See Vergo run AP automation with Plex
Who runs Plex?
Plex, from Rockwell Automation, is a cloud ERP designed for manufacturers, with receivables, payables and general ledger accounting alongside production. Its human capital management module handles employee expenses for travel and education, which leaves plant spend — parts, tooling, freight — as a separate flow to code. If your finance team lives in Plex, the AP automation layer should adapt to it, not the other way round.
Does Vergo do AP automation for Plex?
Yes. Vergo captures, codes and routes supplier invoices, then posts them to Plex as journal entries.
Does Vergo replace Plex?
No. Plex stays the system of record. Vergo sits in front of it, capturing, coding and reviewing spend before it reaches the ledger.
How is Plex connected?
Plex issues API keys per customer tenant, so your administrator enables access once; Vergo then reads your GL accounts and departments and writes through the journal entries API Plex publishes for developers.
Does Vergo pay suppliers?
No. Vergo captures, codes, approves and syncs invoices; payment stays on the rails the business already uses.
