The fields, the party identifiers, the exact statutory wording for each tax treatment and the AUD rule — each cited to the statute or the tax authority, not a summary of one.
The content Australia's rules put on the face of the document, beyond the parties, line items and totals every invoice carries.
The registration numbers and their formats the Australia rules expect on the invoice.
When no tax is charged, the invoice has to say why — in the words the law names. Each is linked to the statute or tax authority it was read from.
InvoiceReverse charge — recipient to account for GST (Division 84, GST Act 1999)GST-free — export of goods (s. 38-185, GST Act 1999)GST-free supply (Division 38, GST Act 1999)Input-taxed supply (Division 40, GST Act 1999)Not connected with Australia — no GST (s. 9-25, GST Act 1999)GST not charged by the supplier — GST on the taxable importation is paid by the importer (Division 13, GST Act 1999)ATO: 'Tax invoice', seller identity, ABN, date, description incl. quantity and price, GST amount or 'Total price includes GST', extent taxable; buyer identity or ABN for A$1,000+; 'invoice' (not 'tax invoice') for an unregistered seller.
A plain PDF still counts as the invoice in Australia; a structured e-invoice is accepted where the buyer asks for it.
Invoice by Juros-AI builds the Australia e-invoice — EN 16931 UBL (Peppol BIS 3.0) — and checks it against the official schema on your own machine before anything is sent. Invoice by Juros-AI reads any invoice into clean data and is adding compliant invoice creation — the same rules on this page, built into the engine, run entirely on your own hardware. No cloud, nothing uploaded, no figure invented.
Every generated invoice is validated on your machine against the official artefacts — the OASIS UBL/CII schemas, the CEN EN 16931 schematron, Peppol BIS 3.0, KoSIT XRechnung, FatturaPA, KSeF FA(3) and the Peppol PINT packages. This page is a reference for build scoping; it is not legal or tax advice.