How do card transactions get into EasyFarm?
By import file. EasyFarm has no API — it is locally installed farm accounting software whose data paths are file-based, with electronic banking import on the way in and Excel or FINPACK export on the way out. So card activity reaches the books either typed in by hand or brought in as prepared transaction data through the import.
What does the manual month end look like?
- Gather receipts from the truck cab, the shop bench, and everyone's wallets.
- Download or wait for the card statement.
- Work out which purchase was fuel, which was repairs, which was feed or vet or seed — and code each to the right expense account.
- Enter the lines into EasyFarm one at a time.
It is a full evening or more each month, done from memory weeks after the purchases, and the coding quality is whatever memory allows. Tax time inherits every shortcut taken along the way.
How does Vergo automate the import?
Vergo moves the capture to the moment of purchase and builds the import file for you:
- Capture: purchases on Vergo cards appear in real time; whoever spent snaps the receipt and codes it from their phone at the counter.
- Coding: each transaction carries the vendor and expense-account references your EasyFarm books use — fuel, repairs, supplies, feed — applied while the purchase is fresh.
- Export: Vergo generates a custom-built CSV matched to the import format EasyFarm expects. You review the batch and bring it in through the import.
To be plain about the mechanism: this is a file integration, the kind EasyFarm is designed for. Vergo does not sync with EasyFarm live, because the software has no API — what changes is that the import file shows up finished instead of being built at the kitchen table.
How often should you import?
Monthly fits most farm bookkeeping rhythms; weekly keeps batches small during busy seasons like planting and harvest when card activity spikes. Because coding happens as purchases are made, the export is ready whenever you sit down to the books.
What about receipts at tax time?
Receipts stay attached to each transaction in Vergo. Every line imported into EasyFarm traces back to a documented purchase with the receipt and coding on record — which is exactly what your tax preparer, lender, or FSA paperwork asks for.
What changes about doing the books?
The import stays a normal EasyFarm step, run when you sit down to the books. What disappears is the evening before it — the receipt pile, the statement, the coding from memory. You review a prepared batch instead of building one, and the books stay current through planting and harvest instead of falling a season behind.
Can card transactions flow into EasyFarm automatically?
No — EasyFarm has no API, so there is no live feed. Vergo generates a custom CSV matched to EasyFarm's import format, and you bring it in through the import.
What does the export contain?
Each card transaction with date, amount, vendor, and the expense-account coding applied in Vergo, arranged in the format EasyFarm expects.
Who codes the purchases on a farm with several spenders?
Whoever made the purchase codes it in Vergo from their phone; you review the batch before importing instead of reconstructing the month from a statement.
Does this help at tax time?
Yes. Consistent expense-account coding all year and receipts attached to every transaction mean the imported books hold up when your preparer or lender looks closely.
