Key takeaways
- Plex, from Rockwell Automation, is a cloud ERP designed for manufacturers, with AR, AP and GL accounting.
- Plex places employee expenses in its human capital management module, aimed at travel and education claims.
- Plant card spend, such as MRO parts, tooling and freight, is a different flow that usually reaches the GL by hand.
- Vergo proposes account and department from your history, texts for receipts and posts journal entries through Plex's API.
Where should you go next?
How do you automate expense management in Plex, step by step?
- Enable API access. Your administrator enables an API key for your Plex tenant once; Vergo then posts coded card spend as journal entries through Plex's journal entries API, with department and account on each line.
- Connect your existing cards. Plant cards, purchasing cards and travel cards: connecting your existing cards involves no card applications, no re-issuing and no banking change.
- Collect receipts by text. Employees handle everything by text message — no app to download, no portal login — and Vergo chases missing receipts itself instead of waiting for a report.
- Code each line. Vergo proposes the GL account and department for every receipt line, with the reason.
- Post to Plex. Confirmed spend posts as journal entries, so the GL is current without statement keying.
What does Plex need on each card transaction?
- GL account: maintenance supplies, tooling, freight, travel and so on.
- Department: the plant area or function that owns the cost.
- Receipt: for audit and for warranty or vendor disputes on parts.
Where does Plex stop and automation start?
Plex's HCM module handles employee expenses for travel and education, with expedited claims processing. Manufacturing card spend looks different: a maintenance tech buying a bearing at 2 a.m. to restart a line, or a buyer paying for expedited freight. That spend needs to land on the right account and department quickly, and its receipt needs to exist. Vergo reads the receipt itself, line by line, and predicts the GL account from what was actually bought, not just the vendor name on the header, and proposes the department from how similar purchases were coded.
A practical example
A plastics manufacturer on Plex issues cards to maintenance leads at two plants. One lead buys a heater band and a set of hoses on one receipt. Vergo texts for the photo, proposes the maintenance repairs account with the molding department for the heater band and the facilities department for the hoses, citing earlier purchases. The plant controller confirms, and the journal entry posts to Plex.
How Vergo handles this
Vergo proposes the coding by inference from your own accounting structure and history — no rule library to build, no keyword lists to maintain, and new vendors are coded on first sight. At a plant, that history is how maintenance, tooling and freight have been charged by department. Approval workflows are optional and fit how you already control spend: route by GL account or by amount — or skip approval flows entirely and let policy flags catch only what breaks a rule. Card spend, employee reimbursements and AP invoices run through one coding model — same coding, same review, one reconciliation — and payment stays on the rails you already use.
Frequently Asked Questions
Does Vergo post to Plex directly?
Yes, as journal entries through Plex's journal entries API, after your administrator enables an API key once.
Can Vergo code to departments?
Yes. Vergo proposes the department with the account on each line.
Does this replace Plex HCM expense claims?
It can sit alongside them. Vergo is built for card spend and can also run reimbursements.
Is Vergo only for manufacturers on Plex?
Plex users are manufacturers, and Vergo codes to whatever accounts and departments your tenant uses.
Do we need new cards?
No. Connecting your existing cards involves no card applications, no re-issuing and no banking change.
