What are the ways into TELUS Farm Accounting?
TELUS Farm Accounting (formerly Farmplan Business Cloud) supports bank feeds and document-capture imports such as Dext and AutoEntry, and publishes no API. So card transactions arrive one of two ways: as uncoded bank-feed lines to be worked through, or as an import file. The import file is where automation can actually help — if the file arrives complete.
Why do bank feeds leave work behind?
A feed line tells you a card was charged at a merchant for an amount. It does not say which enterprise the spend belongs to, whether the charge needs splitting, or where the receipt is. On a farm running cards across family members and staff — fuel, parts, vet, feed — that decoding is real work, done by whoever keeps the books, usually well after the purchase when nobody remembers the details.
How does the Vergo import work?
- Spend is captured as it happens. Every card transaction appears in Vergo immediately. The cardholder photographs the receipt and applies coding from the field, not from a pile of paper in the office.
- Vergo builds the import file. A structured CSV, custom-built to match the import format TELUS Farm Accounting expects — columns and values arranged so the file loads cleanly.
- The bookkeeper runs the import. The export drops into the system's import routine as a routine load. What arrives is coded, split where needed, and backed by receipts stored in Vergo.
How often should the import run?
Weekly keeps the books current through the season; monthly works if that matches your rhythm with your accountant. Because coding happens continuously in Vergo, the import cadence is a choice, not a bottleneck.
What keeps the import clean?
Alignment. Keep the coding lists in Vergo matched to the categories your books use, so exported values validate on import. Vergo holds the receipt against each transaction permanently, which matters when a charge is queried at year end or by your accountant.
What changes at year end?
Year end is where farm bookkeeping shortcuts get expensive. With the Vergo route, every card transaction that entered the books arrived coded, split, and with its receipt stored — so accountant queries get answered from the record, not reconstructed from memory. The import files themselves also form a clean audit trail of exactly what entered the system and when.
Can card transactions post automatically into TELUS Farm Accounting?
Not via API — none is published. The working automation is a matched CSV import: Vergo builds the file in the format the system expects and your bookkeeper loads it.
Is this better than the bank feed?
It completes what the feed leaves out. Feed lines carry no coding or receipts; the Vergo export arrives coded, split, and receipt-backed.
What does the cardholder have to do?
Photograph the receipt and pick the coding on their phone at the time of purchase. Everything downstream is automatic.
Does this work with an accountant or bureau doing the books?
Yes — whoever runs TELUS Farm Accounting runs the import. Vergo produces the file; the load is a standard step in the system.
