Capture

Email capture (M365 / Gmail / IMAP)

Monitored mailboxes ingest attachments and HTML-body documents automatically; each inbox can pin a document type or auto-classify.

Drag-and-drop upload

PDF, scans, photos, Excel, HTML, forwarded .eml, with per-file progress and a batch summary.

Pictures inside emails

An order pasted into an email as a screenshot or photo is read like an attachment, and the email itself previews beside the fields.

EDI intake (X12)

850, 860, 810, 856 parsed exactly; 855 and 997 join the documents they answer instead of becoming queue items.

Free EDI X12 viewer

Paste an 850, 810, 855, 856, 860, or 997 and read it as tables in your browser, on a port of the EDI intake parser. Nothing is uploaded.

E-invoices (UBL/Peppol, Factur-X, cXML)

Parsed deterministically at confidence 1.0. No AI call, nothing to misread.

Extraction

AI extraction, no templates

Claude reads layouts it has never seen; the prompt is generated from your field schema.

Train on your samples

Upload real documents per type; review the guidance before it goes live.

Learning from corrections

Reviewer edits aggregate into new guidance automatically: one systematic fix, not row-by-row.

Plain-English processing rules

Ordinary sentences applied to every document; toggle each rule on or off.

Model & key as configuration

Choose the model, rotate the key, tune caching. Takes effect on the next document, no restart.

Checks & intelligence

Validation tied to fields

Every issue carries a stable code and highlights the exact field that caused it.

Duplicate vs. reissue detection

Same number, same total = resend (warning). Same number, different total = reissue (error). Only the later copy is flagged.

Two- & three-way matching

Invoice ↔ PO, optionally ↔ receipt; receipts from captured packing slips or the ERP's own records.

Vendor statement reconciliation

Each line resolves to matched / never-captured / amounts-disagree / listed-twice, to the cent.

Credit memo linkage

Linked to the invoice offset; over-crediting flagged cumulatively; posted as vendor credits, never payables.

Related documents

The paperwork trail around any document, computed on demand.

Item catalog matching

Lines resolve to your own item numbers, part number first; a description-only match is a suggestion to confirm, and a size or pack family shows a picker.

Per-line price check

Each line's price compared with the catalog or the referenced quote, never across currencies; an authoritative price that disagrees stops the document for review.

Supplier collaboration

Order confirmations without a portal

A signed link; confirm, propose changes, or decline. No supplier account, ever.

Inbound shipment board

In transit / received / invoiced, overdue on top, promise never counted as delivery.

Supplier scorecards

Five measures from documents you already capture; dashes, never fake zeros.

Workflow & controls

Auto / Review lanes

Clean documents flow; flagged ones queue for a human, per document type.

Approval routing

Rules by amount / vendor / GL / type; delegation; reminders; signed no-login approve links.

Straight-through posting

Optional auto-post gated on the lowest field confidence, with a circuit breaker on failures.

Payment-file export

Proposal CSV or NACHA ACH from approved bills; no money movement, by design.

GL-code suggestions

From your keyword rules, then from how the same item was coded before.

Review panel with one-click fixes

Each flag explains itself and offers its own fix: approve a suggested item, confirm a quantity, accept a total. Approve review clears the rest, on the record.

Urgent work first

Rush orders get a badge, pin to the top, and have their own filter and dashboard tile. What counts as urgent is configuration.

Missing-info email drafts

For a document with gaps only the customer can fill, a ready-to-send request listing just those gaps. Drafted, never sent on its own.

Tamper-evident audit trail

Append-only and hash-chained: every ingest, edit, review decision, and export, with a named actor and before/after values. An altered entry breaks the chain.

Records & access

Microsoft 365 & Google sign-in

Entra ID for the tenants you list, or Google Workspace; password sign-in can be switched off, with an admin-only break-glass.

Four roles, enforced on the server

Viewer, reviewer, approver, administrator, from your own Entra app roles or groups if you like. Every write declares its least role.

Archive, never delete

Archiving keeps the record and its original file, records who and why, and every record carries a retention date.

Inspection copies

Any record as printable HTML or JSON: data, full history, and a live check of the audit chain.

21 CFR Part 11 controls

The §11.10 record controls built in and covered by named tests, with electronic signatures as a setting. Validation stays with you.

Electronic signatures

Each release signed by re-entering a password or signing in to Microsoft again, with name, time, and meaning recorded on the record and its inspection copy.

Separation of duties

Optional: whoever entered or changed a document cannot approve or post it. Documents nobody touched need only one approver.

Change log and reasons

Every settings, rule and access change logged with who and before/after; every field edit records why.

Sessions and passwords to your policy

Inactivity sign-out, maximum session length, minimum password length and account lockout, all as settings.

Access and audit-trail reviews

Quarterly-ready reports of who has access and what was changed after release, each attested in the change log.

Annex 11, ISO 13485, SOX

What each asks, where DynamoDocs meets it, and the gaps, on one page each.

Your brand, not ours

Name, logo, favicon, and a palette per colour mode, carried through the app, its emails, and its printed copies.

Export & integration

ERP export with field mapping

A visual per-type map shapes the exact payload; required fields block export until filled.

13+ ERP connectors

QuickBooks, Xero, Business Central, F&O, NetSuite, Sage Intacct, Acumatica, Infor XA, SAP, Sage 50, REST, CSV.

Outbound EDI

997, 855, 865, 856, 810, generated only for clean documents, with per-partner implementation guides as config.

Export-once protection

A successful post can't silently repeat; a deliberate re-post is confirmed and recorded.

Event webhooks

HMAC-signed lifecycle events to your endpoints.

Read-only API

Versioned /api/v1 with hashed bearer keys; writes refused by design.

Book a working session, not a sales call

Bring two or three of your real documents: your ugliest invoice, a customer PO, an EDI file. In 30 minutes we'll run them through extraction, validation, and a mapping to your ERP, live. You'll leave knowing exactly what your rollout would look like, and you'll get the founder, not a sales team.