OptionalcompareHow invoice numbers are ordered when a number range is given.
The default compares digit runs numerically, so 2024/9 sorts before
2024/10. Plain text ordering puts them the other way round and would
silently drop invoices from the middle of a requested range — which is
the kind of mistake an audit is precisely designed to find.
OptionalinvoiceFirst invoice number to include, inclusive.
OptionalinvoiceLast invoice number to include, inclusive.
OptionalissueFirst issue date to include, inclusive, as yyyy-mm-dd.
OptionalissueLast issue date to include, inclusive.
OptionalnowInjectable clock, so an export is reproducible in tests.
The data export an invoicing program must be able to produce.
Decree 23/2014. (VI. 30.) NGM requires every invoicing program to have a built-in "adóhatósági ellenőrzési adatszolgáltatás" function that exports the invoices issued in a given date range, or in a given invoice number range, as XML.
Two structures are permitted. Annexes 2 and 3 of the decree define one (
szamla.xsd); section 13/A(1) permits the other — the structure published for the online invoice data service, which isinvoiceData.xsd. This implementation produces the second, because it is the same schema this project already generates, validates and round-trips against NAV's own sample documents.That choice belongs to the taxpayer, not to this library. If your auditor asks for the Annex 3 structure specifically, this export is not it.