E-Invoicing for Clients: Peppol Setup and the BAS

E-invoicing sends structured invoice data between your client’s software and their buyer’s software through Peppol. Start with the client’s ABN and ledger settings, confirm the buyer’s requirements, then test delivery and the resulting ledger entry before changing the normal invoicing routine.

How E-Invoicing Actually Works in Australia

Australian Peppol e-invoicing exchanges invoice fields through accredited access points. Emailing a PDF remains an emailed invoice, even when the sender calls it an e-invoice.

The four-corner model has a supplier, the supplier’s access point, the buyer’s access point and the buyer. The supplier creates an invoice in their software. Their access point checks the recipient’s receiving capability and sends the standardised data to the buyer’s access point. That provider delivers it to the buyer’s software.

The Australian Taxation Office (ATO) is the Australian Peppol Authority. It sets local provider requirements and supports the Australian and New Zealand specifications. The ATO administers the framework but cannot view the invoices exchanged through it. The government’s e-invoicing explanation describes this boundary.

Consider a fictional supplier’s invoice for equipment repairs. With email, the buyer opens the attachment and types the invoice number, charges and GST into a bill. With Peppol, those fields arrive in the buyer’s software. The buyer checks them against the purchase before approval.

Removing transcription reduces errors that cause disputes and helps the buyer match the invoice to its order. It does not resolve a disagreement about whether the repairs were completed.

Switching E-Invoicing on Inside a Client’s Ledger

Check the client’s legal identity and invoice defaults before enabling e-invoicing. Match the ABN to the correct entity, distinguish its legal name from its trading name and review default GST rates. Obtain the client’s written instruction if your practice will accept provider terms or register on their behalf.

Xero Central’s help article, Register to receive eInvoices, gives this receiving setup:

1. Use an administrator or standard user account in the client’s paid Xero organisation. Confirm its ABN in organisation settings.
2. Open Purchases, select Bills and choose Set up eInvoicing, then Register to receive eInvoices.
3. Search using the ABN and check the returned business details.
4. Enter the responsible business contact, accept the terms under the client’s authority and complete registration.

The result is a registered receiving organisation. Incoming positive invoices appear as draft bills for review. A trial or demo organisation cannot complete this setup.

Sending is separate. Xero Central’s Send an eInvoice instructs users to enter the client’s registered name and ABN in organisation settings. Add the buyer’s ABN to its contact’s Tax field under Financial Details. Create the invoice, select Send as an eInvoice and confirm sending. Xero records the sent status in History and notes and the contact’s Activity tab.

The recipient must be registered to receive. Xero says the sender does not need its own receiving registration to send.

MYOB’s eInvoicing help places registration under Sales settings, in the E-invoicing tab. It supports MYOB Business and online AccountRight files accessed in a browser. After registration, Share has a Send eInvoice option. Reckon One’s eInvoicing help uses a separate eInvoicing portal, also reached through the Day to Day shortcut. An administrator connects the correct book and authorises provider access.

QuickBooks Australia describes Peppol exchange through a third-party solution connected to QuickBooks. Use that provider’s Australian setup, rather than applying another country’s QuickBooks e-invoicing menu. An ordinary QuickBooks invoice alone does not establish a Peppol connection.

Where the ledger lacks the required connection, compare an add-on, a provider portal or a replacement ledger using the ATO’s eInvoicing Ready register. Compare send and receive support separately. Include Australian PINT A-NZ compatibility, ledger permissions, client consent, GST fields, purchase-order references, attachment handling and the ability to export records when leaving. Include subscription and transaction charges qualitatively in the decision.

AI-assisted extraction reads a PDF, while AI coding suggests accounts or tax treatment. Peppol exchange carries structured data across the network. Check the GST and customer fields whichever method produces them. An AI invoicing label does not establish Peppol compatibility.

For a supply-chain buyer, obtain its ABN, order-number format, reference requirements and supplier onboarding instructions. Send a representative invoice and have the buyer confirm the correct invoice reached its accounts-payable team. Agree on one delivery channel. If an email copy is required, mark it as a copy of the same invoice and prevent a second bill being entered.

Registering the Client’s ABN on the Peppol Network

The ledger’s provider or a separate access point registers the client’s receiving address with their consent. Your practice can complete the steps under the client’s written authority. Registration is a receiving arrangement, not a tax registration or an ATO agent appointment.

An Australian participant commonly uses its ABN as its network identifier. Keep one receiving registration for that identifier and coordinate any provider change. A second ledger does not mean the same ABN can receive the same invoice independently through two registrations.

If registration reports that the ABN is already in use, identify the old provider from the client’s records and arrange deregistration or migration. Keep access to old invoices and resolve transactions in transit before the change. Do not enter a different entity’s ABN to get past the error.

The ATO’s Peppol guidance identifies the public Peppol Directory as a receiving-capability lookup. Search for the legal entity and match its ABN, rather than relying on a similar trading name. Confirm the result with the provider’s registration status and a received test invoice. A directory result describes receiving capability. It does not prove that an invoice has been posted or paid.

What the Business to Government Mandate Requires

