PEPPOL Transport Infrastructure Agreements in Norway Implementing the PEPPOL Transport Infrastructure in the Norwegian market

Annex 5 Special domain requirements

Annex5-RegionalDomain_v3p0-NO_20121108

PEPPOL Transport Infrastructure Agreements in Norway – Annex 5 Special domain requirements

1.

APPLICABLE DOMAIN

1.1

DEFINITION OF DOMAIN The PEPPOL Authority has been delegated the authority over the implementation and use of the PEPPOL Transport Infrastructure as defined in the PEPPOL Authority Agreement within the following domain:

The country of Norway.

2.

DOMAIN SPECIFIC SERVICES AND SERVICE LEVELS

2.1

ADDITIONAL REQUIREMENTS The PEPPOL Authority will enforce the below stated additional restrictions and criteria on PEPPOL AP Providers and PEPPOL SMP Providers with whom they contract. Disputes related to the content and application of requirements stated in this annex may be broth forward to the Ministry of of Government Administration, Reform and Church Affairs for final arbitration.

2.2

SERVICES RELATED TO THE PROVISION OF A PEPPOL SMP

2.2.1

Business Documents In addition to the defined PEPPOL Business Documents (PEPPOL BIS), the SMP Provider must support the Business Documents (EHF documents) listed in section 2.4 for registration in the SMP.

2.3

SERVICES RELATED TO THE PROVISION OF A PEPPOL AP

2.3.1

Interoperability testing of AP services The PEPPOL AP Provider shall complete interoperability testing of his AP services prior to production. Any such testing shall be agreed with the PEPPOL Authority. Established PEPPOL AP Providers are obliged to contribute to successful interoperability testing with 14 days’ notice.

2.3.2

End-to-end testing between PEPPOL Participants Subject to prior agreement, the PEPPOL AP Provider is expected to contribute to end-to-end testing of message exchange between PEPPOL Participants.

Annex5-RegionalDomain_v3p0-NO_20121108

PEPPOL Transport Infrastructure Agreements in Norway – Annex 5 Special domain requirements

2.3.3

Reporting PEPPOL AP Providers shall report on the number of transactions (i.e. the number of each Document Identifier) sent and/or received to the PEPPOL Regional Authority on a monthly basis. Reports shall be sent by electronic mail to [email protected] no later than 10 working days following the end of the month being reported. A reporting template will be provided.

2.3.4

Business Documents In addition to the defined PEPPOL Business Documents (PEPPOL BIS), the AP Provider shall provide support for the Business Documents listed in section 2.4 (EHF Documents), if requested by the PEPPOL Participants they services. If a PEPPOL Participant requires support for EHF documents listed in section 2.4, the AP Provider must ensure that support for the equivalent PEPPOL BIS is also registered in the relevant PEPPOL SMP.

2.3.5

Validation of Business Documents When acting as a Sending AP, the AP Provider must ensure that business documents received from its customers are confirmed as valid instances according to the applicable rules before accepting them for transport through their AP services, either by providing such services on behalf of their customers or by ensuring that the customer himself has performed such validation.

2.3.6

Registration of Norwegian PEPPOL Participants in SMP The AP Provider must ensure that any Norwegian PEPPOL Participant they service is registered in the PEPPOL SMP nominated by the PEPPOL Authority.

2.3.7

Participation in AP Provider Fora The PEPPOL Authority will establish an AP Provider Fora to supervise operation of the infrastructure, including arbitration of any disputes amongst PEPPOL AP Providers. The AP Provider Fora is anticipated to meet four times per year. The AP Provider shall ensure that it is adequately represented in meetings of the AP Provider Fora.

Annex5-RegionalDomain_v3p0-NO_20121108

Page 3 of 5

PEPPOL Transport Infrastructure Agreements in Norway – Annex 5 Special domain requirements

2.4

ADDITIONAL BUSINESS DOCUMENTS

Business Document Document ID Profile: Standalone Invoice urn:oasis:names:specification:ubl:schema:xsd:InvoiceInvoice according to EHF 2::Invoice##urn:www.cenbii.eu:transaction:biicoretrdm010:ver1.0:#urn:ww w.peppol.eu:bis:peppol4a:ver1.0#urn:www.difi.no:ehf:faktura:ver1::2.0 Profile: Standalone Credit Note according to EHF urn:oasis:names:specification:ubl:schema:xsd:CreditNoteCredit Note according to EHF 2::CreditNote##urn:www.cenbii.eu:transaction:biicoretrdm014:ver1.0:#urn: www.cenbii.eu:profile:biixx:ver1.0#urn:www.difi.no:ehf:kreditnota:ver1::2. 0 Profile: Invoice, Credit Note and Reminder according to EHF urn:oasis:names:specification:ubl:schema:xsd:InvoiceInvoice according to EHF 2::Invoice##urn:www.cenbii.eu:transaction:biicoretrdm010:ver1.0:#urn:ww w.cenbii.eu:profile:biixy:ver1.0#urn:www.difi.no:ehf:faktura:ver1::2.0 urn:oasis:names:specification:ubl:schema:xsd:CreditNoteCredit Note according to EHF 2::CreditNote##urn:www.cenbii.eu:transaction:biicoretrdm014:ver1.0:#urn: www.cenbii.eu:profile:biixy:ver1.0#urn:www.difi.no:ehf:kreditnota:ver1::2. 0 urn:oasis:names:specification:ubl:schema:xsd:ReminderReminder according to EHF 2::Reminder##urn:www.cenbii.eu:transaction:biicoretrdm017:ver1.0:#urn: www.cenbii.eu:profile:biixy:ver1.0#urn:www.difi.no:ehf:purring:ver1::2.0

Annex5-RegionalDomain_v3p0-NO_20121108

Process ID urn:www.cenbii.eu:profile:bii04:ver1.0

urn:www.cenbii.eu:profile:biixx:ver1.0

urn:www.cenbii.eu:profile:biixy:ver1.0

Page 4 of 5

PEPPOL Transport Infrastructure Agreements in Norway – Annex 5 Special domain requirements

3.

SIGNATURE On the basis that the PEPPOL AP Provider has signed a PEPPOL AP Provider Agreement with a PEPPOL Authority, the provisions contained in this Annex 5 shall apply to any services offered within the domain defined in § 1.1.

Place and date

For the PEPPOL Authority Name Position Signature

For the PEPPOL AP Provider

Olav Kristiansen Senior Adviser

*****

Annex5-RegionalDomain_v3p0-NO_20121108

Page 5 of 5