Does TELUS Farm Accounting publish an API?
No. TELUS Farm Accounting — the UK farm accounts package formerly known as Farmplan Business Cloud, which passed from Proagrica to TELUS Agriculture — publishes no public API and offers no developer resources. The routes it does support for bringing data in are bank feeds and document-capture imports such as Dext and AutoEntry.
Those routes matter, but they are not an API: there is no documented way for another platform to read from or write to the system programmatically.
What does that mean for expense automation on the farm?
It means no card platform can claim a live sync with TELUS Farm Accounting. Bank feeds will show that a card was charged, but a feed line is not a coded transaction — someone still has to say which enterprise the spend belongs to, attach the receipt, and split charges that cover more than one thing. On a farm business running several cards across the family and staff, that reconciliation lands on whoever does the books.
How does Vergo connect without an API?
Through structured CSV exports custom-built to the import format TELUS Farm Accounting expects. Card transactions are captured in Vergo as they happen; cardholders attach receipts and apply coding from their phones; and the finished, coded data exports as a file shaped for the system's import. The bookkeeping side receives complete transactions rather than a bank feed to decode.
Is a CSV export a real integration?
It is the honest one. The system's published inbound routes are file- and feed-based, so a matched file is how outside data is meant to arrive. The difference Vergo makes is that the file is built automatically from already-coded spend, not assembled by hand from statements at month end.
What should you ask any expense tool about this system?
Ask whether it claims a live connection — if it does, be skeptical, because the system publishes nothing to connect to. Ask whether its export matches the import format the system expects, or whether it hands you a generic file to rework. And ask where receipts end up. Vergo claims no API, builds the export to match the system's import, and keeps every receipt stored against its transaction.
What does the workflow feel like day to day?
Cards get used as normal — fuel, parts, vet, feed. Each holder codes their own spend from their phone in seconds. The bookkeeper, whether in the farm office or at the accountant's, runs an import on their own schedule and receives complete transactions. Nobody sits down with a statement and a highlighter.
Does TELUS Farm Accounting have a public API?
No. The system, formerly Farmplan Business Cloud, publishes no API and no developer resources. Its supported inbound routes are bank feeds and document-capture imports like Dext and AutoEntry.
Can Vergo sync directly with TELUS Farm Accounting?
Not by API — none exists. Vergo provides custom-built CSV exports matched to the system's import format — the working automation path for card spend.
Do bank feeds solve card expenses?
Only partly. A feed shows the charge but carries no coding, receipt, or split. Vergo captures those at the point of spend and delivers them in the export.
Did Farmplan Business Cloud have an API?
No — the product's integration posture did not change with the TELUS Agriculture rebrand. File-based import remains the route in.
