| supports |
|
Visma |
Increased adoption of eInvoices |
| supports |
|
Power office |
Increased adoption of eInvoices |
| supports |
|
Fiken |
Increased adoption of eInvoices |
| supports |
|
Fiken |
Adoption of eReceipts |
| supports |
|
Xledger |
Increased adoption of eInvoices |
| supports |
|
Microsoft Dynamics |
Increased adoption of eInvoices |
| supports |
|
DNB |
Increased adoption of eInvoices |
| supports |
|
DNB |
Adoption of eReceipts |
| supports |
|
Regnskaps Norge IKT-forum |
Increased adoption of eInvoices |
| supports |
|
Zirius |
Adoption of eReceipts |
| |
|
1. Use of digital business documents |
1.1 Adoption of digital business documents |
| |
|
1.1 Adoption of digital business documents |
A. Adoption of eInvoices: Complete the implementation of eInvoice standard and extend regulations beyond public procurement |
| |
|
1.1 Adoption of digital business documents |
C. Adoption of eReceipts |
| |
|
Exchanging business documents |
1.1 Adoption of digital business documents |
| |
|
SME |
Exchanging business documents |
| |
|
A. Adoption of eInvoices: Complete the implementation of eInvoice standard and extend regulations beyond public procurement |
1.1.1 Compliance with CEN semantic model EN-16931 for invoices |
| |
|
A. Adoption of eInvoices: Complete the implementation of eInvoice standard and extend regulations beyond public procurement |
1.1.2 Complete the implementation of the OpenPeppol BIS specification (send and receive invoices) |
| |
|
A. Adoption of eInvoices: Complete the implementation of eInvoice standard and extend regulations beyond public procurement |
1.1.5 Incentives for receiving eInvoices - Authorities send only eInvoices if the receiver is able to receive them |
| |
|
A. Adoption of eInvoices: Complete the implementation of eInvoice standard and extend regulations beyond public procurement |
1.1.7 Seller has the option to only send / sends (by system default) an eInvoice, if the receiver is able to receive them |
| |
|
A. Adoption of eInvoices: Complete the implementation of eInvoice standard and extend regulations beyond public procurement |
1.1.3 Market the eInvoice feature to their customers. E.g. recommend the sending of an eInvoice if the customer is able to receive it |
| |
|
A. Adoption of eInvoices: Complete the implementation of eInvoice standard and extend regulations beyond public procurement |
1.1.4 Communicate and promote the business case to the SMEs |
| |
|
A. Adoption of eInvoices: Complete the implementation of eInvoice standard and extend regulations beyond public procurement |
1.1.6 Create incentives in when governments require payments e.g. extending the payment deadline for businesses that can receive an eInvoice |
| |
|
A. Adoption of eInvoices: Complete the implementation of eInvoice standard and extend regulations beyond public procurement |
1.1.8 Buyer can demand an eInvoice |
| |
|
A. Adoption of eInvoices: Complete the implementation of eInvoice standard and extend regulations beyond public procurement |
1.1.9 Making eInvoicing mandatory in the Nordics |
| |
|
Regulators |
1.1.5 Incentives for receiving eInvoices - Authorities send only eInvoices if the receiver is able to receive them |
| |
|
Regulators |
1.1.7 Seller has the option to only send / sends (by system default) an eInvoice, if the receiver is able to receive them |
| |
|
Regulators |
A. Adoption of eInvoices: Complete the implementation of eInvoice standard and extend regulations beyond public procurement |
| |
|
Regulators |
1.1.4 Communicate and promote the business case to the SMEs |
| |
|
Regulators |
1.1.8 Buyer can demand an eInvoice |
| |
|
Regulators |
1.1.9 Making eInvoicing mandatory in the Nordics |
| |
|
Regulators |
1.1.6 Create incentives in when governments require payments e.g. extending the payment deadline for businesses that can receive an eInvoice |
| |
|
Business systems |
1.1.1 Compliance with CEN semantic model EN-16931 for invoices |
| |
|
Business systems |
A. Adoption of eInvoices: Complete the implementation of eInvoice standard and extend regulations beyond public procurement |
| |
|
Business systems |
1.1.2 Complete the implementation of the OpenPeppol BIS specification (send and receive invoices) |
| |
|
Business systems |
1.1.3 Market the eInvoice feature to their customers. E.g. recommend the sending of an eInvoice if the customer is able to receive it |
| |
|
C. Adoption of eReceipts |
1.1.11 Implement eReceipt in OpenPeppol network, connecting to the PoS (B2x) |
| |
|
C. Adoption of eReceipts |
1.1.10 Standardize the content of eReceipts |
| |
|
C. Adoption of eReceipts |
1.1.12 Implement receiving eReceipts in Business systems |
| |
|
C. Adoption of eReceipts |
1.1.13 Implement mapping and routing from national eReceipts systems to the OpenPeppol network |
| |
|
C. Adoption of eReceipts |
1.1.14 Mobile payment services sends eReceipts (B2B) |
| |
|
C. Adoption of eReceipts |
1.1.15 Implement eReceipts for all PoS-systems (are able create them) |
| |
|
C. Adoption of eReceipts |
1.1.16 Have an eReceipt follow the Credit/debit card transaction flow |
| |
|
Business systems |
C. Adoption of eReceipts |
| |
|
Business systems |
1.1.12 Implement receiving eReceipts in Business systems |
| |
|
Standardisation organisations |
1.1.10 Standardize the content of eReceipts |
| |
|
Standardisation organisations |
C. Adoption of eReceipts |
| |
|
Point of sales systems |
C. Adoption of eReceipts |
| |
|
Point of sales systems |
1.1.15 Implement eReceipts for all PoS-systems (are able create them) |
| |
|
Point of sales systems |
1.1.14 Mobile payment services sends eReceipts (B2B) |
| |
|
Regulators |
C. Adoption of eReceipts |
| |
|
Regulators |
1.1.13 Implement mapping and routing from national eReceipts systems to the OpenPeppol network |
| |
|
OpenPeppol |
C. Adoption of eReceipts |
| |
|
OpenPeppol |
1.1.11 Implement eReceipt in OpenPeppol network, connecting to the PoS (B2x) |
| |
|
Receive invoice |
1.1 Adoption of digital business documents |
| |
|
Receive invoice |
Customer (Buyer) |
| |
|
Send invoice |
1.1 Adoption of digital business documents |
| |
|
Send invoice |
Vendor/Supplier (Seller) |
| |
|
Send receipt from POS |
Vendor/Supplier (Seller) |
| |
|
Send receipt from POS |
1.1 Adoption of digital business documents |
| |
|
Receive receipt |
Customer (Buyer) |
| |
|
Receive receipt |
1.1 Adoption of digital business documents |
| |
|
Increased adoption of eInvoices |
1.1 Adoption of digital business documents |
| |
|
Adoption of eReceipts |
1.1 Adoption of digital business documents |
| supports |
|
Norwegian regulation "Forskrift om bokføring" |
Adoption of eReceipts |
| |
|
D. Adoption of eOrders, eCatalogs |
1.1.18 Implement in OpenPeppol BIS Orders and Order confirmations messages in for businesses |
| |
|
D. Adoption of eOrders, eCatalogs |
1.1.17 Compliant with eOrdering BIS format (based on the on the CEN WS/BII Profile 28 Ordering) |
| |
|
D. Adoption of eOrders, eCatalogs |
1.1.19 Compliant with eCatalog BIS format |
| |
|
D. Adoption of eOrders, eCatalogs |
1.1.20 Implement in OpenPeppol BIS eCatalog for Business systems |
| |
|
Business systems |
1.1.17 Compliant with eOrdering BIS format (based on the on the CEN WS/BII Profile 28 Ordering) |
| |
|
Business systems |
D. Adoption of eOrders, eCatalogs |
| |
|
Business systems |
1.1.18 Implement in OpenPeppol BIS Orders and Order confirmations messages in for businesses |
| |
|
Business systems |
1.1.19 Compliant with eCatalog BIS format |
| |
|
Business systems |
1.1.20 Implement in OpenPeppol BIS eCatalog for Business systems |
| |
|
Receive order |
Vendor/Supplier (Seller) |
| |
|
Receive order |
1.1 Adoption of digital business documents |
| |
|
Create and send order |
Customer (Buyer) |
| |
|
Create and send order |
(Purchase) Order |
| |
|
Create and send order |
1.1 Adoption of digital business documents |
| |
|
Send order confirmation |
Vendor/Supplier (Seller) |
| |
|
Send order confirmation |
1.1 Adoption of digital business documents |
| |
|
Receive order confirmation |
Customer (Buyer) |
| |
|
Receive order confirmation |
1.1 Adoption of digital business documents |
