How do I import credit card transactions into Cashflow Manager?

How do transactions normally get into Cashflow Manager?

Two ways: typed into the program's money-in and money-out records, or brought in from a file. Cashflow Manager is desktop software with no public API, so there is no third route — no feed from a card platform, no background sync. For a business putting real volume through company cards, typing each transaction and its allocation quickly becomes the slowest part of the bookkeeping.

What goes wrong with importing a raw card statement?

The card provider's export is built for statements, not bookkeeping. Dates come in the provider's format, columns sit in the wrong order, merchant strings are cryptic, and there are no allocations to your columns or categories. Every import starts with spreadsheet cleanup, and every cleanup is a chance to introduce an error you'll chase at reconciliation time.

How does the Vergo workflow change this?

With Vergo, the structure is built before the file exists. Spend happens on Vergo cards; each transaction is captured with its date, merchant, amount, and the coding your team applies, with the receipt photographed and attached at the point of purchase. When you're ready to bring the period into the books, Vergo generates a custom-built CSV export matched to the import format Cashflow Manager expects.

The routine:

• Spend on Vergo cards through the period; coding and receipts are captured as you go.
• Review and approve the transactions in Vergo.
• Download the Cashflow Manager-matched CSV on the computer where the program runs.
• Import the file and reconcile.

Is a file import as good as a sync?

For Cashflow Manager it is the only option, so the question is really whether the file arrives clean — and that is what the matched export guarantees. No platform can offer an API sync with Cashflow Manager, because no API exists. What can be automated is everything up to the import: capture, coding, receipts, and a file in the right shape every time.

What does setup involve?

Getting started is one honest afternoon: issue Vergo cards to the people who spend, agree the coding categories so the export matches how the books are kept, and run a single test import into Cashflow Manager to confirm the file lands cleanly. From then on the shape of the file never changes, so the routine never changes either. If a transaction is ever questioned months later, the answer is in Vergo — the receipt, the coding, and who spent it — rather than in a shoebox or an old email thread.