Billing operations guide
Set up a patient refund queue that keeps approvals visible
A refund workflow for credit balances that screens the source, documents the approval ladder, and protects the patient conversation.
On this page
Screen the credit before it becomes a refund
A patient credit is not automatically a refund, because the credit may belong to a payer, a duplicate payment, or a pending adjustment. Start the queue with the account history, the original payment source, and the current responsibility split. Confirm that no other payer or claim is still expected to post to the account. If the source is unclear, the item belongs in an investigation queue rather than a refund queue.
Duplicate payments, posting errors, and contractual adjustments can all create a credit that looks patient-facing. Compare the payment trace to the remittance and the bank deposit before accepting the balance as refundable. Check whether the credit came from a card, check, or patient portal payment, because the return path differs. A refund built on the wrong source is harder to reverse than a delayed decision.
Build the approval ladder into the queue
Define refund thresholds and the role that must approve each level before the queue goes live. A small refund may need one reviewer, while a larger refund or an unusual payment path may need a manager and a finance check. Put the threshold and the approver in the queue record, not in a separate policy that staff rarely open. The approver should see the evidence, not only the amount.
Record the preparer, the approver, the approval time, and the payment method in one place. If the approver asks for more evidence, keep the request and the response with the case. Do not let an approval given in a chat message disappear when the thread is archived. The queue should show the decision path even when the original conversation is gone.
Verify the payment source and patient share
Verify the patient share against the latest remittance and the approved financial agreement. A credit may exist because the patient paid before the payer processed the claim, and the correct action may be to hold the balance until adjudication finishes. Check whether a statement or collection activity is already in progress, because a refund can cross with a bill. The queue should flag that conflict before release.
If the patient paid by card, confirm the card return path and the time window allowed by the processor. If the payment came by check, confirm the mailing address and whether the check has cleared. For a portal payment, keep the portal reference with the refund record. The method matters because a refund sent to the wrong path creates a new dispute.
Protect the patient conversation
The patient conversation should be factual and limited to the balance, the refund method, and the expected timing. Do not speculate about payer responsibility or promise a date the finance team has not confirmed. Use approved contact channels and record the date, time, and summary of the conversation. If the patient disputes the balance, route the case to the billing owner instead of continuing the refund.
A refund notice should include the account reference, the amount, the method, and a contact for questions. Avoid placing full payment details in an email or a portal message when a secure link is available. Follow the organization's privacy policy for any document that includes protected health information. The refund queue is a financial control and a privacy control at the same time.
Record the refund and its evidence
After release, record the refund date, amount, method, reference number, and the person who released it. Attach the approval and the source verification to the same case. Reconcile the refund to the bank or processor statement during the next close. A refund that leaves the queue without a matching payment record is an open item, not a completed one.
If the refund is rejected or returned, reopen the case with the reason and the new next action. Keep the original approval visible so the reviewer can see what changed. Do not create a second case that hides the first decision. The history is what protects the team when a patient or auditor asks why the money moved.
Audit refunds before month end
Sample refunds each month across amounts, payment methods, and approvers. Check that the source was verified, the approval level matched the threshold, and the payment reached the intended recipient. Look for repeat causes such as duplicate posting or a missing payer response. Feed those findings into payment posting and customer billing support so the queue improves.
Handle a credit that is not refundable
Some credits should never become refunds because they belong to an open payer process or a pending adjustment. If the payer has not finished adjudication, hold the balance and set a review date. If the credit came from a duplicate payment, correct the duplicate before considering a refund. The queue should show the reason for the hold and the owner who will revisit it.
A credit may also belong to a different patient or account because of a posting error. Do not move the money to a new account or send a refund until the identity is confirmed. Keep the suspected match and the evidence for it in the case. If the identity cannot be resolved, route the case to the billing owner and leave the credit visible.
When a credit is not refundable, close the refund task with a clear disposition such as applied, transferred, or held for payer review. Link the disposition to the accounting entry that supports it. A closed task with no disposition teaches the next reviewer nothing and invites the same investigation again.
Authoritative references
Philippines staffing intake
Define the role before hiring begins.
Share the tasks, tools, schedule, and approval limits for your Filipino team member. The intake turns those details into a practical staffing brief.
Contact Us