Purchase order, ASN and invoice automation
A PunchOut catalogue gets the order raised. This is everything that happens afterwards — the documents that decide whether you get paid on time.
What it is
Once a buyer approves a requisition, a stream of documents starts moving between you. A purchase order comes to you. An advance shipping notice goes back when you dispatch. An invoice follows. Each one has a required format, and each one can be rejected.
Automating that stream means these documents move as structured cXML between the buyer’s system and yours, rather than as PDFs somebody rekeys. The order lands in your system directly, and the invoice arrives in theirs already matching the order it belongs to.
The commercial reason to care is invoice rejection. An invoice that does not reconcile against the purchase order and the receipt goes into an exception queue, and exception queues are measured in weeks.
Who needs it
What we do
- Receive purchase orders from the buyer’s system as cXML and deliver them into your ERP or order system.
- Generate and transmit advance shipping notices when you dispatch.
- Produce cXML invoices that reference the correct purchase order and line items, formatted to that buyer’s requirements.
- Handle the three-way match fields — PO reference, line identifiers, quantities, tax treatment — that determine whether an invoice reconciles.
- Monitor document flow and alert on failures, rather than letting a rejected document sit unnoticed.
- Adjust when the buyer changes their document requirements, which they periodically do.
What you provide
No developer, and far less of your time than you are expecting.
Timeline and price
Three to six weeks of build work, depending on how accessible your order system is. Document testing with the buyer runs alongside and typically requires several cycles.
This is the Order Loop tier: $349/month for year one, stepping down to $219 from year two. Additional buyer connections are $450 once. You do not start paying until the connection is live in your buyer's production system.
The buyer's testing queue is usually the longer half and it is not ours to control — why supplier enablement takes the time it takes.
Common questions
Do we need PunchOut first?
Not necessarily. Document automation works whether the order originated from a PunchOut catalogue or another route. In practice buyers usually ask for both, which is why Order Loop includes the catalogue as well.
What if our ERP has no API?
Common, and workable. File-based exchange over SFTP, database-level integration, or a scheduled export are all viable. The integration approach adapts to the system you have.
Does this handle tax and regulatory e-invoicing mandates?
cXML invoicing to a buyer’s procurement platform and statutory e-invoicing to a tax authority are different obligations that sometimes overlap. Tell us which markets you invoice into and we will tell you plainly which parts we cover and which need a specialist provider.
Find out what your buyer actually requires
Send us the requirement your buyer sent you. We will tell you which tier covers it and how long it takes — before you commit to anything.
Start a conversation See pricing