The fields, the party identifiers, the exact statutory wording for each tax treatment and the NOK rule — each cited to the statute or the tax authority, not a summary of one.
The content Norway'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 Norway 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.
Omvendt avgiftsplikt — merverdiavgiftsloven § 11-1 (kjøper beregner avgiften)Reverse charge
Fritatt for merverdiavgift (0 %) — merverdiavgiftsloven kap. 6VAT exempt (zero rate)
Uten norsk merverdiavgift — levering fra utlandet; innførselsmerverdiavgift beregnes av importøren (merverdiavgiftsloven § 3-29, § 11-1)VAT not charged — supply from abroad; import VAT is accounted for by the importer (Norwegian VAT Act § 3-29).
Bokføringsforskriften § 5-1-1: nummer og dato, partene (org.nr + MVA, Foretaksregisteret), ytelsens art og omfang, leveringstidspunkt og -sted, vederlag, betalingsforfall, merverdiavgift i NOK spesifisert per sats.
A plain PDF still counts as the invoice in Norway; a structured e-invoice is accepted where the buyer asks for it.
Invoice by Juros-AI builds the Norway 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.
Invoice