Settings in CSC Options of Remittance Profile

CSC Tab Options	Option	Description
Consolidated Services Claim payment Posting	Enable Posting to CSC Claims	Enables matching logic for the following 835 segments during the ERA Posting process: REFEA Segment REF01 (2100 level)-EA - Medical Record Identification Number identifies the CSC Claim from the superclaim_encounters table. REFEA - the REF6R line item control number is used to match to the service line(s) for ERA posting. REF6R - is used for UB/837I posting of CSC and Non-CSC Claim payments. On the Default tab, in the Charge Matching Options, you must select Use Bundled Payment Processing for UB Claim to this segment. REFEA - If not returned , the 2100 Service Lines REF6R is used to look for a match. REF6R - identifies a match to a CSC Claim, each payment’s line item is posted to the matching REF6R. REFEA and REF6R - are missing, the normal Remittance Profile Settings will be used.
When option is disabled	When the option is disabled, and the payment is matched as a CSC claim payment, the payment will not post. The ERA Import Posting report, you receive a message that the payment has not posted because of how it is configured.
CSC Claim Level Payments and Adjustments - 1500 and UB	Distribute Claim-Level Payments - 1500	Select one of the following options: Apply to remaining line item balance FIFO Weighted
Distribute Claim-Level Adjustments - 1500	Select one of the following options: Apply to remaining line item balance FIFO Weighted
Distribute Claim-Level Payments - UB	Select one of the following options: Apply to remaining line item balance FIFO Weighted
Distribute Claim-Level Adjustments - UB	Select one of the following options: Apply to remaining line item balance FIFO Weighted
CSC Claim Level Transaction Codes	CSC Payment Transaction Code	Select a payment transaction code to be used for CSC claim-level payments. Note: When this field is blank, the transaction code in the Default Payment field in the Payer > Practice > Transactions is used.
CSC Adjustment Transaction Code	Select an adjustment transaction code to be used for CSC claim-level adjustments. Note: When this field is blank, the transaction code in the Default Adjustment field in the Payer > Practice tab > Transactions is used.

Help Guide for NextGen® Enterprise PM 8

CSC Options Tab - Options and Settings

You can use the following list of options and descriptions to make settings on the CSC Options tab in your Remittance Profile. CSC Tab Options Option Description Consolidated Services Claim payment Posting Enable Posting to CSC Claims Enables matching logic for the following 835 segments during the ERA Posting process: REF*EA Segment REF01 (2100 level)-EA - Medical Record Identification Number identifies the CSC Claim from the superclaim_encounters table. REF*EA - the REF*6R line item control number is used to match to the service line(s) for ERA posting. REF*6R - is used for UB/837I posting of CSC and Non-CSC Claim payments. On the Default tab, in the Charge Matching Options, you must select Use Bundled Payment Processing for UB Claim to this segment. REF*EA - If not returned , the 2100 Service Lines REF6R is used to look for a match. REF6R - identifies a match to a CSC Claim, each payment’s line item is posted to the matching REF*6R. REF*EA and REF*6R - are missing, the normal Remitt

File Maintenance Help for NextGen® Enterprise 8

CSC Options Tab - Options and Settings

You can use the following list of options and descriptions to make settings on the CSC Options tab in your Remittance Profile. CSC Tab Options Option Description Consolidated Services Claim payment Posting Enable Posting to CSC Claims Enables matching logic for the following 835 segments during the ERA Posting process: REF*EA Segment REF01 (2100 level)-EA - Medical Record Identification Number identifies the CSC Claim from the superclaim_encounters table. REF*EA - the REF*6R line item control number is used to match to the service line(s) for ERA posting. REF*6R - is used for UB/837I posting of CSC and Non-CSC Claim payments. On the Default tab, in the Charge Matching Options, you must select Use Bundled Payment Processing for UB Claim to this segment. REF*EA - If not returned , the 2100 Service Lines REF6R is used to look for a match. REF6R - identifies a match to a CSC Claim, each payment’s line item is posted to the matching REF*6R. REF*EA and REF*6R - are missing, the normal Remitt

