Australian GST, BAS and Peppol readiness for Odoo 19

Open the entity, obligation and reviewer registers

Create one register for legal entities and branches, another for ABN and GST-registration evidence, and a third for the people who prepare, review and lodge each obligation. A branch label is not a substitute for the legal entity, and an Odoo company name is not proof of registration or reporting cycle. Record the source document, effective date, owner and next revalidation date for every row.

The BAS agent and reviewer register identifies who prepares workings, who approves GST treatment, who lodges and who pays. Keep those actions separate even if one person holds several roles. The client's issued statement, instalment notice and adviser instructions take precedence over a generic project calendar.

Replace every synthetic example with your own evidence, assign an owner, record the evidence and result, and mark each item Passed, Blocked or Not applicable.

• Legal entity and branch: Example Coastal Distribution Pty Ltd, Newcastle branch. Owner: entity finance owner. Evidence: ASIC and entity records checked. Result: Blocked pending client evidence.
• ABN and GST status: synthetic training entity, not a real registration. Owner: Australian tax reviewer. Evidence: registration evidence and effective date recorded. Result: Blocked pending client evidence.
• BAS preparation and review: client preparer and independent accountant reviewer. Owner: BAS owner. Evidence: preparation, review and lodgement responsibilities recorded. Result: Blocked pending client evidence.
• Source revalidation: before each reporting-cycle change. Owner: content owner. Evidence: dated source and decision log. Result: Blocked pending client evidence.

Reviewed 6 November 2026. General implementation guidance only; it is not tax, payroll, employment or legal advice. Confirm your obligations with a qualified Australian specialist.

Classify transaction samples before configuring taxes

GST is 10% on taxable supplies, not every transaction. Use the ATO's overview of how GST works with its separate guidance on taxable sales, GST-free sales and input-taxed sales. Eligible purchases used to make GST-free sales may qualify for GST credits; purchases used to make input-taxed sales generally do not qualify. The credit decision belongs to the purchase and its use, not to the sale label alone.

Out-of-scope or not-reportable treatment is not a synonym for GST-free or input-taxed. Use the ATO's simpler BAS bookkeeping guide when constructing examples. No automatic classification is accepted from a product, customer, legacy tax code or item name.

• Standard consulting service: review whether it is a taxable supply. Related eligible purchases require their own credit assessment. Owner: tax reviewer. Evidence: tax invoice and classification rationale. Result: Blocked pending client evidence.
• GST-free training example: review the GST-free classification rather than treating it as zero by convention. Eligible purchases used to make GST-free sales may qualify for GST credits. Owner: tax reviewer. Evidence: supply and purchase decisions. Result: Blocked pending client evidence.
• Residential rent example: review potential input-taxed treatment. Purchases used to make input-taxed sales generally do not qualify for GST credits. Owner: tax reviewer. Evidence: use and supply evidence. Result: Blocked pending client evidence.
• Non-business adjustment example: review potential out-of-scope or not-reportable treatment separately from GST-free and input-taxed labels. Owner: accountant. Evidence: source document and separate decision. Result: Blocked pending client evidence.
• Customer credit note: examine the original supply and adjustment. Owner: receivables owner and tax reviewer. Evidence: original invoice, credit note and approved treatment. Result: Blocked pending client evidence.

For each sample, capture sale or purchase, supply or refund, entity, date, amount, evidence, treatment, GST amount, credit treatment, invoice documentation, Odoo tax mapping and named approver. Acceptance compares the source expectation with the transaction, journal and BAS workings rather than checking only the displayed tax rate.

Test GST credits and the A$82.50 document threshold

The ATO's A$82.50 including GST tax-invoice threshold is a documentation threshold in context, not automatic entitlement to a GST credit. Review when a GST credit can be claimed alongside the purchase, business use, supplier evidence and other eligibility conditions. Do not turn the threshold into a pricing line or a rule that every credit is allowed.

Use synthetic amounts solely to test documentation behaviour, not to determine a client's legal position. Include a purchase below the threshold with supporting evidence, one above it with a complete tax invoice, one above it with a missing document and a later corrected invoice. Record who requests the correction and when the credit enters the reviewed workings.

• Document threshold: purchase below A$82.50 including GST. Owner: Australian tax reviewer. Expected control: eligibility and available evidence are still reviewed. Evidence: source document and reviewer decision. Result: Blocked pending client evidence.
• Tax invoice required: purchase above the threshold. Owner: Australian tax reviewer. Expected control: complete documentation where applicable. Evidence: invoice fields checked. Result: Blocked pending client evidence.
• Missing invoice: supplier document withheld. Owner: payables owner. Expected control: credit held in an exception queue. Evidence: follow-up owner and status. Result: Blocked pending client evidence.
• Corrected invoice: supplier reissues the document. Owner: payables owner and tax reviewer. Expected control: original and correction linked without duplication. Evidence: correction reference and updated review. Result: Blocked pending client evidence.

