What are the options for card transactions in AccuFund?
AccuFund publishes no public API — its Workbench layer consumes other vendors' APIs to bring data in, but exposes none for third parties to post through — so card activity enters either by manual entry or by file import in a layout AccuFund accepts.
Manual entry is how most AccuFund organizations handle it: statements arrive, the finance office chases program staff for receipts, and each charge gets coded to a fund, program, and account before entry. In fund accounting that coding step carries real stakes — a charge posted to the wrong fund or grant is a compliance issue, and reconstructing what a statement line was for, weeks later, is where mistakes happen.
How does the Vergo workflow handle it?
1. Program staff code as they spend. When a charge hits a Vergo card, the cardholder tags the fund, program, and account in the app and snaps the receipt. The person who made the purchase — who knows which grant it belongs to — does the coding on the day of the spend.
2. Vergo builds the import file. Vergo produces a custom-built CSV export matched to the import format AccuFund expects, with the fund and account coding carried on every line — not a bare bank export the finance office has to rework.
3. Finance imports and reviews. The finance team pulls the export, loads it into AccuFund, and reviews the batch. Statement reconciliation and rekeying drop out of the close; the review and control steps stay.
Why not import the bank's file directly?
A bank export has dates, merchants, and amounts — no funds, no programs, no accounts. Every line would still need coding by the finance office, usually by asking program staff what each charge was, and the columns would still need reshaping to AccuFund's layout. The Vergo file arrives already coded because the cardholders tagged each charge at purchase, with receipts attached in Vergo for anything auditors ask about later.
What does this change at audit time?
Every imported transaction traces back to a coded charge with its receipt and approval history in Vergo. Instead of a box of statements and a folder of loose receipts, the organization has a clean import trail — and nothing entered AccuFund without the finance team loading and reviewing the batch.
Can card spend sync into AccuFund automatically?
No. AccuFund publishes no public API for outside software to post through, so no platform offers a supported direct sync. Vergo automates the file-import path with custom CSV exports matched to AccuFund's format.
Who codes charges to funds and programs?
The cardholders — typically program staff — in Vergo at the time of purchase, with receipts attached. The finance team receives a fully coded batch.
What does the finance team do at month end?
Pull the CSV export from Vergo, import it into AccuFund, and review the batch. Collection, receipt-chasing, and rekeying are gone; review and control remain.
Does this help with grant compliance?
Yes. Fund and program coding happens on the day of the spend by the person who knows the grant, and every transaction keeps its receipt and approval trail in Vergo for auditors.
