AI document extraction for auditors preparing audit evidence

Dynamite Docs
Source → result
Invoice evidence: Trace each checked valueEvidence reference: AP-042 p1. Document: INV-1042. Date: 2026-09-18. Illustrative example, not extracted customer data.SOURCE DOCUMENTInvoice evidenceEvidence referenceAP-042 p1DocumentINV-1042Date2026-09-18Trace each checked valueEvidence referenceAP-042 p1DocumentINV-1042Date2026-09-18Keep the source with your working…
Evidence reference
AP-042 p1
Document
INV-1042
Keep the source with your working papers. Illustrative example.

Prepare invoice and statement rows for working papers while retaining a clear route back to the source evidence.

Try a document extraction

Answer in 30 seconds

Prepare invoice and statement rows for working papers while retaining a clear route back to the source evidence.

Audit preparation often starts with a folder of invoices, bank statements, and supporting documents. Dynamite Docs can extract draft document fields and table rows for a working-paper register. The reviewer compares the result with the original file before the data enters a test schedule.

Choose the fields for the procedure you intend to perform. An invoice register for vouching may need supplier, invoice number, date, currency, amount, and a reviewer-assigned evidence reference. A statement schedule may need account, period, and transaction detail. Keep the population definition, exclusions, and sampling decisions in the audit team’s own working papers.

Documents to prepare

Invoice evidence

Capture supplier, document number, document date, currency, line values, tax, and total. Retain credit notes as separate documents and preserve signs rather than merging them into invoice totals.

Statement schedules

Extract transaction rows and period balances. Check that the complete statement is present and that page order has not changed during scanning.

Supporting records

Prepare fields from purchase orders or expense evidence using the schema needed for the procedure. Add source locators yourself when assembling the reviewed register.

An illustrative evidence preparation schedule

Fictional records and reviewer-assigned references. Review notes indicate preparation status, not an audit conclusion.

Dynamite Docs
Inside the output
Invoice evidence: Trace each checked valueEvidence reference: AP-042 p1. Document: INV-1042. Date: 2026-09-18. Illustrative example, not extracted customer data.Source-linked field inspectorInvoice evidenceAP-042 p1INV-10422026-09-18Evidence referenceAP-042 p1DocumentINV-1042Date2026-09-18
Evidence reference
AP-042 p1
Document
INV-1042
Date
2026-09-18
Keep the source with your working papers. Illustrative example.
Evidence referenceDocumentDateCurrencyTotalPreparation note
AP-042 p1INV-10422026-09-18USD1180.00Compared with source
AP-043 p1CN-10432026-09-21USD-80.00Credit note sign checked

Review against the source

Dynamite Docs
The review
Invoice evidence: Trace each checked valueCompare identifiers, dates, and amounts with the source rather than relying on a confidence score.. Verify document count, page completeness, repeated documents, and omitted rows before treating the register as a population.. Keep extraction corrections separate from evidence observations and record the reviewer and review date in your working papers.. Illustrative example, not extracted customer data.SOURCE DOCUMENTInvoice evidenceEvidence referenceAP-042 p1DocumentINV-1042Date2026-09-18Review before exportEvidence referenceAP-042 p1Compare with the source on the leftAccept after reviewKeep the source with your workingpapers.Original stays…
Evidence reference
AP-042 p1
Document
INV-1042
Date
2026-09-18
Keep the source with your working papers. Illustrative example.
  • Compare identifiers, dates, and amounts with the source rather than relying on a confidence score.
  • Verify document count, page completeness, repeated documents, and omitted rows before treating the register as a population.
  • Keep extraction corrections separate from evidence observations and record the reviewer and review date in your working papers.
  • Retain the original evidence under your firm’s retention and access policies; an exported row is not the original document.

Prepare a reviewed handoff

Dynamite Docs
The handoff
Invoice evidence: Trace each checked valueDefine the preparation schema. Review each extracted record. Transfer checked rows to the working paper. Illustrative example, not extracted customer data.FROM SOURCE FILE TO A RESULT YOU CAN USEInvoiceevidenceReview workspaceTrace eachcheckedvalue1Define thepreparationschema2Review eachextracted record3Transfer checkedrows to theworking paper
  1. 01Define the preparation schema
  2. 02Review each extracted record
  3. 03Transfer checked rows to the working paper
Keep the source with your working papers. Illustrative example.
  1. Define the preparation schema

    Select fields that support the planned procedure. Include currency and source identification, and document how unreadable or missing values will be treated.

  2. Review each extracted record

    Check the proposed values beside the source. Leave unresolved fields blank or flag them for follow-up rather than filling in an assumed value.

  3. Transfer checked rows to the working paper

    Export to Excel, CSV, or JSON. Verify counts and totals after import and attach the evidence references, reviewer notes, and procedure documentation required by your firm.

Use the accepted output

The output is a reviewed preparation table for an audit team’s existing working papers. Excel supports a register and exception sheets. JSON can carry fields and rows for an internal application with a defined schema.

Review Excel, CSV, and JSON export formats

Processing choices and allowances

Choose hosted AI, your own provider keys, or local Ollama on an eligible plan. Each successfully processed hosted page uses one PE. Free and Hobby BYOK use the same PE allowance; Pro and Ultra BYOK cost zero PE, with provider charges and limits still applying. Failed pages cost zero PE.

Check current plans, page limits, and capabilities and review storage and data-residency policies before processing sensitive records. Local model inference is a separate choice from browser-local file storage.

Workflow boundaries

  • Dynamite Docs does not select samples, determine evidence sufficiency, or issue audit conclusions.
  • Extraction cannot authenticate a document or prove that a recorded transaction occurred.

Questions about this workflow

Are exported rows audit evidence by themselves?

They are a preparation aid. Keep the original documents and the firm’s evidence references, and assess the information under your own audit methodology.

How should unreadable values be handled?

Record the exception and request a clearer source or other appropriate evidence. Do not infer a missing amount simply because it makes a total balance.

Loading Dynamite Docs… This page is taking longer than expected. Reload page.