The acceptance pack retains the raw document, eligibility decision, Odoo tax and account mapping, BAS effect and approval. A tax-invoice checkbox or a document attachment icon is not sufficient evidence of the underlying decision.

Separate imports, reverse charge and deferred GST

Imported goods and offshore purchases require transaction-specific assessment. Read the ATO guidance on GST and imported goods and reverse charge on offshore purchases. Conditions, entity status, intended use and supporting records matter; there is no universal import rule.

Reverse charge is conditional and is not deferred GST. Deferred GST concerns a separate process and balance. Reviewed Odoo 19 Australian documentation describes a manual deferred-GST process, so the runbook includes a manual deferred-GST review, supporting entry, balance reconciliation and named accountant approval. Neither treatment is automated into a universal rule.

• Imported stock: review customs, import and credit evidence. Owner: tax reviewer and inventory owner. Evidence: supplier, import and stock records reconciled. Result: Blocked pending client evidence.
• Offshore service: assess the reverse-charge conditions. Owner: Australian tax reviewer. Evidence: conditional tax mapping and report effect checked. Result: Blocked pending client evidence.
• Deferred-GST balance: confirm the separate eligibility and process. Owner: accountant and finance controller. Evidence: manual entry and balance reconciliation retained. Result: Blocked pending client evidence.
• Supplier correction: link the original treatment and correction. Owner: payables owner and tax reviewer. Evidence: no duplicate GST or inventory effect. Result: Blocked pending client evidence.

Acceptance fails if a project template selects reverse charge or deferred GST without evidence for the transaction. It also fails if the deferred-GST balance has no manual owner or cannot be tied to the supporting records.

Build the BAS calendar from the issued statement

Monthly BAS is generally due on the 21st of the following month. Standard quarterly due dates are generally 28 October, 28 February, 28 April and 28 July. Annual eligibility and the applicable 31 October or 28 February date require confirmation. Use the ATO's BAS due-date guidance and GST and PAYG instalment-notice guidance as primary references.

The issued statement, actual GST and PAYG cycle, instalment notice and any tax-agent concession prevail. A generic quarterly reminder must not override a monthly obligation or an agent-specific arrangement. PAYG withholding, PAYG instalments, BAS and Single Touch Payroll (STP) also remain different calendars and controls.

• Reporting cycle: client-confirmed monthly or quarterly example. Owner: BAS reviewer. Evidence: issued statement or instalment notice. Result: Blocked pending client evidence.
• Due date: date copied from the actual notice. Owner: client agent or accountant. Evidence: notice plus applicable concession evidence. Result: Blocked pending client evidence.
• Preparation cut-off: internal working date before the obligation. Owner: finance preparer. Evidence: completed transaction and reconciliation checklist. Result: Blocked pending client evidence.
• Lodgement and payment: separate external actions. Owner: authorised client roles. Evidence: lodgement receipt and bank evidence where applicable. Result: Blocked pending client evidence.

The project runbook records who closes the period, resolves exceptions, reviews the report, lodges through the client's chosen channel and confirms payment. Calendar entry creation is not lodgement evidence.

Reconcile Odoo GST grids, BAS and TPAR without auto-filing

Review the Odoo 19 Australian localisation and retain the relevant documentation change record with the build-evidence pack. Configure taxes, accounts, grids and report mappings using approved samples. The outputs remain reviewable workings, and the reviewed documentation provides no direct BAS lodgement to the ATO.

Reconciliation ties source transactions to journals, tax grids, BAS values and the trial balance. TPAR receives its own supplier, payment and reporting review where applicable; it is not assumed to follow the same transaction population as BAS. Deferred-GST balances are manually reconciled and not buried in a generic suspense account.

• Taxable sale and GST: approved source and line calculation. Owner: finance preparer. Evidence: invoice, journal and grid references. Result: Blocked pending client evidence.
• GST-free and input-taxed samples: different supply treatments and purchase-credit consequences. Owner: Australian tax reviewer. Evidence: report placement and purchase-credit decision. Result: Blocked pending client evidence.
• BAS working total: sum of approved grid lines. Owner: accountant. Evidence: report output and reconciliation residual. Result: Blocked pending client evidence.
• TPAR population: independently approved supplier payments. Owner: TPAR reviewer. Evidence: included and excluded row listing. Result: Blocked pending client evidence.
• Deferred-GST balance: manual schedule agrees to supporting records. Owner: finance controller. Evidence: entry, balance and approval. Result: Blocked pending client evidence.

No direct BAS lodgement is claimed. The accountant-approved sample pack includes routine and exception rows, corrections, report version, residuals and sign-off before the client's authorised lodgement process begins.

Apply five-year and seven-year record rules by record class

Most ATO business records are retained for five years, with exceptions. Fair Work time-and-wages records require seven years. ASIC financial records require at least seven years. Use the primary guidance from the ATO, Fair Work and ASIC, then assign the obligation and any exception by record class rather than imposing one database-wide period.

