What are the options for getting card activity into Accounting CS?
Accounting CS is an on-premise system in the Thomson Reuters CS Professional Suite, and it has no public API — the Thomson Reuters developer portal covers ONESOURCE and tax products, not the CS suite. So card transactions get in two ways: staff key them manually, or they come in as a spreadsheet import in a layout Accounting CS accepts.
For a firm processing books for many clients, manual entry is the bottleneck. Each client's statements have to be collected, receipts matched, charges coded to the right accounts, and every line typed in. The import route removes the typing, but historically not the prep: someone still had to assemble a correctly shaped spreadsheet with the coding filled in.
How does the Vergo workflow handle it?
1. Cardholders code as they spend. The client's staff carry Vergo cards. When a charge lands, the cardholder tags the account and category in the app and snaps the receipt. Coding happens at the point of spend, by the person who knows what the purchase was.
2. Vergo produces the import file. Vergo generates a custom-built CSV export matched to the import layout Accounting CS expects — columns arranged for the spreadsheet import, coding included, not a raw bank download that needs rework.
3. The firm imports and reviews. Staff pull the export and load it through the Accounting CS import, then review the batch as usual. The statement-collection and rekeying steps disappear; the firm's review step stays.
Why not just import the bank's export?
A bank file carries dates, merchants, and amounts, but no account coding and no receipts. Every line still needs to be coded by staff, and the columns still need to be mapped into the layout Accounting CS wants. That is the same manual work relocated into a spreadsheet. The Vergo file arrives coded because the cardholders did it upfront, with receipts already attached in Vergo if anything needs checking.
What changes for the firm at month end?
Instead of a shoebox month — statements in, receipts chased, hours of entry per client — the firm receives a ready file per client and spends its time on review and advisory work. Nothing posts without the firm loading the import, so control over the client ledger stays exactly where it was.
Is there an API alternative to file import for Accounting CS?
No. Thomson Reuters publishes no public API for the CS Professional Suite, so file import is the supported way to bring outside transactions in. Vergo builds its exports to match that import.
Who does the transaction coding?
The client's cardholders, in Vergo, at the time of purchase — each charge tagged to the right account with its receipt attached before the file ever reaches the firm.
What format does Vergo export for Accounting CS?
A custom-built CSV matched to the import layout Accounting CS expects, so it loads through the standard spreadsheet import without manual reshaping.
Does the firm still review what posts?
Yes. The export is a reviewable batch, and nothing enters Accounting CS until the firm imports it. Vergo replaces the collection and rekeying work, not the firm's review.
