Interest, Medical Record Fees, Supplies, and Insurance Overpayments

Interest payments, medical records fees, supply transactions, and insurance overpayments are all posted in Unassigned Payments.

Before You Begin

Please read Unassigned Payments: Add/Delete Patient Payments.

Posting an Interest Payment

Interest payments received from an insurance company should be posted in Unassigned Payments. The system will automatically create a charge line for the amount of the payment. The payment entered will then be applied, leaving a zero balance due. 

  • Transaction Type: Set as INTEREST
  • Payment Code: Make a selection based on the payer
  • Insurance: Select the payer that sent the interest payment

Posting Medical Record and Supply Payments

Medical records and supplies are entered using the same method as Interest payments. The only difference in the Transaction Type.

  • Medical Records: Set Transaction Type as MEDICAL RECORD
  • Supplies: Set Transaction Type as SUPPLY RECORD

Important: If a charge was manually entered for Medical Records or Supplies, do not enter the corresponding payment with the Transaction Type. This will result in duplicate charges. Instead, post the payment directly to the charge using the Add Payments page or enter an Unassigned Payment as COPAY.

Posting an Insurance Overpayment

Insurance Overpayments are entered using the same method as Interest payments. 

  • Transaction Type: Set as INS OVERPAYMENT
  • Payment Code: Make a selection based on the payer
  • Insurance: Select the payer that had the overpayment

Important: Your unallocated amount will always be zero. If there is already an insurance overage, the payment will automatically be applied to that charge, if there is not a charge the system will create one and automatically move the overpayment amount.

Patient Ledger

Interest, Medical Record Fees, and Supply are all reflected on the Ledger Full/Visit with a CPT code of INT. However, Insurance Overpayments are listed as INSOVER.

Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.