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

Your own fields

Any document. The fields you need.

Build a field list from scratch using clear names and example values. Save it once and apply the same structure to subsequent documents.

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.

Fields

Choose fields to suit your document.

For each field, provide its name, extraction instruction, example and data type.

Fields

6 on the ready list
  • Text
  • Number
  • Money
  • Date
  • Yes or no
  • List with columns

TRACEWISE / DOCUMENT WORKFLOW

Your document. Your field definition.

Build text, number, amount, date, yes/no and repeating-row fields. Describe exactly what should be read and whether a value is required. Reuse and version the definition across your documents.

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.
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.

How do I describe a field?

Provide a short name, a plain-language instruction and an example. If the field returns empty, clarify where to look or what to exclude, then run the document again.

Can a field be a table?

Yes. A list field defines its own columns for repeated content such as invoice lines or employment history. Each list row comes from the source document.

Can I change a field list later?

Yes. Edits create a new field-list version. Previously processed documents retain their existing version until you choose Read again.

Do I need to train anything?

No labelled training set is required. Describe each field and provide an example. Refine unclear instructions and rerun when needed; after a field-list edit, up to three rereads per document per day are included.

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.

Can I check the results before I download?

Yes. Review the source beside the extracted values, correct errors and confirm the file. Corrections retain the original reading, and exports include confirmed files only.

Try your first document. Review, then export.