|
INVOICE
v. 2.1
|
|
|
|
|
|
Problem
Statement |
|
|
The Invoice Message is defined as
requesting payment for goods or services under conditions agreed upon between
the seller and the buyer. It contains the necessary information needed for
payment consisting of parties, items, prices, amounts and quantities.
|
|
|
Objective |
|
|
To supply the detail design of the
(specific) business transaction needed to meet the requirements of the
referenced BRAD(s).
|
|
|
Audience |
|
|
The audience of the
standards would be any participant in the global supply chain. This would
include retailers, manufacturers, service providers and other third parties.
|
|
|
Business
Context
|
|
|
Industry:
All
Geopolitical:
All
Product:
All
Process: Pay
Official
Constraints: European VAT-regulations, Sales tax(?)
Roles: uyer, Seller, Payer, Remit To, Tax Representative,
Ship To
System
Capabilities:
EANCOM, XML
|
|
|
Business
Transaction View
|
|
|
Business
Transaction Use Case
Diagram |
|
|
The diagram below illustrates the parties
and the roles they (can) play in the invoicing and payment processes.
- Amongst others, the invoice transaction
sets the preconditions for the payment process. Therefore the invoice also
contains information about the parties that will become active during the
payment process, i.e. the payer and the payee.
- Furthermore
there might be a third party involved, such as a factor
|
|
|
 |
|
|
Figure 1 – Parties and roles in the invoicing
and payment processes
|
|
|
Use
Case
Description: Invoice
|
|
|
 |
|
|
Figure 2 – Use Case Diagram: Invoice Business
Transaction
|
|
|
|
Use Case ID
|
BTY1
|
|
Use Case Name
|
Invoice
|
|
Use Case Description
|
The invoice
message enables the supplier to send an invoice to the manufacturer related
to delivered goods (in case of non consignment scenario) or to used (consumed)
goods (in case of a consignment scenario)
|
|
Actors (Goal)
|
Buyer: To receive
the invoice
Seller: To send
the invoice
Remit-to: To
receive the invoice
|
|
Performance Goals
|
|
|
Preconditions
|
Invoice created
|
|
Post conditions
|
Invoice received
|
|
Scenario
|
Begins when: the
seller generates an invoice based on the goods deliveries or consumption
reports (in case of consignment).
Continues with:
|
Step #
|
Actor
|
Activity Step
|
|
1.
|
Seller
|
Issue and sends the
invoice to the buyer.
|
|
2.
|
Buyer
|
Receives the
invoice.
|
Ends when:
The
buyer receives the invoice.
|
|
Alternative Scenario
|
Begins when: the
seller generates an invoice based on the goods delivered or consumption
reports (in case of consignment) and the payment is to be made to a remit-to.
Continues with:
|
Step #
|
Actor
|
Activity Step
|
|
1.
|
Seller
|
Issue and sends the invoice to the Buyer and to the Remit-to
|
|
2.
|
Buyer and Remit-to
|
Receive the invoice.
|
Ends when:
The buyer and remit-to receives the invoice.
|
|
Business Transaction Rules
|
N/A
|
|
|
|
Business
Transaction Activity Diagram |
|
|
Not
available |
|
|
Business
Transaction Sequence Diagram |
|
|
Not
available |
|
|
Use
Case
Description: Self Billing Invoice
|
|
|
 |
