Stop keying documents into Acumatica

Acumatica AP automation: supplier invoices to Bills

Supplier invoices arrive in a shared mailbox (Microsoft 365, Gmail, or any IMAP inbox) or by upload. DynamoDocs reads each one with AI, header and every line, and checks it before anything reaches Acumatica: required fields present, totals that add up, a vendor it can resolve, and no second copy of an invoice already processed.

An invoice that passes is posted as an Acumatica Bill: vendor, reference number, date, due date, currency, and description on the header; GL account, inventory ID, quantity, unit cost, amount, and line description on each line. One that fails lands in a review queue with the problem named on the field, beside the original PDF, so a reviewer corrects one value and posts it.

Approval routing is there when you want it, by amount band, vendor, GL account, or document type, with out-of-office delegation and approve or reject links that work without a login. Two- and three-way matching are available too, with receipts taken from the packing slips you already receive (advance ship notices count as receipts only if you turn that on). Approved bills can be exported as a payment proposal CSV or a NACHA file; DynamoDocs never moves money.

Supplier credit memos are recognized as their own document type, linked to the invoice they offset, and flagged when they cite nothing or credit more than the original. They are not yet posted to Acumatica automatically: rather than risk booking a credit as a payable, they wait for your team.

Order-to-cash and sales order automation

Customer purchase orders are the other half of the inbox. DynamoDocs captures them from email, upload, or EDI, extracts the header and every line, and posts a sales order (order type SO) to Acumatica with the customer, their PO number in the customer order field, the order date, the requested date, and each line’s inventory ID, quantity, and unit price. Requests for quote become sales quotes (order type QT).

Lines missing an inventory ID, or quantities and prices that break a rule you set, are held for order entry to confirm instead of posting half right. For EDI partners, DynamoDocs answers each order automatically once it passes validation: an 855 acknowledgment for a new order or an 865 for a change. The 856 ship notice and 810 invoice the partner expects later in the cycle go out from the same order.

Where it stops: DynamoDocs does not create the AR invoice inside Acumatica or apply the customer’s payment. It gets the order in correctly and keeps the trading partner answered; billing and cash application stay in Acumatica.

Document processing and data extraction

Five document types go through the same pipeline: supplier invoices, credit memos, customer purchase orders, requests for quote, and vendor statements. Statements are reconciled line by line against the invoices and credits already processed, to the cent, and never post anything.

Extraction does not depend on a template per vendor. The AI reads layouts it has never seen, and each field it is unsure of is flagged for review rather than guessed. Document types, fields, and validation rules are settings, so adding a field to what you capture does not need a developer.

EDI for Acumatica

DynamoDocs reads X12 850 purchase orders, 860 order changes, 810 invoices, and 856 ship notices, and sends 997 functional acknowledgments, 855 order acknowledgments, 865 change acknowledgments, 856 ship notices, and 810 invoices. It also reads the 999s partners send back and reconciles them against what was sent.

Each trading partner is a configuration record: its ISA qualifier and ID, how documents travel (AS2, SFTP, or a folder that an SPS Commerce, Cleo, or TrueCommerce client already watches), which responses go out automatically, and the specifics of that partner’s implementation guide. Both transports are tested against independent implementations: AS2 against Mendelson’s public test server and SFTP against OpenSSH. No trading partner certifies a vendor in advance; each runs its own test cycle with you, and we support that cycle.

How it connects to Acumatica

DynamoDocs uses Acumatica’s contract-based REST API on the Default endpoint, with the endpoint version set per instance. It signs in as a service user for the company and branch you specify, writes the record (Bill or SalesOrder), and signs out. Vendors, customers, GL accounts, and inventory IDs are mapped to your own in a point-and-click field mapper.

A new connection runs in simulation mode until you switch it live, so you can inspect every mapped record before the first real post. If you would rather import than post, the same mapped records can be written as CSV files for an Acumatica import scenario.

MYOB Acumatica (Australia and New Zealand)

MYOB sells Acumatica in Australia and New Zealand as MYOB Acumatica. It is the same platform with the same contract-based REST API, so everything on this page applies unchanged: the same connector, the same Bills and sales orders, the same EDI. Invoices in AUD or NZD carry their currency through to the Bill.

Enterprise deployments can be self-hosted or run in a dedicated cloud region; the security page covers data handling in detail.

For measured production numbers, the distributor case study covers four months of live AP, run on Epicor Prophet 21 rather than Acumatica.