Informējam, ka Sistēma pielāgota darbam ar interneta pārlūkprogrammu Internet Explorer (8. un jaunākām versijām) un Mozilla Firefox (3.6 un jaunākām versijām).
Izmantojot citu interneta pārlūkprogrammu, brīdinām, ka Sistēmas funkcionalitāte var tikt traucēta.
This Technical Specification defines the purpose, governance, and functional requirements of an eInvoicing Registry for
Core Invoice Usage Specifications (CIUS) and Extension Specifications. Once developed the Registry will serve as a
structured, transparent, and publicly accessible repository, facilitating the discovery, registration, and management of
Specifications that restrict or extend the EN 16931 Core Invoice Model.
The scope includes:
Definition of Registry Services – The structure, functions, and metadata required for CIUS, Extension Specifications,
validation artefacts, and code lists.
Governance Model – Roles and responsibilities of CEN/TC 434 and other Stakeholders
Submission & Verification Processes – How specifications are intended to be submitted, reviewed, and approved.
Functional Specification – Key features, metadata requirements, user access, and future enhancements.
Reģistrācijas numurs (WIID)
82144
Darbības sfēra
This Technical Specification defines the purpose, governance, and functional requirements of an eInvoicing Registry for
Core Invoice Usage Specifications (CIUS) and Extension Specifications. Once developed the Registry will serve as a
structured, transparent, and publicly accessible repository, facilitating the discovery, registration, and management of
Specifications that restrict or extend the EN 16931 Core Invoice Model.
The scope includes:
Definition of Registry Services – The structure, functions, and metadata required for CIUS, Extension Specifications,
validation artefacts, and code lists.
Governance Model – Roles and responsibilities of CEN/TC 434 and other Stakeholders
Submission & Verification Processes – How specifications are intended to be submitted, reviewed, and approved.
Functional Specification – Key features, metadata requirements, user access, and future enhancements.
