Stop keying documents into SAP ECC and S/4HANA

SAP ECC and S/4HANA: what differs

On S/4HANA, DynamoDocs posts to the standard OData APIs, and the target fields use their names: CompanyCode, InvoicingParty, SupplierInvoiceIDByInvcgParty, and DocumentDate on a supplier invoice; SalesOrderType, SalesOrganization, SoldToParty, and PurchaseOrderByCustomer on a sales order.

On ECC, those APIs do not exist. The usual route is an OData service built in SAP Gateway, or middleware you already run, that accepts the same shape. Either way, a new connection runs in simulation mode and shows the exact payload before anything posts.

SAP AP automation: supplier invoices

Invoices arrive in the AP mailbox or by upload and are read by AI, header and lines, then validated before they reach SAP: required fields present, totals that reconcile, a supplier that resolves, and no duplicate of an invoice already processed.

A passing invoice posts with company code, invoicing party, the supplier's invoice number, document and posting dates, gross amount, and currency, and lines carrying the purchase order reference, GL account, quantity, and item amount. One that fails a rule waits in a review queue with the problem named on the field, beside the original document.

Approval routing, delegation, and no-login approve links are available and off by default. Approved invoices can be exported as a payment proposal CSV or a NACHA file; DynamoDocs never moves money.

Customer POs to sales orders

Customer purchase orders become sales orders with order type, sales organization, sold-to party, the customer's PO number, requested delivery date, and currency, and lines carrying material, requested quantity and unit, and net amount. Requests for quote become sales quotations with a valid-to date.

EDI orders take the same path. DynamoDocs answers an 850 with a 997 and an 855, an 860 with an 865, and sends the 856 and 810 later in the cycle. Billing and cash application stay in SAP.

Document processing and extraction

Extraction does not need a template per supplier or customer. The AI reads layouts it has not seen, flags fields it is unsure of, and hands clean data to validation. Invoices, credit memos, customer POs, requests for quote, and vendor statements share the pipeline; statements reconcile to the cent against what was already processed and post nothing.

EDI alongside SAP

DynamoDocs reads X12 850, 860, 810, and 856 and sends 997, 855, 865, 856, and 810, over AS2, SFTP, or a folder a VAN client watches. Inbound 999s are reconciled against what was sent. AS2 is tested against Mendelson's public server and SFTP against OpenSSH. Each partner runs its own test cycle before going live; no vendor is certified in advance.

How it connects

You provide the OData base URL, the service path, the company code, and a bearer token for a technical user. Transient failures (rate limits and server errors) are retried with backoff; validation errors from SAP are shown on the document rather than retried. Credentials are encrypted with AES-256-GCM and never shown back in the browser.

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