What is the supported way to get card data into CYMA?
CYMA's documented route for bringing in outside data is its import/export capability — the import dialogs built into the product. CYMA does not publish a public API, so there is no direct programmatic feed from a card provider or expense platform. The practical question is therefore how to produce an import file that carries everything your books need, not just what the bank knows.
What is wrong with importing the raw card statement?
A card provider's export has dates, amounts, and merchant names — no account coding, no department or category assignment, no receipts. Someone in the office ends up decorating each line after the fact, usually by emailing cardholders about purchases they barely remember. That reconstruction is where the month-end time goes.
How does Vergo prepare the import for CYMA?
Vergo moves the coding to the point of purchase. Cardholders attach receipts and code transactions in Vergo when they spend; admins review in one place. When you are ready to book activity, Vergo generates a custom-built CSV export matched to CYMA's import format — structured so your on-premise CYMA installation accepts it through its import dialog without column surgery.
What does the cycle look like in practice?
1. Team members spend on Vergo cards and capture receipts from their phones. 2. Transactions are coded in Vergo against your CYMA account structure. 3. On your close cadence, Vergo produces the CSV built for your CYMA setup. 4. Your bookkeeper runs the import in CYMA. 5. Reconciliation confirms totals rather than creating data — the imported activity already mirrors the card program.
Does this fit an on-premise installation?
Yes — that is a strength of the file-based approach. Vergo runs in the cloud and generates the export; the import runs locally in your CYMA environment, on your schedule, with no connector installed on your server.
Can card transactions flow into CYMA automatically over an API?
No — CYMA does not publish a public API. Transactions come in through CYMA's import capability, and Vergo generates the structured file that capability expects.
What format is the Vergo export for CYMA?
A custom-built CSV matched to CYMA's import format, arranged for your CYMA setup rather than a generic template.
Where does the coding happen?
In Vergo, at the time of purchase. The file that reaches CYMA already carries the account and department coding, so nothing is re-keyed inside CYMA.
How often should we run the import?
On whatever cadence you close — weekly or monthly are typical. Vergo generates the export on demand, so the import schedule is entirely yours.
