The fields, the party identifiers, the exact statutory wording for each tax treatment and the HUF rule — each cited to the statute or the tax authority, not a summary of one.
The content Hungary'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 Hungary 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.
Adómentes Közösségen belüli termékértékesítés — Áfa tv. 89. §VAT exempt intra-Community supply
Területi hatályon kívüli — teljesítés helye külföld (Áfa tv. 37. §)Not taxable in Hungary
Magyar áfa nélkül — harmadik országból történő értékesítés; az import áfát az importáló fizeti (Áfa tv. 24. §)VAT not charged — supply outside the scope of Hungarian VAT; import VAT is accounted for on importation by the importer (Art. 2(1)(d), 30, 70 and 201, Directive 2006/112/EC).
Áfa tv. 169. §: kelte, sorszám, eladó adószáma, vevő adószáma (belföldi adóalanynál), nevek/címek, megnevezés/mennyiség, teljesítés napja, adóalap, egységár, engedmény, adómérték, áthárított adó forintban.
A plain PDF still counts as the invoice in Hungary; a structured e-invoice is accepted where the buyer asks for it.
Invoice by Juros-AI builds the Hungary 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