cXML invoices: what to clarify after a PunchOut order.

Where the invoice fits

An invoice comes after the buyer has created or approved an order, so it is downstream from the PunchOut catalog session. The supplier and buyer must agree how invoice information is represented, routed and matched to the purchase order.

cXML includes invoice document support in its broader standard, but the presence of an invoice document in the standard does not prove that every buyer requires cXML invoices or that every connection uses the same fields.

Invoice questions to settle with the buyer

• Does the buyer require cXML InvoiceDetailRequest or another invoice channel?
• Which PO number, line references and supplier identifiers must be included?
• When is the invoice considered ready to send?
• Which tax, freight, currency and payment fields are required?
• Where should the invoice be delivered and how is acceptance confirmed?
• What happens when an invoice does not match the approved PO?

Use the transaction history to locate invoice issues

1. 01

   Find the buyer connection

   Start with the procurement relationship and store used for the transaction.

2. 02

   Confirm the PO

   Check that the approved PO and Shopify order belong to the same journey.

3. 03

   Review invoice stage

   See whether invoice generation was recorded for the transaction.

4. 04

   Compare requirements

   Match the recorded activity to the buyer-specific format and delivery agreement.

What PunchOut Central verifies

The supplied product playbook confirms invoice generation as the final tracked transaction stage. It does not confirm one universal cXML invoice exchange for every buyer. Confirm the buyer-specific invoice behavior during onboarding before publishing a technical commitment.

This distinction keeps the educational explanation useful while avoiding a claim that the platform replaces an accounting or accounts-payable system.