Start free

Bank statement fields

Bank statements, one transaction to a row.

Read the account details, the balances and every transaction, with its date, description, money out and money in. The transactions are added up against the totals the statement prints.

Your workspace

This is where you work. See it before you sign up.

The same workspace you get when you sign up, opened on the screen closest to this kind of document. Pick a tab to see the rest.

The fields step for the bank statement list: one row for each value, with its name, its kind and a Needed tick.

Pick the ready list nearest your document, such as an invoice, a receipt or a bank statement, or start with a blank one.

Then name each value you want, say what kind it is, and change any field you like.

Read your own files after you sign up: the free plan reads 30 pages a month.

What it reads

Bank statement fields. Change any of them.

The ready field list starts with these fields. Reword a field, remove it, or add your own.

Fields

10 on the ready list
  • Bank
  • Account name
  • Account number
  • Currency
  • From
  • To
  • Opening balance
  • Closing balance
  • Total money out
  • Total money in

Transactions

A list, one row for each
  • Date
  • Description
  • Money out
  • Money in
  • Balance

Tested on real documents

Tested on two real statements.

We read two real bank statements, 48 pages in all, with the ready Bank statement field list. Then we checked every cell against an answer key. These are the figures of the version we tested.

983 of 983

transactions found on the two statements. None missed, none invented.

48 pages, 983 rows

1,966 of 1,966

amounts and running balances right.

1,638 on the 36-page statement exactly; 328 on the 12-page statement by size (92 kept their printed minus sign)

1,358 of 1,365

boxes in the right place. But only 1,365 of 3,932 values had a box at all.

The second figure is the weak spot.

A fintech wallet statement

Two months, two accounts in one file (a wallet and a savings account), phone-bank PDF. 36 pages, 819 rows.

A fintech wallet statement: 36 pages
What was countedCountWhat it means
Transactions found819 of 819 rowsNone missed, none invented.
Amounts exactly right819 of 819 rowsMoney in or money out, to the kobo.
Running balances exactly right819 of 819 rows
Money in and money out mixed up0 of 819 rows
Dates on the right day818 of 819 rows
Descriptions word for word781 of 819 rows28 of the 38 misses differ only in spacing; 6 lost the first line where the row starts at the bottom of a page; 4 have misread characters.
Values at the top of the statement right10 of 10 values
Boxes in the right place1,064 of 1,071 boxes
Values that had a box on the pageWeak spot1,071 of 3,276 valuesA weakness of the version tested: most right values had no box and said Not on the page.
Time from upload to ready14 minutes 8 seconds36 pages.
Cost of the reading₦1,768 (about $1.11)At ₦1,600 to the dollar.

A naira account statement from a payments app

Nine months, newest first, one signed amount column, phone-bank PDF. 12 pages, 164 rows.

A naira account statement from a payments app: 12 pages
What was countedCountWhat it means
Transactions found164 of 164 rowsNone missed, none invented.
Amounts the right size164 of 164 rows92 money-out amounts were stored with their printed minus sign.
Running balances exactly right164 of 164 rows
Dates on the right day164 of 164 rows
Descriptions word for word163 of 164 rows
Values at the top of the statement right10 of 10 values
Boxes in the right place294 of 294 boxes
Values that had a box on the pageWeak spot294 of 656 values
Time spent reading2 minutes 51 seconds12 pages.
Cost of the reading₦293 (about $0.18)At ₦1,600 to the dollar.

The pages, with Takarda’s boxes

What it found, on the page.

Page 1 of a fintech wallet statement, blurred so no word can be read, with coloured boxes over the dates, descriptions and amounts Takarda found.
A fintech wallet statement, page 1 of 36.
Page 22 of the same wallet statement, blurred so no word can be read, with a coloured box over most rows' date, description and amount.
The same statement, page 22 of 36.
Page 1 of a naira account statement from a payments app, blurred so no word can be read, with coloured boxes over the values at the top and the dates, descriptions and amounts in the table.
A naira account statement from a payments app, page 1 of 12.

