0
XRechnung/ZUGFeRD: configured SEPA direct debit (59) silently becomes payment means 68
Source: invoiceninja/invoiceninja#13347 · opened by @juergen-schadek
Invoice Ninja version v5.13.47 Environment Docker, self-hosted, unmodified official application image. Interface React; reproduced directly through the native PHP e-document service to isolate backend generation. Can you reproduce the issue on one of our demo sites? Not tested on the public demo. Reproduced locally on v5.13.47. Pre-flight checks • Reviewed the self-hosting troubleshooting documentation. • Searched existing issues for duplicates; no matching 59-to-68 report found. Have you reported this issue on Slack or the forum? No. Have you inspected the application logs? Not applicable to this reproduction: generation completes without an exception and returns the wrong payment-means code. Describe the bug A configured SEPA direct-debit payment means (code 59) is silently replaced with code 68 in generated XRechnung/CII XML. The UI/settings support selecting 59, and the configured value is retained. Changing to a ZUGFeRD profile does not solve the issue. Steps …
No pledges yet. Be the first to back this.
Comments
Similar requests
Mollie Integration (Add Sepa Direct Debit support)
3 votes · 0 comments
Interac as a payment type
1 vote · 0 comments
Make it possible to link multiple transactions to an expense
1 vote · 0 comments
Allow a merged Zugferd-Document (PDF+XML) to create an Expense
2 votes · 0 comments
Feature request: embed invoice documents as attachments in the e-invoice XML (BG-24 / AdditionalReferencedDocument)
1 vote · 0 comments
No comments yet.