Vážení zákazníci, v letošním roce budeme expedovat poslední objednávky ve středu 18. 12. 2024.

Těšíme se s vámi na shledanou od pondělí 06. 01. 2025.

 

Menu
0
Total price
0 €
PRICES include / exclude VAT
Homepage>PD CEN/TR 16931-9:2024 Electronic invoicing VAT reporting and gap analysis with current e-invoicing standardization deliverables
Sponsored link
sklademVydáno: 2024-11-26
PD CEN/TR 16931-9:2024 Electronic invoicing VAT reporting and gap analysis with current e-invoicing standardization deliverables

PD CEN/TR 16931-9:2024

Electronic invoicing VAT reporting and gap analysis with current e-invoicing standardization deliverables

Format
Availability
Price and currency
Anglicky Secure PDF
Immediate download
318.46 €
You can read the standard for 1 hour. More information in the category: E-reading
Reading the standard
for 1 hour
31.85 €
You can read the standard for 24 hours. More information in the category: E-reading
Reading the standard
for 24 hours
95.54 €
Anglicky Hardcopy
In stock
318.46 €
Označení normy:PD CEN/TR 16931-9:2024
Počet stran:36
Vydáno:2024-11-26
ISBN:978 0 539 32047 3
Status:Standard
DESCRIPTION

PD CEN/TR 16931-9:2024


This standard PD CEN/TR 16931-9:2024 Electronic invoicing is classified in these ICS categories:
  • 35.240.20 IT applications in office work
  • 35.240.63 IT applications in trade
The European Commission will in its project “VAT in the digital age” mandate that VAT reporting on intra-EU transactions is performed in near real time and based on EN 16931. This document defines the impact of this legislation on the various deliverables of CEN/TC 434, with a focus on the subset to be sent to tax authorities and how EN 16931-1 will need to be changed. NOTE 1 The ViDA proposal only applies to EU member states. This document does not define the subset of the electronic invoice to be sent to the authorities. NOTE 2 The definition of that subset is a task of the European Commission. As the subset message is not an invoice, but a VAT report, it is not regarded as a Core Invoice Usage Specification (CIUS). The subset therefore needs not to obey the rules for developing a CIUS. For example, not all mandatory elements in the invoice need to be part of the subset.