Skip to content
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

Updates about SpecifiedTradeSettlementHeaderMonetarySummation and SpecifiedTradeSettlementPaymentMeans #729

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

adn35350
Copy link

@adn35350 adn35350 commented Feb 4, 2025

This pull request introduces two new changes:

  • Addition of the tag /rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:ApplicableHeaderTradeSettlement/ram:SpecifiedTradeSettlementHeaderMonetarySummation/ram:LineTotalAmount which must be present in the BASICWL profile according to the Factur-X v1.07.2 standard.
  • Possibility of setting a code other than 58 in the /rsm:CrossIndustryInvoice/rsm:SupplyChainTradeTransaction/ram:ApplicableHeaderTradeSettlement/ram:SpecifiedTradeSettlementPaymentMeans/ram:TypeCode tag. The Factur-X v1.07.2 standard allows codes other than this one. In particular, when transferring Factur-X to ChorusPro. Chorus Pro is a French government platform for invoice transmission. For example, the platform only accepts code 30 for SEPA transfers.

I hope this pull request can be merged soon.

Adriann LERAY added 2 commits February 4, 2025 09:25
In the Factur-X 1.07.2 specifications the tag LineTotalAmount must be present not only for BASIC profile but also BASICWL profile.
…s/ram:TypeCode

Factur-X 1.07.2 specifications indicate that the ram:TypeCode can be other code than 58. Espacially for ChorusPro which expect 30 for SEPA credit transfer
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant