Connect QAD Adaptive ERP to EDI instantly
Join thousands of businesses moving EDI orders, invoices and fulfilment updates between QAD Adaptive ERP and their trading partners on XEDI, no manual re-keying.
No credit card needed ✦ Free EDI mailbox included
Getting started with QAD Adaptive ERP EDI
XEDI connects QAD Adaptive ERP with customer and supplier EDI, handling the schedules, releases, despatch advice and self-billing that automotive and life sciences programmes run on, without anyone re-entering them.
One managed platform, no custom code
XEDI maps QAD Adaptive ERP to your trading partners and validates every document, so data flows straight into the systems your teams already use.
QAD's customers trade on schedules, not purchase orders
Most EDI writing assumes a discrete purchase order arrives and is fulfilled. An automotive programme does not work that way. A customer sends a delivery schedule or release carrying firm and forecast horizons, revised repeatedly, and what you owe them is a cumulative position rather than a list of open orders.
QAD is built for exactly that, which is why it is the ERP of choice in those sectors. The integration has to respect it: a release replaces rather than adds, cumulative received quantities have to reconcile against the customer's own figures, and a mismatch is a production problem rather than a paperwork one.
The ASN is the document that gets you paid
In a self-billing programme there is often no invoice from you at all. The customer pays against what they received, which means the despatch advice carries the commercial weight, and a label that does not scan at goods-in becomes a debit note weeks later.
So the pack detail matters more here than almost anywhere else: serial shipping container codes, handling unit hierarchy, and the exact label format the customer's plant expects. We hold those requirements per programme rather than asking you to interpret them.
What your team sees day to day
You get an EDI mailbox and a portal that works like an inbox. Releases and schedules arrive, your team is notified, and the current position is visible without opening a customer portal per programme.
The despatch advice is raised from the shipment rather than re-entered, amended where what ships differs from what was called off, with SSCC labels for the handling units. Where a customer self-bills, the reconciliation position is visible; where they do not, the invoice follows and its delivery is confirmed in the dashboard.
The integration sits over that workflow and automates it, so releases land against QAD demand and shippers raise the ASN. Smaller operations run the portal alone; our API suits enterprises wanting finer granularity; for a QAD site the integration is normally the right answer.
Documents you can exchange
- Delivery schedules and releases landing against QAD demand
- Order acknowledgements and schedule responses
- Despatch advice and ASN messages from QAD shipments
- Invoices, or reconciliation where a customer self-bills
- Inventory and consumption reports where a customer requires them
Built for QAD Adaptive ERP teams
Whoever owns QAD Adaptive ERP in your business, XEDI keeps EDI accurate and hands-off.
- QAD administrators and MIS teams
- Automotive tier one and tier two suppliers
- Life sciences manufacturers
- Planning and despatch teams
- Finance teams handling self-billing
QAD Adaptive ERP EDI document types
The set depends on the customer programme rather than on QAD, but an automotive or life sciences supplier normally runs these.
| Document | What it carries | Direction |
|---|---|---|
| Delivery schedules | Firm and forecast requirements over a horizon, replacing the previous release rather than adding to it. | Customer to QAD |
| Just-in-time calls | Short-horizon call-offs against an agreed schedule, often to a specific dock and time window. | Customer to QAD |
| Advanced shipping notices | Pack and handling unit detail raised from the QAD shipper, carrying the labels the receiving plant scans. | QAD to customer |
| Invoices | Raised from QAD where the customer does not self-bill, referenced to the despatch. | QAD to customer |
| Self-billing reconciliation | The customer's view of what they received and will pay, against your own despatch record. | Customer to QAD |
| Inventory and consumption reports | Stock or usage at the customer's site where a consignment arrangement is in place. | Either direction |
How to connect QAD Adaptive ERP with EDI using XEDI
A QAD connection is less about transport than about respecting how schedules and cumulative quantities behave. The sequence below is what onboarding looks like from your side.
-
01
We scope the QAD domain, sites and customer programmes that carry EDI demand.
-
02
We build the mapping between each customer's schedule, release and shipment messages and your QAD demand and shipper records.
-
03
We configure validation for cumulative quantities and schedule horizons, so a bad release is caught before it reaches planning.
-
04
We prove the schedule, ASN and invoice flows against what each customer requires and against how your QAD sites are set up.
-
05
You get demand landing against the right site with the cumulative position intact, and we keep it right as programmes change.
Ready to connect QAD Adaptive ERP?
Talk through documents, mapping, testing and go-live with XEDI.
Everything about QAD Adaptive ERP EDI
Common requirements
- QAD domain, site and access details
- Customer programme and ship-to structure
- Item, pack and label data
- Cumulative quantity and schedule handling rules
- The trading partners you deal with, or plan to
What we need from you to build it
Only what we cannot hold for you. Each customer programme's requirements are already ours, including their label formats.
- QAD access
- Domain, site and an integration account with rights to the demand, shipper and invoice records in scope.
- Programme and ship-to structure
- Which customer programmes run against which QAD sites, and the dock or unloading point each ship-to resolves to.
- Item and pack data
- Customer part numbers against your own, packaging levels, and the handling unit structure the customer expects to scan.
- Cumulative handling rules
- How cumulative quantities are held and reconciled, and what you want to happen when a customer's figure disagrees with yours.
- Which customers you supply
- The programmes in scope now and next. Their schedule formats and label requirements are already ours.
Why suppliers choose XEDI for QAD Adaptive ERP
- Automotive and life sciences customers are commonly connected already, so a programme can begin without a connectivity project first.
- Schedule and release behaviour is handled properly, so a revised call-off replaces the previous position rather than stacking on top of it.
- Label and handling unit requirements are held per customer programme, which is what keeps an ASN from failing at the receiving dock.
- A new customer programme is not a QAD project. We build it, prove it and hand it over working.
- Cumulative positions are visible against the customer's own figures, rather than being discovered at a debit note.
- If a plant raises a problem, they raise it with us. We are notified on your behalf and fix it before it stops a line.
Does XEDI handle delivery schedules and releases, not just purchase orders?
Yes, and for QAD that is usually the point. Schedules and just-in-time call-offs are handled as releases against a cumulative position rather than as discrete orders, which is how automotive and life sciences programmes actually run.
Can it produce the labels our customer's plant scans?
Yes. Handling unit hierarchy and SSCC labels are generated from the despatch, in the format each customer programme requires, because a label that does not scan at goods-in becomes a debit note later.
What happens if the customer self-bills?
The despatch advice carries the commercial detail, and the customer's self-billing position is reconciled against your own despatch record so a shortfall is visible when it happens rather than at period end.
Plan your QAD Adaptive ERP EDI setup
Everything you need to scope, map and go live with QAD Adaptive ERP, in one place.