YOUR DOCUMENTS KEEP MOVING. EVEN WHEN YOU CLOSE THE TAB. Explore background processing

Bank statement fields

Bank statements, organised by transaction.

Extract account details, balances and transactions, including dates, descriptions, debits and credits. Compare the transaction sums with the statement’s printed totals.

Your workspace

Your documents. Your workspace. Explore the complete workflow.

Preview the workspace on the screen most relevant to this document. Switch tabs to explore the other stages.

TracewiseWorkspace Supplier invoices
FIELD DEFINITION / VERSION 1

Tell Tracewise what matters.

Name each detail and describe where to find it.

Add field +
1
Invoice numberinvoice_number
TextNeeded
2
Supplier namesupplier_name
TextNeeded
3
Invoice dateinvoice_date
DateNeeded
4
Total amounttotal
AmountNeeded
5
Line itemsitems
List of rowsOptional
WHAT TO LOOK FOR · TOTAL AMOUNT

Read the final amount payable exactly as printed, including tax. Leave it empty if it is not on the page.

Text · numbers · dates · yes/no · rowsDefinitions are versioned
Illustrative Tracewise previewA field list of your own.Example data. Your documents and results appear in your workspace.

Choose a template for invoices, receipts or statements, or begin with an empty field list.

Name the information you need, choose its data type and tailor any field.

Use an account with private site access to open your workspace. Check its page allowance and Azure connection before reading documents.

What it reads

Statement fields. Adapt every one.

These fields are included in the template. Edit their descriptions, remove unwanted fields 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

TRACEWISE / DOCUMENT WORKFLOW

Review each movement in context.

Extract transaction dates, descriptions, money in, money out and balances. Missing or unsupported readings remain visible for review; do not treat a completed reading as a completed reconciliation.

TracewiseWorkspace Supplier invoices
CONFIRMED DATA / EXPORT

Ready for the next step.

Export the document revisions you have reviewed and confirmed.

Download ↓
FILE TYPE
XLSX CSVJSON
INCLUDEConfirmed files
Illustrative confirmed invoice export
invoice_numbersupplier_nametotalReview
INV-2048Example supplier1250.00Confirmed
INV-2049Example supplier480.00Confirmed
INV-2050Example supplier795.50Confirmed
Reviewed revisions only.

Warnings and human corrections stay in the review record.

3 illustrative rowsXLSX · CSV · JSON
Illustrative Tracewise previewReviewed data, ready to use.Example data. Your documents and results appear in your workspace.
Read the Tracewise validation studies ↗

TRACEWISE / DOCUMENT WORKFLOW

Trace a reading to the source.

Located values keep OCR word references and a source polygon. An unlocated value is explicitly marked so you can inspect the original.

TracewiseWorkspace Supplier invoices
DOCUMENT REVIEW / REVISION 1

Invoice-2048.pdf

The original and its readings, side by side.

To review
THE ORIGINALPage 1
SAMPLE DOCUMENT
INVOICEINV-2048

Example supplier
Example customer

Document services$1,000.00
Support services$250.00
Total payable$1,250.00
Printed source region
VALUES3 readings
Invoice numberINV-2048On the page · page 1
Supplier nameExample supplierOn the page · page 1
Total amount$1,250.00 Source region · page 1
Your final say.Check the source, correct a value, or keep it as printed.
Illustrative source and extracted valuesConfirm & next ✓
Illustrative Tracewise previewEvery reading has a place.Example data. Your documents and results appear in your workspace.
Read the Tracewise validation studies ↗

TRACEWISE / DOCUMENT WORKFLOW

Check your statement before relying on it.

Compare transaction rows and printed opening and closing balances against the original. Our recorded live validation is currently limited to synthetic invoices; broader statement evaluation remains to be completed.

Read the Tracewise validation studies ↗

Your own fields

Use this template. Shape it around your work.

Edit this template or build a list from scratch. Give each field a short description and an example, save the list, then reuse it across your documents.

No training needed

Explain each field in everyday language.

No labelled training set is needed. Supply a field name, a brief instruction and an example. If a result is missing, make the instruction clearer and run the document again.

01

Choose a name

A short name you would use in a spreadsheet column.

02

Describe the target

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

03

Add an example

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

Any format

From photos and PDFs to Word and text.

Work with the files you receive. Document preparation brings scans, angled photos and clean PDFs into the same extraction workflow.

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

Each upload may contain up to 100 pages and 20 MB. A batch can contain up to 50 files.

Security

Your documents and data remain under your control.

  • Know where processing happens

    Tracewise uses the Azure services configured for this deployment. Storage and processing regions depend on the selected resources; confirm them before uploading sensitive documents.

  • Understand provider data handling

    Model data handling follows the configured Azure service and your deployment’s policies. Review those settings before sending confidential records.

  • Protect the connection

    Use the deployed HTTPS site for uploads. Storage encryption and retention follow the storage service configured for this deployment.

  • Review with a record

    Keep the original extraction alongside reviewer corrections and confirmation history, so changes remain traceable.

Questions

Clear answers to everyday questions.

Does it read a statement with many pages?

Yes. A file may contain up to 100 pages. Transactions from its pages form one list, which can be expanded into separate spreadsheet rows.

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

Yes. Screenshots and photos follow the same workflow. A cropped table can only yield information visible in the image.

Will it tell me if a number looks wrong?

Yes. Transaction debits and credits are totalled and compared with the printed summaries. A discrepancy is labelled Doesn’t match and shows both numbers; the original amounts are retained.

Which files can I upload?

Supported inputs include PDF, JPG, PNG, HEIC, Word (.docx) and plain text (.txt). The limits are 100 pages and 20 MB per file, with 50 files per batch. Unreadable formats receive an explanation so you can provide a supported file.

What if a value is not on the page?

An absent value remains empty with a Not on the page status. A detected value either links to a source box or reports Place not found. Review is still necessary because automated readings can be wrong.

What does it cost?

Start with the allowance shown in your workspace. Azure document reading, review and exports are available. Shared workspaces use role-based invitations; hosted site access is also required. Paid subscriptions remain unconfigured.

Try your first statement. Review, then export.