Xero does not provide a dedicated field on customer invoices for a client’s Purchase Order (PO) number. This is a significant limitation for B2B users.
Many organisations, particularly medium and large companies, require invoices to reference an approved PO number for their accounts payable processes. In some cases, invoices are not processed or paid at all unless the PO number is clearly and separately identified.
Currently, users are forced to include PO numbers in the invoice description or reference field. This is a workaround, not a solution. It makes automated PO-to-invoice matching on the customer’s side more difficult, increases manual handling, and directly contributes to delayed payments and unnecessary administrative overhead — for both the supplier and the customer.
A clearly labelled, dedicated PO Number field on invoices (visible on the invoice PDF and available via API and exports) should be standard functionality. Its absence creates friction in otherwise automated workflows and does not align with common, real-world accounting and procurement practices.
Xero does not provide a dedicated field on customer invoices for a client’s Purchase Order (PO) number. This is a significant limitation for B2B users.
Many organisations, particularly medium and large companies, require invoices to reference an approved PO number for their accounts payable processes. In some cases, invoices are not processed or paid at all unless the PO number is clearly and separately identified.
Currently, users are forced to include PO numbers in the invoice description or reference field. This is a workaround, not a solution. It makes automated PO-to-invoice matching on the customer’s side more difficult, increases manual handling, and directly contributes to delayed payments and unnecessary administrative overhead — for both the supplier and the customer.
A clearly labelled, dedicated PO Number field on invoices (visible on the invoice PDF and available via API and exports) should be standard functionality. Its absence creates friction in otherwise automated workflows and does not align with common, real-world accounting and procurement practices.