We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
There seems to be a problem converting the AdditionalReferencedDocument field to cac:DocumentReference, the TypeCode is missing on the output xml.
// Input CII <am:ApplicableHeaderTradeAgreement> ... <ram:AdditionalReferencedDocument> <ram:IssuerAssignedID schemeID="AAJ">18088852:20221215</ram:IssuerAssignedID> <ram:TypeCode>130</ram:TypeCode> </ram:AdditionalReferencedDocument> ... </ram:ApplicableHeaderTradeAgreement>
// Output UBL <cac:InvoiceLine> ... <cac:DocumentReference> <cbc:ID>18088852:20221215</cbc:ID> </cac:DocumentReference> ... </cac:InvoiceLine>
The text was updated successfully, but these errors were encountered:
Mapping the CII TypeCode to UBL DocumentTypeCode But only if the value is either 50 (BT-17) or 130 (BT-18).
TypeCode
DocumentTypeCode
50
130
Other values are explicitly forbidden and checked by the EN-16931 validation artefacts.
Sorry, something went wrong.
Taking over TypeCode for additional references; #18
42a952e
@L3Mars if that suits you, I will release v1.4.10 immediately.
@phax That would be great, thank you !
Release 1.4.10 is out. Thanks for reporting
phax
No branches or pull requests
There seems to be a problem converting the AdditionalReferencedDocument field to cac:DocumentReference, the TypeCode is missing on the output xml.
The text was updated successfully, but these errors were encountered: