GithubHelp home page GithubHelp logo

UBL-SR-32 about einvoicing-en16931 HOT 9 CLOSED

petredanoiu avatar petredanoiu commented on August 26, 2024
UBL-SR-32

from einvoicing-en16931.

Comments (9)

petredanoiu avatar petredanoiu commented on August 26, 2024

the rule must be

am i correct?

from einvoicing-en16931.

petredanoiu avatar petredanoiu commented on August 26, 2024

the rule must be
[UBL-SR-32]-VAT exemption reason code shall occur maximum once
"UBL-SR-32" value="(count(cac:TaxCategory/cbc:TaxExemptionReasonCode) <= 1)"

from einvoicing-en16931.

MartinForsberg-Ecru avatar MartinForsberg-Ecru commented on August 26, 2024

The cardinality of BT-120, "VAT Exemption Reason text" in the semantic model is 0..1. The UBL XML-schema is more allowing with cardinality is 0..n. The rule checks that only one reason text is used, as that is what the semantic model allows. The syntax binding highlights this discrepancy in the Match-column (CAR-3").
bild

from einvoicing-en16931.

petredanoiu avatar petredanoiu commented on August 26, 2024

hi, martin
thank you for quick reaction
but what about this:
BT-121 card. in semantic model is 0..1 , as in UBL schema (0..1 too), but not schematron rule to validate this
can you explain this to me

many thanks

from einvoicing-en16931.

MartinForsberg-Ecru avatar MartinForsberg-Ecru commented on August 26, 2024

It is expected that the UBL XML Schema would identify a situation where the element is repeated. The XML would not be a valid UBL document and there is no need for a schematron rule.

This goes for all situations where the cardinality of UBL matches the cardinality of the semantic model.

from einvoicing-en16931.

petredanoiu avatar petredanoiu commented on August 26, 2024

and the last one, Martin :
an invoice with multiple lines, different VAT cat.(for example
2 lines with VAT cat. E, rate 0, each line with different tax exception reason;
and
3 lines with VAT cat. S, rate 5, 9 and 19 and different BT-139 (Invoice line allowance reason), each cat. with different rate and different BT-139;
how do i create the xml element BG-23 VAT break down
can you give me an xml file as example
many thanks

from einvoicing-en16931.

MartinForsberg-Ecru avatar MartinForsberg-Ecru commented on August 26, 2024

The lines with Category S should be summarised per rate and result in one TaxSubtotal for each rate.

The design of the EN16931 only allows for a single TaxSubtotal with category code E. This means that there is no possibility to distinguish the line amounts for different exemption reason. (See rule BR-E-01 https://docs.peppol.eu/poacc/billing/3.0/rules/ubl-tc434/BR-E-01/)

Unfortunately, I don't have time to provide you with more guidance than that.

from einvoicing-en16931.

petredanoiu avatar petredanoiu commented on August 26, 2024

from einvoicing-en16931.

oriol avatar oriol commented on August 26, 2024

There is nothing to be done in the rule.

from einvoicing-en16931.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.