How do credit card transactions get into ERP-ONE?
Through file import. Distribution One ERP-ONE publishes no public API — Advantive offers API Services only as a paid add-on module without public documentation — so there is no standard live feed a card program can push through. The dependable route at every ERP-ONE site is a structured import file prepared in the format the system expects.
What does the manual version of this look like?
Without tooling, accounting rebuilds the month from statements:
- Download the card statement for each cardholder or account.
- Chase receipts across branches, buyers, and drivers.
- Code each line to vendor, GL account, and branch or department.
- Reshape the bank's CSV into whatever ERP-ONE's import will accept — or key entries in one at a time.
In a distribution business with fuel, freight, supplier, and shop spend spread across many cards, that is days of reconstruction, done weeks after the money moved.
How does Vergo automate the import?
Vergo replaces the statement-reconstruction step by capturing everything at the point of spend, then generating the import file:
- Capture: transactions on Vergo cards appear in real time; spenders attach receipts and code purchases from their phones.
- Coding: each line carries the vendor, GL account, and branch or department references your ERP-ONE import needs before export.
- Export: Vergo generates a custom-built CSV matched to ERP-ONE's import format. Accounting reviews the batch and runs the import.
This is a file-based integration, stated plainly: Vergo does not sync with ERP-ONE over an API, because no public API exists. The gain is that the file arrives finished — formatted, coded, receipt-backed — instead of being built by hand.
How often should the import run?
Whatever cadence your close runs on — weekly batches keep the review small, monthly matches a traditional close. Because coding happens continuously rather than at month end, the export is always current, and the import becomes a routine review step instead of a backlog.
What happens to receipts?
Receipts stay attached to each transaction in Vergo. Every imported entry in ERP-ONE traces back to a documented card transaction with spender, receipt, and coding — the trail you want for supplier disputes and audit sampling.
What changes for the accounting team?
The import step itself stays familiar — ERP-ONE's own file import, run on your schedule. What disappears is everything upstream of it: statement downloads, receipt chasing across branches, after-the-fact coding, and spreadsheet reshaping. The team's role shifts from data entry to review, and close week stops depending on how fast card spend can be reconstructed.
Can card transactions flow into ERP-ONE automatically?
No — ERP-ONE has no public API for a live feed. Vergo generates a custom CSV matched to ERP-ONE's import format, and your accounting team runs the import.
What fields does the export include?
Date, amount, vendor, and the GL account and branch or department coding applied in Vergo, arranged in the format ERP-ONE expects on import.
Who does the coding?
Cardholders code their own purchases in Vergo as they spend; finance reviews before export instead of reconstructing from statements.
Does this work across multiple branches?
Yes. Branch or department references are part of the coding on each transaction, so one export can carry correctly attributed spend from every location.