Every character is blurred on purpose. The coloured boxes are where Takarda found each value. Some rows have no box: those are the values that said Not on the page although they were right, described below.

How we measured it

An answer key, checked twice.

We built the answer key from each file’s own text, with the position of every value. We then checked it against what the statement prints about itself: its transaction counts, totals, opening and closing balances and every running balance. Two people compared the key with the page pictures. Neither found a problem.

Takarda’s rows were matched to the key’s rows by date, amount and balance. Every cell was compared by value: money to the kobo, dates by day, descriptions word for word. Each box was compared with the key’s position for the same cell.

These are the figures of the version tested. We have since changed how Takarda reads statements: more boxes on statement rows, one check for each account, dates with a time, amounts without their minus sign, fewer wasted reads and descriptions that cross a page break. Those changes have not been measured again, so none of them is counted here.

What went wrong

Shown, not hidden.

Most of the trouble was in the labels, not the values: right values that said Not on the page or Doesn’t match. A few values were wrong too. These are the problems we found.

A fintech wallet statement

  • ProblemOnly 1,071 of 3,276 values had their box on the page; the rest were right but said Not on the page.
  • ProblemThe file holds two accounts and the field list expected one, so the money in and money out totals were marked Doesn't match although every amount was right.
  • Problem238 dates printed with a time of day were read on the right day but not recognised as dates.
  • Problem24 of 66 reading calls ran out of room on dense pages; a third of the cost was spent on answers that were thrown away and read again.

A naira account statement from a payments app

  • Problem92 money-out amounts kept the minus sign the statement prints, so a download would show them as negative numbers.
  • Problem362 right values had no box and said Not on the page.

Your own fields

Start from this one. Make it yours.

Reword a field, add one, remove one, or start blank. Describe each field in a sentence, give a typical value, and save the field list. Use it for every file after that.

No training needed

Describe a field as you would to a colleague.

There is nothing to train and no files to label. For each field, write its name, say in a sentence what to look for, and give a typical value. If a value comes back empty, reword the sentence and read the file again.

01

Name it

A short name you would use in a spreadsheet column.

02

Say what to look for

One sentence, written as you would explain it to a new colleague.

03

Give a typical value

It shows Takarda the shape of the answer: an amount, a date, a name.

Any format

Photos, scans, PDFs, Word and text.

Upload what you have. Takarda prepares each file before it reads it, so a crooked photo and a clean PDF end up in the same columns.

  • PDF
  • Scans
  • Phone photos
  • Images
  • Word files
  • Text files

A file can have up to 100 pages and be up to 20 MB. Upload up to 50 files at a time.

Security

Your documents stay yours.

  • Kept in Africa, read in Europe

    Stored in Africa (Johannesburg). Takarda AI reads each page in the European Union.

  • Never used for training

    Takarda does not use your documents to train any model.

  • Encrypted

    Files travel over an encrypted connection and are stored encrypted.

  • Every change logged

    Each correction and confirmation is logged with who made it. The original reading stays beside it.

Questions

Plain answers to plain questions.

Does it read a statement with many pages?

Yes, up to 100 pages in one file. The transactions come back as one list with a row for each, and you can spread it so every transaction has its own row in Excel.

Can it read the statement my bank app shows as a screenshot?

Yes. Screenshots and photos are read like any page. A screenshot that cuts off part of the table can only give you the part it shows.

Will it tell me if a number looks wrong?

Yes. Money out and money in are added up from the transactions and compared with the totals the statement prints. A difference is marked Doesn't match with both numbers beside it. Takarda never changes a figure to make it fit.

Which files can I upload?

PDFs, JPG, PNG and HEIC pictures, Word (.docx) files and plain text (.txt) files. A file can have up to 100 pages and be up to 20 MB, and you can upload up to 50 files at once. A file Takarda cannot open is refused with a plain note on what to send instead.

What if a value is not on the page?

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.

What does it cost?

The Free plan reads 30 pages a month. Paid plans start at ₦30,000 a month for 250 pages, in naira, month to month. You pay for the pages Takarda reads, not for the people on your team.

Read your first bank statement. Download it checked.