Does Liberty Accounts publish a public API?
No. Liberty Accounts consumes external APIs — it connects to HMRC for tax filing and to Companies House — but it publishes no outbound API of its own for third-party platforms to read from or write to. Although it is a hosted, cloud-based system, there is no developer program or documented interface a card platform could build a live sync against.
What does that mean for expense automation at a charity?
It means no card platform can claim a direct API sync with Liberty Accounts. Charities and small organisations on Liberty handle card spend manually: download the statement, chase receipts from staff and volunteers, code each line — including to the right fund where spend is restricted — and enter or import the results. For a treasurer or finance officer, that is a recurring monthly chore, and fund-level accuracy is the part most at risk when coding happens weeks after the spend.
How does Vergo work with Liberty Accounts without an API?
Through matched file imports. Card transactions land in Vergo in real time; spenders attach receipts from their phone; each transaction is coded as it is reviewed. Vergo then generates a custom-built CSV export matched to the import format Liberty Accounts expects, ready to load in one step.
The coding, receipt collection, and approvals happen in Vergo during the month; Liberty receives a clean, structured file instead of a statement to re-key.
Is a file-based connection dependable?
Yes — for a system with no published API, a matched import file is the working automation path. The usual weakness of file imports is format drift, which is why Vergo builds the export to Liberty's specific import layout rather than handing you a generic CSV to rework. The receipt trail stays in Vergo, which matters for charity audit and Gift Aid-adjacent record keeping.
What should treasurers take away?
Two things. First, be wary of any card product implying a live sync with Liberty Accounts — there is no published API for one to be built on, so ask how the data actually moves. Second, no API does not mean staying manual. The expensive parts of the monthly cycle — receipt chasing, fund coding from memory, spreadsheet re-keying — all move into Vergo at the moment of spend, and Liberty keeps its familiar role as the ledger of record, fed by one clean, correctly formatted import each cycle.
Does Liberty Accounts have an API for integrations?
No. Liberty Accounts consumes HMRC and Companies House APIs for its own features but publishes no outbound API for third-party platforms to connect to.
Can Vergo integrate with Liberty Accounts?
Yes, through files. Vergo provides custom-built CSV exports matched to the import format Liberty Accounts expects, so coded card transactions import without re-entry.
Can charity card spend be coded to funds before import?
Coding happens in Vergo as transactions are reviewed, so spend reaches Liberty allocated the way your chart and fund structure require, rather than reconstructed from a statement.
Isn't Liberty cloud-based — why no direct sync?
Being hosted doesn't create an integration surface. Liberty publishes no developer API, so there is no supported interface for a live third-party sync; file import is the working path.
