ledgaroo

Bank statement PDF to JSON, by API

Send a PDF statement from your own software and get back its transactions, already checked against the balances the statement prints. The same parser and the same checks as the converter on this site.

It is not built yet. What the people on the waitlist need decides what it returns and what it costs, so if you would use it, tell us below.

What it would do

Return the statement as data.
Each transaction with its date, description and amount, and the statement's opening and closing balances, its period and the totals it prints.
Return the checks with it.
Every row is held against the running balance beside it, the totals against the ones the statement prints, and each date against the period. A statement that fails comes back with the failure named, never as rows that look fine.
Or write the file your ledger imports.
Excel, CSV, Xero CSV, QBO, OFX, QIF or MT940, the same files the converter writes.
Read any bank, with no template.
The parser reads the layout of the page rather than a template per bank, so a statement from a bank it has not seen still reads. The banks page lists the ones we have tested.
Answer in about a second.
In a trial on the kind of server it would run on, a 200-page statement was read in under a second.
Be priced by volume.
A plan of its own, priced by how many statements you send, because unlike the converter each one costs us something to read.

Scanned statements are undecided: we have not yet tried reading them on the server.

Where your statement goes

The API would be the one way of using Ledgaroo where your statement leaves your computer. It would be sent to our server, read, answered and not kept.

The converter on this site stays as it is, and keeps reading every statement in your browser.

Join the waitlist

Tell us how many statements you would send and what you want back. We will write before it opens, and only about the API. Joining costs nothing.