Payment Posting General Configuration

Allow Future Batch Dates

Future dates can be entered in the Remittance Advice Batch and Payment Batch windows in the payment wizard or batch update windows by using settings in the Global Registry key PA_ALLOW_FUTURE_BATCH_DATE. RCM Cloud^® can be set to accept no future dates, all future dates, or a specific range of future dates.

When future dates are not allowed or are limited, a warning message displays when an invalid date is entered.

Configuration

For this configuration, use the key(s) in Global Registry Maintenance with the settings described in the table below.

Apply Overpayments to Unpaid Billing Events

Payments that exceed a visit’s current balance can be applied to unpaid balances on additional billing events by enabling System Registry key PAYMENT_ENTRY_FLOAT. When enabled, the overpayment functionality can either apply the overpayment as a specific adjustment code or it can apply the overpayment with the payment code from the original payment or a configurable payment code.

The overpayment functionality progresses through all of the patient’s billing events, including late billing events. If a balance remains from the original payment after all of the billing events are paid off, the overage remains on the original billing event.

The payment can be limited to self pay billing event balances by enabling the System Registry key PAYMENT_FLOAT_SELFPAY. This would allow billing events that are still pursuing an insurance payer to be skipped, and the overpayment would only apply to self pay billing events.

Configuration

For this configuration, use the key(s) in Global Registry Maintenance with the settings described in the table below.

System Registry Key	Description
PAYMENT_ENTRY_FLOAT	Determines whether payments exceeding the visit billing event balance are applied to unpaid balances on additional billing events.
	Value 1 Description 0 Overpayment functionality disabled. 1 Overpayment functionality enabled. System uses adjustment code defined in Value 2 to post overpayment adjustments to unpaid balances on additional billing events. 2 Overpayment functionality enabled. If there is no value in Value 2, the system uses original payment code to post overpayments to unpaid balances on additional billing events. If there is a payment code defined in Value 2, the system will use that payment code to post the overpayment to additional billing events. Value 2 Description Adjustment Code or Payment Code Enter an adjustment code from the ADJUSTMENT_MSTR table when Value 1 is set to 1. Enter a payment code from the PAYMENT_MSTR table when Value 2 is set to 2.
PAYMENT_FLOAT_SELFPAY	Determines whether payments exceeding the billing event balance are applied to unpaid balances on any additional billing event or just for self pay billing events.
	Value 1 Description 0 Overpayments applied to any billing event. 1 Overpayments applied only to self pay billing events. All other billing events are skipped.

Change Comments Field Label

The Comments field label in the Payment Line Item window in the new batch wizard and the Line Item Detail tab can be changed using the Global Registry key PAYMENT_BATCH_ADD_INF_FLD_NAME. This allows a customized label for information in this field. If Value 1 is null, the field does not display.

Configuration

For this configuration, use the key(s) in Global Registry Maintenance with the settings described in the table below.

Require Batch Total to Balance

The batch total can be required to balance with its line item payments by enabling the System Registry key PAYENTRY_BTOTAL. When the key is enabled and an out-of-balance batch is attempted to be released, the following error message displays. Click OK then adjust the Batch Total or individual payments to balance.

Configuration

For this configuration, use the key(s) in System Registry Maintenance with the settings described in the table below.

Require Deposit Date

An entry can be required in the Deposit Date field in the Payment Batch window enabling the Global Registry key PAYMENT_DEPOSIT_DATE_REQ. When enabled, a warning message displays when the entry is attempted to be released without a valid deposit date.

The Deposit Date field allows an organization to distinguish between the date the payment was posted and the date when the actual cash or check was deposited in the bank.

Configuration

For this configuration, use the key(s) in Global Registry Maintenance with the settings described in the table below.