Document Automation That People Can Trust

A row in a spreadsheet is useful until one number looks wrong. Then the operator needs the original page, the exact source region, the extraction method, and the rule that accepted it.

Keep the source file immutable. Store a content hash, document version, page reference, and extraction output together. Provenance turns a mysterious value into something a person can verify.

Not every field deserves the same review. A misspelled description may be harmless. A wrong currency, bank account, tax amount, or total can create financial damage.

Use deterministic rules first: types, ranges, totals, allowed vendors, duplicate invoice numbers, and currency consistency. Use a human threshold for uncertain or high-value records.

Do not let an extraction model write directly to accounting, a CRM, or an outbound email. Persist a draft, validate it, collect approval if needed, then execute the side effect with an idempotency key.

This separation makes re-extraction safe. You can improve the parser without repeating the payment, post, or message.

Email attachments, web forms, WhatsApp messages, scans, and uploaded PDFs arrive with different identity and ordering problems. Normalize them into one intake record before processing.

Attach sender, received time, source channel, external message ID, and all files. Deduplicate before extraction because users often resend a document when they do not see an immediate response.

An API success response is not the final proof. Fetch the created object or run a scheduled reconciliation against the source intake. Confirm amounts, status, and attachment presence.

For PDF generation, check file size, required text, storage location, and source-record link. For accounting, compare posted totals and provider IDs. Mark mismatches as repairable failures.

A finance approval can take minutes or days. The workflow should sleep without holding a worker, preserve the exact draft under review, and resume after an authenticated signal.

Orch8 models this as persisted sequence state plus approval and signal steps. The useful part is not the waiting. It is knowing which version of the document was approved when execution resumes.