What makes reimbursements AI-native?
AI-native reimbursement removes the expense report rather than speeding it up. An employee texts a photo of the receipt; Vergo reads it line by line, infers the Plex coding from what was bought and from how your team codes similar spend, and chases anything missing itself. There is no form for the employee to fill in, no code for them to get wrong, and no app to download or portal to log into — the finance team in Plex reviews a proposal with its reason instead of fixing a report.
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 claims post into Plex as journal entries coded to account and department, and the employee is repaid through the process your team already uses — Vergo does not move money. New 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 employee claim?
- GL account: travel, meals, mileage or supplies.
- Department: the employee's plant or function.
- Receipt: kept with the coded entry in Vergo, so every reimbursed line traces back to what was bought.
What does this look like day to day?
A quality engineer drives to a supplier audit and pays for parking and lunch himself. He texts the receipts and the trip. Vergo reads them, proposes travel and meals on the quality department and calculates the mileage through the same model. His manager confirms, and the coded journal entry lands in Plex.
What does the employee have to do?
Text a photo of the receipt. Employees handle everything by text message — no app to download, no portal login — and Vergo chases a missing receipt itself instead of waiting for someone to submit a report. Mileage runs through the same coding model, so a drive and a receipt from the same trip are coded the same way and reach Plex together. The people least likely to install an expense app will still reply to a text, which is why claims stop sitting in wallets until month end.
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 late expense reports. 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
- Reimbursements for manufacturers on Plex
- See Vergo run employee reimbursements 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 employee reimbursements layer should adapt to it, not the other way round.
Does Vergo do employee reimbursements for Plex?
Yes. Employees text their receipts, Vergo codes each line against the structure it reads from Plex, and the approved claim reaches Plex ready for repayment through your usual process.
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 it handle mileage?
Yes. Mileage runs through the same coding model as receipts, so both reach Plex together.
