Overview
A return payment records money that comes back to you after you paid it on a claim. Common examples are a vendor refunding part of a security deposit, a refund of an overpayment, a duplicate payment, or an insured returning funds after recovered property is found.
BriteCore links each return payment to its original payment, lowers Net Paid, and keeps the return out of your recovery reports. Use a recovery instead for money collected from a third party, such as subrogation or salvage.
You can make more than one partial return against the same payment, up to the amount originally paid in each of Loss, Adjusting, and Legal.
Before You Begin
Check these three items before you record a return payment:
- Site setting: On Settings > Modules > Claims, the Enable return payments checkbox must be selected. Only BriteCore can change this setting, so contact BriteCore customer service to request it.
- User permission: Recording or voiding a return payment uses its own claims accounting permission, returnPayments. The Transactions write permission and the recovery permission do not grant it. Ask your administrator to give you read/write access to it.
- Claim and payment: The payment must not be voided, must not be dated in the future, and must have paid the exposure you are working in. You can record a return payment on an open or a closed claim, but not on a historical claim.
Record a Return Payment
- Open the claim and select the Accounting tab. In the left menu, select the coverage the payment was made on. The Transactions list is at the bottom of that screen.
- Find the payment and select Return in its row. Alternatively, select Add, select Record Return Payment…, and then choose the payment in the Choose payment to return against dialog. The dialog shows how much remains to return on each payment.
- In the Record Return Payment dialog, review the payment summary: payment date, payee(s), coverage, payment amount, what has been returned so far, and what remains in Loss, Adjusting, and Legal. If the payment was split across coverages, the dialog shows the full payment and this coverage's share, and you can return up to the share.
- Confirm the Return date (received). It defaults to today. The date cannot be before the payment date or in the future. If the Allow Claim Payment Transaction Date Override setting on Settings > Modules > Claims is off, the date must be today.
- Enter the amount returned in Loss, Adjusting, and Legal. You can return to one category only, for example a deposit refund against a housing payment. Each amount cannot be more than what remains in that category.
- Select a Return reason: Vendor deposit refund, Overpayment refund, Duplicate payment, Recovered property — funds returned by insured, or Other. If you choose Other, enter a description in Describe the reason.
- Optionally, enter a Reference / Check # (digits only), a Payment method if your site shows that field, and Notes.
- Select Save.
While you type, the dialog shows the net paid on the payment after the return and the remaining balance after saving. If a category is over its limit, the field shows how much remains, and a message beside Save explains why it is unavailable. When the return is saved, BriteCore confirms it and shows the remaining balance.
If a payment has been fully returned, its Return action is unavailable and the dialog shows This payment has been fully returned.
How a Return Payment Affects the Claim
The return appears in the Transactions list as its own row, tagged Return Payment, with a negative amount. You can filter the list by the Return Payment transaction type.
- Link to the original payment: Expand the return row to see the Original Payment and the Remaining Balance, and select View original payment to jump to it. Expand the payment row to see its Return Payments and select View return payment.
- Net Paid: The return lowers Net Paid in the same category (Loss, Adjusting, or Legal) as the original payment, at both the exposure and the claim level.
- Reserves on an open claim: BriteCore adds the returned amount back to the reserve on the affected coverage, in the same categories you returned. Net Paid goes down by the same amount, so Total Incurred does not change.
- Reserves on a closed claim: The reserve does not change and the claim stays closed. Net Paid and Total Incurred both go down.
- Audit trail: BriteCore adds a note titled Return Payment Recorded to the claim when you save a return, and a note titled Return Payment Voided when you void one.
To void a payment that has return payments, void its return payments first. You also cannot change the exposure or date of a payment that has return payments.
Void a Return Payment
If you entered a return by mistake, you can void it. The return stays in the ledger marked Voided for audit purposes.
- On the Transactions list, find the return payment and select Void in its row.
- In the Void Return Payment? dialog, review the return, the linked payment, the return amount by category, and the effect on the reserve.
- Enter a Void reason.
- Select Void Return. Select Keep Return to close the dialog without changes.
Voiding the return adds its amount back to the balance that can still be returned on the original payment, and it reverses the reserve change the return made. BriteCore refuses the void if the reserve is now lower than the amount the return restored, and the dialog shows why. On a closed claim, or a claim closed after the return, the reserve does not change. You can void a return even if return payments are later turned off.
What a Return Payment Does Not Do
- BriteCore never issues a return payment as a check. The Reference / Check # field only records a reference for the money you received.
- A return payment does not count as a recovery. BriteCore leaves it out of subrogation, salvage, and other recovery reporting, and you do not need a recovery reserve to record one.
- It does not change loss-free or claims-free discount eligibility.