This is a work-in-progress repository of the Technical Working Group of the NPa, with contributions from service providers.
This repository contains several draft documents related to the invoice-to-payment process, mainly regarding response document types, such as the Message Level Response (MLR) and the Invoice Response Message (IRM), sometimes referred to as the Business Level Response (BLR).
Please note that these documents are in a very early stage, and are far from complete.
This also goes for the list of documents themselves: they may be merged or split up in the future, and documents may be added or removed.
The list of current drafts is as follows:
| Document | Description |
|---|---|
| Briefing | A one-pager describing why response messages are important, and questions for the working group |
| Invoice to Payment Process | A full descriptive document of the potential scenarios in the invoicing process, and when to use which response document |
| Images | A folder for storing all images that are used elsewhere in this repository |
Some of the documents contain diagrams. These are stored in plain-text which can be processed by the mermaid extension. In order to view these diagrams directly on github, you can install the Mermaid add-on for your browser.
Below is a list of links, but we advise you to search for it directly from the addon/extension store of your browser.
Instructions on how to use mermaid locally will be added later.
You can report issues or requests with either the Issues link above, or by forking the repository and creating a Pull Request. See the paragraph below for details on how to add your changes to a file and push the changes to the NPa by using Github in your browser. Alternatively, you can send a direct request to the NPa by email [email protected]. No rights can be derived from submissions.
The final result of this process will be submitted to the Service Provider community for approval.
Create a Github account and login.
Find the repository that contains the project that you want to work on.
A repository can contains files and folders. A folder will most likely contain more files.
Click on a filename to open the file. Click the Edit icon to start editing the file.
If you do not have your own copy of the repository yet, Github will inform you that it has created a "Fork". A fork means you have your private copy of the project that you want to work on.
Now you can edit the file. If you are working on a .MD (markdown) file you can use the following webpage to help you with creating specific formatting: Markdown cheatsheet
After you have made your changes in your private copy of the project, you can push your changes to the repository of the Netherlands Peppol Authority. Give your change request a name and some explanatory text before clicking the "Propose changes" button.
