EDI System Integration

Connect Auto-Invoice to EDI instantly

Join thousands of businesses moving EDI orders, invoices and fulfilment updates between Auto-Invoice and their trading partners on XEDI, no manual re-keying.

No credit card needed ✦ Free EDI mailbox included

Auto-Invoice logo
Overview

Getting started with Auto-Invoice EDI

XEDI covers the trading relationship around invoice automation, so a system automating how invoices are produced or processed gets the partner compliance, references and delivery confirmation that decide whether those invoices are actually paid.

One managed platform, no custom code

XEDI maps Auto-Invoice to your trading partners and validates every document, so data flows straight into the systems your teams already use.

Producing an invoice automatically is not the same as getting it accepted

Invoice automation solves a real problem: producing or processing invoices without somebody typing them. That is worth having and it usually delivers what it promises internally.

What it does not address is the counterparty. A large customer will only accept an invoice carrying their purchase order reference, their delivery note number, tax expressed the way they read it and, increasingly, transmitted the way they mandate. An invoice that is automatically produced and then rejected has not saved anybody anything.

Delivery confirmation is the gap people notice last

Most invoice processes can tell you an invoice was sent. Far fewer can tell you it arrived, which is the question that actually matters when payment is overdue and nobody can say whether the customer ever received it.

Confirming delivery turns an awkward conversation into a short one. It also changes what the finance team chases: an unpaid invoice that definitely arrived is a payment issue, and one that never did is a process issue, and those need entirely different responses.

What your team sees day to day

You get an EDI mailbox and a portal that behaves like an inbox, so the state of every invoice is visible rather than assumed.

Where you sell, the order becomes the despatch advice from the actual shipment with SSCC labels where required, and the invoice follows on delivery with its arrival confirmed. Where you buy, supplier invoices arrive validated against the order and receipt.

Whatever produces your invoices carries on doing so. The EDI capability is bolted onto it, adding the partner requirements and the confirmation that they arrived.

Documents you can exchange

  • Sales invoices sent to partners in the format each requires
  • Delivery confirmation that an invoice reached the recipient
  • Supplier invoices received and validated for processing
  • Credit notes referenced to the invoice they correct
  • Remittance detail supporting allocation
Who it's for

Built for Auto-Invoice teams

Whoever owns Auto-Invoice in your business, XEDI keeps EDI accurate and hands-off.

  • Finance and accounts teams
  • Accounts payable and receivable
  • Shared service centres
  • Businesses automating invoice production
  • Organisations reducing manual invoice handling
Document flows

Auto-Invoice EDI document types

Direction matters here, since issuing and receiving invoices are different problems.

Document What it carries Direction
Sales invoices Issued to each partner in the format and with the references they will match against. You to partner
Delivery confirmation Evidence the invoice reached the recipient, not merely that it was sent. Partner to you
Supplier invoices Inbound invoices validated against the order and receipt before they reach processing. Supplier to you
Credit notes Adjustments referenced to the invoice they correct, so they can be applied automatically. Either direction
Remittance advice What has been paid against which invoices, supporting allocation without reconstruction. Either direction
Rejections Why a partner would not accept an invoice, in time to correct and resend it. Partner to you
Integration

How to connect Auto-Invoice with EDI using XEDI

The measure is invoices accepted rather than invoices produced. The sequence below is what onboarding looks like from your side.

  1. 01

    We establish which direction matters to you: invoices you issue, invoices you receive, or both.

  2. 02

    We agree how invoice data reaches us and in what form.

  3. 03

    We map the references and tax treatment each partner requires to match against.

  4. 04

    We prove the flows including what happens when a partner rejects an invoice.

  5. 05

    You get invoices that are accepted rather than merely produced.

Ready to connect Auto-Invoice?

Talk through documents, mapping, testing and go-live with XEDI.

Detail

Everything about Auto-Invoice EDI

Common requirements
  • Whether invoices are issued, received or both
  • How invoice data is produced today
  • Reference and tax conventions in use
  • Approval and matching rules
  • The partners you invoice or are invoiced by
What we need from you to build it

Only what we cannot decide for you. Partner invoicing requirements are ours to hold and keep current.

Which direction matters
Invoices you issue, invoices you receive, or both, since they are separate pieces of work.
How invoices are produced
What generates them today and in what form they can be handed over.
References and tax
Which references partners match on and how tax should be expressed, because these decide acceptance.
Approval and matching
What your team will accept without intervention, so validation is set to the same tolerance.
The partners involved
Who you invoice or are invoiced by. Their requirements are already held by us.
Why suppliers choose XEDI for Auto-Invoice
  • The partners you invoice are commonly connected already, so invoices can start reaching them correctly straight away.
  • Invoices carry what each partner needs to accept them, not just what your system produces.
  • Delivery is confirmed, so an overdue invoice is a payment question rather than a mystery.
  • Inbound supplier invoices arrive validated, so your team handles genuine exceptions.
  • Partner invoicing requirements change and keeping up with them is ours.
  • If a partner rejects an invoice, it comes to us and is corrected before it becomes an ageing debt.
We already automate invoice production. What does this add?

Acceptance. An invoice produced automatically and then rejected has saved nothing. This adds the references, formats and transmission each partner requires, plus confirmation the invoice actually arrived.

Can you handle invoices we receive as well?

Yes. Inbound supplier invoices are validated against the order and receipt before reaching your processing, using the same tolerances your team applies.

How do we know an invoice was delivered?

Delivery is confirmed rather than assumed, which separates an unpaid invoice that definitely arrived from one that never did. Those need different responses and are usually indistinguishable without it.

Next steps

Plan your Auto-Invoice EDI setup

Everything you need to scope, map and go live with Auto-Invoice, in one place.