Why do card transactions enter Fund EZ by file?
Because that is the interface Fund EZ provides. The nonprofit fund accounting system has no public API — its integration surface is its file import queues for inbound data and Excel/CSV export for outbound. No card platform can push transactions into Fund EZ any other way, so the practical question is how to make the file path fast and accurate.
What does the manual routine look like?
Most Fund EZ organizations run card spend on a statement cycle: download the statement at month end, chase program staff for receipts, work out which fund and grant each charge belongs to, and key the entries in line by line. The keying is tedious; the allocation is the real risk, because grant compliance depends on charges landing against the right funding source, and memory fades fast on a three-week-old purchase.
How does the import work with Vergo?
1. Capture. Card transactions appear in Vergo in real time, and cardholders attach receipts from their phone at the point of purchase.
2. Code. Each transaction is allocated in Vergo to its fund, grant, and account while the context is fresh — by the cardholder or your finance team, per your workflow.
3. Export. Vergo generates a custom-built CSV export matched to the import format Fund EZ expects, coding carried on every line.
4. Import. Your finance team loads the file through Fund EZ's import queue as a single batch. Entries arrive already allocated; the re-keying step disappears.
Is the batch import audit-ready?
Yes, and arguably more so than the manual version. Receipts are attached to each transaction in Vergo at purchase time, allocations are made while the spend is explainable, and the import file gives you a clean record of exactly what entered Fund EZ and when. For grant reporting, that trail — receipt, coding, batch — is the one auditors want to see.
Can I connect a card feed directly to Fund EZ?
No. Fund EZ has no public API, so there is no direct feed. Transactions enter through its file import queues, which is what Vergo's export is built for.
What file does Vergo produce for Fund EZ?
A custom-built CSV matched to the import format Fund EZ expects, with fund, grant, and account coding applied in Vergo on every line.
How does this help with grant compliance?
Allocations are made in Vergo close to the purchase, with the receipt attached — so charges land against the right funding source and the audit trail is complete before the import runs.
How often should we import?
Whatever matches your close — weekly or monthly both work. Coding is continuous in Vergo, so the import itself is a quick batch step at any cadence.
