ADJBALEXCL 

- EXCLUDE CODES FROM ADJUDICATION BALANCED CALCULATION

• A calculation is performed when manually posting payments to confirm that the payment is balanced. 
• The "does it balance" calculation is: Charge-Allowed-Adjustments=0 
• If the result is not zero, a validation warning is presented to the user. 
• Payers will sometimes add codes that throw off this calculation, but the adjudication is still correct. One example would be codes used for sequestration, which made it appear the payer was over-adjusting. If a remit code is being used that is falsely throwing off the Balanced calculation (and therefore triggering false validation warnings), add the code to this setting.
• This will change the Balanced calculation to: Charge-Allowed-Adjustments+Adjustment Exclusions (specified in this setting)=0 
• Multiple codes can be entered as long as they are comma separated, with no spaces.
• Note that the unbalanced edit for Electronic Remits is handled by ERA Management rules (Libraries > ERA Management). The ADJBALEXCL setting only effects manually posted payments.

ALLOWCREDITCARDESCROW 

- ALLOW MONEY TO BE LEFT IN ESCROW WHEN PROCESSING CREDIT CARD

• This setting controls whether or not money can be left in Escrow when processing a credit card payment.

• Yes and (---): Display a checkbox to provide the ability to collect a payment that will remain in Escrow. This is useful when collecting money prior to a visit, such as for a copay.
• No: Do not show the Escrow checkbox. This will only allow credit card payments to be processed that can be immediately applied to a balance.

CCTYPEMAND

- DETERMINE WHETHER CREDIT CARD TYPE IS MANDATORY

• This setting controls whether or not the credit card Type (Visa, Discover, etc.) is required when creating a credit card payment Receipt.

• Yes and (---): The credit card Type is required when adding a credit card payment Receipt.
• No: Do not require the credit card Type to be entered. This may be desired for groups who do not reconcile credit cards within the system.

 Note that Type will still display as a yellow field, but users will be able to save payments without a designated Type.

COMPLETESELFCOPAY

- BYPASS WARNING WHEN INSURANCE IS PATIENT ON A COPAY RECEIPT

• Yes: Bypass the Exception warning:

• When insurance is Patient and 
• the linked Copay Receipt is higher than zero.
• This also sets the Receipt Copay amount to $0.00 since the insurance is Self-Pay.

• No and (---): Do not bypass this warning.

CROSSOVERMAPPING 

- DEFAULT SETTING TO ALLOW CROSSOVER MAPPINGS

• Background: When a Medicare electronic remit comes into the system showing a secondary that does not exist on the Patient's Insurance Profile, that Remit will go on Hold. A user will then need to update the Profile so the remaining balance can be transferred to the correct secondary.
• Crossover Mappings can be used to connect secondary payers on the Medicare Remit to the correct Insurance in the Library. Once mappings have been created, going forward the secondary insurance will be added automatically to the Patient's Insurance Profile when the electronic remit is processed.
• Note that the Policy # will be "UNKNOWN" for the system-added secondary. If the secondary insurance remittance also comes in electronically, the secondary policy # will be automatically updated based on the information in the Remit.

• Yes and (---): Use the Crossover Mapping feature when posting ERAs.
• No: Do not use the Crossover Mapping feature. I will resolve these situations manually.

DWASPOSTED 

- DEFAULT STATUS TO POSTED WHEN MODIFYING A REMIT IN THE DENIAL WORKLIST

• This setting controls the default value of the status field "Change Remit Status/Worklist" on the ERA Remit screen (Manage Electronic Remittance Item screen) for Remits in the status of Denial Worklist (DW), Custom Worklist (CW), or Hold (H).

• Yes: Always default the status field Change Remit Status/Worklist to Posted.
• No and (---): Only mark as Posted if not currently in a CW (Custom Worklist), DW (Denial Worklist) or H (Hold) status.

No is the default (---) behavior.

ERAVIEW

- Default ERA View - Default is Loaded (L)

• This setting controls which ERAs are displayed by default when accessing the ERA List (when clicking All ERAs on the Payments Dashboard)

• LOADED: Only display ERA's with a Status = Loaded 

• ALL: Display all ERA's

HIDECASH 

- HIDE ALL CASH PAYMENT OPTIONS

• This setting allows you to remove the Cash field when adding a new payment Receipt.

• No and (—): Include the Cash field when adding a new payment Receipt.
• Yes: Hide the Cash field when adding a new payment Receipt.

HIDECHECK 

- HIDE ALL CHECK PAYMENT OPTIONS

• This setting allows you to remove the Check field when adding a new payment Receipt.

• No and (—): Include the Check field when adding a new payment Receipt.
• Yes: Hide the Check field when adding a new payment Receipt.

IMPORTERA

1. No and (---): ERAs cannot be uploaded manually by the User.
   
2. Yes: An Import button is added to the ERA List screen for the User to Import ERAs.

HIDECREDITCARD 

- HIDE ALL CREDIT CARD PAYMENT OPTIONS

• This setting allows you to remove the Card (credit card) field when adding a new payment Receipt.

• No and (—): Include the Card field when adding a new payment Receipt.
• Yes: Hide the Card field when adding a new payment Receipt.

MCHARGE 

- ENABLE POSTING OF PATIENT PAYMENTS AT THE CHARGE SCREEN

• Enter Y to add 'Tabs' for Notes & Payments to the Procedures section of the Post Charge screen. For Self Pay Charges where a Receipt has been posted to the Charge, you can access the Payment tab to post a payment and write-off a balance. 
• Set to N - removes these tabs from Charge entry

PRCODE 

- DEFAULT PR CODE

• This setting allows you to create a default PR transaction code (e.g. PR1, PR2 or PR3) to use when posting in Post Expert Mode. 
• Will default after entering the Allowed and Paid amounts.

SEC_CROSSED 

- CROSS CLAIMS BY DEFAULT

• Yes: For manually posted primary Medicare payments, default the "Crossed to Secondary" checkbox as selected. This moves the balance to the secondary, without queuing the secondary Claim for submission. 
• No: Do not automatically select the "Crossed to Secondary" checkbox when posting primary Medicare payments manually.