App
ENG
NLThe Revolution that will bring Peppol e-Invoicing to life.
In order to achieve better enforcement of VAT legislation, governments of various countries worldwide decided approximately 15 years ago and in conjunction with one another, to issue a number of new e-Invoicing rules.
1. It was decided that PDF invoices would not remain legally valid, but would be replaced by invoices in a structured format, such as UBL, Peppol BIS Billing 3.0, or other structured invoice formats.
2. It was also decided that the exchange of these invoices had to take place mandatorily via the Peppol network or similar networks.
3. In addition to the definitions for Invoice Formats and Distribution Networks, the authorities also published a Quadrilateral Peppol e-Invoicing Model, which depicts the route that e-Invoices follow when they are sent from supplier to customer via the Peppol network. In this Quadrilateral model, it is stipulated that UBL invoices would be automatically posted to the customer's accounting system directly upon receipt, from the Peppol system.
This automated posting of purchase invoices from the Peppol network, was expected to result in significant labor savings, thereby acting as the Engine behind the adoption of Peppol e-Invoicing.
The Quadrilateral Government Model looks as follows:
All e-Invoicing stakeholders from the relevant countries, such as suppliers of ERP software and e-Invoicing service providers, were requested in a Covenant to comply with the newly issued rules during the development of their new e-Invoicing Software and Services. For instance, ERP software vendors would provide the mechanism that would enable automatic invoice postings from the Peppol network.
However, despite the fact that many government agencies and other parties have spared neither effort nor expense over the past 15 years to get Peppol e-Invoicing off the ground, it did not succeeded; this was due to the fact that the Engine intended to drive the adoption of Peppol e-Invoicing, failed to function.
Companies utilizing the automated posting mechanism, would have had unvalidated and even unseen invoices posted in their accounting systems, rendering their accounting systems and balance sheets completely unreliable, which is why many companies refused to allow the automated posting of invoices.
Of course, over the past 15 years, companies could have exchanged UBL invoices via the Peppol network with each other, even without a functioning e-Invoicing adoption Engine; however, doing so would have entailed roughly 15 to 20 percent higher costs and greater effort regarding their procurement processes. It is therefore understandable that they did not take this step especially given that most companies are already straining to manage their procurement processes adequately.
To kickstart the adoption of Peppol e-Invoicing anyhow, various government bodies are considering making it mandatory and some already have, but it is doubtful whether this is the right approach. Authorities need to consider whether the pressure involved, along with the negative impact on the business community, truly outweighs the positive results expected from the Peppol e-Invoicing initiative.
We believe a better alternative to mandating Peppol e-Invoicing is to develop a New Engine capable of driving its adoption and we can assist authorities with this. However, before delving into that, we first explain why so many companies struggle to get their procurement processes going, and why consequently, they have been unable to incorporate support for Peppol e-Invoicing over the past 15 years.
The procurement process is the process in which suppliers and customers exchange tens of thousands purchase orders, sales orders, order confirmations, bills of lading, goods receipt notes, invoices, and so on with each other, which enables them to monitor and manage their mutual trade in a controlled manner and finally allowing them to Validate the Purchase invoices resulting from that trade and Generate the Sales invoices that also arise from that trade.
The procurement process is the only area of business administration that has never been automated or digitized; it is still conducted in a medieval, paper-based manner. Consequently, the tens of thousands of procurement documents mentioned earlier are printed, sorted, gathered into folders, arranged numerically and alphabetically, filed away, and stored in binders and archives for years. Because of this, procurement processes can turn into massive, labor-intensive puzzles, especially when companies have hundreds or even thousands of pending purchase and sales orders, each potentially consisting of three to four separate procurement documents.
So in summary: We have established that the original government Peppol e-Invoicing adoptionEngine, based on the automated booking of purchase invoices, has failed to function over the past 15 years, meaning a new approach is required to get Peppol e-Invoicing off the ground.
Furthermore, we have noted that companies are already struggling to keep their current procurement processes in order, and that adding support for Peppol e-Invoicing would be the straw that breaks the camel's back .
What then could be more logical than automating and digitizing the procurement process and leveraging the resulting massive efficiency gains as the New Engine to drive the adoption of Peppol e-Invoicing.
We have incorporated this vision into an improved model, we called the "Procurement Document Model," which is presented below.
As can be seen, the Procurement Document Model is clearly derived from the government's Quadrilateral Model, to which we have added a large number of Procurement functions and a Database where all Procurement documents can be stored.
During the development of the Procurement Document Model, we ensured that the rules agreed upon in the Covenant with the government authorities were not violated.
The Procurement Document Model is based on the principle that a PDF version of the same invoice is sent along with every UBL invoice that is distributed. This was done because, while UBL invoices are extremely suitable for visualizing VAT flows between companies, they are unsuitable for accountants to use for bookkeeping. UBL invoices naturally remain the legally valid invoices, whereas PDF invoices play only a supporting role; therefore, the use of PDF invoices in this manner is not in conflict with the Covenant.
Within the Procurement Document Model, automatic posting naturally plays no role whatsoever; instead, Purchase Invoices are only posted to the accounting system after they have been validated, numbered, approved, and coded.
The efficiency benefits that can be achieved with the Procurement Document Model, and which are necessary to serve as a Engine for the adoption of Peppol e-Invoicing, do not stem from improper actions such as the automatic posting of invoices, but simply from the Automating and Digitizing of the normal procurement process. As a result, procurement documents Never need to be printed again, which leads to the following efficiency, cost, and environmental benefits, among others:
- A significant saving on time and personnel costs, because unprinted documents do not entail any associated work, such as printing, sorting, collecting, and storing the documents in binders and archives.
- No more paper and printer costs.
- Space savings because the cabinets and rooms where these documents were stored and archived no longer need to be used for that purpose.
- A Formidable lower environmental impact, because no paper is consumed in the Procurement Process anymore.
The Procurement Document Model covers a much broader area than the Government Model, which focuses exclusively on invoices, whereas the Procurement Document Model Automate and Digitizes All documents and All functions that are part of the Procurement Process. Moreover, the Procurement Document Model has been optimized for the processing of UBL invoices.
Thanks to all these savings and optimizations, Apps developed based on the Procurement Document Model can generate an extremely strong Engine, which can easily kickstart the adoption of Peppol e-Invoicing. We estimate that Apps developed based on the PDM model can lead to savings of as much as 30 to 40 percent on Procurement, including the processing of UBL invoices.
The fact that the entire Procurement Document Model is displayed on the customer side of the schema might give the impression that it can only be used for a Customer role, but that is not the case.
The Procurement Document Model represents a complete business model in which not only customer functionalities are supported, but also supplier functionalities, such as sending Outgoing e-Invoices (see the blue arrows in the model). The Procurement Document Model is therefore fully usable for developing Apps for All categories, such as government and businesses, regardless of whether this is done from the customer or supplier role.
Regarding the Covenant with the e-Invoicing stakeholders, we are of the opinion that, given the fact that the Peppol e-Invoicing adoption engine is not functioning, the relevant authorities have a duty to revoke or amend the Covenant. As long as this does not happen, the e-Invoicing stakeholders will continue to comply with this Covenant, with the result that the Peppol e-Invoicing project cannot get off the ground.
We did not limit ourselves to designing the Procurement Document Model, but based on this model, we developed an entirely new Web App called:
The dossiers are created by PDM users based on properties they define themselves, but dossiers are often created based on Purchase- and Sales Orders, in order to facilitate the Validation of purchase invoices and the Invoicing of sales orders.
Dossiers can be traced within the PDM App within a few seconds by searching by name or date, which provides a huge advantage in terms of workload compared to the old-fashioned manual searching for paper folders, where it often takes minutes to find the right folder.
The Procurement Document Model shows that All procurement documents, including those documents that are Not distributed via the Peppol network but are part of the procurement process, are included in the PDM process.
This may involve waybills, delivery notes, delivery notes, and correspondence between supplier and customer, but also photos of documents that are not present in digital form but only on paper; all these documents can be digitized by taking photos and included in the PDM process.
Within the PDM App, all Invoices (PDF, UBL, Incoming and Outgoing) and all underlying documents are stored in the PDM database for the entire fiscal retention period of administrations, where they are easily traceable and accessible. This in contrast to the current practice, in which invoices are stored unstructured on hard drives or in dusty archives, where they are difficult to trace and access.
Within the PDM App, an overview of Incomplete Dossiers can be requested. Incomplete Dossiers are Dossiers to which no purchase or sales invoice has yet been added. The “Incomplete Dossiers” overview is used to detect Sales Orders Not Yet Invoiced, thereby reducing the risk of forgotten invoicing. This overview is also used to detect Purchase Invoices Yet to Be Received.
Journal entries created with the PDM App are digital in nature and can therefore potentially be automatically imported by ERP Apps for posting, which in turn increases the efficiency of the PDM App. Naturally, this function is only available if it is also supported by the ERP Apps.
The fact that PDM is a WEB App also brings additional efficiency benefits, as certain tasks, such as approving purchase invoices, can be performed via the internet. This prevents bottlenecks in the procurement process caused by waiting for those who need to approve the purchase invoices to be present at the office.
However, others such as bookkeepers, administration offices, and accountants can also perform their work via the internet when using the PDM App. This is a huge breakthrough, particularly for Bookkeepers, because although accounting applications have been accessible via the Web for many years, this professional group could previously operate almost exclusively from the office, as procurement documents were not yet accessible via the internet.
And to give you a head start with the live use of the PDM App, we go through two practical exercises below that you can perform live on this website, within the PDM App.
-The first exercise shows how UBL invoices are supported by the PDM App and how UBL invoices can be displayed within the PDM App. If you wish to perform this exercise, you can do so as follows:
Click on: "PDM App" at the very top left of the menu on this page and then click on "Login" on the right page to log in to the PDM App. You will then arrive at a page in the PDM App displaying a list of uploaded documents.
You can now view each document on this list in PDF or UBL with a single press of the corresponding button.
-In the second exercise, we will show you how to upload UBL/PDF e-Invoice pairs to the PDM App:
To do this, click on "Upload UBL+PDF Docs." in the left menu, then on "choose files" on the right, select 1 UBL file and 1 PDF file, and then click on "Open" to upload the files to the PDM App.
Next, click on "Assignable Documents" in the left menu, after which you will arrive at the same page you visited earlier, but which now also lists the documents you uploaded; you can view these documents in UBL or PDF as well.
If you would like to evaluate the PDM App Exclusive and Intensive, you can request a free 2-month evaluation period from us at the bottom of this page. PDM is new to the e-Invoicing world and can trigger a gigantic Peppol e-Invoicing revolution, but certainly also an enormous Environment and Sustainability revolution, so it is definitely a good reason to proceed with an evaluation.
However, until government bodies change course and adopt the Procurement Document Model to launch Peppol e-Invoicing, there is nothing stopping companies or government agencies from using our app right now. All the benefits described above, such as increased efficiency, space savings, and a significantly reduced environmental impact, apply just as much when companies use the PDM App without implementing Peppol e-Invoicing.
We are therefore enabling companies and government agencies to evaluate the PDM App today, allowing them to discover firsthand the tremendous benefits it offers while also preparing for the potential future mandate of Peppol e-Invoicing.
The PDM App is a WebApp that runs on external WebServers; therefore, no PDM Software needs to be installed on your systems to evaluate or use the PDM App.
The PDM App is available in English, making it easy to use worldwide.
PDM is intuitive to use and furthermore, every page within the PDM App provides an explanation of the purpose and use of the respective page and the relationship between the different pages, and should there be a need for further explanation, we are of course willing to provide it.
The free evaluation entails no obligation whatsoever; you can stop at any time, but if you decide to continue after 2 months, you will simply pick up where you left off during the evaluation period.
The only thing you need to do now is request an Evaluation after which you will receive a Link from us, which you only need to click to start the evaluation of the PDM App.
1. It was decided that PDF invoices would not remain legally valid, but would be replaced by invoices in a structured format, such as UBL, Peppol BIS Billing 3.0, or other structured invoice formats.
2. It was also decided that the exchange of these invoices had to take place mandatorily via the Peppol network or similar networks.
3. In addition to the definitions for Invoice Formats and Distribution Networks, the authorities also published a Quadrilateral Peppol e-Invoicing Model, which depicts the route that e-Invoices follow when they are sent from supplier to customer via the Peppol network. In this Quadrilateral model, it is stipulated that UBL invoices would be automatically posted to the customer's accounting system directly upon receipt, from the Peppol system.
This automated posting of purchase invoices from the Peppol network, was expected to result in significant labor savings, thereby acting as the Engine behind the adoption of Peppol e-Invoicing.
The Quadrilateral Government Model looks as follows:
NB: For the sake of brevity, on this website we use the terms UBL as a collective name for all structured invoice formats related to UBL, and Peppol as a collective name for all Networks related to the Peppol Network.
All e-Invoicing stakeholders from the relevant countries, such as suppliers of ERP software and e-Invoicing service providers, were requested in a Covenant to comply with the newly issued rules during the development of their new e-Invoicing Software and Services. For instance, ERP software vendors would provide the mechanism that would enable automatic invoice postings from the Peppol network.
However, despite the fact that many government agencies and other parties have spared neither effort nor expense over the past 15 years to get Peppol e-Invoicing off the ground, it did not succeeded; this was due to the fact that the Engine intended to drive the adoption of Peppol e-Invoicing, failed to function.
Companies utilizing the automated posting mechanism, would have had unvalidated and even unseen invoices posted in their accounting systems, rendering their accounting systems and balance sheets completely unreliable, which is why many companies refused to allow the automated posting of invoices.
Of course, over the past 15 years, companies could have exchanged UBL invoices via the Peppol network with each other, even without a functioning e-Invoicing adoption Engine; however, doing so would have entailed roughly 15 to 20 percent higher costs and greater effort regarding their procurement processes. It is therefore understandable that they did not take this step especially given that most companies are already straining to manage their procurement processes adequately.
To kickstart the adoption of Peppol e-Invoicing anyhow, various government bodies are considering making it mandatory and some already have, but it is doubtful whether this is the right approach. Authorities need to consider whether the pressure involved, along with the negative impact on the business community, truly outweighs the positive results expected from the Peppol e-Invoicing initiative.
We believe a better alternative to mandating Peppol e-Invoicing is to develop a New Engine capable of driving its adoption and we can assist authorities with this. However, before delving into that, we first explain why so many companies struggle to get their procurement processes going, and why consequently, they have been unable to incorporate support for Peppol e-Invoicing over the past 15 years.
The procurement process is the process in which suppliers and customers exchange tens of thousands purchase orders, sales orders, order confirmations, bills of lading, goods receipt notes, invoices, and so on with each other, which enables them to monitor and manage their mutual trade in a controlled manner and finally allowing them to Validate the Purchase invoices resulting from that trade and Generate the Sales invoices that also arise from that trade.
The procurement process is the only area of business administration that has never been automated or digitized; it is still conducted in a medieval, paper-based manner. Consequently, the tens of thousands of procurement documents mentioned earlier are printed, sorted, gathered into folders, arranged numerically and alphabetically, filed away, and stored in binders and archives for years. Because of this, procurement processes can turn into massive, labor-intensive puzzles, especially when companies have hundreds or even thousands of pending purchase and sales orders, each potentially consisting of three to four separate procurement documents.
So in summary: We have established that the original government Peppol e-Invoicing adoptionEngine, based on the automated booking of purchase invoices, has failed to function over the past 15 years, meaning a new approach is required to get Peppol e-Invoicing off the ground.
Furthermore, we have noted that companies are already struggling to keep their current procurement processes in order, and that adding support for Peppol e-Invoicing would be the straw that breaks the camel's back .
What then could be more logical than automating and digitizing the procurement process and leveraging the resulting massive efficiency gains as the New Engine to drive the adoption of Peppol e-Invoicing.
We have incorporated this vision into an improved model, we called the "Procurement Document Model," which is presented below.
As can be seen, the Procurement Document Model is clearly derived from the government's Quadrilateral Model, to which we have added a large number of Procurement functions and a Database where all Procurement documents can be stored.
During the development of the Procurement Document Model, we ensured that the rules agreed upon in the Covenant with the government authorities were not violated.
The Procurement Document Model is based on the principle that a PDF version of the same invoice is sent along with every UBL invoice that is distributed. This was done because, while UBL invoices are extremely suitable for visualizing VAT flows between companies, they are unsuitable for accountants to use for bookkeeping. UBL invoices naturally remain the legally valid invoices, whereas PDF invoices play only a supporting role; therefore, the use of PDF invoices in this manner is not in conflict with the Covenant.
Within the Procurement Document Model, automatic posting naturally plays no role whatsoever; instead, Purchase Invoices are only posted to the accounting system after they have been validated, numbered, approved, and coded.
The efficiency benefits that can be achieved with the Procurement Document Model, and which are necessary to serve as a Engine for the adoption of Peppol e-Invoicing, do not stem from improper actions such as the automatic posting of invoices, but simply from the Automating and Digitizing of the normal procurement process. As a result, procurement documents Never need to be printed again, which leads to the following efficiency, cost, and environmental benefits, among others:
- A significant saving on time and personnel costs, because unprinted documents do not entail any associated work, such as printing, sorting, collecting, and storing the documents in binders and archives.
- No more paper and printer costs.
- Space savings because the cabinets and rooms where these documents were stored and archived no longer need to be used for that purpose.
- A Formidable lower environmental impact, because no paper is consumed in the Procurement Process anymore.
The Procurement Document Model covers a much broader area than the Government Model, which focuses exclusively on invoices, whereas the Procurement Document Model Automate and Digitizes All documents and All functions that are part of the Procurement Process. Moreover, the Procurement Document Model has been optimized for the processing of UBL invoices.
Thanks to all these savings and optimizations, Apps developed based on the Procurement Document Model can generate an extremely strong Engine, which can easily kickstart the adoption of Peppol e-Invoicing. We estimate that Apps developed based on the PDM model can lead to savings of as much as 30 to 40 percent on Procurement, including the processing of UBL invoices.
The fact that the entire Procurement Document Model is displayed on the customer side of the schema might give the impression that it can only be used for a Customer role, but that is not the case.
The Procurement Document Model represents a complete business model in which not only customer functionalities are supported, but also supplier functionalities, such as sending Outgoing e-Invoices (see the blue arrows in the model). The Procurement Document Model is therefore fully usable for developing Apps for All categories, such as government and businesses, regardless of whether this is done from the customer or supplier role.
Regarding the Covenant with the e-Invoicing stakeholders, we are of the opinion that, given the fact that the Peppol e-Invoicing adoption engine is not functioning, the relevant authorities have a duty to revoke or amend the Covenant. As long as this does not happen, the e-Invoicing stakeholders will continue to comply with this Covenant, with the result that the Peppol e-Invoicing project cannot get off the ground.
In connection with the above, we therefore also state that our Procurement Document Model is free of any license, so everyone is free to use it at their own discretion. Government bodies could use it to amend the Covenant, and software developers can use it to develop Apps similar to our PDM App, which is described below.
We did not limit ourselves to designing the Procurement Document Model, but based on this model, we developed an entirely new Web App called:
Procurement Document Manager, abbreviated PDM
Practical implementations of the model in the PDM App
Within the PDM App, documents are collected in digital Dossiers of related documents, just as paper procurement documents are collected in related paper folders.The dossiers are created by PDM users based on properties they define themselves, but dossiers are often created based on Purchase- and Sales Orders, in order to facilitate the Validation of purchase invoices and the Invoicing of sales orders.
Dossiers can be traced within the PDM App within a few seconds by searching by name or date, which provides a huge advantage in terms of workload compared to the old-fashioned manual searching for paper folders, where it often takes minutes to find the right folder.
The Procurement Document Model shows that All procurement documents, including those documents that are Not distributed via the Peppol network but are part of the procurement process, are included in the PDM process.
This may involve waybills, delivery notes, delivery notes, and correspondence between supplier and customer, but also photos of documents that are not present in digital form but only on paper; all these documents can be digitized by taking photos and included in the PDM process.
Within the PDM App, all Invoices (PDF, UBL, Incoming and Outgoing) and all underlying documents are stored in the PDM database for the entire fiscal retention period of administrations, where they are easily traceable and accessible. This in contrast to the current practice, in which invoices are stored unstructured on hard drives or in dusty archives, where they are difficult to trace and access.
Within the PDM App, an overview of Incomplete Dossiers can be requested. Incomplete Dossiers are Dossiers to which no purchase or sales invoice has yet been added. The “Incomplete Dossiers” overview is used to detect Sales Orders Not Yet Invoiced, thereby reducing the risk of forgotten invoicing. This overview is also used to detect Purchase Invoices Yet to Be Received.
Journal entries created with the PDM App are digital in nature and can therefore potentially be automatically imported by ERP Apps for posting, which in turn increases the efficiency of the PDM App. Naturally, this function is only available if it is also supported by the ERP Apps.
The fact that PDM is a WEB App also brings additional efficiency benefits, as certain tasks, such as approving purchase invoices, can be performed via the internet. This prevents bottlenecks in the procurement process caused by waiting for those who need to approve the purchase invoices to be present at the office.
However, others such as bookkeepers, administration offices, and accountants can also perform their work via the internet when using the PDM App. This is a huge breakthrough, particularly for Bookkeepers, because although accounting applications have been accessible via the Web for many years, this professional group could previously operate almost exclusively from the office, as procurement documents were not yet accessible via the internet.
Live use of the PDM App from this website
If the PDM app seems too good to be true, we would like to remove any doubt by giving you the opportunity to use and evaluate our PDM App LIVE from this website.And to give you a head start with the live use of the PDM App, we go through two practical exercises below that you can perform live on this website, within the PDM App.
-The first exercise shows how UBL invoices are supported by the PDM App and how UBL invoices can be displayed within the PDM App. If you wish to perform this exercise, you can do so as follows:
Click on: "PDM App" at the very top left of the menu on this page and then click on "Login" on the right page to log in to the PDM App. You will then arrive at a page in the PDM App displaying a list of uploaded documents.
You can now view each document on this list in PDF or UBL with a single press of the corresponding button.
-In the second exercise, we will show you how to upload UBL/PDF e-Invoice pairs to the PDM App:
To do this, click on "Upload UBL+PDF Docs." in the left menu, then on "choose files" on the right, select 1 UBL file and 1 PDF file, and then click on "Open" to upload the files to the PDM App.
Next, click on "Assignable Documents" in the left menu, after which you will arrive at the same page you visited earlier, but which now also lists the documents you uploaded; you can view these documents in UBL or PDF as well.
Incidentally, when evaluating the PDM App on this website, do not pay attention to the type or content of the documents present in the App, because, as you have been able to ascertain yourself, the PDM App on this website is publicly accessible and any website visitor can upload any document to the PDM App, meaning there is no logical connection between the documents in the App.
If you would like to evaluate the PDM App Exclusive and Intensive, you can request a free 2-month evaluation period from us at the bottom of this page. PDM is new to the e-Invoicing world and can trigger a gigantic Peppol e-Invoicing revolution, but certainly also an enormous Environment and Sustainability revolution, so it is definitely a good reason to proceed with an evaluation.
We would like to advise any government body considering making Peppol e-Invoicing mandatory to first familiarize itself with PDM and determine that mandating Peppol e-Invoicing can be omitted when PDM is used, because it optimally supports Peppol e-Invoicing while simultaneously leading to enormous efficiency improvements and cost savings for companies.
As a result, companies will voluntarily start using the PDM App and thereby implicitly support Peppol e-Invoicing, without having to be forced to do so.
As a result, companies will voluntarily start using the PDM App and thereby implicitly support Peppol e-Invoicing, without having to be forced to do so.
Evaluating the PDM App
In previous sections, we have focused heavily on convincing government bodies that the strategy they have employed so far to kickstart Peppol e-Invoicing is not the right one. We have highlighted not only the poor results achieved with this approach but also the flaws in the strategy itself, explaining why our PDM app would be a far superior option for driving the adoption of Peppol e-Invoicing.However, until government bodies change course and adopt the Procurement Document Model to launch Peppol e-Invoicing, there is nothing stopping companies or government agencies from using our app right now. All the benefits described above, such as increased efficiency, space savings, and a significantly reduced environmental impact, apply just as much when companies use the PDM App without implementing Peppol e-Invoicing.
We are therefore enabling companies and government agencies to evaluate the PDM App today, allowing them to discover firsthand the tremendous benefits it offers while also preparing for the potential future mandate of Peppol e-Invoicing.
The PDM App is a WebApp that runs on external WebServers; therefore, no PDM Software needs to be installed on your systems to evaluate or use the PDM App.
The PDM App is available in English, making it easy to use worldwide.
PDM is intuitive to use and furthermore, every page within the PDM App provides an explanation of the purpose and use of the respective page and the relationship between the different pages, and should there be a need for further explanation, we are of course willing to provide it.
The free evaluation entails no obligation whatsoever; you can stop at any time, but if you decide to continue after 2 months, you will simply pick up where you left off during the evaluation period.
The only thing you need to do now is request an Evaluation after which you will receive a Link from us, which you only need to click to start the evaluation of the PDM App.