Retention covers more than database rows. Tax invoices, source exports, reconciliation packs, employee records, company records, attachments, provider messages, access logs and approvals may have different owners and locations. Legal holds, contract requirements and other obligations can extend the period; the matrix does not reduce them.

• ATO business records: most are retained for five years, with exceptions. Owner: finance record owner. Evidence: record class, exception assessment, retention start, location and access. Result: Blocked pending client evidence.
• Fair Work time-and-wages records: seven years. Owner: payroll record owner. Evidence: access, correction and audit ownership. Result: Blocked pending client evidence.
• ASIC financial records: at least seven years. Owner: company-records owner. Evidence: record location and retrieval owner. Result: Blocked pending client evidence.
• Migration evidence: assign the period by the records it contains and any applicable exception, never one database-wide period. Owner: data and finance owners. Evidence: read-only source, mapping, approval archive and retrieval test. Result: Blocked pending client evidence.

A successful retention test retrieves a sampled record with its context and approvals, confirms permitted access and proves that an export or archive has not orphaned the attachment needed to understand it.

Treat Peppol as a provider and buyer-acceptance workstream

Australian B2B eInvoicing is voluntary; there is no universal B2B mandate. The ATO's eInvoicing overview and business guidance explain that both parties need connectivity and that the ATO does not receive or inspect invoice content. Delivery does not mean buyer approval, payment, ATO clearance or legal compliance.

Commonwealth Non-corporate Commonwealth Entity receiving requirements are separate. The government eInvoicing guidance states a target of eInvoicing reaching 30% of all invoices received by Australian Government entities by 1 July 2026, with those entities working with suppliers to achieve it. The 18 June 2026 stewardship message discusses December 2026 objectives in the same government-entity context. These targets do not create a general business mandate.

PINT A-NZ Billing Process 1.1.3 is Final with release date 8 June 2026. Consult the direct release notes and Australian Peppol profile, but do not infer deployed Odoo 19 validation from publication. Specification applicability, XML schema, provider, endpoint, transport and buyer acceptance are separate tests.

Rehearse routine and exception evidence

• Endpoint master: synthetic buyer endpoint and identifier scheme. Owner: customer master owner. Evidence: approved endpoint and effective date. Result: Blocked pending client evidence.
• Both-party connectivity: sender and receiver capabilities checked. Owner: provider owners. Evidence: connectivity evidence for both parties. Result: Blocked pending client evidence.
• XML and schema: PINT applicability assessed for the selected flow. Owner: build and provider testers. Evidence: XML file and validation result. Result: Blocked pending client evidence.
• Transmission and exceptions: send, reject, retry and duplicate scenarios. Owner: access-point provider. Evidence: message IDs, status and exception queue. Result: Blocked pending client evidence.
• Buyer business acceptance: delivered invoice reviewed by a synthetic buyer. Owner: buyer and client process owners. Evidence: receipt, approval and rejection evidence kept distinct. Result: Blocked pending client evidence.

Prove the Odoo 19 and provider boundary, then run exceptions

Reviewed Odoo 19 electronic-invoicing documentation and its change record exclude Australia from Odoo-operated Peppol registration-eligible countries and describe ANZ access-point work as in progress. The Australian localisation supports Peppol XML download for a separate provider. XML download does not prove provider connectivity, transport, buyer acceptance or current PINT validation.

Check the exact provider against the ATO Peppol service-provider register and OpenPeppol provider register. Provider register presence is not a recommendation. Odoo was not found on the reviewed Australian register, and Odoo SA's Belgian BOSA listing is not Australian accreditation. Recheck this point when selecting a provider rather than treating it as a permanent absence claim.

• GST-free sale: confirm that eligible purchases used to make the sale may qualify for GST credits. Owner: Australian tax reviewer. Stop condition: unexplained grid or purchase-credit result. Result: Blocked pending client evidence.
• Input-taxed sale: confirm that purchases used to make the sale generally do not qualify. Owner: Australian tax reviewer. Stop condition: incorrect purchase-credit treatment. Result: Blocked pending client evidence.
• Out-of-scope or not-reportable transaction: review it separately from GST-free and input-taxed labels. Owner: accountant. Stop condition: automatic classification detected. Result: Blocked pending client evidence.
• Missing invoice or offshore purchase: retain the exception and conditional assessment. Owner: payables and tax owners. Stop condition: credit or reverse charge assumed. Result: Blocked pending client evidence.
• Endpoint rejection or provider outage: make message, retry and duplicate controls visible. Owner: provider and integration owners. Stop condition: unclear delivery or duplicate risk. Result: Blocked pending client evidence.
• Credit note and duplicate submission: retain the original link and idempotency evidence. Owner: receivables and provider owners. Stop condition: duplicate document or unowned exception. Result: Blocked pending client evidence.

Odoo 20 material is separately labelled roadmap education and never supplies evidence for an Odoo 19 requirement. Complete provider-specific tests before relying on the workflow. Continue with the AUD migration guide, POS recovery checklist and payroll readiness guide for their related evidence packs.