How do I import credit card transactions into Causeway?

What are the routes into Causeway for card transactions?

Causeway publishes no public API, so card spend enters the same way other transaction data does: keyed into the system, or brought in as a structured import file. For a construction business with company cards spread across contracts and sites, keying is the expensive option — every fuel stop and merchant run has to be typed with its job reference and cost heading, usually weeks after the money was spent.

Why not just import the card provider's statement file?

Because it carries none of what Causeway needs. A card statement export has the provider's date format and column order, cryptic merchant strings, and — critically — no contract, job, or cost-heading references. Someone still has to reshape the file and add the costing line by line, which is the retyping problem in a different spreadsheet.

How does the Vergo-to-Causeway workflow run?

Vergo front-loads the coding to the moment of spend, then hands you a file in Causeway's shape:

• Site and office staff spend on Vergo cards; the app prompts for a receipt photo and the job and cost coding at purchase.
• Approvers review transactions in Vergo — coding is corrected while the spend is fresh, not at month-end.
• The accounts team downloads a custom-built CSV export matched to the import format Causeway expects.
• The file is imported into Causeway and the card account reconciled.

The result is card spend landing in the costing ledger already allocated, with the receipt for every line stored against the transaction in Vergo.

Is this an integration or a workaround?

Call it what it is: a file-based integration, which is the only honest kind for a system with no public API. Nothing about Causeway changes — imports work the way they always have. What changes is the quality of the file arriving: matched format, complete coding, every line backed by a captured receipt, every month the same routine.

What does this change on site and in the office?

On site, cardholders stop hoarding paper — the receipt is photographed at the merchant and the job coding chosen in the same moment. In the office, the accounts team stops rebuilding a month of spend from statements and memory: the import file arrives coded, and exceptions are handled in Vergo where the receipt and the spender are one click away. Setup is a short exercise — issue cards, mirror your contract and cost-heading references in Vergo, run one test import — and the routine holds from then on.