Accounts payable automation, minus the data entry

DynamoDocs is accounts payable automation software that removes manual invoice keying from the AP workflow. Supplier invoices are captured from a monitored mailbox or upload, AI extracts and classifies the data, validation catches problems before they reach the ledger, and approved bills are posted into your ERP. AP staff handle only the small fraction that fail validation, which commonly cuts AP document-handling labor by 80–95%.

Yes, and it is controlled by a setting. Two-way matching compares each invoice to the purchase order it references: line subtotals plus per-line quantity and price, within tolerances you set. Three-way matching adds the receipt, so an invoice for a delivery that never arrived does not pass. The receipt can come from packing slips captured as documents or from your ERP's own receiving records, so you are not asked to re-key data your ERP already holds. Only a shortfall raises an exception; an over-delivery is a warehouse question rather than an AP one, and a unit-of-measure conflict is reported for a person to settle instead of guessed at. Three-way matching is off by default, because switching it on before receipts are actually being captured flags every invoice as nothing-received and buries the real exceptions on day one.

With routing rules, edited in Settings. Each rule matches on an amount band, vendor, GL account, or document type (first matching rule wins) and names the approver; with no matching rule, your default approvers take it, and administrators can always approve. An approver who is out of office delegates to a named cover until a date they set, and the record shows who approved on whose behalf. Reminders chase anything sitting unactioned, and the notification carries a signed approve/reject link that works without a login round-trip. A link goes stale the moment the document is re-routed, so an old email cannot approve the wrong version. Nothing posts unapproved while the gate is on, every decision lands in the audit trail, and the whole thing is off by default so your flow does not change until you turn it on.

They are a first-class document type with a path of their own, so a credit never has to be squeezed through the invoice flow as a negative amount. A credit memo is classified automatically on arrival (including from UBL credit notes, Factur-X, and EDI 810s flagged as credits) and linked to the invoice it references. It is flagged for review when no invoice references it, when the invoice it cites never arrived, or when a vendor's cumulative credits exceed the invoice they reference. If the invoice arrives after the credit, the waiting memo is re-checked automatically. Approved credits post to your ERP as a vendor credit where the ERP supports one; where it does not, DynamoDocs refuses a live post instead of quietly booking your credit as a payable.

Yes. Statements are a document type of their own. Upload one (or let it arrive by email) and each line is resolved against what you have actually captured from that vendor: matched, never-captured (an invoice you may have missed), amounts-disagree (to the cent, because a tolerance would hide exactly what the check exists to find), or listed-twice. Negative statement lines are matched against credit memos, closing balances are excluded from the math because a balance is not a document, and if a referenced invoice arrives later the statement re-reconciles itself. A statement never posts anything to your ERP; it produces evidence your AP team acts on.

No, and that is deliberate: DynamoDocs never moves money. What it does is remove the manual step between approval and payment: bills that have passed the approval gate can be exported as a payment-proposal CSV or an ACH (NACHA) file that your own bank upload or ERP payment run executes, with credits netted per vendor and vendors with missing or invalid banking details skipped with stated reasons instead of guessed at. Banking data is held encrypted, masked on read, and admin-only, and generating the ACH file is admin-only too. Your bank and your existing controls stay exactly where they are. DynamoDocs just hands them a clean, approved batch.

Yes, indirectly but materially. The reason month-end AP is painful is that invoices pile up and get keyed in a rush, so liabilities land in the wrong period and the close drags. Because DynamoDocs captures, codes, and posts invoices continuously as they arrive, your payables are recorded in the correct period throughout the month instead of in a last-minute batch. That means fewer unrecorded liabilities at cutoff, a shorter close, and a cleaner accrual position, with a full audit trail from each ledger entry back to the original invoice.

They overlap but are not identical. Invoice automation focuses on turning an incoming invoice into an accurate posted record: capture, extraction, matching, and posting. Accounts payable automation is the broader workflow around it: coding to the general ledger, routing for approval, controlling who can authorize a payment, and keeping the audit trail for the close. DynamoDocs covers both, so an AP team gets touchless processing of clean invoices and a controlled, coded, and approved path for everything else.

No, and that is the point. You send a supplier a signed link and they answer on a single page: confirm the order as written, propose a different delivery date or quantity, or say they cannot fulfil it. There is no login, no password, and no account created at any stage, because requiring suppliers to register is precisely the step that stops supplier-facing software from getting used. The link is scoped to one order and one contact and expires, and by default the supplier is asked for the last four characters of the order number before the order is shown, so a forwarded email does not hand the order to anyone who receives it. A confirmation as written changes nothing about the order. An answer that changes it is flagged and routed to review, so nobody plans against a date the supplier never agreed to. This is deliberately not a supplier portal: there is no standing login, no dashboard, and nothing for your suppliers to maintain.

Yes, on an inbound shipment view built from documents you are already capturing: advance ship notices, packing slips, and the purchase orders they reference. Nothing extra needs to be collected. Shipments show as in transit, received, or invoiced, and an advance ship notice is treated as the supplier's statement of intent rather than proof of arrival, so goods are never reported as on hand while they are still on a truck. Overdue is measured against whatever date was actually committed to, and a supplier's own promised date takes precedence over the date you originally asked for. Anything open or overdue stays visible however old it is, because the shipment that went missing two months ago is the one most worth finding.

Yes, from the paperwork already flowing through it rather than from anything you have to enter. Each supplier gets on-time delivery, whether shipments arrived complete, whether invoice prices matched the order, how clean their paperwork lands, and how often they answer when asked. Two rules keep the numbers honest. A measure with no evidence shows a dash rather than zero, because ranking a supplier you have never measured below one that is genuinely poor is worse than saying nothing. And only documents a reviewer has finished with are scored, since a document still in review might reflect an extraction problem rather than a supplier problem, and a scorecard should not move because someone is on holiday.

Manually keying a single document into an ERP typically takes 5–10 minutes and costs $2–$6 in labor, before you count the cost of correcting the errors that hand-keying introduces. DynamoDocs processes documents in seconds and only asks a person to review the small fraction that fail validation, which commonly cuts document-handling labor by 80–95%. On a team handling a few thousand documents a month, that is the equivalent of one to several full-time roles returned to higher-value work, plus a faster close and fewer downstream corrections. Use the interactive calculator on this page to model your own volume, minutes-per-document, and labor rate and see the annual figure for your operation.

ERP targets include Infor XA, SAP, Dynamics 365, Business Central, QuickBooks Online, NetSuite, Sage Intacct, Sage 50, Xero, Acumatica, Epicor Kinetic, Epicor Prophet 21, SYSPRO, IFS Cloud, Plex, Macola, Deltek Costpoint, Sage 100, Sage 300, Dynamics GP, Oracle ERP Cloud, Odoo, and Zoho Books, plus any system via a generic REST or CSV connector. Documents arrive via Microsoft 365, Google Workspace/Gmail, any IMAP mailbox, drag-and-drop upload, or EDI, over SFTP, AS2, or a folder your VAN client already watches.

Every document is validated automatically. Clean ones pass through on their own. Anything that fails a rule is flagged field by field and sent to a review queue, so people only handle the exceptions. You can also train the extractor on your own sample documents to improve accuracy on your vendors' formats.

No. Document types, fields, validation rules, and ERP field mappings are all configuration edited in a Settings UI. Adding a type or field is a settings change, not a coding project.