|
REQUEST FOR PAYMENT v. 2.0.2 |
|
|
|
|
|
Problem
Statement |
|
|
The Core Request for Payment Message
is defined as requesting payment for goods or services under conditions
agreed upon between the seller and the buyer. It contains only
the necessary information needed for payment consisting of parties,
items, and quantities. Extensions are available to add
functionality and are categorized by business process. For
example, the Core Request for Payment could be used with the Simple
Invoice Ex-tension for data relative to pricing and reference numbers. |
|
|
Objective |
|
|
To supply the detail design of a
request for Payment 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
System
Capabilities:
EAN.UCC
Official
Constraints: None |
|
|
Business
Transaction View
|
|
|
Request for payment is the process of
communicating the request for payment data elements between the seller,
buyer.
|
|
|
Business
Transaction Use Case
Diagram |
|
|
|
|
|
|
|
|
Use Case
Description
|
|
|
| Use
Case Name: |
Add Request for Payment |
| Use
Case Description: |
N/A |
| Actors
(Goal): |
The two general players in the
Request of Payment process are the "seller" and the "buyer".
- Seller :
Manufacturer or supplier of the item or the Remit-to.
- Buyer :
Retailer or distributor of the item.
|
| Preconditions:
|
N/A |
| Postconditions: |
N/A |
| Scenario: |
N/A |
|
|
|
Business
Transaction Activity Diagram |
|
|
Not
available
|
|
|
Business
Transaction Sequence Diagram |
|
|
Not
available |
|
|
|
|
|
TOP |
|
|
|
|
|
|
|
