eInvoicing – Ontology Requirements Specification Document (ORSD)

Resources

  1. eInvoicing semantic data model (SR EN 16931)

  2. https://docs.peppol.eu/poacc/billing/3.0/bis/

eInvoicing

In the procurement domain, eInvoicing (electronic invoicing) refers to the digital exchange of invoice documents between a Buyer and a Seller. Unlike traditional paper invoices, eInvoices are generated, transmitted, and received in a structured digital format (typically using XML), thus enabling faster and more accurate processing, reducing errors and enhancing compliance with tax regulations.
eInvoicing improves efficiency, enables real-time tracking, and supports better financial management by streamlining the entire invoicing workflow. In the context of eProcurement Ontology (ePO), eInvoicing plays a crucial role in understanding the actual public spending. Modelling the concepts from the eInvoicing in the eProcurement Ontology will enable the creation of data sets containing invoicing information. Such data sets are foreseen in solutions like the Public Procurement Data Space (PPDS).

Roles involved

  • Buyer

  • Seller

  • Payee (if it is different than the Seller)

  • Seller Tax representative The model does not explicitly show who the service provider is, nor are any checks made on who the service provider is.

Activity description

  1. The Seller generates an invoice and the additional supporting documents.

  2. The Seller sends the invoice to the Buyer.

  3. The Buyer receives and processes the invoice.

  4. The Buyer pays the Seller/Payee the amount of the invoice before the due date. *Other administrative flows to be covered (for example penalties, cancelled invoice etc.)

Use case

Use case Description Actors Flow

1. Generating the Invoice

The Seller generates an invoice with the amount the Buyer needs to pay for the received goods, services or supplies.

Seller

The Seller generates an invoice.

2. Sending the Invoice

The Invoice sender sends the invoice to the Buyer to be reviewed and processed by the Buyer.

Seller

The Seller sends the invoice to the Buyer.

3. Receiving and processing the Invoice

The Buyer receives and processes the Invoice so he can pay for the received goods, services or supplies.

Buyer

The Buyer receives and processes the Invoice.

4. Invoice payment

The Buyer pays the Seller the amount of the invoice before the due date

Buyer

The Buyer pays the Seller the amount of the Invoice.

User Stories

Code Role User Story

INV-1

Buyer

As a Buyer, I want to know the Seller’s identification information at the invoice (document) level.

INV-2

Buyer

As a Buyer, I want to know the Payee identification information at invoice (document) level, if different from the Seller.

INV-3

Buyer

As a Buyer I want to know the information about payment at invoice (document) level.

INV-4

Seller

As a Seller, I want to know the Buyer’s financial account information.

INV-5

Buyer

As a Buyer I want to know the information to trace back to the related order at the invoice (document) level.

INV-6

Buyer

As a Buyer I want to know the information to trace back to the related order line at the invoice line level.

INV-7

Buyer

As a Buyer I want to know the information to trace back to the related contract from the invoice (document) level.

INV-8

Buyer

As a Buyer I want to know the information to trace back to the related despatch advice from the invoice (document) level.

INV-9

Buyer

As a Buyer I want to know the information to trace back to the related receipt advice from the invoice (document) level.

Natural Language Statements

  1. An invoice has an unique identifier.

  2. An invoice has a date of issuance.

  3. An invoice can have a payment due date.

  4. An invoice must have a currency of all the amounts (except for the total VAT amount in accounting currency).

  5. An invoice can refer to the procurement project.

  6. An invoice can refer to the contract.

  7. An invoice can refer to an order.

  8. An invoice can refer to a despatch advice.

  9. An invoice can refer to a receipt advice.

  10. An invoice can refer to a lot.

  11. An invoice can have a textual note.

  12. An invoice can have payment terms.

  13. An invoice can refer to previous invoices.

  14. An invoice has to specify information about the Seller.

  15. An invoice has to specify information about the address of the Seller.

  16. An invoice can specify the contact point information of the Seller.

  17. An invoice has to specify information about the Buyer.

  18. An invoice has to specify information about the address of the Buyer.

  19. An invoice can specify the contact point information of the Buyer.

  20. An invoice can specify information about the Payee, if different than the Seller.

  21. An invoice can specify information about the Seller’s tax representative.

  22. An invoice can specify information about where and when the goods and services invoiced are delivered.

  23. An invoice can specify information about it’s delivery period.

  24. An invoice can specify information about the address to which goods and services invoiced were or are delivered.

  25. An invoice can specify the payment instructions.

  26. An invoice can specify the credit transfer payments.

  27. An invoice can specify information about a card used for payment contemporaneous with invoice issuance.

  28. An invoice can specify a direct debit.

  29. An invoice can specify information about allowances applicable to the Invoice as a whole.

  30. An invoice can specify information about charges and taxes other than VAT, applicable to the invoice as a whole.

  31. An invoice has to specify the monetary totals for the invoice.

  32. An invoice has to specify information about VAT breakdown by different categories, rates and exemption reasons.

  33. An invoice may refer to one or many additional supporting documents.

  34. An invoice has to refer to one or many invoice lines.

  35. An invoice line may specify information about it’s delivery period.

  36. An invoice line may specify information about allowances applicable to the Invoice as a whole.

  37. An invoice line may specify information about charges and taxes other than VAT, applicable to the invoice as a whole.

  38. An invoice line has to specify information about the price applied for the goods and services invoiced on the invoice line.

  39. An invoice line has to specify information about the VAT applicable for the goods and services invoiced on the invoice line.

  40. An invoice line has to specify information about the goods and services invoiced on the invoice line.

  41. An invoice line may provide information about properties of the goods and services invoiced.