D R A F T TEIS Working Paper 47

d r a f t teis working paper 4.7 payment notification business processes and practices -------------------------------- model busin

D R A F T TEIS Working Paper
4.7 Payment Notification
Business Processes and Practices
--------------------------------
Model Business Practices:
[italicized words represent non-ratified language]
2.1.1.me1 [This MBP is suggested for use when the usage sent by the
meter reading entity cannot be used by either the Billing Party or the
Non-Billing Party.] If, upon examination, it is determined that the
usage sent by the meter reading entity cannot be used by an
appropriate party(s) it should be rejected. Rejection, accompanied by
appropriate uniform error code(s), should be communicated via the
appropriate Uniform Electronic Transaction within one (1) Business Day
of receipt of the file to the appropriate party(s).
2.5.1.me2 [This MBP is suggested for use when the Non-Billing Party
cannot use the Billing Party’s invoice transaction (Rate Ready
Ready)]. If, upon examination, it is determined that the Billing
Party’s transaction cannot be used by the Non-Billing Party it should
be rejected. Rejection, accompanied by appropriate uniform error
code(s), should be communicated via the appropriate Uniform Electronic
Transaction within one (1) Business Day of receipt of the file to the
appropriate party(s).
2.6.1.me3 [This MBP is suggested for use when the Supplier cannot use
the Distribution Company’s invoice transaction (Single Retail Supplier
Billing)]. If, upon examination, it is determined that the
Distribution Company’s transaction cannot be used by the Supplier it
should be rejected. Rejection, accompanied by appropriate uniform
error code(s), should be communicated via the appropriate Uniform
Electronic Transaction within one (1) Business Day of receipt of the
file to the appropriate party(s).
2.4.1.7 [The 2nd bullet of this MBP should be modified. This suggested
modification is submitted for consideration]. Hold the transaction for
processing on the next bill and notify the Non-Billing Party within
two (2) Business Days via Uniform Electronic Transaction that the
charges were received late and will be reflected on the next bill.
2.6.1.me4 [This MBP is suggested for the Single Retail Supplier
Billing section]. When the Distribution Company’s files are received,
the Supplier should acknowledge receipt of a file via Uniform
Electronic Transaction within one (1) Business Day of receipt of file.
2.8.1.x10 [This MBP is suggested for the Payment Notification section]
When the customer makes multiple payments on account, each payment
should be separately identified on the payment notification.
[Bk].4.7 payment notification (Collections)
-------------------------------------------
[Bk].4.7.1 Technical Implementation Of Business Process
Related MBP’s: 2.8.1.3, 2.8.1.4, 2.8.1.x10
The Payment Notification/Collections transaction is used in the
‘Assumption of Receivables’ scenario to enable Non-Billing Parties to
identify accounts that are delinquent. It is the communication of all
payments and adjustments made to customer accounts by the Billing
Party. A single Payment Notification transaction is sent each day.
The transaction is sent by the Billing Party. The transaction is
received by the Non-Billing Party.
The transaction is identified by the Collection Unique ID.
Each original Payment Notice header contains Transaction Purpose,
Collection Unique ID, Transaction Date, Total Monetary Amount, Billing
Party ID and name, and Non-Billing Party ID and name.
The Payment Notice detail repeats for each payment being reported.
Multiple payments for a single customer are allowed. Each original
Payment Notice detail contains Customer name and ID, Supplier ID,
Service Type, Assigned line number, transaction reference number for
the amount, and payment/adjustment indicator.
[Bk].4.7.2 Sample Paper Transaction
Payment Notification Header
Transaction Date:
20040413
Collection Unique ID:
04132004TR4877
Trans Purpose:
Original
Billing Party (BP) Name:
Distribute-It Incorporated
BP Entity Common Code ID:
123456789
Non-Billing Party (NBP) Name:
Sell-It Incorporated
NBP Entity Common Code ID:
546897321
Total Monetary Amount
$190.00
Detail
Customer Acct ID:
12345767890
NBP Customer Acct ID:
12345656788
Customer Name
John Doe
Service Type:
Electric
Transaction Reference Number
Dkoejdhkk20040511
Payment / Adjustment Flag:
Payment
Payment Level Allocated Amount::
$100.00
Customer Acct ID:
12345767890
NBP Customer Acct ID:
12345656788
Customer Name
John Doe
Service Type:
Electric
Transaction Reference Number
Dkoejdhkk20040514
Payment / Adjustment Flag:
Payment
Payment Level Allocated Amount::
$90.00
Note: this example shows a notification for a single customer, so the
Total Monetary Amount is $190.00. In the event other customers are to
be reported, the Total Monetary Amount would include those monies
associated with the other customers.
[Bk].4.7.3 Data Dictionary
Item
Current BP Data Elem. Name ID
Description
Use
Conditions
Comments
Group
1
Transaction Purpose [TransPurpose]
Purpose of Transaction
M
[Original, Cancel]
0:ColHdr
2
Collection Unique ID [CollectionID]
Unique Number assigned by the originator of this transaction. This
should be unique over time.
M
0:ColHdr
3
Transaction Date [CollectionDate]
Date this transaction was created by the sender's application system.
M
0:ColHdr
4
Total Monetary Amount Allocated [TotalAmt]
Total Monetary Amount allocated to the non-billing party; Sum of all
detail amounts in this transaction.
M
0:ColHdr
5
Billing Party Name [BillPtyName]
Billing Party's Name
M
1:Biller
6
Billing Party ID [BillPtyID]
BP Entity Common Code ID (DUNS Number or DUNS+4 Number or other
mutually-agreed upon number)
M
1:Biller
7
Non-Billing Party Name [NBPName]
Non-Billing Party's Name
M
1:NonBiller
8
Non-Billing Party ID [NBPID]
NBP Entity Common Code ID (DUNS Number or DUNS+4 Number or other
mutually-agreed upon number)
M
1:NonBiller
9
Billing Party Acct ID [BillPtyAcctID]
Billing Party Customer Account Number
M
1:CustInfo
10
Non-Billing Party Amount Allocated for Account [NBPAmtAlloc]
Total Monetary Amount allocated for this customer account by the
billing party on behalf of the non-billing party or adjustment amount
allocated by the billing party on behalf of the non-billing party.
M
1:CustInfo
11
Non-Billing Party Account ID [NBPAcctID]
NBP Customer Account Number
RBC
Send if previously sent
1:CustInfo
12
Billing Party Old Account ID [BillPtyOldAcctID]
Previous Billing Party Account Number
BC
Send if BPAcctID changed in last 45 days
1:CustInfo
13
Transaction Detail ID [TransDtlID]
Unique Number identifying this customer account record.
M
1:ColDtl
14
Type of Adjustment [AdjustType]
Adjustment reason code
C
Send when Payment/Adjustment code indicates Adjustment
[Adjustment, Insufficient Funds, Returned Items]
1:ColDtl
15
Posting Date [PostDate]
Date the payment or adjustment was posted in the billing party’s
system. Format: CCYYMMDD
M
1:ColDtl
16
Payment Level Allocated Amount [PayLevelAmt]
Individual allocated amount or amounts. If more than one customer
payment was posted to this customer account, this will be repeated for
each customer payment.
M
1:ColDtl
17
Billing Party Customer Name [BillPtyCustName]
Customer name as it appears on the customer bill.
M
1:CustInfo
18
Payment/Adjustment Indicator
Indicates whether the Payment Level Allocated Amount is a payment or
an adjustment
M
[Payment or Adjustment]
19
Service Type
Indicates the type of energy
M
[Gas or Electric]
[Bk].4.7.4 Code Values Dictionary
[??under construction??]
[Bk].4.7.5 X12 EDI Subtab
Data Element Cross Reference to ASC X12
Sample ASC X12 Transaction
ASC X12 Mapping Guidelines
Transaction Set Tables
[Bk].4.8 Application Advice
---------------------------
[Bk].4.8.1 Technical Implementation Of Business Process
Related MBP’s: See Table Below
The Application Advice transaction is the communication between
companies that advises trading partners of success or failure in
certain business processes. The use of the Application Advice UET
enables trading partners to automate processes for common exceptions,
and for common notifications. The following retail energy business
processes use the Application Advice:
Application Advice Use
MBP References
Invalid Usage – This negative acknowledgement, sent by the party
receiving usage, notifies the sender that usage was bad.
2.1.1.me1 (draft)
Invalid Invoice – This negative acknowledgement, sent by the party
receiving an invoice, notifies the party that generated the invoice
that it was bad.
2.4.1.3
2.4.1.6
2.5.1.me2 (draft)
2.6.1.me3 (draft)
Invoice Missed Bill Window – This negative acknowledgement, sent by
the Billing Party, notifies the Non-Billing Party that the invoice was
received after the bill window had expired.
2.4.1.7 (revised)
Invoice Success – This positive acknowledgement, sent by the Billing
Party, notifies the NBP that their invoice was received and placed on
the bill to Customer.
2.4.1.2
2.6.1.me4 (draft)
The UET consists of the following logical groups of data:
*
Envelope
*
Billing Party
*
Non-Billing Party
*
Customer
*
Advice Details, including rejection information where applicable.
Envelope information contains the App Advice Action, the App Advice
Date, and the App Advice ID.
Billing Party group contains Billing Party ID, Billing Party Name,
Billing Party Technical Contact.
Customer group contains Billing Party Account ID, Billing Party Old
Account ID, 1:CustInfo, Customer Name, Non-Billing Party Account ID.
Non-Billing Party group contains Non-Billing Party ID, Non-Billing
Party Name, Non-Billing Party Technical Contact.
Application Advice Detail group contains Bill Due Date, Cross
Reference ID, Date Bill Rendered, Outstanding Balance, Rejection
Level, Rejection Reason, Rejection Text.
[Bk].4.8.2 Sample Paper Transaction
Application Advice Header
Transaction Date:
20040413
App Advice ID:
04132004TR4877
Action Required:
Do Not Resend
Trans Purpose:
Billing Party (BP) Name:
Distribute-It Incorporated
BP Entity Common Code ID:
123456789
BP Technical Contact:
John Distribute
BP Technical Contact Phone:
713.111.1111
Non-Billing Party (NBP) Name:
Sell-It Incorporated
NBP Entity Common Code ID:
546897321
Customer Name:
Joe Customer
Customer Acct ID:
12345767890
NBP Customer Acct ID:
12345656788
Service Type:
Electric
Rejection Level:
Entire Transaction Rejected
Transaction Set Rejected:
810
Rejection Code:
MBW
Rejection Description:
Missed Bill Window
[Bk].4.8.3 Data Dictionary
Trans
Data Elem. Name [ID]
Description
Use
Condition
Comments and Code Value
Group
1
App Advice Action [AppAdvAction]
Indicates whether the receiver of the AA is expected to resend the
transaction or not.
M
[Resend, Do Not Resend, Accept]
0:AAHdr
2
App Advice Date [AppAdvDate]
Date that the data was processed by the sender's application system.
M
0:AAHdr
3
App Advice ID [AppAdvID]
A unique transaction identification number assigned by the originator
of this transaction. This number must be unique over time.
M
0:AAHdr
4
Billing Party ID [BillPtyID]
Billing Party's DUNS Number or DUNS+4 Number
M
1:BillPtyName
5
Billing Party Name [BillPtyName]
Billing Party's Name
M
1:BillPtyName
6
Billing Party Technical Contact [BillPtyContact]
Billing Party Contact information (Telephone, Email, Fax) to resolve
this particular issue.
RBC
[M] if BP sends transaction
1:BillPtyName
7
Billing Party Account ID [BillPtyAcctID]
Billing Party Customer Account Number
M
1:CustInfo
8
Billing Party Old Account ID [BillPtyOldAcctID]
Previous Billing Party Customer Account Number
RBC
1:CustInfo
9
Customer Name [CustName]
Customer Name as it appears on the Customer's Bill
M
1:CustInfo
10
Non-Billing Party Account ID [NBPAcctID]
Non-Billing Party Customer Account Number
RBC
1:CustInfo
11
Non-Billing Party ID [NBPID]
Non-Billing Party's DUNS Number or DUNS+4 Number
M
1:NBPName
12
Non-Billing Party Name [NBPName]
Non-Billing Party's Name
M
1:NBPName
13
Non-Billing Party Technical Contact [NBPContact]
Non-Billing Party Contact information (Telephone, Email, Fax) to
resolve this particular issue.
RBC
[M] if NBP sends transaction
1:NBPName
14
Bill Due Date [BillDueDate]
Date customer payment is due (for Acceptance of a Bill Ready Invoice)
RBC
2:AADtl
15
Cross Reference ID [OrigCrossRefID]
Cross Reference Number from the Invoice or Payment transaction.
M
2:AADtl
16
Date Bill Rendered [BillRendDate]
Date bill was rendered to the customer (for Acceptance of a Bill Ready
Invoice)
RBC
2:AADtl
17
Outstanding Balance [OutstandingBal]
Total outstanding balance that printed on bill for non-billing party
(for Acceptance of a Bill Ready Invoice)
RBC
2:AADtl
18
Rejection Level [RejLev]
Code indicating rejection level (e.g. entire, partial, accepted).
M
[Entire Transaction Rejected, Part of Transaction Rejected, Entire
Transaction Accepted, Item is Rejected
2:AADtl
19
Rejection Reason [RejReason]
Code indicating rejection reason
C
[M] if RejLev indicates reject
2:AADtl
20
Rejection Text [RejText]
Text explaining rejection reason
C
[M] if RejLev indicates reject
2:AADtl
21
Transaction Set [TransSet]
Transaction Number that is being reponded to
M
2:AADtl
[Bk].4.8.4 Code Values Dictionary
[??under construction??]
[Bk].4.8.5 X12 EDI Subtab
Data Element Cross Reference to ASC X12
Sample ASC X12 Transaction
ASC X12 Mapping Guidelines
Transaction Set Tables