Why is importing the only path into Tabs3?
Tabs3 does not publish a public API, SDK, or developer programme, so no card platform can post transactions into it directly. The supported way to bring outside data in is Tabs3's own import routines — which means the real question for a firm is how the import file gets built, not whether one is needed.
What does the manual version look like?
Without automation, someone downloads the card statement, opens it in a spreadsheet, splits shared charges, chases cardholders for receipts and coding, reshapes columns to match what Tabs3's import expects, and fixes whatever the import rejects. For a legal practice, that also means attributing each charge correctly before it reaches billing — a client lunch and a filing fee do not belong in the same bucket, and errors surface at the worst time: invoicing.
How does Vergo automate the import?
Vergo replaces the spreadsheet stage entirely:
- Capture at the point of spend. Each card transaction appears in Vergo the moment it happens. The cardholder attaches the receipt and applies coding from their phone, while the purchase is still fresh.
- A custom-built export matched to Tabs3. Vergo produces a structured CSV shaped to the import format Tabs3 expects — columns, order, and values arranged so the file imports cleanly rather than needing manual repair.
- Run the import in Tabs3. Because Tabs3 runs on-premise, your billing or accounting staff run the import where the system lives. The export is built so this step is a routine load, not a troubleshooting session.
How often should you run the import?
As often as your close rhythm needs — weekly imports keep spend current for billing, while some firms run it monthly alongside the card statement. Because the coding work happens continuously in Vergo rather than in a month-end scramble, the cadence is your choice instead of a constraint.
What should you watch for?
Two things. First, keep coding lists in Vergo aligned with Tabs3 so exported values match what the import validates against. Second, treat receipts as part of the same workflow — Vergo stores them against each transaction, so documentation is already attached when a charge is questioned later.
What changes for the firm in practice?
The visible change is at month end: the statement-reconciliation project disappears, replaced by an import that takes minutes. The quieter change is data quality. Charges get coded by the people who made them, at the time they made them, so the answers are right — and when billing questions a charge weeks later, the receipt and coding are already on record in Vergo rather than in someone's memory.
Can card transactions feed into Tabs3 automatically?
Not by API — Tabs3 publishes none. The working automation is a matched file import: Vergo builds a custom CSV in the format Tabs3 expects and your team runs the import.
What file format does the Vergo export use?
A structured CSV custom-built to Tabs3's import format, so transactions land in the right fields without column reshaping.
Who runs the import into Tabs3?
Your billing or accounting staff, on the system where Tabs3 is installed. Vergo produces the file; the load itself is a routine step inside Tabs3.
Where do receipts live in this workflow?
In Vergo, attached to each transaction by the cardholder at the time of spend — so the paper trail exists before the import ever runs.
