Peppol International Invoice model review - PINT
Dear OpenPeppol members,
Attached is a draft of the Peppol International Invoice Model, called PINT
The draft is being distributed for introduction and to invite comments on the following:
the design of the model and its ability to foster invoice interoperability in a global setting.
the detailed specification of the PINT data model.
the rules applied to the content of the PINT data model.
general proofreading issues like wording, spelling, grammar and layout.
Please note that the document and its annexes are draft and thus not a release candidate. Comments received will be processed and the draft updated to a final version which is scheduled to be published on November 1st this year.
You are herewith invited to review the attached drafts and comment as listed above and also encouraged to evaluated the PINT by considering how it can be applied in your country or other countries that you have direct experience with doing busines in, taking into account relevant legal environment and business practices. If you find lack of clarity or necessary support then please send a short description of the use case to georg@midran.is
Please provide comment on the content of the specification by using the attached comment spreadsheet (it makes it easier to consolidate comments from multiple reviews and process them systematically). Proofreading comments may be done in-line using Tracking.
Kindly provide your comments before end of day Friday August 28th, in the latest time zone (GMT+11). Earlier comments will be appreciated.
Artifact | File |
---|---|
PINT specification Defines the PINT methodology, data model, compliance and rules. | |
PINT datamodel Detailed data model as normative appendix to the specification | |
PINT guideline A guideline on how different parts of the PINT can be restricted to support various use cases. Informative. | |
Minimum PINT message An message example that represents the minimum invoice content that a receiver of the PINT can expect and needs to be ready to process in one way or another. | |
Validation artifacts Technical artefacts to validate whether an invoice message complies with the rules stated in the normative specification. | |
Comment template A template for providing comments on the different documents that are up for review. |