Validation fails when BT-41 "PersonName" and BT-41-0 "DepartmentName" are both provided; same with BT-56 and BT-56-0

We are in the process of implementing e-invoices in our software. I've started about a year ago with creating some test e-invoices, but then more important tasks came up and I'm now picking up the work again. Last year, all the generated test e-invoices validated without errors. Now valitool version 3.25.19 still validates them as valid, but Mustang version 2.22.0 reports following errors: > Error [CII-SR-465]-Only one BT-41 element is allowed on an invoice. [ID FX-SCH-A-000350] from /xslt/ZF_240/FACTUR-X_EXTENDED.xslt) /\*:CrossIndustryInvoice[namespace-uri()='urn:un:unece:uncefact:data:standard:CrossIndustryInvoice:100'][1]/\*:SupplyChainTradeTransaction[namespace-uri()='urn:un:unece:uncefact:data:standard:CrossIndustryInvoice:100'][1]/\*:ApplicableHeaderTradeAgreement[namespace-uri()='urn:un:unece:uncefact:data:standard:ReusableAggregateBusinessInformationEntity:100'][1] > Error [CII-SR-466]-Only one BT-56 element is allowed on an invoice. [ID FX-SCH-A-000351] from /xslt/ZF_240/FACTUR-X_EXTENDED.xslt) /\*:CrossIndustryInvoice[namespace-uri()='urn:un:unece:uncefact:data:standard:CrossIndustryInvoice:100'][1]/\*:SupplyChainTradeTransaction[namespace-uri()='urn:un:unece:uncefact:data:standard:CrossIndustryInvoice:100'][1]/\*:ApplicableHeaderTradeAgreement[namespace-uri()='urn:un:unece:uncefact:data:standard:ReusableAggregateBusinessInformationEntity:100'][1] Is it really an error, when BT-41 "PersonName" and BT-41-0 "DepartmentName" are both provided? Or when BT-56 "PersonName" and BT-56-0 "DepartmentName" are both provided? I could not find any official information that only BT-41 or BT-41-0 but not both can be provided. As far as I understand the documentation, it should be OK to supply both. I think this is a bug in Mustan Version 2.22.0. I've attached an example e-invoice: [ACTestFixtureMitAuftragsrabatt_MitAuftragsrabatt_Test.xml](https://github.com/user-attachments/files/26033020/ACTestFixtureMitAuftragsrabatt_MitAuftragsrabatt_Test.xml)