Why is there no direct card feed into FBS?
FBS Systems publishes no public API reference for its farm accounting software, so there is no endpoint a card platform can deliver transactions to. FBS runs on-premise and takes outside data through file imports. Every card programme running alongside FBS therefore ends at the same step: getting a coded batch of transactions into the books without typing them in one at a time.
What does the manual version look like?
The familiar month-end routine: download the card statement, collect receipts from whoever was buying parts, fuel, and supplies, figure out which enterprise and account each charge belongs to, and key the entries into FBS by hand. On an operation with several cardholders, that is hours of data entry — and the allocation quality suffers, because it happens weeks after the purchase.
How does the import work with Vergo?
1. Capture. Card transactions land 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 while the purchase is fresh, so the coding reflects what the spend was actually for.
3. Export. Vergo generates a custom-built CSV export matched to the import format FBS expects, with the coding carried on every line.
4. Import. Your bookkeeper loads the file into FBS as a single batch. The entries arrive already allocated, and the re-keying step is gone.
Is a batch import good enough?
For FBS it is the only option — no published API means no platform can offer a direct sync. And judged on its own, the batch import handles the part of card admin that actually consumes time: coding and data entry both happen before the file exists. The import itself takes minutes and can run at whatever cadence fits your close, weekly or monthly.
Can a card platform feed transactions straight into FBS?
No. FBS publishes no public API, so no direct feed exists. Transactions enter FBS through file import, which is the path Vergo's export is built for.
What format is Vergo's export for FBS?
A custom-built CSV matched to the import format FBS expects, with each line carrying the coding applied in Vergo.
When does the coding happen?
In Vergo, at or near the time of purchase — not at month end. The allocations travel into FBS on the import file.
How often should the import run?
Whatever fits your routine. Because coding is continuous in Vergo, the FBS import is a quick batch step whether you run it weekly or monthly.
