How do card transactions get into Axon?
Axon Trucking Software has no public API, so outside data enters Axon through its own import capability rather than through a programmatic connection. A trucking company's real choices are manual entry, reshaping raw card-statement downloads by hand, or using a platform that produces an import-ready file. Vergo takes the third path: custom-built CSV exports matched to Axon's import format.
Why not just download the card statement?
A statement download is a list of bank lines with no receipts, no approvals, and no coding. Fuel, maintenance, tolls, and office spend all look the same until someone codes each line — which is exactly the month-end work a card program is supposed to remove. An import file only saves time if it arrives already coded.
What does the Vergo-to-Axon workflow look like?
Drivers and staff spend on Vergo cards. Receipts are captured from a phone at the point of purchase, and coding rules apply the accounts your Axon books use as transactions land. Approvers clear the spend in Vergo. At your close cadence, you export the coded transactions as a CSV built to your Axon import layout and run the import. Entries arrive coded and documented, so reconciliation is verification rather than re-keying.
What setup is required?
One mapping exercise: confirm the file layout against your Axon import and align the account codes in Vergo with the ones in your Axon chart. Vergo builds the export to that format once; after that, every export follows it. Because Axon publishes no API, this file handoff is the strongest honest automation available — and with the coding done upstream, it is fast.
How does this change month end for the office?
Before: a stack of crumpled fuel receipts from drivers, a statement download, and hours of matching and coding line by line. After: the receipts were captured weeks ago at the pump, the coding accrued as the spend happened, and month end is one export and one import. The books in Axon reflect card activity accurately without the office re-doing work the platform already did — and every imported line has a receipt and an approval behind it in Vergo if anyone asks later.
Can transactions post into Axon automatically?
No — Axon has no public API, so nothing can post in programmatically. The working path is Vergo's custom CSV export matched to Axon's import format.
What does the CSV contain?
Date, amount, vendor, and the account coding applied in Vergo, laid out to match your Axon import.
How often should we import?
Whatever cadence fits your close — weekly or monthly. The export takes minutes once the format is mapped.
Where do the receipts live?
In Vergo, attached to each transaction as the audit trail; the CSV carries the accounting data Axon books.
