Does AJS publish a public API?
Not that anyone can find. AJS is a hosted legal practice management and accounting system used by South African law firms, and neither ajs.co.za nor ajsglobal.com carries any developer documentation — no API reference, no integration guides for third parties. An unpublished API may exist behind the scenes for the vendor's own use, but for practical purposes there is nothing an outside platform can build a documented sync against.
What does that mean for a law firm's expense automation?
It means card and expense platforms cannot offer a genuine API sync into AJS, and any implication otherwise is not backed by published documentation. The realistic path is file-based: automate the capture and coding of card spend outside AJS, then bring the finished data in through import.
For a legal practice, the coding question is sharper than in most businesses: expenses must land against the right matter, and the distinction between recoverable disbursements and firm overhead has billing and trust-accounting consequences. That coding is exactly what gets mangled when someone reconstructs a card statement weeks after the spend.
How does Vergo work with AJS?
Vergo issues corporate cards and captures every transaction at the point of sale. Fee earners attach receipts from their phones and code each purchase — to the matter where it belongs, or to the firm's own accounts — while the context is fresh. Vergo then provides custom-built CSV exports matched to AJS's import format, so the file loads without re-mapping.
The routine: spend on Vergo cards, code and document in Vergo, export the formatted file, import into AJS. Vergo does not claim an API connection with AJS, because none is published; it provides the working automation path for the system as it actually is.
Could AJS expose an API in future?
Possibly — a hosted product could add developer documentation at any time, and this page reflects what is published today. If AJS releases a public API, deeper integration becomes possible; until then, building on the documented import path is the honest choice, and it already removes the manual work that makes card reconciliation painful in a firm.
Does AJS have a public API for integrations?
No public API documentation exists — there is no developer content on ajs.co.za or ajsglobal.com. Whatever may exist internally, third parties have nothing documented to build against.
How does Vergo get card transactions into AJS?
Through custom-built CSV exports matched to AJS's import format. Transactions are captured, receipt-matched, and coded in Vergo, then loaded into AJS by file import.
Can card spend be coded to matters before it reaches AJS?
Yes. Fee earners code purchases to matters in Vergo at the point of spend, so the import file arrives with matter allocation already done rather than reconstructed at month-end.
Is a file import acceptable for a firm's accounting controls?
Yes, treated as a batch posting: verify the batch total against the export, spot-check matter coding, and post. Because coding happens at the point of spend, exceptions are rare and visible.
