Why can't a card feed connect directly to MCSJ?
Edmunds GovTech MCSJ, the on-premise ERP used by municipalities and local government entities, does not publish a public API. No card platform can push transactions into it over a live connection. Card and p-card spend reaches MCSJ the way other outside data does: as a batch that someone keys or imports.
What does the manual process look like?
Finance pulls the monthly p-card statement, matches each purchase to a receipt collected from the cardholder, determines the fund, department, and account for each line, and enters the batch into MCSJ. In fund accounting, the allocation step is the slow part — a single card statement can touch a dozen funds, and every line has to land in the right one for budget reporting to hold up.
How does Vergo automate the import?
Vergo moves the coding to the point of purchase and turns the batch into a file. Your MCSJ account structure is loaded into Vergo, so when an employee makes a purchase, they pick the fund, department, and line item from your real chart and attach the receipt on their phone. Finance reviews the coded transactions, then exports a custom-built CSV matched to the import format MCSJ expects and loads it into MCSJ.
What is the step-by-step?
1. Issue Vergo cards to staff who purchase — public works, parks, administration.
2. At purchase, the cardholder codes the transaction against your MCSJ funds and accounts and snaps the receipt.
3. Finance reviews and approves in Vergo, catching miscodes before they reach the ledger.
4. Export approved transactions as a CSV built for MCSJ's import format.
5. Import the batch into MCSJ and reconcile against the card statement.
How does this hold up for audit?
Better than the statement-and-shoebox method. Every transaction in the import carries its receipt, coder, approver, and timestamps in Vergo, so when the auditor asks about a line in MCSJ, the documentation trail is one search away.
What does this change for the finance office?
The p-card statement stops being a month-end research project. Allocation questions get answered at the point of purchase by the employee who bought the item, not reconstructed weeks later from a merchant name. Receipts stop trickling in on paper because they are captured on phones at the register. And budget-to-actual reports get more trustworthy, because card spend reaches MCSJ coded to the right fund and line on a regular cadence instead of landing in a lump after the statement clears. The work that remains — review and a file import — fits inside a normal close.
Can I connect a p-card feed directly to Edmunds GovTech MCSJ?
No. MCSJ publishes no public API, so live card feeds are not possible. Transactions enter MCSJ by batch entry or file import.
How do transactions get coded to the right fund?
Your MCSJ funds, departments, and accounts are loaded into Vergo, and cardholders code each purchase against that structure when they buy. Finance reviews before anything is exported.
What file does Vergo produce for MCSJ?
A custom-built CSV export matched to the import format MCSJ expects, so the batch loads without reshaping in a spreadsheet first.
How often should we import?
On your normal cadence — many finance offices import monthly with the statement cycle, though weekly imports keep budget-to-actual reporting more current.