Non-corporate Commonwealth entities must be able to receive Peppol e-invoices. For your supplier client, confirm the agency’s receiving ABN and invoicing instructions before the first exchange. The receiving requirement does not itself impose a universal private-business obligation to send every invoice through Peppol.

The Department of Finance’s payment-policy guidance separates the existing rules from announced replacement terms. Under the existing policy, eligible Peppol invoices have maximum payment terms of five calendar days. Both parties must be capable of exchanging them and must agree to use that method.

The payment period starts on the next calendar day after satisfactory delivery is acknowledged and a correctly rendered invoice is received. Disputed amounts and listed policy exceptions are outside that payment obligation. If the final day is a non-business day, payment is due on the next business day. The current policy has no general $1 million contract-value ceiling.

Finance has announced replacement maximum terms of 10 business days for all invoice forms. Apply them only once the new policy commences. Use Finance’s transition and commencement details to identify which rules cover the contract and invoice. The agency’s acceptance of Peppol and the applicable payment terms are separate questions.

What Changes on the BAS and in the GST Records

E-invoicing changes how invoices arrive, not the client’s GST treatment or the basis used to prepare the business activity statement (BAS). A valid network exchange still needs a valid tax invoice and correct accounting treatment.

Under the ATO’s tax invoice requirements, check the supplier’s identity and ABN, issue date, description, quantity where applicable and price. The invoice must identify taxable supplies and the GST payable. For total prices of at least $1,000, it must also identify the recipient or their ABN.

The structured fields must carry this information. The ATO accepts qualifying Peppol invoices as intended tax invoices even without the literal Tax Invoice label. The ATO’s tax invoice guidance explains the requirements.

Before approving an incoming bill, compare the supplier and buyer details with the correct client entity. Confirm the purchase, account code, GST treatment and amount. Xero applies supplier purchase defaults to incoming e-invoices, so a wrong default can repeat across later bills. A network-valid bill can still be a private expense, relate to the wrong entity or have an incorrect GST treatment.

For an outgoing Xero invoice, check the legal name, ABN, invoice numbering and customer details. Review the line-level GST coding and confirm one receivable exists. The ordinary invoice records the sale. Sending it through Peppol adds a delivery action and status to that invoice. Avoid creating another sale simply to resend it.

Recording payment is a separate action. Match the bank receipt or remittance to the receivable, account for payment-provider fees and investigate short payments. Refer changed bank details to the client’s person responsible for verifying payment instructions through an independently established contact. Use the payment-redirection checks for that separate task.

Keep the invoice data and a readable rendering available throughout the required record-retention period. Most business tax records must be kept for five years, with longer periods applying in some circumstances. Preserve the complete invoice and supporting records when changing providers. An inaccessible portal history is not a usable record. The ATO’s record-keeping rules explain the general requirements.

For the first BAS period, use an exception list or compliance dashboard to check:

• Rejected exchanges against their corrected invoice and delivery result.
• Received documents against bills actually created in the ledger.
• Invoice numbers and amounts across email copies and Peppol records for duplicates.
• Credit notes against the original bill or sale.
• Supplier defaults and GST totals against the source documents.
• Receipts, fees and outstanding balances against the receivables ledger.

Assign each exception an owner and resolve it before closing the period. Add this reconciliation to the client’s BAS preparation checklist.

Standards and Compliance a Practice Should Check

Australia and New Zealand use PINT A-NZ Billing for Peppol invoice exchange. The ATO’s technical e-invoicing guidance points to the shared rules. OpenPeppol publishes the PINT A-NZ Billing specification, including invoice syntax and validation rules.

When a client says they already e-invoice, ask them to show a sent network transaction and a received document. Confirm the provider’s Australian accreditation through the Peppol service-provider register. Check the entity identifier, supported document types and receiving registration. Compare a representative invoice’s mandatory fields with the buyer’s purchasing requirements and the GST records.

Peppol reduces exposure to invoice interception through email. Providers identify network participants and exchange data through accredited access points. That does not establish that every charge is authorised or every bank-detail change is legitimate. Staff must still check supplier authority and purchases. A compromised ledger account or dishonest participant can create an invoice that needs investigation.

Taking on a Client Who is Already on the Network

Record the client’s network arrangement during handover so the next bookkeeper can trace each invoice. Ask for the access point and connected ledger, registered ABN, registration confirmation and the person authorised to change it. Record invoice volumes, major buyers, required references and whether the client sends, receives or does both.

Keep the network details in the client’s practice record alongside the ledger access and invoice procedure. Record where structured invoices can be exported, who reviews rejected exchanges and how staff detect emailed duplicates. If the client uses Xero, carry the responsible staff member and organisation details into the practice’s Xero client setup. Place the connection among the client-facing tools in your accounting software stack record.

When the client changes provider, agree on the last invoice handled by the old connection and the first handled by the new one. Export the old records, finish outstanding exceptions and coordinate the receiving-registration transfer. Test an outgoing invoice and an incoming bill where both directions are used. Confirm delivery status and exactly one corresponding ledger entry before telling trading partners to use the new connection.