EXAMPLE INSTRUCTIONS / NOT A COMPLETE TEMPLATE
Ask for what is printed.
Read the printed invoice identifier and final total. Keep missing information empty. Do not calculate a replacement for a printed amount.
TRACEWISE WALKTHROUGH / A RECORDED SYNTHETIC INVOICE
One invoice.
A visible trail.
Follow a real Azure reading of a synthetic document
through source review, confirmation and export.
THE EXAMPLE / 6 NOVEMBER 2026
METRONE-TEST-001.
USD 27.50.
The recorded live test processed a one-page synthetic invoice with one item. Its expected identifier and USD 27.50 total were recovered, reviewed and retained in the approved export. This is a test fixture, not a customer document.
The interface excerpts below explain the workflow using validated fields. They simplify the presentation and do not reproduce the original document’s page geometry. No new AI request runs on this page.
01 / DEFINE THE OUTPUT
A field list
is the brief.
The invoice template names the fields to extract and gives repeating items their own columns. You can edit descriptions, change required fields or add the information your workflow needs.
The document keeps the definition version used for its reading. A later field-list edit does not retroactively change an existing approved snapshot.
Write useful field descriptions02 / READ THE DOCUMENT
A structured result.
The original beside it.
Recorded fields from the live synthetic invoice.
Presentation excerpt, not a live account view.
SOURCE / BASIC INVOICE FIXTURE
The original stays available.
Azure Document Intelligence supplied OCR text and positions. The configured GPT-6 Astra deployment read the selected invoice fields from that evidence.
Each located reading retained the raw text and real OCR word references used to establish its source. The saved evidence checks found no invalid source references in the five-file test set that includes this invoice.
SAVED READING / SELECTED FIELDS1 PAGE
| FIELD | READING |
|---|---|
| Invoice number | METRONE-TEST-001 |
| Currency | USD |
| Total | 27.50 |
| Item rows | 1 |
Missing information stays empty. A reading is not an approval.
03 / INSPECT AND DECIDE
Open the evidence.
Keep a deliberate record.
In the workspace, select a field to inspect its source location and explanation. These expandable notes describe what to check.
Invoice number · METRONE-TEST-001
Compare the identifier with the printed invoice number. A source link identifies the evidence used for the reading; it does not replace your inspection of the document.
Total · USD 27.50
Check the final printed amount and its currency. Repeated amounts elsewhere on a page can create source ambiguity, so inspect the selected location and any warning. Do not change a printed figure merely to make arithmetic reconcile.
Line items · one row
Compare the extracted row with the source and check that no item was missed or duplicated. The recorded fixture contained one item; this walkthrough does not invent additional line details.
Missing or unclear information
Keep absent values empty. Inspect Check and Place not found explanations. Correct an extraction error or retain the printed value with a reason; the first reading remains available.
Independent reading in the current workflow
Selected uncertain fields can now receive another model reading of the saved OCR evidence with the first answer withheld. Its comparison remains separate from the primary result. This recorded invoice run happened before that feature was added, so no second-pass outcome is claimed for it.
Confirm the document
Review the visible warnings and confirm explicitly. The recorded basic invoice was confirmed through the live interface. Confirmation saved the approved revision; the AI did not perform that action.
04 / DOWNLOAD THE APPROVED SNAPSHOT
Useful files.
The same reviewed values.
Excel, CSV and JSON were downloaded through the published interface. Local parsing verified the confirmed invoice identifier, USD 27.50 total, item values and null missing fields. Unconfirmed test files were excluded.
Choose the list layout that fits your next tool. Expanding items repeats document-level fields on each item row; nested JSON can preserve the list structure.
Explore export optionsAVAILABLE FORMATS
XLSXCSVJSON
Exports use the approved revision.
Spreadsheet output protects text that could be interpreted as a formula. Approval provenance stays connected to the exported data. A changed document needs review and confirmation again before its new revision is eligible.
EXCERPT / NOT A DOWNLOAD OF THE COMPLETE RESULT
{
"invoice_number": "METRONE-TEST-001",
"currency": "USD",
"total": 27.50
}A SECOND RECORDED WORKFLOW
Three pages finished
with the tab closed.
A separate live test uploaded one synthetic PDF with three invoices. Scheduled processing saved all three in Review before the workspace was reopened. Their totals were USD 11.00, 22.00 and 33.00.
After human confirmation, XLSX, CSV and JSON matched across three rows and 25 columns. Each child had one item beginning at row index zero, and the original split source was excluded from the export.
Read the background studyWHEN TO CLOSE THE PAGE
Wait for upload acceptance.
Once the upload-success message appears, the server can continue without the workspace, this computer or an open browser. Uploading bytes still requires a connection. Return to inspect results and confirm them; completion does not equal approval.
KEEP THE SCOPE IN VIEW
An observed workflow.
Not universal accuracy.
The dated live evaluation covered five single-invoice fixtures and a three-page split PDF: eight synthetic invoice results. It included poor-quality input, an ambiguous date, missing information and an embedded instruction attempt. It did not establish results for every document type, language or layout.
Use the same discipline on your own authorised documents: define the fields, inspect the source, resolve the warnings and confirm deliberately.
Tracewise