Before
Vendors send orders and invoices as PDFs. Someone types the lines into a spreadsheet or the accounting system, and the mistakes are quiet ones: a line that doesn't multiply out, a total that doesn't match, the same invoice paid twice.
Plenty of tools promise to read documents without a template. We wanted one that says plainly what it does when the reading is wrong.
What we built
You drop in a vendor's PDF. Parselo reads every line item and runs 8 checks before it hands anything over:
- The lines add up to the document's total.
- Every line is complete.
- The document has its number.
- No lines are missing from the middle.
- The currency is one it knows.
- Each line multiplies out to the amount printed on it.
- The same invoice number hasn't already come in from the same vendor.
- The reading is confident enough overall.
The checks are plain code, not AI, and each one is tested. If a check fails, the document is held instead of sent on. Everything that passes goes out as a CSV or as rows in your Google Sheet, with no template to build and nothing to map.
How it runs week to week
Documents that pass every check go straight out. The ones that don't wait in one queue, grouped by the check that stopped them, so a batch of documents with the same problem is one job, not a pile of separate ones.
A document that fails is read again by a stronger model before it lands in that queue.
Results
No results yet, and we won't make any up. Parselo is live, and every document it has read so far is one we made ourselves to test it. The first distributor to run real documents through it will set the numbers on this page.
What this looks like for your business
If your team keys vendor orders or invoices in by hand, the checks are the part that matters. They catch the expensive mistakes, like a duplicated invoice or a line that doesn't multiply out, before they reach your books.
See it at parselo.app, or book a call and we'll talk through how your documents arrive today.