A sale is finished, the work is done, and the invoice goes out. Then the waiting starts. The customer may receive a perfectly good PDF, but someone still has to open it, read it, and enter the details into another system. A missing purchase order reference or unclear line description can turn that small task into a chain of emails. That pressure grows when a government agency or a larger customer asks suppliers to use e-invoicing. For Australian and New Zealand businesses, Business Central supports the Peppol PINT A-NZ format through its E-Documents framework. It gives the finance team a way to send structured invoice information from the system where the invoice was created, rather than creating a separate version for the customer.
Why PDFs Create Friction
A PDF invoice is easy for a person to read. It is not necessarily easy for an accounting system to use. The recipient may need to type the invoice number, amounts, tax details, payment terms, and purchase order reference into its own accounts payable process. Every handoff creates another chance for a number to be missed, a field to be interpreted differently, or the invoice to wait in the wrong queue. E-invoicing changes the form of that handoff. It sends invoice data in an agreed structured format that the receiving accounting system can read. The invoice still needs accurate details and approval. The information can move as data instead of being reconstructed from a document. Peppol is the network and set of standards that carries those electronic business documents between organisations. It is not a separate connection for every customer. A business uses its chosen access point to send the invoice. The network passes it to the recipient's access point, which delivers it to the recipient's system.
A Format Built for A-NZ
Australian and New Zealand suppliers face a practical question when a trading partner wants Peppol e-invoices. They need a format that both sides recognise and a way to send it without disrupting their everyday invoice process. PINT A-NZ is the Peppol electronic invoice format supported in Business Central for those markets. Microsoft made that localisation generally available on 1 April 2025. The useful part is that the work stays connected to the sales invoice. On the E-Document Service page, the business selects PINT A-NZ as the document format and selects a Peppol service provider through the service integration settings. The provider acts as the access point for document exchange. The framework can also support manual upload or email when those delivery methods are the appropriate choice. This lets a business start with the customer that has asked for e-invoicing. The finance team can continue creating and posting sales invoices in Business Central. It does not need to download invoice information, rebuild it in another product, and then keep two versions aligned.
One Supplier's First Invoice
Consider a Wellington engineering supplier that wins maintenance work with a large facilities contractor. Each month, the supplier invoices for completed maintenance work and spare parts. The contractor asks for Peppol e-invoices because its accounts payable system handles structured documents automatically. Without a shared format, the supplier could email a PDF and hope it reaches the right person. If the contractor cannot quickly identify the purchase order or understand a line, the invoice can sit in a query queue. The supplier may keep chasing payment without knowing that the hold-up started with invoice handling. With PINT A-NZ configured in Business Central, the supplier creates its sales invoice in the usual workflow. The E-Document Service applies the selected format, and the chosen Peppol provider sends the document through the access point. The contractor receives structured invoice information that its system can process, instead of a PDF that needs manual interpretation. That does not guarantee an immediate payment. The invoice still needs the right work details and the customer's normal approval. It does remove an avoidable pause between systems, which can reduce the risk of an invoice being lost, retyped incorrectly, or held before it reaches the appropriate queue.
Start with Clean Data
A structured format cannot repair incomplete information after the invoice has been sent. If a customer record is wrong or a required purchase order reference is missing, the invoice still has a problem. Before using Peppol with a trading partner, check the customer record, contact details, purchase order references, tax treatment, payment terms, and item or service descriptions. Then agree the operating process with the customer. Confirm which Peppol identifiers it uses, when it wants the first live invoice, and who should investigate a rejected or missing document. A Business Central partner or finance lead can help choose and configure the service provider that operates as the Peppol access point. The setup separates the document format from the service integration, giving the business a clear way to choose PINT A-NZ and its provider.
Build Confidence Gradually
Replacing every invoice process at once can feel risky. Start with one customer ready for Peppol, test the complete path, and make sure the team knows how to handle exceptions. Standard invoices can remain available for customers not ready for electronic exchange. Once that first process is working, extend the same approach to more trading relationships. The invoice remains a Business Central record, while PINT A-NZ provides a consistent way to exchange it through the Peppol network.
Why It Matters
Peppol PINT A-NZ gives Australian and New Zealand businesses a practical route to structured e-invoicing with government agencies and larger trading partners. It reduces avoidable invoice handling without pulling the sales process out of Business Central. For a small team, that means less time wondering where an invoice went and more confidence that it arrived in a form the customer can use.