App
ENG
NLThe Revolution that will bring e-Invoicing via Peppol 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 Four-corner 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 Four-corner model, it is stipulated that UBL invoices are 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 e-Invoicing via Peppol.
The Four-corner Model of the authorities 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 Products; for instance, suppliers of ERP apps have developed the mechanism that enables automatic invoice postings from the Peppol network.
But despite the fact that many government agencies and various other parties have spared no effort over the past 15 years to get e-Invoicing off the ground, it has barely succeeded, and that doesn't surprise us at all.
Technically, it is quite a feat to get e-Invoices booked from the supplier's accounting system into the customer's accounting system via the Peppol network without human intervention, but automatic booking means that the customer ends up with Unvalidated invoices in their accounting.
Traditionally, when purchase invoices are received, the underlying procurement documents such as order slips and delivery notes are first attached, after which the invoices are validated, coded, and posted based on these procurement documents.
But when it comes to automatically posting Purchase Invoices from the Peppol network, the invoices are posted directly into the customer's accounting system upon arrival, even before the underlying procurement documents can be attached. This means that validating and coding the invoices based on the underlying procurement documents is skipped, and the posting of the unvalidated Purchase Invoices takes place using a standard pre-programmed journal entry.
Posting unvalidated Purchase Invoices results in the accounting losing all reliability, which is why these automatic invoice postings have often been rejected over the past 15 years, and will likely continue to be rejected in the future.
To confirm our view that there is something wrong with automatically posting Purchase Invoices, we present the following perspective:
If automatically posting Purchase Invoices had been accounting-wise acceptable, it would have led to up to 50% work savings in the procurement process, and companies would have been lining up to implement e-Invoicing.
But the reality is different. Companies were not lining up to implement e-Invoicing; on the contrary, it remained so quiet that governments are now considering forcing companies to start using e-Invoicing, and some countries, like Belgium and Germany, have already done so.
Governments, by the way, don’t seem to realize that automatically posting purchase invoices is fundamentally wrong; otherwise, they would have been a bit more cautious about making e-Invoicing mandatory. It actually makes quite a difference whether a company is required to do something that leads to a 50% work saving or something that results in a 15% increase in workload.
The 15% increase in workload is our estimate of the extra work that needs to be done when e-Invoicing becomes mandatory, without having an adoption engine available.
We are anticipating that sooner or later people will conclude that the current Engine meant to drive the adoption of e-Invoicing can't function, and that there will be a need for a new Engine. That's why we developed the PDM Web App, which Digitalizes and Automates the procurement process, making it much more efficient and thus able to serve as the New Engine for the adoption of e-Invoicing.
In the coming years, we will act as a lifeline for companies that run into trouble due to government-mandated e-Invoicing, but we're more than just a lifeline. Our PDM App can already, even without e-Invoicing mandates, take companies' procurement processes to a much higher level by Digitalizing and Automating them, which can reduce the time and costs spent on the procurement process by up to 40%.
The procurement process is the process where suppliers and customers exchange tens of thousands of purchase orders, sales orders, order confirmations, waybills, delivery notes, invoices, etc., to initiate, monitor and manage their trade with each other, and ultimately to Validate the resulting Purchase Invoices and Create the Sales Invoices.
The procurement process is the last piece of business administration that has never been Digitized or Automated and is still conducted in a very old-fashioned Paper way, which means that the many tens of thousands of procurement documents mentioned above have to be: printed, sorted, collected in folders, arranged by number and alphabetically, and stored and kept for many years in binders and archives.
Procurement processes can turn into large, labor-intensive puzzles, especially when companies have hundreds or even thousands of pending purchase and sales orders, each of which can consist of three to four separate procurement documents, meaning companies have to really go all out to manage their procurement process properly.
So what could be more logical than to Digitize and Automate the Procurement process and use the huge efficiency benefits that come from this as the New Engine to kickstart the adoption of e-Invoicing.
We have incorporated this vision into an improved square model, which we have called the “Procurement Document Model”, and show it below.
As you can see, the Procurement Document Model is clearly derived from the governments' Four-corner model, and we have added a large number of Procurement functions and a Database where all procurement documents are stored.
In developing the Procurement Document Model, we carefully ensured that the rules agreed upon in the Covenant with the governments were not violated, so that the purpose for which e-Invoicing via Peppol was set up, namely to improve the enforcement of VAT legislation in accordance with European ViDA legislation, can still be fully achieved.
Please note, the PDM App is Not a Billing App, so you can't create Sales Invoices with it. The PDM App does have the information in the records that can be used to create Sales Invoices, but the actual creation of the Sales Invoices, as usual, is left to the ERP or Billing Apps, which can of course make use of the information available in the PDM App.
To explain how the PDM works, we break down the functioning of the PDM App into 2 parts, namely:
1. The Digitization part and
2. The Automation part.
1. In the Digitization section, it is described which documents are Digitized by the PDM App, and to keep it short, these are All imaginable Purchase and Sales procurement documents that companies exchange with each other, From Quote to Invoice, including UBL invoices and photos, as well as all procurement documents that are not exchanged via Peppol, but for example just by email.
And the way all these documents are Digitized by the PDM App is by Uploading them to the PDM App, which is an alternative to printing these documents.
So when using the PDM App, procurement documents are NO LONGER printed on paper, like used to be the case, but are Uploaded to the PDM App, which also explains the Digitization Claim we make regarding our PDM App, and which prevents printing hundreds of thousands of documents per year, bringing not just huge Efficiency benefits, but also massive Sustainability advantages.
2. In the Automation section, it is described which digital features are required within the PDM App to carry out the procurement process digitally, and these are the following digital features:
-A. Dossier Creation, All procurement documents uploaded to the PDM app are collected within the PDM App in shared dossiers, consisting of related documents.
This dossier creation is done by the PDM user, who also sets up the dossiers. The PDM user decides for themselves which criteria to use to create the dossiers, but for running a procurement process, it’s useful to do it based on Purchase and Sales Orders, just like in the past when paper folders were organized according to Purchase and Sales Orders.
-B. Approval, When the purchasing dossiers are complete, meaning that the purchase invoices have also been received, the dossiers are submitted to the budgetholders for approval.
During approval, a PurchaseSerialNumber is also assigned to the PurchaseInvoices and they are linked to the current Bookyear.
-C. Coding, After approval, the PurchaseInvoices (and, if necessary, also the SalesInvoices) are coded by the PDM user, based on the underlying documents in the dossier, and only after that can the PurchaseInvoices be posted in the accounting system.
All procurement documents stored in the PDM database are kept there for many years, where they are easy to trace and access, even if they are several years old, without having to dig through dusty archives.
Within the Procurement Document Model, with every UBL invoice that is distributed, a PDF version of the same invoice is also sent along. This is done because UBL invoices are very suitable for visualizing VAT flows between companies, but for accountants to use them for bookkeeping, they are unsuitable. Of course, UBL invoices remain the legally valid invoices, while the PDF invoices only play a supporting role, so using PDF invoices in this way is not in conflict with the Covenant.
To ensure that the UBL and PDF invoices always remain inseparably linked within the PDM App, they are uploaded to the PDM App as a InvoicePair, and you can also try uploading them as an InvoicePair live on this page, as an exercise in the PDM App.
The Enormous efficiency benefits achieved with the PDM App, which are necessary to function as an Engine for the adoption of e-Invoicing, come from the Digitization and Automation of the Entire Procurement Portfolio, so not just the Invoices, but All Procurement Documents, from Quote to Invoice, regardless of whether they are distributed via the Peppol Network or by email, and this brings a whole range of Efficiency, Cost, and even Environmental benefits as listed below:
-A significant saving in time and personnel costs, because documents that aren't printed also don't involve related tasks such as printing, sorting, collecting, and storing the documents in folders and archives.
-No more paper and printer costs.
-Space savings since the cabinets and spaces where these documents were stored and archived no longer need to be used for that purpose.
-A Formidably lower impact on the environment, because no paper is used in the Procurement process.
Thanks to all these efficiency benefits, the Procurement Document Model generates an extremely strong Engine, making the adoption of e-Invoicing via Peppol easy to launch.
We estimate that the use of the PDM App can lead to savings of up to 30 to 40 percent on the Procurement process, including the processing of UBL invoices.
Another feature that increases the efficiency of the PDM App is the Incomplete Dossiers overview. Incomplete Dossiers are files to which no Purchase or Sales Invoice has yet been added. The “Incomplete Dossiers” overview can be used to detect Sales Orders Yet to be Invoiced, thereby reducing the chance of Forgotten Invoicing. This overview is also used to detect Purchase Invoices that are still to be received.
Journal entries created with the PDM App are digital in nature and can therefore potentially be automatically imported for posting by ERP Apps, which further increases the efficiency of the PDM App. Of course, this feature is only available when it is supported by the ERP Apps.
The fact that PDM is a WEB App also brings extra efficiency benefits, because certain tasks, like approving Purchase Invoices, can be done over the internet. This prevents bottlenecks in the procurement process since employees who need to approve the Purchase Invoices don't have to be in the office.
But others, like accountants, administrative offices, auditors, and even tax inspectors, can also carry out their work through the internet using the PDM App. Especially for Accountants, this is a huge breakthrough. Even though ERP applications have been usable via the web for many years, this group could still mostly only work from the office because the procurement documents they deal with frequently were not yet accessible online.
And to help you with your first live use of the PDM App, we go through two practical exercises below that you can perform live on this website, in 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 want to do this exercise, you can do it as follows:
Click on: "PDM App" at the very top left of this page’s menu and then click on "Login" on the right side of the page to log in to the PDM App. You will then land on a page in the PDM App that displays a list of uploaded documents.
You can now view any document on this list in PDF or UBL with just one click of the corresponding button.
- In the second exercise, we’ll show you how to upload a UBL/PDF Invoice Pair to the PDM App:
To do this, click on "Upload UBL+PDF Docs." in the left menu and then click on “choose files” on the right, select 1 UBL file and 1 PDF file, and then click "Open" to upload the files to the PDM App.
Next, click on "Assignable Documents" in the left menu, which will take you to the same page you visited earlier, but now also lists the documents you uploaded. You can also view these documents in UBL or PDF.
If you would like to evaluate the PDM App Exclusive and Intensive, you can request a free 2-month trial with us at the bottom of this page. PDM is new in the e-Invoicing world and can trigger a huge e-Invoicing revolution, but also a massive Environmental and Sustainability revolution, so definitely a good reason to give it a try.
We therefore enable companies and governments to start evaluating the PDM App now, so they can see for themselves the huge benefits that can be achieved with it and, moreover, be prepared for the possibly mandatory use of e-Invoicing via Peppol.
The PDM App is a Web App that runs on external WebServers, so there’s no need to install any PDM Software 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 in addition, each page within the PDM App provides explanations about the purpose and use of that page and how the different pages are connected, and if there is a need for further explanation, we are of course happy to provide it.
The free trial comes with no obligations; you can stop at any time, but if you decide to continue after 2 months, you simply pick up from where you left off during the trial period.
All you need to do now is request a Trial, after which you will receive a Link from us, which you just 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 Four-corner 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 Four-corner model, it is stipulated that UBL invoices are 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 e-Invoicing via Peppol.
The Four-corner Model of the authorities looks as follows:
Note, 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, Peppol as a collective name for all Networks related to the Peppol Network, and the term e-Invoicing always stands for e-Invoicing via Peppol
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 Products; for instance, suppliers of ERP apps have developed the mechanism that enables automatic invoice postings from the Peppol network.
But despite the fact that many government agencies and various other parties have spared no effort over the past 15 years to get e-Invoicing off the ground, it has barely succeeded, and that doesn't surprise us at all.
Technically, it is quite a feat to get e-Invoices booked from the supplier's accounting system into the customer's accounting system via the Peppol network without human intervention, but automatic booking means that the customer ends up with Unvalidated invoices in their accounting.
Traditionally, when purchase invoices are received, the underlying procurement documents such as order slips and delivery notes are first attached, after which the invoices are validated, coded, and posted based on these procurement documents.
But when it comes to automatically posting Purchase Invoices from the Peppol network, the invoices are posted directly into the customer's accounting system upon arrival, even before the underlying procurement documents can be attached. This means that validating and coding the invoices based on the underlying procurement documents is skipped, and the posting of the unvalidated Purchase Invoices takes place using a standard pre-programmed journal entry.
Posting unvalidated Purchase Invoices results in the accounting losing all reliability, which is why these automatic invoice postings have often been rejected over the past 15 years, and will likely continue to be rejected in the future.
To confirm our view that there is something wrong with automatically posting Purchase Invoices, we present the following perspective:
If automatically posting Purchase Invoices had been accounting-wise acceptable, it would have led to up to 50% work savings in the procurement process, and companies would have been lining up to implement e-Invoicing.
But the reality is different. Companies were not lining up to implement e-Invoicing; on the contrary, it remained so quiet that governments are now considering forcing companies to start using e-Invoicing, and some countries, like Belgium and Germany, have already done so.
Governments, by the way, don’t seem to realize that automatically posting purchase invoices is fundamentally wrong; otherwise, they would have been a bit more cautious about making e-Invoicing mandatory. It actually makes quite a difference whether a company is required to do something that leads to a 50% work saving or something that results in a 15% increase in workload.
The 15% increase in workload is our estimate of the extra work that needs to be done when e-Invoicing becomes mandatory, without having an adoption engine available.
We are anticipating that sooner or later people will conclude that the current Engine meant to drive the adoption of e-Invoicing can't function, and that there will be a need for a new Engine. That's why we developed the PDM Web App, which Digitalizes and Automates the procurement process, making it much more efficient and thus able to serve as the New Engine for the adoption of e-Invoicing.
In the coming years, we will act as a lifeline for companies that run into trouble due to government-mandated e-Invoicing, but we're more than just a lifeline. Our PDM App can already, even without e-Invoicing mandates, take companies' procurement processes to a much higher level by Digitalizing and Automating them, which can reduce the time and costs spent on the procurement process by up to 40%.
The procurement process is the process where suppliers and customers exchange tens of thousands of purchase orders, sales orders, order confirmations, waybills, delivery notes, invoices, etc., to initiate, monitor and manage their trade with each other, and ultimately to Validate the resulting Purchase Invoices and Create the Sales Invoices.
The procurement process is the last piece of business administration that has never been Digitized or Automated and is still conducted in a very old-fashioned Paper way, which means that the many tens of thousands of procurement documents mentioned above have to be: printed, sorted, collected in folders, arranged by number and alphabetically, and stored and kept for many years in binders and archives.
Procurement processes can turn into large, labor-intensive puzzles, especially when companies have hundreds or even thousands of pending purchase and sales orders, each of which can consist of three to four separate procurement documents, meaning companies have to really go all out to manage their procurement process properly.
So what could be more logical than to Digitize and Automate the Procurement process and use the huge efficiency benefits that come from this as the New Engine to kickstart the adoption of e-Invoicing.
We have incorporated this vision into an improved square model, which we have called the “Procurement Document Model”, and show it below.
As you can see, the Procurement Document Model is clearly derived from the governments' Four-corner model, and we have added a large number of Procurement functions and a Database where all procurement documents are stored.
In developing the Procurement Document Model, we carefully ensured that the rules agreed upon in the Covenant with the governments were not violated, so that the purpose for which e-Invoicing via Peppol was set up, namely to improve the enforcement of VAT legislation in accordance with European ViDA legislation, can still be fully achieved.
Please note, the PDM App is Not a Billing App, so you can't create Sales Invoices with it. The PDM App does have the information in the records that can be used to create Sales Invoices, but the actual creation of the Sales Invoices, as usual, is left to the ERP or Billing Apps, which can of course make use of the information available in the PDM App.
To explain how the PDM works, we break down the functioning of the PDM App into 2 parts, namely:
1. The Digitization part and
2. The Automation part.
1. In the Digitization section, it is described which documents are Digitized by the PDM App, and to keep it short, these are All imaginable Purchase and Sales procurement documents that companies exchange with each other, From Quote to Invoice, including UBL invoices and photos, as well as all procurement documents that are not exchanged via Peppol, but for example just by email.
And the way all these documents are Digitized by the PDM App is by Uploading them to the PDM App, which is an alternative to printing these documents.
So when using the PDM App, procurement documents are NO LONGER printed on paper, like used to be the case, but are Uploaded to the PDM App, which also explains the Digitization Claim we make regarding our PDM App, and which prevents printing hundreds of thousands of documents per year, bringing not just huge Efficiency benefits, but also massive Sustainability advantages.
2. In the Automation section, it is described which digital features are required within the PDM App to carry out the procurement process digitally, and these are the following digital features:
-A. Dossier Creation, All procurement documents uploaded to the PDM app are collected within the PDM App in shared dossiers, consisting of related documents.
This dossier creation is done by the PDM user, who also sets up the dossiers. The PDM user decides for themselves which criteria to use to create the dossiers, but for running a procurement process, it’s useful to do it based on Purchase and Sales Orders, just like in the past when paper folders were organized according to Purchase and Sales Orders.
-B. Approval, When the purchasing dossiers are complete, meaning that the purchase invoices have also been received, the dossiers are submitted to the budgetholders for approval.
During approval, a PurchaseSerialNumber is also assigned to the PurchaseInvoices and they are linked to the current Bookyear.
-C. Coding, After approval, the PurchaseInvoices (and, if necessary, also the SalesInvoices) are coded by the PDM user, based on the underlying documents in the dossier, and only after that can the PurchaseInvoices be posted in the accounting system.
All procurement documents stored in the PDM database are kept there for many years, where they are easy to trace and access, even if they are several years old, without having to dig through dusty archives.
Within the Procurement Document Model, with every UBL invoice that is distributed, a PDF version of the same invoice is also sent along. This is done because UBL invoices are very suitable for visualizing VAT flows between companies, but for accountants to use them for bookkeeping, they are unsuitable. Of course, UBL invoices remain the legally valid invoices, while the PDF invoices only play a supporting role, so using PDF invoices in this way is not in conflict with the Covenant.
To ensure that the UBL and PDF invoices always remain inseparably linked within the PDM App, they are uploaded to the PDM App as a InvoicePair, and you can also try uploading them as an InvoicePair live on this page, as an exercise in the PDM App.
The Enormous efficiency benefits achieved with the PDM App, which are necessary to function as an Engine for the adoption of e-Invoicing, come from the Digitization and Automation of the Entire Procurement Portfolio, so not just the Invoices, but All Procurement Documents, from Quote to Invoice, regardless of whether they are distributed via the Peppol Network or by email, and this brings a whole range of Efficiency, Cost, and even Environmental benefits as listed below:
-A significant saving in time and personnel costs, because documents that aren't printed also don't involve related tasks such as printing, sorting, collecting, and storing the documents in folders and archives.
-No more paper and printer costs.
-Space savings since the cabinets and spaces where these documents were stored and archived no longer need to be used for that purpose.
-A Formidably lower impact on the environment, because no paper is used in the Procurement process.
Thanks to all these efficiency benefits, the Procurement Document Model generates an extremely strong Engine, making the adoption of e-Invoicing via Peppol easy to launch.
We estimate that the use of the PDM App can lead to savings of up to 30 to 40 percent on the Procurement process, including the processing of UBL invoices.
Reflections on the Covenant with e-Invoicing stakeholders
We believe that given the fact that the e-Invoicing adoption Engine of the governments does not appear to be working, the governments concerned have a duty to revoke or amend the Covenant, because as long as this does not happen, the e-Invoicing stakeholders will continue to conform to this Covenant, and continue to develop products and services, that have not functioned in the past 15 years and will not function in the future, with the result that the e-Invoicing project does not get off the ground.
In connection with the above, we also mention that our Procurement Document Model is free of any license, so anyone is free to use it as they see fit. Governments could use it to adapt the Covenant, and software developers could use it to develop similar apps, like our PDM App, which is described below.
Extra efficiency benefits provided by the PDM App
Dossiers can be tracked within the PDM App in just a few seconds by searching by name or date, which offers a huge efficiency advantage compared to the old-fashioned way of manually searching through paper folders, where it often takes many minutes to find the right folder.Another feature that increases the efficiency of the PDM App is the Incomplete Dossiers overview. Incomplete Dossiers are files to which no Purchase or Sales Invoice has yet been added. The “Incomplete Dossiers” overview can be used to detect Sales Orders Yet to be Invoiced, thereby reducing the chance of Forgotten Invoicing. This overview is also used to detect Purchase Invoices that are still to be received.
Journal entries created with the PDM App are digital in nature and can therefore potentially be automatically imported for posting by ERP Apps, which further increases the efficiency of the PDM App. Of course, this feature is only available when it is supported by the ERP Apps.
The fact that PDM is a WEB App also brings extra efficiency benefits, because certain tasks, like approving Purchase Invoices, can be done over the internet. This prevents bottlenecks in the procurement process since employees who need to approve the Purchase Invoices don't have to be in the office.
But others, like accountants, administrative offices, auditors, and even tax inspectors, can also carry out their work through the internet using the PDM App. Especially for Accountants, this is a huge breakthrough. Even though ERP applications have been usable via the web for many years, this group could still mostly only work from the office because the procurement documents they deal with frequently were not yet accessible online.
Live use of the PDM App from this website
If the PDM app seems too good to be true, we want to remove any doubts by giving you the opportunity to use and review our PDM App LIVE from this website.And to help you with your first live use of the PDM App, we go through two practical exercises below that you can perform live on this website, in 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 want to do this exercise, you can do it as follows:
Click on: "PDM App" at the very top left of this page’s menu and then click on "Login" on the right side of the page to log in to the PDM App. You will then land on a page in the PDM App that displays a list of uploaded documents.
You can now view any document on this list in PDF or UBL with just one click of the corresponding button.
- In the second exercise, we’ll show you how to upload a UBL/PDF Invoice Pair to the PDM App:
To do this, click on "Upload UBL+PDF Docs." in the left menu and then click on “choose files” on the right, select 1 UBL file and 1 PDF file, and then click "Open" to upload the files to the PDM App.
Next, click on "Assignable Documents" in the left menu, which will take you to the same page you visited earlier, but now also lists the documents you uploaded. You can also view these documents in UBL or PDF.
When reviewing the PDM App on this website, don't pay attention to the type or content of the documents in the App, because as you may have noticed, the PDM App on this site is publicly accessible and any visitor can upload any document to the PDM App, so 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 trial with us at the bottom of this page. PDM is new in the e-Invoicing world and can trigger a huge e-Invoicing revolution, but also a massive Environmental and Sustainability revolution, so definitely a good reason to give it a try.
We would advise any government considering making e-Invoicing via Peppol mandatory to first look into PDM and recognize that mandatory e-Invoicing via Peppol might not be necessary when PDM is used, because it optimally supports e-Invoicing via Peppol and at the same time leads to huge efficiency improvements and cost savings for companies.
As a result, companies will voluntarily start using the PDM App and in doing so implicitly support e-Invoicing via Peppol, without being forced to do so.
As a result, companies will voluntarily start using the PDM App and in doing so implicitly support e-Invoicing via Peppol, without being forced to do so.
Evaluation of the PDM App
All the benefits described above, such as Increased efficiency, Space saving, and a Significantly lower environmental impact, still apply when companies use the PDM App Without the obligation to implement e-Invoicing.We therefore enable companies and governments to start evaluating the PDM App now, so they can see for themselves the huge benefits that can be achieved with it and, moreover, be prepared for the possibly mandatory use of e-Invoicing via Peppol.
The PDM App is a Web App that runs on external WebServers, so there’s no need to install any PDM Software 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 in addition, each page within the PDM App provides explanations about the purpose and use of that page and how the different pages are connected, and if there is a need for further explanation, we are of course happy to provide it.
The free trial comes with no obligations; you can stop at any time, but if you decide to continue after 2 months, you simply pick up from where you left off during the trial period.
All you need to do now is request a Trial, after which you will receive a Link from us, which you just need to click to start the evaluation of the PDM App.