Acumatica EDI Integration Services

EDI transactions

Connect the complete order-to-cash conversation

Scope the X12 documents your trading partners require and the Acumatica or operational records each document needs. These supplier-side examples are confirmed against the partner's version and implementation guide.

1. 01 / Buyer → supplier

   Order

   EDI 850

   Purchase Order

   What does the buyer need?

   Mapping details

   Sales order and configured order type

   Map customer, inventory item, unit, warehouse, requested dates, and buyer references into the appropriate order workflow.

2. 02 / Supplier → buyer

   Confirmation

   EDI 855

   Purchase Order Acknowledgment

   What can you supply, and when?

   Mapping details

   Reviewed sales-order commitment

   Send acceptance and changes from the agreed business status, including quantities and promised dates.

3. 03 / Supplier → buyer

   Fulfillment

   EDI 856

   Advance Ship Notice

   What shipped, and how is it packed?

   Mapping details

   Confirmed shipment + package data

   Build the ASN from the shipping event and packing records, including external warehouse details if Acumatica does not hold them.

4. 04 / Supplier → buyer

   Billing

   EDI 810

   Invoice

   What is the buyer being charged?

   Mapping details

   Approved invoice

   Translate the agreed invoice state and preserve PO, shipment, charge, and line references.

5. 05 / Buyer → supplier

   Payment

   EDI 820

   Payment / Remittance

   Which invoices does the remittance cover?

   Mapping details

   Finance reconciliation + application visibility

   Match retailer remittance references, invoice amounts, and deductions to approved finance records. Define how Acumatica receives reconciliation status; a remittance message alone does not establish payment settlement.

The business journey is shown in sequence; actual timing follows the partner agreement. An EDI 820 carries payment instructions or remittance information. Payment execution and settlement are confirmed through the agreed finance and banking process.

Additional scope can include 860 order changes, 940 warehouse shipping orders, 945 shipping advice, or EDIFACT equivalents. A technical acknowledgment is separate from a commercial acceptance. Documents and directions are agreed for each partner.

Frequently asked questions

Acumatica EDI integration FAQs

• Can you map Acumatica custom fields to EDI?

  We review whether the fields are exposed in the endpoint contract and scope extensions where needed. Field availability and business validation are confirmed before partner testing.

• Does the integration work with multiple warehouses?

  Multi-warehouse flows can be included. We define routing, stock availability, shipment splitting, and document references for the agreed Acumatica setup.

• What happens when an Acumatica endpoint changes?

  The integration contract and regression scenarios should be reviewed as part of the change. We agree version ownership and testing responsibilities in the support scope.

• What is included in a Acumatica EDI integration project?

  The agreed scope covers discovery, source-to-target mapping, connectivity, validation, exception handling, end-to-end testing, and go-live support. Deliverables identify the trading partners, document types, application records, and any ERP or warehouse changes required. Ongoing support responsibilities are agreed separately.

• How long does Acumatica EDI implementation take?

  Timing depends on partner testing windows, document complexity, master-data readiness, interface access, and application changes. After discovery, we provide a dated plan with dependencies and acceptance criteria rather than promise one timeline for every project.

• Can we retain our current EDI provider or VAN?

  We assess the existing provider's interfaces, mapping ownership, transport agreements, and support responsibilities. The project can focus on the application connection where suitable. If migration is needed, we plan partner testing, reconciliation, and cutover explicitly.

• How is EDI integration priced?

  Scope is driven by the number of partners and document maps, application interfaces, custom fields, warehouse dependencies, environments, and support requirements. We separate implementation work from any recurring service, transport, or third-party licensing costs in the proposal.