What are your options for card transactions in CrewCost?
Because CrewCost does not publish a public API, there is no direct sync from any card program. Your real options are keying transactions in by hand, importing a raw card-provider file and coding it afterward, or importing a file that is already structured and job-coded. The last option is the only one that holds up once several crews carry cards.
Why not just import the bank's export file?
A card statement export tells CrewCost what was spent and where — but not which job it belongs to, which cost category it hits, or whether a receipt exists. In construction, that coding is the whole point: job cost reports are only as current as the coding behind them. Cleaning up a raw export in a spreadsheet each month means job costs run weeks behind actual spend.
How does the Vergo workflow deliver coded transactions?
Vergo issues the cards, so it sees each transaction the moment it happens. The cardholder — superintendent, PM, or office staff — snaps the receipt and codes the purchase to its job from their phone. When you are ready to book activity, Vergo generates a custom-built CSV export matched to CrewCost's import format. The bookkeeper imports one file and the card spend lands in CrewCost with its coding intact.
What are the steps, start to finish?
1. Issue Vergo cards to the people who spend. 2. Receipts and job coding are captured at the point of purchase. 3. Admins review and approve spend in Vergo. 4. Vergo produces the CSV built for your CrewCost setup on your close cadence. 5. Import the file into CrewCost and reconcile — the numbers already match the card program.
How long does the import step take?
Minutes. Because the export is matched to CrewCost's import format rather than a generic template, there is no monthly column-mapping exercise — the file is built to be accepted as-is.
Can Vergo sync with CrewCost through an API?
No — CrewCost does not publish a public API. Vergo integrates by producing custom CSV exports matched to CrewCost's import format instead.
Who codes the transactions to jobs?
The cardholders, in Vergo, at the time of purchase — so the file that reaches CrewCost is already job-coded rather than coded after the fact by the office.
What does the bookkeeper actually do each cycle?
Generate the CSV export in Vergo, import it into CrewCost, and reconcile. The data entry and receipt-chasing that normally fill that cycle are already done.
Does this work for reimbursements too?
Yes — out-of-pocket expenses submitted through Vergo follow the same path: captured and coded in Vergo, then delivered to CrewCost in the structured export.
