Billing operations guide
Run a weekly unbilled charge reconciliation without guessing
A practical weekly routine for finding unbilled work, separating timing from defects, assigning owners, and proving the balance moved.
On this page
Define what counts as an unbilled charge
An unbilled charge is revenue the team has earned but has not yet released to a payer or customer, and the definition should be narrow enough to count. Include completed services with a missing code, a hold, an unapproved rate, or a failed transmission. Exclude work that is still in progress or waiting for a scheduled start. Write the definition in the reconciliation file so every reviewer counts the same items.
The source of an unbilled item is the encounter, timesheet, shipment, or usage record that proves the work happened. A billing system report shows what the billing team has, not necessarily what operations delivered. Reconcile the two views before treating a gap as a billing error. If the source record is incomplete, the item belongs in an evidence queue rather than a write-off.
Reconcile the charge capture report to source activity
Start the weekly reconciliation by freezing both the source activity and the billing release report for the same cutoff. Match on a stable identifier such as an encounter number, order number, or subscription period, and keep manual matches separate. Investigate items that appear in one report but not the other before adjusting either system. A one-sided match can reflect a timing difference, a duplicate identifier, or a genuine omission.
Group the differences into timing, missing source, coding hold, approval hold, transmission failure, and unknown. Count each group and assign a reviewer who can explain the cause. Do not let the unknown bucket become the largest one without an owner. A small set of categories helps the team see whether the problem sits in operations, billing, or the interface between them.
Assign an owner to every aging bucket
Every aging bucket needs a named owner and a next action date, even when the action is to wait for an external response. The owner may be a billing specialist, a coding lead, a sales operations manager, or a client contact. Put the owner's role in the file rather than a personal nickname that will mean nothing next quarter. When ownership changes, update the file on the same day the queue is reassigned.
A weekly review should read the oldest five items and the largest three items, because those two views expose different risks. Age shows where the process has stalled, while value shows where the financial exposure is concentrated. Ask the owner to explain the next concrete step and the date it will happen. Close the meeting with a short list of decisions, not a promise to follow up later.
Investigate holds before writing them off
A hold is a decision to delay billing, and each hold needs a reason, an approver, and a review date. Common holds include missing documentation, a contract question, a coding review, or a client request. A hold without an expiration date becomes an accidental write-off because nobody revisits it. Report holds separately from true unbilled work so the team does not hide delay inside a broad metric.
Before writing off an unbilled item, confirm that the service was not delivered or that the contract does not allow billing. Get approval from the owner who can accept the revenue loss. Keep the evidence that supported the decision and the date it was made. A write-off that cannot be explained later is a control failure even if the accounting entry is correct.
Document the weekly sign-off
The weekly sign-off should fit on one page and show the opening balance, additions, releases, write-offs, and closing balance by category. Add the count of items older than the team's threshold and the number of items without a source. The preparer signs the page and the reviewer signs a separate line. Both names should be visible in the file, not buried in a chat thread.
Reconcile the closing balance to the billing system and explain any difference between the two. If the reconciliation depends on a manual spreadsheet, keep the version and the formula notes with the packet. Test one or two items back to the source each week so the report does not drift away from reality. Link the routine to billing reconciliation and month-end billing support where the same controls apply.
Fix the cause behind repeat gaps
Repeat gaps usually point to a handoff that lacks a required field or a deadline that nobody owns. Review three months of categories and look for the same source, team, or interface. Fix one cause at a time and measure whether the category shrinks before adding another project. The goal is fewer surprises at month end, not a longer reconciliation checklist.
What to do when the source is late
When the source record is late, keep the item in an evidence queue and set a follow-up date instead of estimating the charge. Record who was asked, what was requested, and when the response is due. If the service date is approaching a billing deadline, escalate before the deadline passes. A late source can still become a billable item, but an invented value cannot be repaired easily.
Use a temporary hold code that shows the item is waiting on operations, not on the billing team. Review those holds at the same weekly meeting and ask for an update from the source owner. If the source never arrives, document the search and route the write-off decision to the authorized owner. The reconciliation should show the outcome either way.
Track how often the same source team is late, because a repeat pattern may need an upstream fix. A missing timesheet field or an interface delay is a process issue that the billing team cannot solve alone. Bring the evidence to the operations owner and agree on a change. The weekly reconciliation then becomes a feedback loop instead of a cleanup exercise.
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