How do card transactions get into BS&A?
BS&A publishes no public API, so no card platform can post transactions into it directly. BS&A does, however, accept third-party file imports in a defined layout. That makes file import the working route: transactions arrive as a structured file rather than being typed in one at a time.
Why not just type them in?
Manual entry is how many BS&A shops handle card statements today: a finance clerk works through the statement line by line, coding each charge to its fund, department, and account, then matching receipts. On a busy card program that is hours of month-end work, and coding errors made under deadline are the ones that surface in audit.
Why won't a raw bank export import cleanly?
A bank CSV has dates, merchants, and amounts — none of the coding BS&A needs. Fund, department, and account still have to be added to every line, and the file has to be reshaped into the layout BS&A's import expects. The export saved the typing of amounts, but the real work remained.
How does Vergo's export solve this?
Vergo does the coding upstream and the formatting automatically. Spend happens on Vergo cards; each transaction is coded in Vergo — fund, department, account, receipt attached — at or near the point of purchase. Vergo then produces a custom-built CSV matched to BS&A's import format.
The workflow:
1. Staff spend on Vergo cards.
2. Charges are coded in Vergo with your BS&A fund and account structure; receipts are captured on the spot.
3. On your close cadence, export the BS&A-formatted file from Vergo.
4. Import it into BS&A. The layout matches, so it loads without remapping.
What about receipts and audit?
Receipts stay attached to their transactions in Vergo, giving you a per-charge audit trail without paper. The coded amounts land in BS&A through the import, so the ledger reflects card spend with the fund and account detail your reporting requires.
What if our fund and account structure changes?
The coding lists in Vergo mirror your BS&A chart, so when funds, departments, or accounts change, the lists are updated once and every subsequent transaction is coded against the current structure. The export keeps matching what the import expects.
How long does the import take?
Minutes. Because the file is already in the shape BS&A expects and every line is coded, the import is the shortest step in the process — the time that used to go into re-keying and coding is what the workflow removes.
Can card transactions post into BS&A automatically?
No — BS&A has no public API, so direct posting is not possible. The supported route is file import, which Vergo's matched export automates.
What layout does the import file need?
BS&A accepts third-party imports in a defined layout. Vergo builds its export to match BS&A's import format, so the file loads without manual reshaping.
Does the coding come through in the import?
Yes. Fund, department, and account coding applied in Vergo carries into the export file, so BS&A receives fully coded entries.
Where are receipts kept?
In Vergo, attached to each transaction — a per-charge audit trail that does not depend on paper receipts making it back to the finance office.
