EDI partners and email orders, one queue

DynamoDocs is EDI integration software that speaks X12 in both directions inside a broader document-automation pipeline. It reads 850 purchase orders, 860 order changes, 810 invoices, and 856 ship notices, and sends the 997, 855, 865, 856, and 810 documents partners require, automatically and only for documents that pass validation. Transport is SFTP, AS2, or a folder an existing VAN client (SPS Commerce, Cleo, TrueCommerce) already watches. EDI documents parse exactly, with no AI step and no per-document EDI surcharge, and land in the same queue as PDF and email documents, so both channels share one set of rules and one ERP mapping.

The capability is included on every plan. There is no separate EDI product or licence, and no per-document EDI surcharge. An EDI document counts toward your plan volume exactly like a PDF does, and costs us less to process than one, because X12 parses deterministically with no AI extraction step. What is metered is connections: one channel to one counterparty or network. For classic retail EDI that is usually one per trading partner; for a supplier network or VAN it is one connection to the network, with buyers underneath it as configuration. See the pricing page for the per-connection numbers.

That depends on your partner, not on DynamoDocs. Many large trading partners exchange only through a VAN, and that mode is fully supported: DynamoDocs reads and writes a folder your VAN client already watches, so SPS Commerce, Cleo, or TrueCommerce keep doing what they do now. Where a partner offers a direct SFTP or AS2 connection, DynamoDocs connects directly and no VAN is involved. Either way the documents, rules, and ERP mapping are identical, and changing transport later changes nothing else.

No vendor is, until you run that partner's test cycle. Every partner certifies against its own implementation guide, typically over two to four rounds, regardless of which software you use. What DynamoDocs changes is the cost of each round: because a partner's guide lives in configuration, a correction is a settings change instead of a development project. To be straight about the stage: both transports are verified against genuinely foreign implementations (AS2 against a public third-party server, SFTP against OpenSSH's own server software), but no trading partner has certified DynamoDocs yet.

The usual setup is a translator for EDI partners and a separate capture tool for everyone who emails a PDF, which means two sets of validation rules, two ERP mappings, and two queues that cannot see each other's documents. The cost shows up in operations: a tolerance changed twice, an approval threshold that applies in one system and not the other, and the same order arriving as an 850 and an emailed confirmation looking like two orders because neither system can compare them. DynamoDocs runs both channels through one queue, one set of rules, and one mapping, while your VAN or direct connections keep doing exactly what they do now.

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.