Title image Connecting to Peppol

OZEDI’s Peppol access point is available for software providers that are looking to offer e-Invoicing and other Peppol functionality.

The OZEDI solution enables access to Peppol without needing to sign up to openPEPPOL or become accredited by the Australian Taxation Office (ATO) or the Ministry of Business Innovation and Employment (MBIE) in New Zealand.

OZEDI access point test environment

OZEDI has an e-Invoicing sandbox for software providers to test their REST API and ensure they are ready to send and receive e-Invoices.

There are three steps for software providers to follow to get started using OZEDI’s access point test environment.

Step 1: Validate your UBL documents with the A-NZ Standards

To test your UBL documents are correct, OZEDI recommends the Validex tool.

Validation Tool
Step 2: Register for OZEDI’s e-Invoicing test environment

Once you’ve tested and confirmed that you’re outputting valid UBL, contact OZEDI to register for a test account. Then you are ready to start testing with OZEDI’s REST API.

• For a list of endpoints and in-depth instructions check out OZEDI’s API documentation.

Note: endpoints are only available to registered clients.

Step 3: Production and end-to-end testing

For the final stage of testing, before you can begin sending and receiving invoices in production, OZEDI will allow you to set yourself up as both an e-Invoice sender and receiver. This step means you can fully test your REST API end-to-end.

OZEDI can also set you up with one-way processing if needed.

Get started

Once you’ve tested and confirmed your e-Invoices are accepted by Peppol and our API, contact us to finalise your account set-up. OZEDI will register your brand in the production environment so you can begin sending and receiving e-Invoices.

Peppol-specific technical information

Peppol e-Documents use a specific Universal Business Language (UBL) which is a complex form of XML. Check out examples of the Australian and New Zealand standard’s (A-NZ) common Peppol Business Interoperability Specifications (BIS) documents.

There are a range of XML namespaces to note in this UBL, for example cbc and cac.

UBL code example

In this line, “urn:oasis:names:specification:ubl:schema:xsd:Invoice-2” is assigned to the cbc namespace.

Assigning to the namespaces then allows the IssueData entity at that urn to be referenced, like so:

<cbc:IssueData>

What is OASIS and a UBL Schema?

In the standard A-NZ invoice, you’ll see this line:

UBL Example code

This line means the example invoice is tested against a schema at that address.

All UBL documents sent on the Peppol network are validated by schemas created by OASIS.

OASIS is a non-profit organisation that aims to standardise technologies.

“The Organization for the Advancement of Structured Information Standards (OASIS) is a global non-profit consortium that works on the development, convergence, and adoption of open standards for security, Internet of Things, energy, content technologies, emergency management, and other areas.”

Wikipedia

OASIS created UBL, which Peppol uses for all e-Documents.

Why do software providers trust OZEDI as their Accredited Access Point?

OZEDI is a leading e-Invoicing authority in Australia and New Zealand and we are accredited by both the ATO (Australia) and the MBIE (New Zealand).

We sit on the working groups that shape the Peppol standard and are a driving force behind the design of the new international invoice standard.

Since 1981, our founders have been innovating in Australia’s accounting and payroll industry, and to this day we continue to focus on being Australasia’s leading digital delivery experts.

Our digital solutions and services are trusted by the Australian Federal Government and over 100 software providers.

Interested in learning more? Visit the e-Invoicing section for software providers on our website to start your e-Invoicing journey.

Menu