Repository navigation
Conversation
Neither format passed the official KoSIT validator (XRechnung 3.0.2 configuration): 0 of 20 generated test documents were accepted. XRechnung (UBL): - use the KoSIT CustomizationID (urn:...#compliant#urn:xeinkauf.de:kosit:xrechnung_3.0) - emit Party and PostalAddress elements in UBL schema order - add the fields XRechnung requires: BuyerReference, seller and buyer EndpointID, seller contact (name, phone, email), PaymentMeans (BR-DE-1) - omit the header DueDate on credit notes ZUGFeRD (CII): - emit TradeParty, TradeAddress, TradeTax and header settlement elements in CII schema order - seller electronic address as URIUniversalCommunication instead of a SEID tax registration; add contact, BuyerReference, due date, payment means Both, via a shared xml/en16931.ts: - map the reduced-rate code AA (not in EN 16931) to S; always emit the rate for Z/E/AE; exempt (E) with reason for Kleinunternehmer - tax number as scheme FC instead of DE-TAX; drop the buyer tax number, which EN 16931 has no field for - one allowance per VAT category for the document discount (BR-32) - emit negatively stored credit notes with positive amounts (BR-27) - payee account from the structured IBAN/BIC settings, falling back to a checksum-valid IBAN in the bank details text Settings: add company_contact_name (contact person / Ansprechpartner), used as the e-invoice seller contact and falling back to the company name. Validator: report missing seller VAT ID (BR-CO-26), XRechnung phone/email/ buyer address, a missing IBAN, and VAT that does not match the taxable amount. The latter flags invoices with a document discount, because calculateInvoiceTotals computes VAT before the discount (separate fix). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Neither format passed the official KoSIT validator (XRechnung 3.0.2 configuration): 0 of 20 generated test documents were accepted.
XRechnung (UBL):
ZUGFeRD (CII):
Both, via a shared xml/en16931.ts:
Settings: add company_contact_name (contact person / Ansprechpartner), used as the e-invoice seller contact and falling back to the company name.
Validator: report missing seller VAT ID (BR-CO-26), XRechnung phone/email/ buyer address, a missing IBAN, and VAT that does not match the taxable amount. The latter flags invoices with a document discount, because calculateInvoiceTotals computes VAT before the discount (separate fix).