Creditcrest Extract
A bank’s PDF, a scan, a workbook or a banking file in; its transactions out.
Part of Creditcrest Statement, in Creditcrest Decisioning Suite.
Only the rows, checked.
Every transaction as data, with whether the statement’s own balances agree.
What you do here. Give a statement file, or try an invented one of each kind, and get its rows with the statement’s own checks.
Try a sampleTry it end to endTake the tour- You bring
- A statement file of any kind, locked or not
- You get
- Date, description, amount and balance for each, as data
- Holds the line
- Rows that do not add up are flagged, never smoothed over
Try it
Pick an invented statement, or give your own.
What it reads
- A PDF statement
- A CSV export
- An Excel workbook (.xlsx)
- An Excel 97–2003 workbook (.xls)
- An OpenDocument spreadsheet (.ods)
- A web page saved as a spreadsheet
- An Excel 2003 XML spreadsheet
- An OFX, QFX or QBO file (Quicken, QuickBooks, MYOB, Xero)
- A QIF file (Quicken, MYOB)
- A SWIFT MT940 or MT942 file
- An ISO 20022 camt.052, camt.053 or camt.054 file
A PDF is read from where its words sit, and a scanned one by text recognition that runs here: no file goes to any other service.
What comes back
Each transaction’s date, description, amount (money out is negative) and the balance after it. The statement’s period, its opening and closing balances, and two checks: how many printed balances agree with the amounts read, and whether the opening balance plus the transactions comes to the closing one. Where they do not, it says so.
For a program
POST /v1/statement/extract with the file as the body, or as a multipart file, returns the same answer as JSON. Get a sandbox key in one call.
Price
$1.45 a file through the API, the price of a statement read. Pricing