How do credit card transactions get into LEVESYS?
By import file. LEVESYS publishes no public API, so there is no direct feed from a bank or card program into the ERP. Card spend enters LEVESYS the way other external batch data does: as a structured file loaded through the system's import routine.
What does the manual month look like?
- Statements download at month-end, weeks after the spend happened.
- The office chases receipts across site crews and supervisors.
- Every line gets coded to a job and cost code in a spreadsheet.
- The spreadsheet is reshaped into an importable layout — or entries are keyed in by hand.
Until that cycle finishes, job cost reports are missing weeks of card spend, which distorts cost-to-complete on active jobs.
How does Vergo automate the LEVESYS import?
Vergo moves the coding to the moment of spend. A transaction appears in Vergo as soon as the card is used; the field worker photographs the receipt on the spot; the office allocates the line to its job and cost code the same day. When you are ready to post, Vergo generates a custom-built CSV export matched to the import format LEVESYS expects — not a generic bank export you have to rework, but a file shaped for the system's import routine.
The last step is the import itself, run inside LEVESYS like any other batch load. The file arrives coded, receipt-backed, and reconciled.
How often should contractors run the import?
Weekly imports keep job costing close to real time, which matters on fast-moving jobs. Monthly fits a standard close. Either way, the export is ready whenever you are, because the coding happened during the month.
What should you check on the first import?
Run a small test batch. Confirm job numbers and cost codes map to your LEVESYS structure, verify GST treatment and date formats, and check the batch posts to the intended period. After that, the format is locked and imports become routine.
What does this mean for job cost accuracy?
Card spend is usually the last cost category to reach the job ledger, because it depends on statements and receipts arriving. When coding happens at the moment of spend and the import runs weekly, that lag collapses: project managers see card costs against their jobs within days, cost-to-complete stays honest, and there is no end-of-job surprise from a month of uncoded card purchases. The import file is the delivery mechanism; the real change is when the coding happens.
Can a card feed connect straight into LEVESYS?
No — LEVESYS publishes no API for live feeds. The working path is a matched file import, which Vergo prepares automatically.
Are transactions job-coded before they reach LEVESYS?
Yes. Coding to jobs and cost codes happens in Vergo as spend occurs, so the import file arrives pre-allocated.
What about receipts and GST records?
Receipts attach to each transaction in Vergo at the point of purchase and stay there for audit. The import file carries the ledger and job-costing data.
How much time does this save at month-end?
The statement-chasing, receipt-hunting, and spreadsheet re-keying disappear. Close-out becomes exporting one file from Vergo and importing it into LEVESYS.
