What are the options for card spend in JOBPOWER?
JOBPOWER has no API — the vendor confirms it — so a direct card feed is off the table for every platform. Card transactions enter JOBPOWER either by hand or by import. Manual entry means the bookkeeper keys each line from statements, then chases superintendents and PMs for the job each purchase belongs to. An import posts the whole month in one batch — if the file carries the job costing JOBPOWER needs.
Why does a plain card statement export fall short?
Job costing. A statement export has merchant names and amounts, but no job numbers and no cost codes — and in construction accounting, an uncosted expense is unfinished work. Turning the statement into an importable, costed batch is the spreadsheet exercise that eats the first week of every month, and it depends on people remembering weeks-old purchases.
How does the Vergo workflow get transactions into JOBPOWER?
1. Crews and PMs spend on Vergo cards. Each transaction lands in Vergo when it settles — no waiting for the statement.
2. Costing happens at the point of purchase. The cardholder snaps the receipt and tags the job and cost code from their phone in the moment. Recurring vendors — fuel, supply houses — are coded automatically by rules.
3. Vergo generates the import file. The CSV export is custom-built to match the import format your JOBPOWER system expects, with every line carrying its job and cost code. No remapping, no spreadsheet surgery.
4. Your bookkeeper imports the batch. The file loads into JOBPOWER as a standard import after review. Posting stays under office control, and job cost reports pick up card spend without the month-end lag.
What changes at month-end?
The reconstruction disappears. Receipts are already attached, jobs are already tagged by the person who made the purchase, and the file is already in JOBPOWER's shape. The close becomes a review and one import measured in minutes — and job costs are current enough to act on, not archaeology. That currency matters on active work: a PM who can see this week's card spend against the job's budget catches an overrun while there is still time to do something about it.
Is this an API integration?
No, and no platform can honestly offer one for JOBPOWER, because there is no API to build on. This is a file-based integration where the file is engineered for your JOBPOWER import — automation everywhere except the final click your bookkeeper keeps.
Can Vergo post card transactions straight into JOBPOWER?
No platform can — JOBPOWER has no API, per the vendor. Vergo generates a custom-built CSV export matched to your JOBPOWER import format, and your bookkeeper posts it as a reviewed batch import.
How do job numbers and cost codes get on each line?
At the point of purchase: cardholders tag the job and cost code from their phone when they spend, and rules code recurring vendors automatically. The export arrives fully costed.
What does the bookkeeper do each month?
Review the coded batch in Vergo, export the CSV, and run one import in JOBPOWER. The chasing, coding, and receipt-matching that used to fill the first week of the month is already done.
Do receipts make it into the record?
Yes — every receipt is captured by phone at purchase and stays attached to its transaction in Vergo, so backup for any line in JOBPOWER is a few seconds away.
