What are the options for getting card transactions into FastFund?
Araize FastFund Accounting does not publish a public API, so there is no direct programmatic route for an expense platform to post card transactions into the system. Outside data enters FastFund through the product's own import capability. In practice a nonprofit finance team has three options: key transactions in by hand, reshape a raw card-statement download into something importable, or use a platform that produces an import-ready file for you.
Why is a raw statement download not enough?
A statement export from your card provider is a list of bank lines. It carries no receipts, no approvals, and none of the coding fund accounting requires — no fund, no program, no account distribution. Someone still has to touch every line before it can enter FastFund correctly, which is why "we download the statement" usually means hours of month-end cleanup.
How does Vergo prepare the import file?
Vergo issues the corporate cards and captures each transaction as it happens. Cardholders attach receipts from their phones, and coding rules apply the accounts and dimensions your chart requires — including the fund and program coding your reporting depends on. When you are ready to bring the activity into FastFund, Vergo produces a custom-built CSV export matched to FastFund's import format. The columns and layout are set up for your system once, then every export follows it.
What does the workflow look like month to month?
Day to day, cardholders spend and snap receipts; approvers clear transactions in Vergo. At whatever cadence you close — weekly or monthly — you export the coded transactions and import the file into FastFund. The entries arrive with the coding already applied, so reconciliation is a check, not a re-keying exercise. There is no waiting on a sync and nothing to reconcile between two live systems, because the file is the handoff.
What should you check before the first import?
Confirm the file layout against your FastFund import screen, and confirm the account, fund, and program values in Vergo mirror your FastFund lists exactly — an import is only as clean as the codes in it. Vergo builds the export to your format at setup, so this is a one-time mapping, not a monthly chore.
Can Vergo post transactions directly into FastFund?
No — FastFund publishes no public API, so no platform can post directly. Vergo provides custom CSV exports matched to FastFund's import format instead.
What is in the export file?
Coded card transactions: date, amount, vendor, account distribution, and the fund and program coding your team applied in Vergo, laid out for FastFund's import.
How long does an import take?
Once the export format is mapped at setup, producing the file and importing it into FastFund takes minutes per cycle.
Do receipts come across in the file?
Receipts and approvals live in Vergo as the audit trail for each transaction; the CSV carries the accounting data FastFund needs to book the entries.
