docimprint

Finance & audit workflows

How do finance teams use DocImprint for invoice processing?

Teams POST invoices to /v1/extract with structured or invoice modes to extract line items, totals, and vendor fields with paragraph-level citations. Evidence bundles preserve the original PDF and OCR output for auditors.

Can reconciliation agents pay per document without an account?

Yes. x402 USDC micropayments on Base let autonomous agents pay $0.010–$0.075 per call without API keys. Wallet address becomes the resource owner for bundle retrieval and legal hold.

How do evidence bundles help SOX and audit reviews?

Each bundle includes manifest SHA-256, EIP-191 signature, and per-artifact hashes verifiable offline via GET /v1/keys. Auditors can download ZIP artifacts and confirm nothing changed since capture — without trusting DocImprint at review time.

Typical finance agent workflow

An autonomous reconciliation agent monitors a shared inbox for invoice PDFs. For each document it calls POST /v1/extract with store=true to create an evidence bundle, then runs claim-check mode to validate totals against ERP records. Discrepancies trigger human review with bundle_id citations.

For quarterly SEC filings, teams use compare mode to detect version drift between filing periods. Collections aggregate all bundles for a fiscal year, enabling cross-document Q&A with Merkle-proven citations.

API keys with monthly credits suit predictable finance team volume ($49/mo Pro plan). x402 suits event-driven agents processing variable invoice volume without prepaid commitments.

Recommended extract modes

Evaluation metrics (labeled examples)

Example scenario: A reconciliation agent processes 200 invoice PDFs/month. Claim-check validates totals in <3s per document. Evidence bundles verify offline in <10ms via GET /v1/keys. Merkle citation proofs average ~320 bytes (O(log n) for typical invoices).

Illustrative workflow metrics — not customer testimonials. Your results vary by document complexity.

Related