eInvoicing / PEPPOL
PostMaster Connect platform enabling PEPPOL-compliant electronic invoice exchange between software systems — AR eInvoices sent securely from GP directly into customers' accounting software, and AP eInvoices received from suppliers via the PEPPOL network into Docuphase.
System Details
PostMaster ConnectWhat is eInvoicing?
vs Email / PDFeInvoicing is the electronic exchange of invoice information directly between software systems. Aidacare uses PostMaster Connect to send structured XML invoices (not PDFs) through the PEPPOL network, which routes them to the customer's own Access Point and into their finance system automatically.
eInvoicing / PEPPOL Flow Diagram
Source Document
eInvoicing / PEPPOL flow diagram — from source document
AR Flow — Outbound eInvoices to Customers
GP → PEPPOL → Customer Finance SystemA polling mechanism picks up posted invoices in GP and pushes them to the client's PEPPOL access point. PostMaster Connect converts the GP invoice into a structured PEPPOL XML eInvoice and delivers it through the PEPPOL network to the customer's Access Point, from where it flows directly into their finance system.
Access Point Routing — Key Concept
Peppol ID = ABN (AU)The invoice is addressed to the customer using their Peppol ID — in Australia, this is commonly based on their ABN. Aidacare's Access Point then uses PEPPOL lookup services to route the invoice correctly.
- Is the customer registered for PEPPOL?
- What document types can they receive?
- Which Access Point should receive the invoice?
- What address, certificate, and security details are required?
The Service Metadata Locator (SML) helps Access Points discover trading partner addressing details — similar to how the internet finds websites from domain names. This is the core infrastructure that makes PEPPOL routing work.
Invoices are sent as structured XML eInvoices — not PDFs. This allows the customer's finance system to ingest the invoice data directly without any manual re-keying.
Peppol PINT A-NZ Billing — defines invoice and credit note transactions and localises the tax context for Australian GST requirements.
AR eInvoicing — Integration Diagram
LLD ReferenceAR eInvoicing integration — from MS-GP Integration Low Level Design
AP Flow — Inbound eInvoices from Suppliers
Supplier → PEPPOL → DocuphasePostMaster Connect listens on Aidacare's PEPPOL access point for inbound supplier eInvoices. On receipt, it validates the invoice data against GP vendor records and forwards valid invoices to Docuphase for AP approval workflow. Invoices that fail validation are placed in an error/exception queue.
What PostMaster Connect Validates (AP)
Exception Queue on FailureSupplier is matched against GP vendor records. Unrecognised vendors trigger the exception queue.
Supplier ABN on the eInvoice is validated against the GP vendor's registered ABN.
Purchase order number on the eInvoice is cross-checked against GP purchase orders.
Duplicate invoice number detection — prevents double-processing of the same supplier invoice.
Tax codes and GST amounts are validated. Mismatched or missing tax data routes the invoice to the exception queue.
If any validation fails (vendor, PO, or tax code does not match) the invoice is placed in an error/exception queue for manual review.
AP eInvoicing — Integration Diagram
LLD ReferenceAP eInvoicing integration — from MS-GP Integration Low Level Design
GP Data → eInvoice Field Mapping
8 field mappings| # | GP Field / Source | eInvoice Field (PEPPOL) | Notes |
|---|---|---|---|
| 1 | Customer Number | Buyer Party | GP Customer ID maps to the PEPPOL Buyer Party identifier |
| 2 | Customer ABN / Peppol ID | Buyer Electronic Address | Used for PEPPOL network routing to customer's Access Point. In Australia, the ABN is the basis of the Peppol ID. |
| 3 | Invoice Number | Invoice ID | GP document number maps to PEPPOL Invoice ID |
| 4 | Invoice Date | Issue Date | GP invoice date maps to PEPPOL Issue Date |
| 5 | Item Lines | Invoice Lines | GP SOP/AR invoice line items map to PEPPOL Invoice Line elements |
| 6 | GST | Tax Total | Australian GST maps to PEPPOL Tax Total in PINT A-NZ Billing context |
| 7 | Total Amount | Payable Amount | GP document total maps to PEPPOL Payable Amount (LegalMonetaryTotal) |
| 8 | PO Number | Order Reference | Customer purchase order number maps to PEPPOL Order Reference |
What is PEPPOL?
Pan-European Public Procurement On-LinePEPPOL (Pan-European Public Procurement On-Line) is an international standards framework and network infrastructure for electronic document exchange between businesses and governments. It is governed by OpenPeppol, a non-profit international association.
The Australian Taxation Office operates the Australian/NZ PEPPOL access point authority. All AU businesses registered for eInvoicing are listed on this network, discoverable by their ABN-based Peppol ID.
The global OpenPeppol network (peppol.eu) interconnects trading partners across Europe, Asia-Pacific, and other regions. PostMaster Connect supports both AU/NZ and International PEPPOL.
Access Point Routing — How PEPPOL Finds Your Customer
SML / SMP LookupWhen Aidacare's Access Point needs to deliver an eInvoice to a customer, it performs a PEPPOL lookup using the customer's Peppol ID. The lookup resolves four things:
OpenPeppol's Addressing and Capability Lookup is built on the Service Metadata Locator (SML). It works similarly to how the internet's DNS finds websites from domain names — except instead of resolving hostnames to IP addresses, it resolves Peppol IDs to Access Point endpoints. This is the core infrastructure that makes decentralised PEPPOL routing work at scale.
Customer Peppol ID & AU/NZ Billing Standard
Customer Peppol ID Discovery (Australia)
In Australia, a customer's Peppol ID is commonly derived from their Australian Business Number (ABN). The format used on the ATO PEPPOL network is:
If a customer is not registered for PEPPOL, Aidacare cannot deliver an eInvoice via PEPPOL to them — an alternative method (email PDF) is required for those customers.
Peppol PINT A-NZ Billing
The Australian and New Zealand standard for PEPPOL invoicing is Peppol PINT A-NZ Billing. It:
- Defines invoice and credit note transaction structures
- Localises the tax context for GST (Goods and Services Tax)
- Is the mandated standard for Australian government eInvoicing
- Ensures compliance with ATO eInvoicing framework
eInvoicing / PEPPOL flow diagram — from source document
Integration with GP (Microsoft Dynamics GP)
Polling (AR) + Listening (AP)For outbound AR eInvoicing, PostMaster Connect uses a polling mechanism that periodically scans GP for newly posted AR invoices. When a posted invoice is found, it is picked up and pushed to the customer's PEPPOL access point. This is an automated background process running on AIDAPOS01V.
For inbound AP eInvoicing, PostMaster Connect listens on Aidacare's PEPPOL access point for incoming eInvoices from suppliers. When a new invoice arrives, it is automatically received, validated, and forwarded to Docuphase. This is an always-on listener process running on AIDAPOS01V.
Integration with Docuphase (AP Approval Workflow)
AP Exception HandlingFor inbound supplier eInvoices (AP flow), PostMaster Connect forwards validated invoices to Docuphase, which is Aidacare's AP approval and document management system. Docuphase handles the approval routing, coding, and ultimately the posting of the invoice to GP AP.
Invoice is forwarded to Docuphase for normal AP approval workflow — coding, approval routing, and GP posting.
If vendor, PO number, or tax code does not match, the invoice is placed in the error/exception queue for manual review and intervention.