|
|
Figure 3 – Use Case Diagram: Self Billing
Invoice Business Transaction
|
|
|
|
Use Case ID
|
BTY2
|
|
Use Case Name
|
Self Billing
Invoice
|
|
Use Case Description
|
The Self-billing invoice enables the
buyers to issue the invoice themselves and make payment accordingly. It
includes information on the contract(s) referenced, the line-item quantities
and prices of each line-item delivered as well as the total value of the
invoice. The invoice message can reference multiple contracts, deliveries and
items.
|
|
Actors (Goal)
|
Buyer: To send
the invoice
Seller: To
receive the invoice
|
|
Performance Goals
|
|
|
Preconditions
|
Invoice created
|
|
Post conditions
|
Invoice received
|
|
Scenario
|
Begins when: the buyer issues an invoice
based on the goods deliveries or consumption reports (in case of
consignment).
Continues with:
|
Step #
|
Actor
|
Activity Step
|
|
1
|
Buyer
|
Issue and
sends the invoice to the seller.
|
|
2
|
Seller
|
Receives
the invoice.
|
Ends when:
Seller
receives the invoice.
|
|
Alternative Scenario
|
No Alternative Scenario
|
|
Business Transaction Rules
|
N/A
|
|
|
|
Business
Transaction Activity Diagram |
|
|
Not
available |
|
|
Business
Transaction Sequence Diagram |
|
|
Not
available |
|
|
Use
Case
Description: Credit Invoice
|
|
|
 |
|
|
Figure 4 – Use Case Diagram: Credit Invoice Business
Transaction
|
|
|
|
Use Case ID
|
BTY3
|
|
Use Case Name
|
Invoice
Correction
|
|
Use Case Description
|
The invoice enables the seller to
invoice corrections on previously sent invoices.
|
|
Actors (Goal)
|
Buyer: To receive
the invoice
Seller: To send
the invoice
Remit-to: To
receive the invoice
|
|
Performance Goals
|
|
|
Preconditions
|
Invoice disputed
|
|
Post conditions
|
Credit or Debit
note received.
|
|
Scenario
|
Begins when: In case of
disputes the buyer requests the invoice to be corrected.
Continues with:
|
Step #
|
Actor
|
Activity Step
|
|
1
|
Seller
|
The seller issues and sends an
invoice with the approved corrections.
|
|
2
|
Buyer
|
The buyer receives the invoice.
|
Ends when:
Buyer
receives the credit invoice.
|
|
Alternative Scenario
|
Begins when: In
case the seller needs to make a correction, or in case of disputes the buyer
requests the invoice to be corrected, and the payment is to be made to the
remit-to.
|
Step #
|
Actor
|
Activity Step
|
|
1
|
Seller
|
Issue and
sends the invoice with the approved corrections to the buyer and to the
Remit-to.
|
|
2
|
Buyer
|
Receive the
invoice.
|
Ends when: The
buyer and Remit-to receive the invoice.
|
|
Business Transaction Rules
|
|
1
|
In
case of this transaction the invoice type CREDIT_NOTE or DEBIT_NOTE must be
used.
|
|
|
|
|
Business
Transaction Activity Diagram |
|
|
Not
available |
|
|
Business
Transaction Sequence Diagram |
|
|
Not
available |
|
|
Use
Case
Description: Credit Invoice
|
|
|
 |
|
|
Figure 4 – Use Case Diagram: Self Billing
Invoice Correction Business Transaction
|
|
|
|
Use Case ID
|
BTY6
|
|
Use Case Name
|
Self Billing
Invoice Correction
|
|
Use Case Description
|
The invoice enables the buyer to
invoice corrections on previously sent invoices.
|
|
Actors (Goal)
|
Buyer, Seller
|
|
Performance Goals
|
|
|
Preconditions
|
Invoice disputed.
|
|
Post conditions
|
Credit or debit
note received.
|
|
Scenario
|
Begins when: In case of
disputes the buyer requests the invoice to be corrected.
Continues with:
|
Step #
|
Actor
|
Activity Step
|
|
1
|
Buyer
|
Issues and sends an invoice with the
corrections.
|
|
2
|
Seller
|
Receives the invoice.
|
Ends when:
Seller
receives the debit invoice.
|
|
Alternative Scenario
|
No Alternative Scenario
|
|
Business Transaction Rules
|
|
1
|
In
case of this transaction the invoice type CREDIT_NOTE or DEBIT_NOTE must be
used.
|
|
|
|
|
Business
Transaction Activity Diagram |
|
|
Not
available |
|
|
Business
Transaction Sequence Diagram |
|
|
Not
available |
|
|
|
|
|
Business Document Example |
|
|
Code Lists |
|
|
|
|
|
XML
Signature |
|
|
Security for XML Messages |
|
