How do credit card transactions get into BRIX?
BRIX, the Hyphen Solutions construction accounting system, does not publish a public API, so no card platform can post transactions into it directly. That leaves two routes: manual entry, or file import. Manual entry means a bookkeeper keying each charge with its job and cost coding. File import means loading a structured file — and it only works cleanly when the file matches the layout BRIX expects.
Why do generic bank exports fail?
A raw CSV from your bank or card provider carries date, merchant, and amount — but nothing BRIX actually needs for job costing. No job, no cost code, no GL account, no receipt reference. Someone still has to add all of that, transaction by transaction, either in a spreadsheet before import or inside BRIX after. The import saved typing but not the real work.
How does Vergo make the import work?
Vergo moves the coding upstream. Spend happens on Vergo cards, and each transaction is coded in Vergo — job, cost code, GL account, with the receipt attached — by the person who made the purchase or by the accounting team. Vergo then generates a custom-built CSV export matched to BRIX's import format: columns in the order BRIX expects, values in the vocabulary your BRIX file uses.
What does the workflow look like month to month?
1. Spend on Vergo cards. Field and office staff use their cards as normal.
2. Code in Vergo. Each charge gets its job, cost code, and account. Receipt capture happens at the point of purchase, not at month end.
3. Export. On your close cadence — weekly or monthly — run the BRIX-formatted export from Vergo.
4. Import into BRIX. Load the file in your hosted BRIX environment. Because the layout matches, it goes in without remapping.
What about receipts and job cost reports?
Receipts live in Vergo, attached to each transaction, so the audit trail is there when you need it. Job costing lands in BRIX through the import — coded spend hits the right jobs and cost codes, so your BRIX job cost reports reflect card spend without waiting on a shoebox of receipts to be sorted.
Is this a real integration if there's no API?
It is the only kind of integration BRIX supports. We say that plainly: BRIX publishes no API, so anything described as a live sync is not built on public BRIX interfaces. A matched file export is dependable, auditable, and removes the re-keying — which is what the automation was for.
Can a card platform post transactions directly into BRIX?
No. BRIX publishes no public API, so direct posting is not possible. Transactions come in through file import.
What does Vergo's BRIX export contain?
Card transactions coded in Vergo — job, cost code, GL account — structured as a CSV matched to BRIX's import format so it loads without remapping.
How often should I import into BRIX?
Whatever matches your close cadence. Most teams export from Vergo and import weekly or at month end; the export takes minutes either way.
Where do receipts go?
Receipts are captured and stored in Vergo, attached to each transaction. The coded amounts flow into BRIX via the import; the receipt audit trail stays in Vergo.
