Does Soluno publish a public API?
No. Soluno publishes no public API for its legal accounting ledger. Soluno is now sold as Actionstep Legal Accounting, and the article that once described its integration options 404s. The Actionstep developer documentation that does exist covers practice management, not the Soluno accounting ledger.
What does that mean for card and expense automation?
With nothing published, no card or expense platform can offer a supported direct sync into Soluno. Card spend reaches a hosted system like this one of two ways: someone keys each charge in against matters, clients, and disbursement codes, or the finance team imports a file laid out the way Soluno expects.
Manual keying is what most teams fall back on, and it is where the month goes. The statement arrives weeks after the spend, receipts have to be chased from the people who made the charges, and every line still needs coding before it can be entered. Until that happens, the spend is invisible in reporting.
How does Vergo work with Soluno?
Vergo makes the file path behave like automation. Cardholders code each transaction in Vergo at the moment of spend — matter and disbursement coding, receipt captured on the phone — and approvals run before anything leaves Vergo. Vergo then produces a custom-built CSV export matched to the import format Soluno expects, so the accounting team loads one coded batch instead of rekeying a month of activity or reshaping a bank download in a spreadsheet.
Vergo does not claim an API sync with Soluno, because Soluno does not publish one for anyone to use. What Vergo provides is the working path: coding captured once, at the source, and a ready import file at close.
What does the finance team see while the month runs?
This is the part manual entry cannot give you. Because every charge is coded and receipted in Vergo as it happens, the finance team can see committed card spend by matter and disbursement before the statement arrives and before anything is imported. Budget owners get a live picture rather than a retrospective one, and the import at close becomes a confirmation of numbers people have already seen.
Card controls sit in the same place. Limits, merchant restrictions, and per-card rules are set in Vergo, so overspend is prevented at the point of purchase instead of being discovered during coding. For a hosted system with no API surface, that front-end control is what closes the gap: the ledger stays the system of record, and the mess never reaches it.
Could Soluno open an API later?
Possibly. Vendors add developer interfaces when enough of their customers ask for them. But planning a card programme around an interface that does not exist is a bad bet, so treat file-based integration as the dependable path with Soluno today and revisit if the vendor publishes documentation.
What should you ask a vendor claiming a Soluno integration?
Ask exactly how the data moves. If the answer is a file the customer imports, that is a CSV integration and it should be described as one. Ask to see the export run against your own chart of accounts before you sign anything — a file that does not match your matter and disbursement structure creates work rather than removing it.
Does Soluno have a public API?
No. Soluno publishes no public API for its legal accounting ledger. There is no developer portal or published documentation for third parties to build against.
Can any expense platform sync directly with Soluno?
Not through a documented interface. Any vendor claiming a direct Soluno sync is either describing a file import or a private arrangement, so ask which.
How does Vergo get card transactions into Soluno?
Cardholders code charges to matters, clients, and disbursement codes in Vergo with receipts attached, and Vergo generates a custom CSV export matched to the format Soluno imports.
Can the batch be reviewed before it hits the ledger?
Yes. Approvals happen in Vergo before the export is generated, and nothing enters Soluno until your team runs the import.