Help Guide for NextGen® Enterprise PM 8

Bundled Payments

For bundled payments, the ERA Import Posting report functions as described below: If an Encounter Level Payment Distribution method is not selected in the Remittance Profile library, the ERA Import Posting report displays the following message: "Bundled payment was not posted because Encounter Level Distribution method was not enabled in the Remittance Profile". Note: The ERA Posting process cannot post bundled payments unless an Encounter Level Payment Distribution method has been selected in the Remittance Profile. If the claim is UB/837I and no claim was found for the encounter of the NU bundled payment, the ERA Import Posting report displays the following message: "Bundled payment was not posted because no claim was identified for this encounter". If the claim is UB/837I and no match was found for the NU bundled payment, the ERA Import Posting report displays the following message: "Bundled payment was not posted because no charge match was found for this revenue code". If the clai

Help Guide for NextGen® Enterprise PM 8

Bundled Payments

For bundled payments, the ERA Import Posting report functions as described below: If an Encounter Level Payment Distribution method is not selected in the Remittance Profile library, the ERA Import Posting report displays the following message: "Bundled payment was not posted because Encounter Level Distribution method was not enabled in the Remittance Profile". Note: The ERA Posting process cannot post bundled payments unless an Encounter Level Payment Distribution method has been selected in the Remittance Profile. If the claim is UB/837I and no claim was found for the encounter of the NU bundled payment, the ERA Import Posting report displays the following message: "Bundled payment was not posted because no claim was identified for this encounter". If the claim is UB/837I and no match was found for the NU bundled payment, the ERA Import Posting report displays the following message: "Bundled payment was not posted because no charge match was found for this revenue code". If the clai

Help Guide for NextGen® Enterprise PM 8

Reporting Bundled Payments

The table below outlines how the ERA Import Posting report handles bundled payments. If... Then the ERA Import Posting Report displays the following message: No Encounter Level Payment Distribution method is selected in the Remittance Profile "Bundled payment was not posted because Encounter Level Distribution method was not enabled in the Remittance Profile". Note: To post bundled payments, you must select the Encounter Level Payment Distribution method in the Remittance Profile. The claim is UB/837I and no claim was found for the encounter of the NU bundled payment "Bundled payment was not posted because no claim was identified for this encounter". The claim is UB/837I and no match was found for the NU bundled payment "Bundled payment was not posted because no charge match was found for this revenue code". The claim is NU and a match was found for the NU bundled payment, but the balances of the charges are 0 or credit "Bundled payment was not posted. Charge match(es) found for this r

Help Guide for NextGen® Enterprise PM 8

Reporting Bundled Payments

The table below outlines how the ERA Import Posting report handles bundled payments. If... Then the ERA Import Posting Report displays the following message: No Encounter Level Payment Distribution method is selected in the Remittance Profile "Bundled payment was not posted because Encounter Level Distribution method was not enabled in the Remittance Profile". Note: To post bundled payments, you must select the Encounter Level Payment Distribution method in the Remittance Profile. The claim is UB/837I and no claim was found for the encounter of the NU bundled payment "Bundled payment was not posted because no claim was identified for this encounter". The claim is UB/837I and no match was found for the NU bundled payment "Bundled payment was not posted because no charge match was found for this revenue code". The claim is NU and a match was found for the NU bundled payment, but the balances of the charges are 0 or credit "Bundled payment was not posted. Charge match(es) found for this r

Settings in CSC Options of Remittance Profile

Recommendations

CSC Options Tab - Options and Settings

CSC Options Tab - Options and Settings

Bundled Payments

Bundled Payments

Reporting Bundled Payments

Reporting Bundled Payments

Settings in CSC Options of Remittance Profile

CSC Options Tab - Options and Settings

CSC Options Tab - Options and Settings

Bundled Payments

Bundled Payments

Reporting Bundled Payments

Reporting Bundled Payments