-
-
Notifications
You must be signed in to change notification settings - Fork 147
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
X-Rechnung direct-debit missing mandatory field BT-90 #370
Comments
If your issue is a question if a mustang generated file is valid(?) please include either the complete source code and/or the complete output so that I can have a look and run it through a validator. |
No, it's not a question, just a notice. I have researched the issue before I opened the ticket. I tested it with KOSIT Version 3.0.1_2023-09-22 and Mustang-Validator 2.10.0. <ram:CreditorReferenceID>[Bank assigned creditor identifier]</ram:CreditorReferenceID> I thought about implementing it myself and submitting a pull request, but your current code structure is not suitable for that without major changes. So I fixed it locally for myself for now by post-processing the XML-string and injecting the missing line. |
Last week I had the same issue with a "xRechnung" with a missing "CreditorReferenceID" (BT-90). |
Even if it is just a notice, could someone please include either the complete source code and/or the complete output so that I can have a look and run it through a validator? |
You can generate any random X-Rechnung with payment type direct debit. Example for Invalid X-Rechnung generated with mustang: Validator error: This is how it should look like: |
Thanks for the PR I assume this is solved now in master head? |
For X-Rechnung with payment method direct debit, the now mandatory field
BT-90
CreditorReferenceID
is missing.The current Validator rejects files without that field.
This is how it should look like:
The problem is, that the field must be inside the
ApplicableHeaderTradeSettlement
-block, not inside the direct-debit-specificSpecifiedTradeSettlementPaymentMeans
-block.So just adding the field into
IZUGFeRDTradeSettlementDebit
won't suffice as it is needed in the higher level xml-block.As a consequence, including the field might require rearranging the code that creates the
ApplicableHeaderTradeSettlement
-block.Is anyone already working on it?
The text was updated successfully, but these errors were encountered: