The product
Ready field lists or your own, many files at once, a review screen with the page beside every value, warnings, and downloads in Excel, CSV and JSON.
What you get
01 Field lists
Start from a ready field list or from a blank one. Each field has a name, a description of what to look for and a typical value. Fields can be text, numbers, money, dates, yes or no, or lists with columns. Changing a field list makes a new version, and files already read keep theirs.
02 Many files
Upload up to 50 files together. Each one becomes a row with its own status: reading, to review, confirmed or error. Filter by status, search by name, and open any file from the table.
03 Review
Open a file and see the document on one side and its values on the other. Click a value and its box lights up on the page. Correct what is wrong; the original reading stays beside your change. Confirm when you are happy.
04 Warnings
A missing value, a number that cannot be read, a total that does not add up, the same file twice: each is flagged with a plain sentence and the numbers. Nothing is changed for you.
05 Downloads
Download the files you confirmed, one row for each. Spread a list such as invoice lines so every line gets its own row. Nothing unconfirmed goes in.
Options
Each field list has a few options. They change how Takarda reads, and you can switch them on or off at any time.
For your own software
An admin can make up to five API keys. A key works only on your account. Every call is logged, rate limited and counted in pages like any upload.
Authorization: Bearer <your key>
POST /api/v1/x/extractions/{field_list}/files send one file
GET /api/v1/x/extractions/{field_list}/files the rows and statuses
GET /api/v1/x/documents/{file} the values, statuses, boxesDocuments
Why it helps
Tested on real documents
We read two real bank statements and a public company report with the version of Takarda we tested, and counted every result against an answer key. The counts, how we measured them and what went wrong are on each page below.
983 of 983
transactions found on two real bank statements (48 pages). None missed, none invented.
19 of 19
fields right on a 37-page public quarterly report, each with its box on the page, using a field list written for it.
1,358 of 1,365
boxes in the right place on the statements. Only 1,365 of 3,932 values had a box at all, and that is the weak spot we found.
These are figures of the version tested, counted against an answer key. What went wrong is listed beside them, not left out.
Questions
Yes. Every ready field list is a starting point. Reword a field, remove one, add your own, or make a list field with columns. Changing a field list makes a new version, and files already read keep theirs.
Yes. Upload up to 50 files together. Each one becomes a row, with its own status: reading, to review, confirmed or error. Check them one by one, then download.
Yes. An admin can make up to five API keys. A key uploads a file into a field list and fetches the rows, the statuses and the boxes. Every call is logged and counts pages like any upload.
Yes, and members are free on every plan. A viewer can look, a reviewer can upload, correct and confirm, and an admin can make and edit field lists and keys.
It reads Not on the page and stays empty. Takarda does not guess to fill a gap. A value that is found points to a box on the page. Some wrong readings can still get through, which is why you look at each file and confirm it before you download.
Excel, CSV or JSON, with one row for each confirmed file. A list such as invoice lines can be spread so every line gets its own row, or kept as one cell. A cell that starts with = or + cannot run as a formula. The purchase order field list also has a sales order download.