Why can't a card feed connect directly to FAST?
Because FAST has no published public API. Constellation HomeBuilder Systems' homebuilder ERP takes data through the application or through file imports, and that is the whole universe of options — no card platform can push transactions into FAST over an endpoint that does not exist. The practical question for a builder's accounting team is therefore not "which API integration?" but "how do we make the file import painless?"
What does the manual routine cost?
The default workflow is statement-driven: download the card statement at month end, match charges to receipts collected from supers and PMs, work out which job each charge belongs to, and key everything into FAST line by line. The keying is slow; the coding is worse, because it happens weeks after the purchase, when nobody remembers which lot that lumber run was for.
How does the import work with Vergo?
1. Capture spend as it happens. Card transactions appear in Vergo in real time, and cardholders snap receipts from the field at the point of purchase.
2. Code in Vergo. Each transaction is allocated to its job and cost code while the context is fresh — by the cardholder, the PM, or accounting, depending on how you set the workflow.
3. Generate the export. Vergo produces a custom-built CSV export matched to the import format FAST expects, with the coding carried on every line.
4. Import the batch. Your accounting team loads the file into FAST. One import replaces the month's re-keying, and job costs arrive already allocated.
How does this compare to an API sync?
For FAST there is nothing to compare against — no API sync exists or can exist until the vendor publishes one. On its own merits, the batch import covers what matters: the coding and data entry are done before the file is generated, receipts are already attached in Vergo for audit, and the import itself takes minutes at whatever cadence fits your close.
Is there a direct bank or card feed into FAST?
No. FAST publishes no public API, so no card platform can feed transactions in directly. The working path is a structured file import.
What does Vergo's export file contain?
Each card transaction with the job and cost code coding applied in Vergo, formatted as a custom CSV matched to what FAST's importer expects.
Do receipts go into FAST too?
Receipts are captured and stored against each transaction in Vergo, so the audit trail lives there; the import file carries the accounting entries into FAST.
How long does the import take?
Minutes. Because coding happens in Vergo throughout the month, the FAST side of the workflow is a single batch import rather than line-by-line entry.
