Start by checking your software capability
Before changing any processes, check whether your accounting system is eInvoicing-ready. Some software products can send eInvoices, some can receive them, and some can do both. In Australia, the eInvoicing Ready product register helps businesses identify certified products that can send or receive valid invoices through an accredited Australian Peppol service provider and register a business on the Peppol network. In New Zealand, the eInvoicing software product list is a useful starting point, but the government recommends confirming capability directly with your provider. Before you go live, make sure your accounting software has the right details for your organisation. This includes:- your legal business name
- Australian business number (ABN) or New Zealand business number (NZBN)
- GST details
- trading names and
- contact information.
Review your invoice fields
eInvoices are structured, which means the data needs to be in the right place. Your accounting software should be set up to capture the fields your customers and suppliers need. Pay close attention to purchase order numbers, invoice references, GST and tax codes, payment terms, bank account details, delivery details and line-item descriptions. The cleaner your invoice data is at the start, the fewer issues your finance team will need to fix later.Decide how you will connect to the Peppol network
Some businesses connect to the Peppol network through their accounting software. Others use a Peppol Access Point or service provider, especially if their software doesn’t natively support it, they have more complex systems or need extra integration support. An Access Point manages the secure exchange of data between your software and the Peppol network. Access point providers have met Peppol requirements around network governance and security, either through New Zealand Peppol Authority accreditation or mutual accreditation with the ATO. The right option depends on your software, invoice volume, integration needs and internal capability.Test before going live
Don’t wait until your first live customer or supplier invoice to find out something is not working. Run test transactions first. Check that invoices can be sent, received, validated and processed correctly. Make sure invoice data lands in the right fields and that your team understands what to do if an eInvoice is rejected. Testing helps you catch simple issues early, before they affect payment timelines or supplier relationships.Update internal processes
eInvoicing may change how your team handles invoices day to day. For example, invoices may no longer arrive in a shared inbox. Approval workflows may start earlier. Data entry may reduce, but exception handling and monitoring may become more important. Document the new process clearly. Your finance team should know where eInvoices arrive, how to check their status, what errors look like and who to contact for support.Train your finance team
Even if the technology is simple, people still need to understand the change. Give your team a practical overview of what eInvoicing is, how it works in your accounting software, what is changing from the old process and how to handle common issues. Keep it simple. The goal isn’t to turn everyone into a Peppol expert. It’s to make sure they feel confident using the system.Monitor performance after go-live
Once eInvoicing is switched on, keep an eye on how it is performing. Track how many invoices are being sent or received via Peppol, how many fail validation, how long invoices take to process and how much manual work is still required. This helps you spot issues early and show the value of the project over time. Using Oracle or TechnologyOne? Check out our upcoming webinars. Oracle: Click here TechnologyOne: Click here Want to see how to get eInvoicing going with your software? Get in touch with our experts below.Request a call
Chat with one of our experts
Just fill out your details below and we'll be in touch within one business day.










