Illinois CPWB. Electronic Data Interchange. Implementation Guide For
|
|
- Julie Paul
- 5 years ago
- Views:
Transcription
1 Illinois Implementation Guide For Electronic Data Interchange CPWB Transaction Set ANSI ASC X12 Version UCB/POR Remittance Advice Version 1.2 CPWG 820 UCB/POR Remittance Advice Version 1.2 Page 1 August 3, 2011
2 Summary of Changes January 6, 2009 Version 1.0 October 24, 2009 Version 1.1 August 3, 2011 Version 1.2 Initial Release. Change Control #010 Corrected examples at the end of the guide to show the appropriate transaction number in the ST segment. They previously showed ST*814*0001 but were fixed to show ST*820*0001. Change Control #032 Clarified ComEd s current implementation of negative remittance advice. CPWG 820 UCB/POR Remittance Advice Version 1.2 Page 2 August 3, 2011
3 Uses for the 820 UCB Remittance Advice RES Interaction with Financial Institution Implementation Notes This 820 UCB/POR Remittance Advice Implementation Guideline will be used to transmit Remittance information from the Utility to the RES for Utility Consolidated Billing/Purchase of Receivables (UCB/POR). This transaction set is not used for the Single Bill Option (SBO) where the RES bills for the utility charges. Current practice of sending the payment and remittance together through the banking system still apply for this bill option. Each 820 UCB Remittance Advice may include multiple accounts. Payment The utilities will use one of three options to remit payment through the banking system and will include the financial re-association trace number in the following fields: o CCD+ - Addenda Record o CTX (EDI 820) RMR02 Element o Wire Transfer OBI Field The financial re-association trace number will also be included in the 820 UCB Remittance Advice in the TRN field. The RES will use this number, along with the total dollar amount to match the funds with the remittance details. The RES will be receiving lump sum payments via their chosen Financial Institution that will reflect the identifier used to match the funds with the details provided in the Remittance transaction. The RES needs to work with its Financial Institution to determine how that information will be provided. Penny Test It is recommended that the utilities send a penny test to the RES to ensure the proper bank accounts are set up as part of the testing and certification process. The Penny Test is preferable to a zero dollar pre-note because a pre-note does not always flow all the way through the banking systems to the receiver s customer system. Instructions for Handling a Negative Remittance Ameren: The Payment Instruction and 820 UCB Remittance Advice will be sent on a daily basis and will include all applicable adjustments as outlined in the guides as long as the adjustments are not larger than the payments. o If the adjustments are larger than the payments, creating a negative remittance advice, Ameren will hold the adjustment that is causing the payment to be negative and continue to process the remaining payments. Ameren will continue to attempt to include the negative amount in its daily payments for a period of 5 days, at which time if the cannot satisfy the amount, they will contact the RES to make arrangements to have the amount repaid to the Ameren. o If the adjustments cause the payments to be zero, Ameren may go send the Remittance Advice without the obligation to make a zero payment. ComEd: The Payment Instruction and 820 UCB Remittance Advice will be sent on a daily basis and will include all applicable adjustments as outlined in the guides as long as the adjustments are not larger than the payments. o If the adjustments are larger than the payments (creating a negative remittance advice), the remittance advice will be transmitted with a zero in the BPR02. o The BPR02 will either contain the total positive amount being moved through the ACH system, which will add up to all your detail line CPWG 820 UCB/POR Remittance Advice Version 1.2 Page 3 August 3, 2011
4 Cross Reference between 867, 810, 820 items (RMR04s), or zero if the total of the detail line items is negative. o If the total of the detail line items is negative in the Day 1 remittance advice, ComEd nets out the negative amount from the Day 2 remittance advice, if the total payment amount in Day 2 is larger than the negative amount. In this case the BPR02 total payment amount in the Day 2 remittance advice will not equal the sum of the Day 2 RMR04s. CPWG has established a Cross Reference Number to tie together the 867, 810 and 820 transactions for UCB/POR, where appropriate. o The 867 initiates the Cross Reference Number in the BPT02 field o The Cross Reference Number then appears in the 810 Invoice (Bill Ready and Rate Ready) in the BIG05. o The Cross Reference Number is finally provided in the 820 UCB Remittance Advice transaction in the REF*6O segment for UCB/POR. RMR Loop Multiple RMR Loops may be sent in each 820 UCB Remittance Advice transaction but each Loop may contain information on only a single transaction amount for a single account/service point. Financial Reassociation Trace Number The RMR Loop contains several REF segments used to further identify the account, such as RES Account Number, Cross Reference Number, Service Point Identifier and Invoice Number. In order to assist the RES with identifying the payment, the Trace Number on the 820 UCB Remittance Advice will be formatted as follows: o Positions 1-2 will contain the literal CP o Positions 3-11 will contain the Utility DUNS Number o Positions will be used by the Utility to uniquely identify this payment (e.g., date/time stamp or sequential number). It is not required to use all 30 characters. This number will appear in the TRN02 of the 820 UCB Remittance Advice and the appropriate reference on the payment, including: o Addenda Record (CCD+) o RMR02 (CTX) o OBI Field (Wire Transfer) Rejection An 820 UCB Remittance Advice transaction will contain remittance information for more than one customer account. 824 Application Advice transaction(s) may be used to reject one or more payments at the account level or may be used to reject the entire 820 transaction. In general, an 820 UCB Remittance Advice transaction may be rejected when it contains validation or syntax errors or required data segments/elements are missing or invalid. Instructions in the 824 Application Advice Implementation Guide should be reviewed for further details. Implementation of Service Point (Ameren) Ameren Mass Market o The Service Point Number will be sent in REF*LU. Ameren Non-Mass Market o The Service Point Number will be sent in REF*LU. CPWG 820 UCB/POR Remittance Advice Version 1.2 Page 4 August 3, 2011
5 820 Payment Order/Remittance Advice Functional Group ID=RA Introduction: This Draft Standard for Trial Use contains the format and establishes the data contents of the Payment Order/Remittance Advice Transaction Set (820) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used to make a payment, send a remittance advice, or make a payment and send a remittance advice. This transaction set can be an order to a financial institution to make a payment to a payee. It can also be a remittance advice identifying the detail needed to perform cash application to the payee's accounts receivable system. The remittance advice can go directly from payer to payee, through a financial institution, or through a third party agent. Heading: Pos. Seg. Req. Loop Notes and No. ID Name Des. Max.Use Repeat Comments M 010 ST Transaction Set Header M 1 M 020 BPR Beginning Segment for Payment M 1 Order/Remittance Advice 035 TRN Trace O 1 c1 LOOP ID - N1 >1 070 N1 Name O 1 c2 Detail: Pos. Seg. Req. Loop Notes and No. ID Name Des. Max.Use Repeat Comments LOOP ID - ENT >1 010 ENT Entity O 1 n1 LOOP ID - RMR >1 150 RMR Remittance Advice Accounts Receivable Open O 1 c3 Item Reference 170 REF Reference Identification O >1 Summary: Pos. Seg. Req. Loop Notes and No. ID Name Des. Max.Use Repeat Comments M 010 SE Transaction Set Trailer M 1 Transaction Set Notes 1. The ENT loop is for vendor or consumer third party consolidated payments. Transaction Set Comments 1. The TRN segment is used to uniquely identify a payment order/remittance advice. 2. The N1 loop allows for name/address information for the payer and payee which would be utilized to address remittance(s) for delivery. 3. Loop RMR is for open items being referenced or for payment on account. CPWG 820 UCB/POR Remittance Advice Version 1.2 Page 5 August 3, 2011
6 Segment: ST Transaction Set Header Position: 010 Loop: Level: Heading Usage: Mandatory Max Use: 1 Purpose: To indicate the start of a transaction set and to assign a control number Syntax Notes: Semantic Notes: 1 The transaction set identifier (ST01) is used by the translation routines of the interchange partners to select the appropriate transaction set definition (e.g., 810 selects the Invoice Transaction Set). Comments: Notes: Required ST~820~ Must Use ST Transaction Set Identifier Code M ID 3/3 Code uniquely identifying a Transaction Set 820 Payment Order/Remittance Advice Must Use ST Transaction Set Control Number M AN 4/9 Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set CPWG 820 UCB/POR Remittance Advice Version 1.2 Page 6 August 3, 2011
7 Segment: BPR Beginning Segment for Payment Order/Remittance Advice Position: 020 Loop: Level: Heading Usage: Mandatory Max Use: 1 Purpose: To indicate the beginning of a Payment Order/Remittance Advice Transaction Set and total payment amount, or to enable related transfer of funds and/or information from payer to payee to occur Syntax Notes: 1 If either BPR06 or BPR07 is present, then the other is required. 2 If BPR08 is present, then BPR09 is required. 3 If either BPR12 or BPR13 is present, then the other is required. 4 If BPR14 is present, then BPR15 is required. 5 If either BPR18 or BPR19 is present, then the other is required. 6 If BPR20 is present, then BPR21 is required. Semantic Notes: 1 BPR02 specifies the payment amount. 2 When using this transaction set to initiate a payment, all or some of BPR06 through BPR16 may be required, depending on the conventions of the specific financial channel being used. BPR06 and BPR07 relate to the originating depository financial institution (ODFI). 3 BPR08 is a code identifying the type of bank account or other financial asset. 4 BPR09 is the account of the company originating the payment. This account may be debited or credited depending on the type of payment order. 5 BPR12 and BPR13 relate to the receiving depository financial institution (RDFI). 6 BPR14 is a code identifying the type of bank account or other financial asset. 7 BPR15 is the account number of the receiving company to be debited or credited with the payment order. 8 BPR16 is the date the originating company intends for the transaction to be settled (i.e., Payment Effective Date). 9 BPR17 is a code identifying the business reason for this payment. 10 BPR18, BPR19, BPR20 and BPR21, if used, identify a third bank identification number and account to be used for return items only. 11 BPR20 is a code identifying the type of bank account or other financial asset. Comments: Notes: Required BPR~I~ ~C~ACH~~~~~~~~~~~~ Must Use BPR Transaction Handling Code M ID 1/2 Code designating the action to be taken by all parties I Remittance Information Only Must Use BPR Monetary Amount M R 1/18 Monetary amount Will contain the total positive amount (including zero) being moved through the banking system, which will add up to all your detail line items (RMRs). For ComEd, when negative payments (adjustments) to individual accounts cannot be offset by the total payment amount on the day the transaction is sent, the BPR02 will not equal the sum of the RMRs. On days when that occurs, no payment is sent and the next day the adjustment is netted out of the total payment, which creates a mismatch between the BPR02 and the sum of the RMR04 elements. Please see the Implementation Notes for handling of negative remittance. Must Use BPR Credit/Debit Flag Code M ID 1/1 Code indicating whether amount is a credit or debit CPWG 820 UCB/POR Remittance Advice Version 1.2 Page 7 August 3, 2011
8 C Credit Must Use BPR Payment Method Code M ID 3/3 Code identifying the method for the movement of payment instructions ACH Automated Clearing House (ACH) FWT Federal Reserve Funds/Wire Transfer - Nonrepetitive Must Use BPR Date O DT 8/8 Date expressed as CCYYMMDD Payer's intended settlement date. This date may be different from the actual settlement date, which is the date your bank is credited by the Federal Reserve for this item. CPWG 820 UCB/POR Remittance Advice Version 1.2 Page 8 August 3, 2011
9 Segment: TRN Trace Position: 035 Loop: Level: Heading Usage: Optional Max Use: 1 Purpose: To uniquely identify a transaction to an application Syntax Notes: Semantic Notes: 1 TRN02 provides unique identification for the transaction. 2 TRN03 identifies an organization. 3 TRN04 identifies a further subdivision within the organization. Comments: Notes: Required In order to assist the RES with identifying the payment, the Trace Number on the UCB Remittance Advice will be formatted as follows: o Positions 1-2 will contain the literal "CP" o Positions 3-11 will contain the Utility DUNS Number o Positions will be used by the Utility to uniquely identify this payment (e.g., date/time stamp or sequential number). It is not required to use all 30 characters. This number will appear in the TRN02 of the UCB Remittance Advice and the appropriate reference on the payment, including: o Addenda Record (CCD+) o RMR02 (CTX) o OBI Field (Wire Transfer) This number is used to tie together the payment and the remittance, which must equal except in the rare occasion that it is necessary to send a negative remittance advice with no associated funds transfer. TRN~3~CP Must Use TRN Trace Type Code M ID 1/2 Code identifying which transaction is being referenced 3 Financial Reassociation Trace Number Must Use TRN Reference Identification M AN 1/30 Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier Unique Identifier that is also sent in the financial transaction, used to reassociate the remittance advice to the payment. CPWG 820 UCB/POR Remittance Advice Version 1.2 Page 9 August 3, 2011
10 Segment: N1 Name (Payer) Position: 070 Loop: N1 Optional Level: Heading Usage: Optional Max Use: 1 Purpose: To identify a party by type of organization, name, and code Syntax Notes: 1 At least one of N102 or N103 is required. 2 If either N103 or N104 is present, then the other is required. Semantic Notes: Comments: 1 This segment, used alone, provides the most efficient method of providing organizational identification. To obtain this efficiency the "ID Code" (N104) must provide a key to the table maintained by the transaction processing party. Notes: 2 N105 and N106 further define the type of entity in N101. Required N1~PR~UTILITY NAME~1~ Must Use N Entity Identifier Code M ID 2/3 Code identifying an organizational entity, a physical location, property or an individual PR Payer Utility Must Use N Name X AN 1/60 Free-form name Payer Name Must Use N Identification Code Qualifier X ID 1/2 Code designating the system/method of code structure used for Identification Code (67) 1 D-U-N-S Number, Dun & Bradstreet 9 D-U-N-S+4, D-U-N-S Number with Four Character Suffix Must Use N Identification Code X AN 2/80 Code identifying a party or other code Payer DUNS or DUNS+4 CPWG 820 UCB/POR Remittance Advice Version 1.2 Page 10 August 3, 2011
11 Segment: N1 Name (Payee) Position: 070 Loop: N1 Optional Level: Heading Usage: Optional Max Use: 1 Purpose: To identify a party by type of organization, name, and code Syntax Notes: 1 At least one of N102 or N103 is required. 2 If either N103 or N104 is present, then the other is required. Semantic Notes: Comments: 1 This segment, used alone, provides the most efficient method of providing organizational identification. To obtain this efficiency the "ID Code" (N104) must provide a key to the table maintained by the transaction processing party. Notes: 2 N105 and N106 further define the type of entity in N101. Required N1~PE~RES NAME~9~ IL00 Must Use N Entity Identifier Code M ID 2/3 Code identifying an organizational entity, a physical location, property or an individual PE Payee Retail Electric Supplier (RES) Must Use N Name X AN 1/60 Free-form name Payee Must Use N Identification Code Qualifier X ID 1/2 Code designating the system/method of code structure used for Identification Code (67) 1 D-U-N-S Number, Dun & Bradstreet 9 D-U-N-S+4, D-U-N-S Number with Four Character Suffix Must Use N Identification Code X AN 2/80 Code identifying a party or other code Payee DUNS or DUNS+4 CPWG 820 UCB/POR Remittance Advice Version 1.2 Page 11 August 3, 2011
12 Segment: ENT Entity Position: 010 Loop: ENT Optional Level: Detail Usage: Optional Max Use: 1 Purpose: To designate the entities which are parties to a transaction and specify a reference meaningful to those entities Syntax Notes: 1 If any of ENT02 ENT03 or ENT04 is present, then all are required. 2 If any of ENT05 ENT06 or ENT07 is present, then all are required. 3 If either ENT08 or ENT09 is present, then the other is required. Semantic Notes: Comments: 1 This segment allows for the grouping of data by entity/entities at or within a master/masters. A master (e.g., an organization) can be comprised of numerous subgroups (e.g., entities). This master may send grouped data to another master (e.g., an organization) which is comprised of one or more entities. Groupings are as follows: (1) Single/Single: Only ENT01 is necessary, because there is a single entity (the sending master) communicating with a single entity (the receiving master). (2) Single/Multiple: ENT05, ENT06, and ENT07 would be used to identify the entities within the receiving master. The sending master is a single entity, so no other data elements need be used. (3) Multiple/Single: ENT02, ENT03, and ENT04 would be used to identify the entities within the sending master. The receiving master is a single entity, so no other data elements need be used. (4) Multiple/Multiple: ENT02, ENT03, and ENT04 would be used to identify the entities within the sending master. ENT05, ENT06, and ENT07 would be used to identify the entities within the receiving master. This segment also allows for the transmission of a unique reference number that is meaningful between the entities. Notes: Required ENT~1 Must Use ENT Assigned Number O N0 1/6 Number assigned for differentiation within a transaction set CPWG 820 UCB/POR Remittance Advice Version 1.2 Page 12 August 3, 2011
13 Segment: RMR Remittance Advice Accounts Receivable Open Item Reference Position: 150 Loop: RMR Optional Level: Detail Usage: Optional Max Use: 1 Purpose: To specify the accounts receivable open item(s) to be included in the cash application and to convey the appropriate detail Syntax Notes: 1 If either RMR01 or RMR02 is present, then the other is required. 2 If either RMR07 or RMR08 is present, then the other is required. Semantic Notes: 1 If RMR03 is present, it specifies how the cash is to be applied. 2 RMR04 is the amount paid. 3 RMR05 is the amount of invoice (including charges, less allowance) before terms discount (if discount is applicable) or debit amount or credit amount of referenced items. 4 RMR06 is the amount of discount taken. 5 RMR08, if present, represents an interest penalty payment, amount late interest paid, or amount anticipation. Comments: 1 Parties using this segment should agree on the content of RMR01 and RMR02 prior to initiating communication. 2 If RMR03 is not present, this is a payment for an open item. If paying an open item, RMR02 must be present. If not paying a specific open item, RMR04 must be present. 3 RMR05 may be needed by some payees to distinguish between duplicate reference numbers. Notes: Required RMR~12~ ~PR~297.00~300.00~3.00 RMR~12~ ~AJ~-95.00~-94.05~.95~CS~ Must Use RMR Reference Identification Qualifier X ID 2/3 Code qualifying the Reference Identification 12 Billing Account Utility Account Number Must Use RMR Reference Identification X AN 1/30 Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier Utility Account Number Must Use RMR Payment Action Code O ID 2/2 Code specifying the accounts receivable open item(s), if any, to be included in the cash application. AJ Adjustment Adjustment to an amount remitted in a prior period for purchased receivables. PR Progress Payment POR Payment Must Use RMR Monetary Amount O R 1/18 Monetary amount POR Payment or Adjustment The sum of the amounts sent in all RMR04 elements must equal the amount in BPR02 and the amount sent in the financial transaction except when BPR02 contains a zero (in the case of a negative remittance advice). For for ComEd, when negative payments (adjustments) to individual accounts cannot be offset by the total payment amount on the day the transaction is sent. No payment is sent on that day and the next day the adjustment is netted out of the total payment, which creates a mismatch between the BPR02 and sum of RMR04 CPWG 820 UCB/POR Remittance Advice Version 1.2 Page 13 August 3, 2011
14 elements. POR Payment: The amount in RMR04 is the net amount of the payment to the RES for the customer receivable purchased by the Utility for the account indicated in RMR02 for the current period. This amount is the sum of the amounts sent in RMR05 (Invoice Amount) and RMR06 (Discount Amount). Adjustment: The amount in the RMR04 element, which may be a credit or a debit, is an adjustment to a previously transmitted POR Payment. Each adjustment must be sent in a separate RMR Loop and the RMR07 and RMR08 elements are required to identify the nature of the adjustment. The amount must be signed if negative. Dep RMR Monetary Amount O R 1/18 Monetary amount Invoiced Amount POR Payments: Required. The amount is the Invoice Amount, which is the total debit or credit billed to the customer for the RES charges for the current period. This amount will equal the amount sent in the TDS segment of the associated 810. Adjustments: Required if the discount was applied to the adjustment amount. The amount is the total debit or credit billed to the customer for the RES for the Adjustment or the total Disputed Charges. The amount must be signed if negative. Dep RMR Monetary Amount O R 1/18 Monetary amount Discount Amount POR Payment: Required. The amount is the Discount Amount, which is the total amount of the discount applied to the current period invoiced amount (sent in RMR05) and is typically negative. Zero is a valid value for the discount amount. Adjustment: Required if the discount was applied to the adjustment amount. The amount must be signed if negative. Dep RMR Adjustment Reason Code X ID 2/2 Code indicating reason for debit or credit memo or adjustment to invoice, debit or credit memo, or payment 26 Invoice Cancelled Cancellation of RES Charges 72 Authorized Return Disputed RES Charges CS Adjustment Dep RMR Monetary Amount X R 1/18 Monetary amount Adjustment Amount Required when RMR03=AJ, otherwise not used. The amount in the RMR08, if populated, will always be the same as the amount in RMR04 and must be signed if negative. CPWG 820 UCB/POR Remittance Advice Version 1.2 Page 14 August 3, 2011
15 Segment: REF Reference Identification (RES Account Number) Position: 170 Loop: RMR Optional Level: Detail Usage: Optional Max Use: >1 Purpose: To specify identifying information Syntax Notes: 1 At least one of REF02 or REF03 is required. 2 If either C04003 or C04004 is present, then the other is required. 3 If either C04005 or C04006 is present, then the other is required. Semantic Notes: 1 REF04 contains data relating to the value cited in REF02. Comments: Notes: Required if provided on the 814 Enrollment or Change transaction. REF~11~ Must Use REF Reference Identification Qualifier M ID 2/3 Code qualifying the Reference Identification 11 Account Number RES Account Number Must Use REF Reference Identification X AN 1/30 Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier RES Account Number CPWG 820 UCB/POR Remittance Advice Version 1.2 Page 15 August 3, 2011
16 Segment: REF Reference Identification (Cross Reference Number) Position: 170 Loop: RMR Optional Level: Detail Usage: Optional Max Use: >1 Purpose: To specify identifying information Syntax Notes: 1 At least one of REF02 or REF03 is required. 2 If either C04003 or C04004 is present, then the other is required. 3 If either C04005 or C04006 is present, then the other is required. Semantic Notes: 1 REF04 contains data relating to the value cited in REF02. Comments: Notes: Required for POR Payments Optional for Adjustments Unique cross reference number used to associate metering information (867MU or 867IU transaction), billing information (810 transaction) and payment information (820 transaction) for a specific billing period for an account. Must Use REF Reference Identification Qualifier M ID 2/3 Code qualifying the Reference Identification 6O Cross Reference Number Unique cross-reference number to link 867, 810, and 820. The cross-reference number originally transmitted in the BPT02, and the BIG05. Must Use REF Reference Identification X AN 1/30 Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier Cross Reference Number CPWG 820 UCB/POR Remittance Advice Version 1.2 Page 16 August 3, 2011
17 Segment: REF Reference Identification (Service Point Identifier) Position: 170 Loop: RMR Optional Level: Detail Usage: Optional Max Use: >1 Purpose: To specify identifying information Syntax Notes: 1 At least one of REF02 or REF03 is required. 2 If either C04003 or C04004 is present, then the other is required. 3 If either C04005 or C04006 is present, then the other is required. Semantic Notes: 1 REF04 contains data relating to the value cited in REF02. Comments: Notes: Ameren Mass Market: Required for POR Payments, Optional for Adjustments Ameren Non-Mass Market: Required for POR Payments, Optional for Adjustments ComEd: Not Used Ameren currently uses an 8-digit Service Point number. All 8 digits, including leading zeros must be provided. REF~LU~ Must Use REF Reference Identification Qualifier M ID 2/3 Code qualifying the Reference Identification LU Location Number Service Point Identifier Must Use REF Reference Identification X AN 1/30 Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier Service Point Identifier CPWG 820 UCB/POR Remittance Advice Version 1.2 Page 17 August 3, 2011
18 Segment: REF Reference Identification (Invoice Number) Position: 170 Loop: RMR Optional Level: Detail Usage: Optional Max Use: >1 Purpose: To specify identifying information Syntax Notes: 1 At least one of REF02 or REF03 is required. 2 If either C04003 or C04004 is present, then the other is required. 3 If either C04005 or C04006 is present, then the other is required. Semantic Notes: 1 REF04 contains data relating to the value cited in REF02. Comments: Notes: Required for POR Payments Optional for Adjustments REF~IK~ Must Use REF Reference Identification Qualifier M ID 2/3 Code qualifying the Reference Identification IK Invoice Number Must Use REF Reference Identification X AN 1/30 Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier Invoice Number from the BIG02 element of the 810 Rate Ready or 810 Bill Ready transaction. CPWG 820 UCB/POR Remittance Advice Version 1.2 Page 18 August 3, 2011
19 Segment: SE Transaction Set Trailer Position: 010 Loop: Level: Summary Usage: Mandatory Max Use: 1 Purpose: Syntax Notes: Semantic Notes: To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending (SE) segments) Comments: 1 SE is the last segment of each transaction set. Notes: Required SE~917~ Must Use SE01 96 Number of Included Segments M N0 1/10 Total number of segments included in a transaction set including ST and SE segments Must Use SE Transaction Set Control Number M AN 4/9 Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set CPWG 820 UCB/POR Remittance Advice Version 1.2 Page 19 August 3, 2011
20 Example 1 POR Payments Scenario: Utility makes 3 POR payments to a RES for charges incurred the month prior. The discount rate is 1%. ST*820*0001 BPR*I*628.65*C*ACH************ TRN*3*CP N1*PR*UTILITY*1* N1*PE*SUPPLIER*9* IL00 ENT*1 RMR*12* *PR*297*300*3 REF*11* REF*6O* REF*LU* Ameren Only REF*IK* RMR*12* *PR*217.8*220*2.2 REF*11* REF*6O* REF*LU* Ameren Only REF*IK* RMR*12* *PR*113.85*115*1.15 REF*11* REF*6O* REF*LU* Ameren Only REF*IK* SE*22*0001 Example 2 Negative Adjustment for Cancel/Rebill Scenario: Utility makes 1 POR payment and adjusts 1 account. The discount rate for the both the payment and adjustment is 1%. The adjustment is the result of a cancel/rebill for this account and therefore can carry the Cross Reference Number of the 867 Cancel transaction. There is no associated 810 Cancel, so the Invoice Number is not included. ST*820*0001 BPR*I*183.15*C*ACH************ TRN*3*CP N1*PR*UTILITY*1* N1*PE*SUPPLIER*9* IL00 ENT*1 RMR*12* *PR*297*300*3 REF*11* REF*6O* REF*LU* Ameren Only REF*IK* RMR*12* *AJ* *-115*1.15*26* REF*11* REF*6O* CANCEL REF*LU* Ameren Only SE*16*0001 CPWG 820 UCB/POR Remittance Advice Version 1.2 Page 20 August 3, 2011
21 Example 3 Negative Adjustment for RES Initiated Cancel Scenario: Utility makes 1 POR payment and adjusts 1 account because RES sent an 810 Reversal (BIG08=17) to the Utility. The Utility has already made payment for the reversed invoice and therefore reverses the payment. The discount rate is 1%. Since the adjustment is a result of a RES initiated Reversal, the Invoice Number is available. ST*820*0001 BPR*I*183.15*C*ACH************ TRN*3*CP N1*PR*UTILITY*1* N1*PE*SUPPLIER*9* IL00 ENT*1 RMR*12* *PR*297*300*3 REF*11* REF*6O* REF*LU* Ameren Only REF*IK* RMR*12* *AJ* *-115*1.15*26* REF*11* REF*6O* REF*LU* Ameren Only REF*IK* CANCEL SE*17*0001 CPWG 820 UCB/POR Remittance Advice Version 1.2 Page 21 August 3, 2011
820 Payment Order/Remittance Advice
820 Payment Order/Remittance Advice Functional Group=RA This Draft Standard for Trial Use contains the format and establishes the data contents of the Payment Order/Remittance Advice Transaction Set (820)
More informationPayment Order/Remittance Advice
820 Payment Order/Remittance Advice Functional Group=RA This Draft Standard for Trial Use contains the format and establishes the data contents of the Payment Order/Remittance Advice Transaction Set (820)
More informationPayroll Deducted and Other Group Premium Payment for Insurance Products
004010X061 820 GROUP PREMIUM PAYMENT FOR INSURANCE PRODUCTS National Electronic Data Interchange Transaction Set Implementation Guide Payroll Deducted and Other Group Premium Payment for Insurance Products
More information835 Health Care Claim Payment/Advice
835 Health Care Claim Payment/Advice Functional Group ID=HP Introduction: This document contains the format and establishes the data contents of the Health Care Claim Payment/Advice Transaction Set (835)
More information820 Payment Order/Remittance Advice
820 Payment Order/Remittance Advice HIPAA/V5010X218: 820 Payment Order/Remittance Advice, Louisiana Medicaid Version: 1.0 Created: 9/20/2011 The purpose of this guide is to clarify the usage of the X12
More information- - - Virginia. Implementation Standard. For Electronic Data Interchange. March 21, 2003 Open Access Version 2.3
Virginia Implementation Standard For Electronic Data Interchange - - - TRANSACTION SET 814 Reinstatement Request and Response Ver/Rel 004010 VA 814 Reinstatement 1 814r-stan2-3.doc August 27, 2001 Version
More informationCheck Payment UCS & X12
820 Heading: Check Payment 005010 UCS & X12 Functional Group=RA Pos Id Segment Name Req Max Use Repeat Notes Usage 0200 BPR Beginning Segment for M 1 Must use Payment Order/Remittance Advice 0350 TRN Trace
More informationPREMIUM PAYMENTS TRANSACTIONS 820 (004010X061)
PREMIUM PAYMENTS TRANSACTIONS 820 (00400X06) SECTION I - NARRATIVE 820 Payment Order/Remittance Advice - Header The header section of the 820 file contains information related to the total payment. Examples
More informationImplementation Guideline
Pennsylvania New Jersey Delaware Maryland Implementation Guideline For Electronic Data Interchange TRANSACTION SET 568 Collections Ver/Rel 004010 568 Collections (4010) 1 IG568v6-16-1.docx Table of Contents
More informationPGW EDI Implementation Guideline
PGW EDI Implementation Guideline For Transaction Set 810 LDC (Rate Ready) Invoice X12 v4010 810 LDC Invoice Rev 1.5 February 4, 2016 Contents Revision Notes:... 3 810 LDC Invoice X12 Structure... 4 Segment:
More informationNew Jersey. Gas Implementation Guideline
New Jersey Gas Implementation Guideline For Electronic Data Interchange TRANSACTION SET 810 LDC Consolidated Bill Ver/Rel 004010 810 LDC Consolidated Bill (4010) 1 IG810v_1-6.doc Summary of Changes...4
More informationImplementation Guideline
Pennsylvania New Jersey Delaware Maryland Implementation Guideline For Electronic Data Interchange TRANSACTION SET 824 Application Advice Ver/Rel 004010 824 Application Advice (4010) 1 IG824v4-01x Table
More informationImplementation Guideline
Pennsylvania New Jersey Delaware Maryland Implementation Guideline For Electronic Data Interchange TRANSACTION SET 824 Application Advice Ver/Rel 004010 824 Application Advice (4010) 1 E EDI 824 Application
More informationPremium Payment Submission Companion Guide. to the. ANSI X (version 4010x61) implementation guide
Premium Payment Submission Companion Guide to the Premium Payment Submission ANSI X 820 (version 4010x61) implementation guide Document History Revision date Revision Commentary May 2003 1.0 Creation date
More informationMERCURY MARINE EFT (ACH) IMPLEMENTATION GUIDE (FINANCIAL EDI)
MERCURY MARINE EFT (ACH) IMPLEMENTATION GUIDE (FINANCIAL EDI) The following guide is intended to facilitate the user in implementing Electronic Data Interchange transactions with Mercury Marine. Every
More informationImplementation Guideline
Pennsylvania New Jersey Delaware Maryland Implementation Guideline For Electronic Data Interchange TRANSACTION SET 814 Advance Notice of Intent to Drop Request and Response Ver/Rel 004010 814 Advance Notice
More information814 General Request, Response or Confirmation
814 General Request, Response or Confirmation Introduction: Functional Group ID=GE This Draft Standard for Trial Use contains the format and establishes the data contents of the General Request, Response
More informationMortgagee Coverage Notification, Billing and Payment of Insurance Premium. Electronic Data Interchange Transaction Set Implementation Guide
Electronic Data Interchange Transaction Set Implementation Guide 811/820 MORTGAGEE COVERAGE NOTIFICATION, BILLING AND PAYMENT OF INSURANCE PREMIUM Implementation Guide Version 2.0 (3030) 1 1. State 2.
More informationChapter 10 Companion Guide 835 Payment & Remittance Advice
Chapter 10 Companion Guide 835 Payment & Remittance Advice This companion guide for the ANSI ASC X12N 835 Healthcare Claim PaymentAdvice transaction has been created for use in conjunction with the ANSI
More informationCostco Wholesale EDI TRADING PARTNER PROFILE REMITTANCE ADVICE
EDI TRADING PARTNER PROFILE REMITTANCE ADVICE Contacts: Misti Reed Supervisor (425) 313-8677 mreed@costco.com Heidi Dirkes EDI Coordinator Vendors A-F (425) 313-6868 hdirkes@costco.com Sue Crippe EDI Coordinator
More informationHEALTHpac 835 Message Elements
Version 1.2 April 21, 2003 1 Table of Contents 1 INTRODUCTION...3 1.1 GENERAL COMMENTS...3 1.2 RELATED DOCUMENTS...4 2 835 MESSAGE ELEMENTS...5 2.1 HEADER - INITIAL...5 2.2 PAYER IDENTIFICATION...6 2.3
More informationEyeMed Vision Care. HEALTHCARE BENEFIT ELIGIBILITY INQUIRY Companion Document to ASC X12N 270 (004010X092)
HEALTHCARE BENEFIT ELIGIBILITY INQUIRY Companion Document to ASC X12N 270 (004010X092) Welcome to EyeMed Vision Care s HIPAA TCS implementation process. We have developed this guide to assist you in preparing
More informationDelivery/Return Base Record UCS & X12
894 Heading: Delivery/Return Base Record 005010 UCS & X12 Functional Group=DX Delivery/Return Base Record - 894 Pos Id Segment Name Req Max Use Repeat Notes Usage 0200 G82 Delivery/Return Base Record M
More informationFarmers Group, Inc. Implementation Standards for EDI Documents
Farmers Group, Inc Implementation Standards for EDI Documents ASC X12 Transaction Set 811 Version 3050 Consolidated Service Invoice/Statement Daily Auto Notification/Billing Created 10/04/2005 Revised
More informationVirginia Implementation Standard. For Electronic Data Interchange. TRANSACTION SET 867 Product Transfer and Resale Report Monthly Usage Ver/Rel
Virginia Implementation Standard For Electronic Data Interchange - - - TRANSACTION SET 867 Product Transfer and Resale Report Monthly Usage Ver/Rel 004010 VA 867 Monthly Usage (4010) 1 867mu-stan2-3.doc
More informationImplementation Guideline
Pennsylvania New Jersey Delaware Maryland Implementation Guideline For Electronic Data Interchange TRANSACTION SET 867 Ver/Rel 004010 867 (4010) 1 Table of Contents January 9, 2002 Summary of Changes...4
More informationEDS Systems Unit. Companion Guide 820 MCE Capitation Payment Transaction
EDS Systems Unit I N D I A N A H E A L T H C O V E R A G E P R O G R A M S Companion Guide 820 MCE Capitation Payment Transaction L I B R A R Y R E F E R E N C E N U M B E R : C L E L 1 0 0 1 7 [ A S C
More informationIAT Modifications Proposed Modifications to the Rules August 15, 2012 ISSUE #1 - IDENTIFICATION OF COUNTRY NAMES WITHIN IAT ENTRIES
Proposed Modifications to the Rules ISSUE #1 - IDENTIFICATION OF COUNTRY NAMES WITHIN IAT ENTRIES APPENDIX THREE ACH RECORD FORMAT SPECIFICATIONS Subpart 3.2.2 Glossary of Data Elements Originator Country
More informationHP S ystems U nit. Companion Guide: 820 MCE Capitation Payment Transaction
HP S ystems U nit I N D I A N A H E A L T H C O V E R A G E P R O G R A M S Companion Guide: 820 MCE Capitation Payment Transaction L I B R A R Y R E F E R E N C E N U M B E R : C L E L 1 0 0 1 7 [ A S
More informationU.S. CUSTOMS AND BORDER PROTECTION AUTOMATED CLEARINGHOUSE CREDIT PROGRAM PAYER PROCEDURES
U.S. CUSTOMS AND BORDER PROTECTION AUTOMATED CLEARINGHOUSE CREDIT PROGRAM PAYER PROCEDURES Automated Clearinghouse (ACH) Credit is an electronic payment process that allows your company to transmit their
More informationStandard Companion Guide
Standard Companion Guide Refers to the Implementation Guide Based on X12 Version 005010X221A1 Health Care Claim Payment/Advice (835) Companion Guide Version Number: 2.0 February 2018 Page 1 of 13 CHANGE
More informationNPI Utilization in Healthcare EFT Transactions March 5, 2012
WEDI Strategic National Implementation Process (SNIP) WEDI SNIP Transactions Workgroup EFT Subworkgroup EFT NPI Utilization Issue Brief NPI Utilization in Healthcare EFT Transactions March 5, 2012 Workgroup
More informationBenefit Enrollment and Maintenance
004010X095 834 BENEFIT ENROLLMENT AND MAINTENANCE National Electronic Data Interchange Transaction Set Implementation Guide Benefit Enrollment and Maintenance 834 ASC X12N 834 (004010X095) May 2000 MAY
More informationTax. Third (TPP. d Party. Payments 7/29/2013. All Rights Reserved
Third d Party Tax Payments (TPP P) Banking Convention Standardized Formatting for Remittance Information in Third Party Tax Paymen nt Addenda Record 7/29/2013 2013 National Automated Clearing Housee Association
More informationTax Payment (TXP) Banking Convention
Tax Payment (TXP) Banking Convention A Guide for Formatting Electronic Tax Payments NACHA s Banker s EDI Council Revised December 2012 1996, revised 2012 National Automated Clearing House Association 13450
More informationCREDIT CARD BULK PROVIDER REQUIREMENTS
CREDIT CARD BULK PROVIDER REQUIREMENTS 1 Nature of Changes Date/Version Page Paragraph Change Description 3/13/2012 v0 76-81, Annual Updates 115 3/13/2012 v0 64, 65, Added table footnotes 73, 82 3/13/2012
More informationACH Credit a transaction through the ACH network originated to pay a receiver (deposit funds into an account).
ACH Glossary For additional information, refer to the current National Automated Clearing House Association (NACHA) Rules or contact us at 205-469-4000 or 888-902-4227. ABA Number also known as Routing/Transit
More information835 Health Care Claim Payment/ Advice Companion Guide
835 Health Care Claim Payment/ Advice Companion Guide Standard Companion Guide Transaction Information Instructions related to Transactions based on ASC X12 Implementation Guides, version 005010 Companion
More information835 Health Care Claim Payment/Advice LA Medicaid
835 Health Care Claim Payment/Advice LA edicaid HIPAA/V5010X221A1/835: 835 Health Care Claim Payment/Advice Version: 1. 1 Created 10/21/2011 Revision 9/23/2013 Author: Publication: EDI Department LA edicaid
More informationNACHA Operating Rules Update: Healthcare Payments
NACHA Operating Rules Update: Healthcare Payments J. Steven Stone, AAP Senior Vice President PNC Bank Chuck Floyd, AAP Manager of Education Viewpointe, LLC 2 Disclaimer This course is intended to provide
More information- - - Virginia. Implementation Standard. For Electronic Data Interchange. March 21, 2003 Open Access Version 2.3
Virginia Implementation Standard For Electronic Data Interchange - - - TRANSACTION SET 814 Enrollment Request and Response Ver/Rel 004010 VA 814 Enrollment 1 814e-stan2-3.doc Summary of Changes August
More informationRefers to the Technical Reports Type 3 Based on ASC X12 version X279A1
HIPAA Transaction Standard Companion Guide Refers to the Technical Reports Type 3 Based on ASC X12 version 005010X279A1 270/271 Health Care Eligibility Benefit Inquiry and Response Companion Guide Version
More informationACH Originator Resources
ACH Originator Resources Revised 06-2017 Table of Contents Introduction...3 ACH Originator Responsibilities...4 ACH Glossary...5 Notification of Change (NOC) Codes... Error! Bookmark not defined. ACH Return
More information810 FM Non-Food/Jewelry Invoice
810 FM Non-Food/Jewelry Invoice Functional Group=IN Applies to: Fred Meyer Group Refer to Program & Requirements for Fred Meyer Non-Food/Jewelry Group for EDI Invoice Business & Technical Requirements
More information837 Health Care Claim: Institutional
837 Health Care Claim: Institutional HIPAA/V4010X096A1/837: 837 Health Care Claim: Institutional Version: Final Modified: 11/29/2006 Current: 11/29/2006 837I4010a1.ecs 1 For internal use only 837I4010a1.ecs
More informationElectronic Payment Instructions for the Hospital Quality Care Assessment
Electronic Payment Instructions for the Hospital Quality Care Assessment Overview Detailed instructions for electronic payment are provided in the following sections: ACH Introduction Page 1 ACH Bank Account
More informationPersonal Health Record Data Transfer Between Health Plans (275)
005010271 Based on ASC 12 275, Version 005010 Standards for Electronic Data Interchange Personal Health Record Data Transfer Between Health Plans (275) VERSION 3.1.4 BASED ON ASC 12 275 VERSION 005010
More informationElectronic Funds Transfer Guide. Automated Clearing House (ACH) Credit Method Application Form and Instructions Included
Electronic Funds Transfer Guide Automated Clearing House (ACH) Credit Method Application Form and Instructions Included INTRODUCTION NOTE - Effective with reports for the quarter ending March 31, 2008
More information(For sweep accounts.) Total dividends earned as of the last day of the statement period. (For line of credit.) Amount advanced today.
Contents: Glossary A B C D E F G H I J K L M N O P Q R S T U V W X Y Z A Top Account Reconciliation Plan (ARP) Accrued Dividends Month to Date ACH Addenda Advance Today Automated Clearing House (ACH) ARP
More informationEyeMed Vision Care. BENEFIT ENROLLMENT AND MAINTENANCE Companion Document to ASC X12N 834 (004010X095A1)
BENEFIT ENROLLMENT AND MAINTENANCE Companion Document to ASC X12N 834 (004010X095A1) Welcome to EyeMed Vision Care s HIPAA TCS implementation process. We have developed this guide to assist you in preparing
More informationBusiness to Business Payments
presents Business to Business Payments The CCD and CTX Entry Disclaimer 2011 NEACH. All rights reserved. This material is not intended to provide any warranties or legal advice, and is intended for educational
More informationCopyright 2017 Lakeland Bank. All rights reserved. This material is proprietary to and published by Lakeland Bank for the sole benefit of its
ACH Originator Guide Copyright 2017 Lakeland Bank. All rights reserved. This material is proprietary to and published by Lakeland Bank for the sole benefit of its clients. Reproduction, distribution, disclosure
More informationFuel Systems Inc Purchase Order Ver ANSI ASC X Fuel Systems Inc. 850 Purchase Order VERSION: ANSI ASC X
Fuel Systems Inc 850 Purchase Order VERSION: ANSI ASC X12 4010 Created: October 19, 2007 Modified: July 23, 2008 850 v4010 Purchase Order.doc Page 1 of 18 850 Purchase Order Functional Group=PO This standard
More informationEDS SYSTEMS UNIT. Pre-Release Companion Guide: 835 Remittance Advice Transaction
EDS SYSTEMS UNIT I N D I A N A H E A L T H C O V E R A G E P R O G R A M S Pre-Release Companion Guide: 835 Remittance Advice Transaction L I B R A R Y R E F E R E N C E N U M B E R : C L E L 1 0 0 1 9
More information835 Payment Advice NPI Dual Receipt
Chapter 5 NPI Dual Receipt This Companion Document explains the from Anthem Blue Cross and Blue Shield (Anthem) during the 835 National Provider Identifier (NPI) Dual Receipt period. The ANSI ASC X12N,
More informationCAQH Committee on Operating Rules for Information Exchange (CORE) Phase III CORE 370 EFT & ERA Reassociation (CCD+/835) Rule version 3.0.
Table of Contents 1 Background Summary... 3 1.1 Affordable Care Act Mandates... 3 1.2 Existing Standards and Operating Rules... 4 1.2.1 ASC X12 v5010 X12 835 Health Care Claim Payment/Advice... 4 1.2.2
More informationGeisinger Health Plan
Geisinger Health Plan Companion Guide for the 834 Benefit Enrollment and Maintenance Refers to the Implementation Guides Based on X12 version 005010X220 Version Number: 1.01 Revised, October 28, 2010 1
More informationHIPAA Summit ACA Operating Rules Update. NACHA The Electronic Payments Association
HIPAA Summit ACA Operating Rules Update March 28, 2012 Janet O. Estep NACHA The Electronic Payments Association 2 NACHA The Electronic Payments Association Non-profit rule-making entity Author of the NACHA
More information05/04/07 Invoice Invoice X12. Pos Id Segment Name Req Max Use Repeat Notes Usage 020 BIG Beginning Segment for M 1 Must use
810 Heading: Invoice 004010 X12 Functional Group=IN Pos Id Segment Name Req Max Use Repeat Notes Usage 020 BIG Beginning Segment for M 1 Must use Invoice 050 REF Reference Identification O 12 Used LOOP
More informationFallon Health. 835 Fallon Health Companion Guide. Health Care Payment Advice. 835 Companion Guide
Fallon Health Health Care Payment Advice 835 Companion Guide Refers to the ASC X12N 835 Technical Report Type 3 Guide (Version 005010X221A1) Companion Guide Version Number: 1.3 October 2017 1 Disclosure
More informationMatching Payments to Services Delivered
Matching Payments to Services Delivered What Every Provider and Health Plan Should Expect, and What Every Trading Partner Should Deliver Tuesday, November 10 th, 2015 2:00-3:00pm ET 2015 CAQH, All Rights
More informationImplementation Guideline
Pennsylvania New Jersey Delaware Maryland Implementation Guideline For Electronic Data Interchange TRANSACTION SET 867 Monthly Usage Ver/Rel 004010 867 Monthly Usage (4010) 1 Table of Contents Summary
More informationGet on First Base with Same-Day ACH Risks
Get on First Base with Same-Day ACH Risks EASTPAY 2016 Information Interchange Mary Gilmeister, AAP, NCP President WACHA Fred Laing, II, AAP, CCM, NCP President UMACHA 1 Disclaimer NACHA owns the copyright
More informationStandard Companion Guide
Standard Companion Guide Refers to the Implementation Guide Based on X12 Version 005010X221A1 Health Care Claim Payment/Advice (835) Companion Guide Version Number: 1.0 December 17, 2013 1 Change Log Version
More informationHUMANA 835 ERA PRE ENROLLMENT INSTRUCTIONS 61101
HUMANA 835 ERA PRE ENROLLMENT INSTRUCTIONS 61101 HOW LONG DOES PRE ENROLLMENT TAKE? Up to 21 business days WHERE SHOULD I SEND THE FORMS? Send the forms to Emdeon via fax to 615 231 4843 or email to batchenrollment@emdeon.com
More informationCareOregon (Remittance Advice) Information Guide
CareOregon 5010 835 (Remittance Advice) Information Guide This document is not intended as a comprehensive 5010 companion guide. The objectives of this document are: 1. To clarify what information is needed
More informationStandards and Operating Rules for Electronic Funds Transfer and Claims Payment/Remittance Advice. 2010, Data Interchange Standards Association
Standards and Operating Rules for Electronic Funds Transfer and Claims Payment/Remittance Advice 2010, Data Interchange Standards Association Overview Our Role and expertise in the Remittance Advice Transaction
More informationHIPAA Transaction Health Care Claim Payment/Advice Standard Companion Guide (835, X221A1)
(underwritten by Dean Health Plan) HIPAA Transaction Health Care Claim Payment/Advice Standard Companion Guide (835, 005010X221A1) Instructions related to Transactions based on ASC X12 Implementation Guides,
More informationCoordinating Healthcare Operating Rules: Financial Services & Healthcare
Coordinating Healthcare Operating Rules: Financial Services & Healthcare 1 Stuart Hanson VP, Healthcare LOB Manager Steve Stone Sr. Vice President 2 Agenda Background Challenges with Acceptance Operating
More informationUSER'S GUIDE ELECTRONIC DATA INTERFACE 834 TRANSACTION. Capital BlueCross EDI Operations
ELECTRONIC DATA INTERFACE 834 TRANSACTION Capital BlueCross EDI Operations USER'S GUIDE Health care benefit programs issued or administered by Capital BlueCross and/or its subsidiaries, Capital Advantage
More informationGlossary of ACH Terms
ABA NUMBER See Routing Number/Transit ACH - The Automated Clearing House network ACCESS DEVICE - A card, code, or other means of access to a consumer s account that may be used to initiate electronic funds
More informationStandard Companion Guide
Standard Companion Guide Refers to the Implementation Guide Based on X12 Version 005010X279A1 Health Care Eligibility Benefit Inquiry and Response (270/271) Companion Guide Version Number 3.0 November
More information810 LDC Consolidated Bill Ver/Rel Implementation Guideline. Pennsylvania New Jersey Delaware Maryland. For Electronic Data Interchange
Pennsylvania New Jersey Delaware Maryland Implementation Guideline For Electronic Data Interchange TRANSACTION SET 810 LDC Consolidated Bill Ver/Rel 004010 810 LDC Consolidated Bill (4010) 1 IG810LDCv6-2x
More informationReturns File Format. Revised 6/10/2010 Page 1 of 8
Returns File Format Revised 6/10/2010 Page 1 of 8 Col Name Data Type Length Description 1 Collection Level Alpha/Numeric 50 Collection service such as guarantee, charge back to merchant, NOC s, etc. 2
More informationBest Practice Recommendation for. Processing & Reporting Remittance Information ( v) Version 3.93
Best Practice Recommendation for Processing & Reporting Remittance Information (835 5010v) Version 3.93 For use with ANSI ASC X12N 835 (005010X222) Health Care Claim Payment/Advice Technical Report Type
More informationCANADIAN PAYMENTS ASSOCIATION ASSOCIATION CANADIENNE DES PAIEMENTS RULE E3 RULES APPLICABLE TO ELECTRONIC DATA INTERCHANGE TRANSACTIONS
CANADIAN PAYMENTS ASSOCIATION ASSOCIATION CANADIENNE DES PAIEMENTS RULE E3 RULES APPLICABLE TO ELECTRONIC DATA INTERCHANGE TRANSACTIONS 2017 CANADIAN PAYMENTS ASSOCIATION 2017 ASSOCIATION CANADIENNE DES
More informationACH Primer for Healthcare. A Guide to Understanding EFT Payments Processing
ACH Primer for Healthcare A Guide to Understanding EFT Payments Processing ACH Primer for Healthcare A Guide to Understanding EFT Payments Processing 2011 NACHA The Electronic Payments Association All
More informationThis is designed to provide those who are not familiar with the ACH Network with a basic understanding of the fundamentals of the ACH Network.
This is designed to provide those who are not familiar with the ACH Network with a basic understanding of the fundamentals of the ACH Network. The ACH Network is a batch processing, store and forward system.
More informationKansas Department of Revenue 915 SW Harrison Street Topeka, KS ED-100 G (Rev. 07/2004)
ED-100 G (Rev. 07/2004) Kansas Department of Revenue 915 SW Harrison Street Topeka, KS 66626 Table of Contents 1. TRANSACTION SET 811 SEGMENT STRUCTURE ANSI X12 V.3050...2 2. TRANSACTION SET 811 MAPPING
More informationPhase III CORE EFT & ERA Operating Rules Approved June 2012
Phase III CORE EFT & ERA Operating Rules Approved June 2012 Phase III CORE 350 Health Care Claim Payment/Advice (835) Infrastructure Rule. 2 CORE v5010 Master Companion Guide Template.... 11 Phase III
More information835 Health Care Claim Payment/Advice
Companion Document 835 835 Health Care Claim Payment/Advice Basic Instructions This section provides information to help you prepare for the ANSI ASC X12 Health Care Claim Payment/Advice (835) transaction.
More information834 Template 1 of 16. Comments and Additional. Info
834 Template 1 of 16 HDR Header (not really a loop) Reference ISA 1 M Required ISA Interchange Control Header R M The ISA is a fixed record length segment and all positions within each of the data elements
More informationANSI ASC X12N 277P Pending Remittance
ANSI ASC X12N 277P Pending Remittance Acute Care COMPANION GUE For Non-covered Transactions April 29, 2016 Texas Medicaid & Healthcare Partnership Page 1 of 19 Revision Date: 5/5/2016 Table of Contents
More informationBMW VDA REMADV Version 1.0 Remittance advice message
Message Implementation Guideline BMW VDA 4988 - REMADV Version 1.0 Remittance advice message based on REMADV Remittance advice message UN D.04A Version: V1.0 Issue date: 09.01.2019 Author: BMW Document
More informationImplementation Guideline
Pennsylvania New Jersey Delaware Maryland Implementation Guideline For Electronic Data Interchange TRANSACTION SET 814 Change Request and Response Ver/Rel 004010 814 Change (4010) 1 E EDI 814 Change ReqResp
More informationCARPENTERS COMBINED FUNDS ELECTRONIC FUNDS TRANSFER (EFT) AUTHORIZATION FORM Please print or type all required information.
CARPENTERS COMBINED FUNDS ELECTRONIC FUNDS TRANSFER (EFT) AUTHORIZATION FORM Please print or type all required information. Employer Information: Employer Number (if known): Employer Name: Address: City,
More informationOregon Department of Revenue. Estimated Corporation Excise and Income Tax. ACH Credit Electronic Funds Transfer. Program Guide
Oregon Department of Revenue Estimated Corporation Excise and Income Tax ACH Credit Electronic Funds Transfer Program Guide Included inside is an application form and instructions 150-102-042 (Rev. 9-03)
More informationEyeMed Vision Care. HEALTH CARE CLAIM: PROFESSIONAL Companion Document to ASC X12N 837 (004010X098A1)
HEALTH CARE CLAIM: PROFESSIONAL Companion Document to ASC X12N 837 (004010X098A1) Welcome to EyeMed Vision Care s HIPAA TCS implementation process. We have developed this guide to assist you in preparing
More informationVendor Specifications 837 Professional Claim ASC X12N Version for. State of Idaho MMIS
Vendor Specifications 837 Professional Claim ASC X12N Version 5010 for State of Idaho MMIS Date of Publication: 12/8/2017 Document Number: TL427 Version: 11.0 Revision History Versio Date Author Action/Summary
More information834 Benefit Enrollment and Maintenance
Companion Document 834 834 Benefit Enrollment and Maintenance Basic Instructions This section provides information to help you prepare for the ANSI ASC X12.84, Benefit Enrollment and Maintenance (834)
More informationImplementation Guideline
Pennsylvania New Jersey Delaware Maryland Implementation Guideline For Electronic Data Interchange TRANSACTION SET 867 Monthly Usage Ver/Rel 004010 867 Monthly Usage (4010) 1 Table of Contents Summary
More informationOBLIGATIONS OF ORIGINATORS
OBLIGATIONS OF ORIGINATORS Revised September 2017 Legal Framework for ACH ACH Operating Rules- NACHA A series of contract law that is made binding by agreements. Regulation E Carries out the purpose of
More informationThe Alignment of Financial Services and Healthcare:
The Alignment of Financial Services and Healthcare: The Electronic Funds Transfer (EFT) Standard And Healthcare Operating Rules for EFT and Electronic Remittance Advice (ERA) Thursday, November 29, 2012
More informationBenefit Enrollment and Maintenance (834) Change Log:
ASC X12 Standards for Electronic Data Interchange Technical Report Type 3 Benefit Enrollment and Maintenance (834) Change Log 005010-007030 SEPTEMBER 2016 SEPTEMBER 2016 1 Intellectual Property Accredited
More information834 Benefit Enrollment and Maintenance
New Mexico Health Insurance Exchange (NMHIX) 834 Benefit Enrollment and Maintenance Standard Companion Guide Transaction Information Version 1.5 06/17/2014 PREFACE This Companion Guide to the v5010 Accredited
More informationKey Information in Electronic Report Delivery (ERD) Reports - NOC
Key Information in Electronic Report Delivery (ERD) Reports - NOC Participant Account Number ERD Report Filename - RTA2014231000008.TXT Batch # - 2014231000008 Printed on Sep 08, 2014 at 12:18 PM Transaction
More informationVersion RC2.0. Best Practices for 403(b) and Related Retirement Plans. Remittance and Census Data Elements
Best Practices for 403(b) and Related Retirement Plans Remittance and Census Data Elements Version RC2.0 May 31, 2012 Effective Date February 1, 2013 Best Practices for 403(b) and Related Retirement Plans
More information5010 Upcoming Changes:
HP Systems Unit I N D I A N A H E A L T H C O V E R A G E P R O G R A M S 5010 Upcoming Changes: 270/271 Eligibility Benefit Transaction Based on Version 5, Release 1 ASC X12N 005010X279 Revision Information
More informationASC X12 N WEB Page Information TG 2 WG 3 FAQ (Frequently Asked Questions):
ASC X12 N WEB Page Information TG 2 WG 3 FAQ (Frequently Asked Questions): A. Can I use my company's internal claim reject codes in the 835 transaction? No. The 835 transaction requires use of the standard
More informationSession 8: ACH. New York Bankers Association-Community Bank Auditors Group Internal Audit Training-June 6-8, 2016
Session 8: ACH New York Bankers Association-Community Bank Auditors Group 2016 Internal Audit Training-June 6-8, 2016 MEMBER OF ALLINIAL GLOBAL, AN ASSOCIATION OF LEGALLY INDEPENDENT FIRMS 2016 Wolf &
More information