EDI with trading partnersReference for the EDI with trading partners connection in Runtara: what it is used for, its capabilities, connection types and the data it handles.AgentsdocsAgentsdocsagentsorder channels

Order channels

EDI with trading partners

EDI is set up by our team during implementation rather than configured from a built-in agent. For each trading partner, we work from the partner's document specs and test files, map documents to and from your ERP inside the workflow, and validate every document before anything is written.

For plans and availability, see the EDI with trading partners integration.

Common use cases

  1. Receive customer purchase orders (850) and create ERP sales orders.
  2. Send order acknowledgments (855), ship notices (856) and invoices (810) from ERP data.
  3. Receive supplier documents and match them to open purchase orders.

Capabilities

  • Partner-specific document mapping
  • Validation against your ERP before anything is written
  • Exceptions held for a person
  • Each document kept with its run record

Setup

Our team sets up each trading partner during implementation, from the partner's specs and test files. Those specs are on the access checklist that starts the two-week clock.

Data handled

  • Purchase orders
  • Order acknowledgments
  • Ship notices
  • Invoices

Glossary

Used in