Comments (7)
The underlying codelist is UNTDID 1153 D16B and this one states "VA" is the correct one - https://www.unece.org/fileadmin/DAM/trade/untdid/d16b/tred/tred1153.htm
But there are other rules that still reference 'VAT':
<param name="UBL-SR-12" value="(count(cac:AccountingSupplierParty/cac:Party/cac:PartyTaxScheme[cac:TaxScheme/cbc:ID='VAT']/cbc:CompanyID) <= 1)"/>
<param name="UBL-SR-13" value="(count(cac:AccountingSupplierParty/cac:Party/cac:PartyTaxScheme[cac:TaxScheme/cbc:ID!='VAT']/cbc:ID) <= 1)"/>
from einvoicing-en16931.
from einvoicing-en16931.
We follow the UNTDID 1153 codelist that uses "VA" instead of "VAT". The SR rules need to be corrected.
from einvoicing-en16931.
Please close when commit is present - thx :)
from einvoicing-en16931.
Solved
from einvoicing-en16931.
In the EN 16931-1:2017 the UNTDID 1153 is referenced only in BT-18 and BT-128.
Is this indication only for the mapping with UBL 2.1 (TS 16931-3-2)?
UNTDID 1153 looks appropriate (VA: VAT registration number) for cac:TaxScheme/cbc:ID in the BT-31 (Seller VAT id) and BT-48 (Buyer VAT id).
Why is it also used in BG-30 (Line VAT information) and in BG-23 (VAT breakdown) where we are not talking about a VAT registration number but simply the VAT ? (UNTDID 5153 is used in some old example -> VAT: Value added tax)
from einvoicing-en16931.
cac:TaxScheme/cbc:ID is not defined in the Norm, but it is required in the UBL syntax. That's why it has been included in the syntax binding.
The use of VA instead of VAT is just for consistency with BT-18 and BT-128, avoiding people using "VA" in one place and "VAT" in another one.
from einvoicing-en16931.
Related Issues (20)
- add missing currency codes HOT 2
- Bug in CII BR-65 HOT 3
- Add EAS code 0218 HOT 1
- BR-17 fails on equal payee and seller
- Move PEPPOL-EN16931-R046 rule to EN16931? HOT 2
- UBL-SR-32 HOT 9
- missing cardinality check for Value added tax point date (BT-7) and Value added tax point date code (BT-8) in CII HOT 1
- Undocumented and missing changes in v.1.3.11 release HOT 3
- BR-33 / BR-CO-21 rules validation doesn't work on CII files (OK on UBL files) HOT 1
- [BR-63] fails if multiple URIUniversalCommunication are present HOT 5
- Tolerance of 1 € on BR-S-09 HOT 2
- BT-32 path check missing in BR-AE-02, BR-AE-03, and BR-AE-04 in CII HOT 1
- Code list changes
- ISO 4217 VEF/VES
- Commit did overwrite PR changes
- CII special ID elements without attributes - not handled correctly
- VAT Category "B" supported even though it is not in the EN
- Contradicting message
- ISO 4217 HRK / Kuna
- Artefacts v1.3.12 (CII) do not check BR-62 / BR-63 correct any more HOT 2
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
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.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from einvoicing-en16931.