edmundgray
commented
8 months ago The EN provides little advice on the Invoice Type Code
Open svanteschubert opened 9 months ago
edmundgray
commented
8 months ago The EN provides little advice on the Invoice Type Code
Background
According to the current XInvoice specification (1.2.2 or 2.0. 0) the following TypeCodes are supported:
BR-DE-17 "With the element "invoice type code" (BT-3) the following codes from the code list UNTDID 1001 shall be used:
NOTE: EU Digital Grow is taking care of the code lists and adds them to the issue tracker every half year. For instance, at the moment this issue is referencing to the current code lists!
Challenges
How do the TypeCodes differ from each other, especially with regard to further processing (scenarios, prerequisites, dependencies, effects in the invoice receipt, further processing processes, ...)?
Should the invoice processing processes be controlled via the TypeCode in the future? Do we want to push this? Are there recommendations / reference processes for this?
Would it be sufficient / professional to map all "invoices" ("normal" invoices, partial invoices, commercial credit notes and corrected invoices) via TypeCode 380 (commercial invoice)?
Scenario "invoice cancellation / invoice correction with negative invoice amount":
Do invoices with a negative invoice amount have to / should be mapped via TypeCode 381 (commercial credit note)?
What are the effects if an invoice with a negative invoice amount is mapped via TypeCode 384 (Corrected invoice), or via TypeCode 380 (Commercial invoice), i.e. how would this be interpreted in the invoice receipt?
Scenario "Partial invoice / Final invoice":
In which scenarios would TypeCode 384, compared to 381, be used?
Do partial invoices require a final invoice? How is it made clear to which partial invoices a final invoice refers (in the current ZUGFeRD version 2.1.1 there is still the problem that, in contrast to the standard and the XInvoice, only one preceding invoice can be referenced)
Are there also reference processes or recommendations for this?
Open Questions
Take into account specifications of the TypeCodes, e.g. at European level.
Standard level, CIUS-X invoice: Short list, as restrictions have been made
Approaches
Distinction between claim/obligation
Construction invoice: TypeCode defined according to VOB and to be used accordingly
Include scenario 8
Develop guideline "Which TypeCode is defined how" Appointment via Doodle
First meeting has taken place, current status was presented to all participants (separate Excel sheet)