CORA
ENNLESFR
Sign inStart free trial

How it works

CORA does the sorting so you only handle the exceptions. Here is exactly what happens between a document arriving and your figures being right.

From invoice to booked, without you

This is a sales invoice being matched to the payment on your bank statement. CORA compares the invoice number, the amount, the currency, the date and the counterparty, scores the match, and books it when it is certain.

CW-2026-014
Blue Bay Trading N.V.
Due 2026-08-19
Cg 4,350.00
MCB Business
2026-08-21
PAYMENT CW-2026-014
+ Cg 4,350.00
  1. 1Invoice sentCW-2026-014 · Blue Bay Trading N.V. · Cg 4,350.00
  2. 2Bank statement comes inMCB Business · 12 lines read and balanced
  3. 3CORA comparesinvoice number · amount · currency · date · counterparty
  4. 4Match found — 99%booked automatically, with the reasons kept
Why CORA is sure
  • invoice number CW-2026-014 in the description
  • amount and currency exact
  • paid 2 days after the invoice date
  • counterparty matches the customer

Connecting your bank

Where a bank supports it, CORA connects to it directly and your transactions arrive on their own — nothing to download, nothing to upload. European accounts go through Ponto, and in the US plans your American account goes through Stripe; you sign in at your own bank in their window, so CORA never sees your login. Mercury and Wise connect directly, with an API key you create in your own account and can revoke there. You give the permission yourself, you see exactly which accounts are shared, and you can withdraw it whenever you like — in CORA or at your bank.

Ponto may charge for their connection. That is a contract between you and Ponto, outside CORA — you pay them directly and it is not part of your CORA subscription.

Or let your bank email the statement in

Every administration in CORA has its own email address. Does your bank send your statement by email each month? Point it at that address and CORA reads it the moment it arrives — checks it against its own opening and closing balance, creates the transactions and starts matching. You never download or upload a thing. The account has to exist in CORA already, so the statement lands on the right one.

1 · Something comes in

A bank statement you upload or that arrives through your bank connection. A purchase invoice you drop in, photograph, or that a supplier emails to your own CORA address. A sales invoice you sent from CORA itself.

2 · CORA reads it

Statements are parsed line by line and checked against their own opening and closing balance. Documents are read for supplier, date, amount, currency and tax — including receipts in a currency you have never used before.

3 · CORA looks for the match

Every bank transaction is compared with your open invoices and receipts on invoice number, amount, currency, date and counterparty. Each candidate gets a score, and the reasons behind that score are written out in plain language.

4 · Certain is booked, doubtful is asked

Above the threshold you set yourself, CORA books it and shows you why. Below it, the match waits in your inbox with the reasons next to it, so deciding takes a second instead of a search.

5 · Your figures follow

Every booking lands in the ledger straight away, so your result, your sales tax position and your reports are current — not something you assemble at the end of the quarter.

6 · And it keeps running

Bank connections sync on their own. Reminders for unpaid invoices go out on their own. Recurring invoices are created on their own. Exchange rates are fetched daily. You get a note when something needs you.

Swipe to see all 6

Try it on your own paperwork

Fourteen days free. Upload one real statement and see how much of it CORA sorts out without you.

Start your 14-day trial See everything CORA does