Eight disciplines. One revenue cycle.
Billing, coding, denial management, AR management, credentialing, eligibility verification, patient support and front office management are usually run as separate functions, by separate people, measured separately. The revenue lost between them is the reason they should not be.
The revenue cycle, in the order it happens
The eight are not a menu of services. They are one process, and each stage inherits whatever the previous stage got wrong.
Coverage confirmed, authorisation requirements identified and demographics captured. A claim that fails here does not fail here — it fails weeks later, in a different department, as a rejection somebody else has to work.
Registration completed and patient responsibility established while the patient is still present, which is the point at which it is most likely to be understood and paid.
Documentation translated into standardised code sets. This is where the claim’s value is set, and where undercoding costs quietly — a denial is visible and gets worked, an under-coded claim is paid and never questioned.
Charges captured against documentation, claims scrubbed against payer-specific rules rather than generic edits, and submitted.
Payments posted against expected reimbursement rather than simply recorded. Denials categorised by root cause. Outstanding balances worked by what is recoverable, before timely-filing limits close them.
None of the above is billable if the provider is not enrolled and current with the payer. Credentialing gaps surface as denials that look like billing errors, which is why they can run for months before anyone traces the cause.
Medical billing
Producing and submitting claims that get paid the first time.
- Charge capture reviewed against documentation before the claim is built.
- Claims scrubbed against payer-specific rules rather than generic edits.
- Clean-claim rate treated as a process metric, not an aspiration.
- Rejections corrected at source so the same error stops repeating.
- Payment posting reconciled against expected reimbursement, not just received.
Medical coding
Translating documentation into codes that reflect the care actually delivered.
- Coding supported by, and traceable to, the clinical documentation.
- Specialty-specific code selection and modifier accuracy.
- Undercoding treated as a revenue problem, not a safe default.
- Documentation queries returned to clinicians where the note is the limiting factor.
- Coding decisions defensible if the claim is ever reviewed.
Denial management
Working denials to resolution — and removing the cause.
- Denials categorised by root cause, not just by payer or dollar value.
- Appeals prepared where the denial is appealable and worth appealing.
- Rejections, denials and underpayments handled as three distinct problems.
- Recurring patterns fed back into coding and front-end processes.
- Appeal deadlines tracked so the right to appeal is never lost to the calendar.
AR Management
Pursuing outstanding balances by what is recoverable, not just what is oldest.
- Receivables prioritised by value, age and likelihood of recovery.
- Aged balances worked before timely-filing limits close them out.
- Payer-side and patient-side balances handled as distinct workflows.
- Write-off decisions made deliberately rather than by default.
- Root causes of ageing fed back upstream so the pattern stops.
Credentialing
Keeping providers enrolled, current, and able to be reimbursed.
- Payer enrolment tracked from application through to approval.
- Re-credentialing and expirations monitored before they lapse.
- CAQH and payer records kept consistent with current practice details.
- New providers progressed in parallel with onboarding, not after it.
- Enrolment status visible, so nobody is scheduled against a payer they cannot bill.
Eligibility verification
Confirming coverage before the encounter, not after the denial.
- Coverage, benefits and plan status confirmed ahead of the visit.
- Prior-authorisation requirements identified before care is delivered.
- Patient responsibility established early enough to be communicated.
- Secondary and tertiary coverage identified up front.
- Verification failures treated as a front-end defect, not a billing one.
- Appointment scheduling, rescheduling and cancellations handled directly.
- Insurance questions answered before they become billing disputes.
- Prescription refill requests routed to the right person, not a voicemail.
- Patient messages and general enquiries covered during agreed hours.
- After-hours and weekend cover where the service agreement includes it.
Front office management
The desk where the revenue cycle actually begins.
- Registration and demographics captured correctly the first time.
- Coverage verified before the encounter, not after the denial.
- Authorisation requirements identified while they can still be obtained.
- Patient responsibility established early enough to be collected at the desk.
- Front-end errors reported as a front-end metric, not absorbed downstream.
The revenue is lost between the disciplines
Each of the eight can be run competently and still lose money at the seams, because no single function owns the handover.
Between the front desk and coding
A mistyped payer ID or subscriber number does not stop a claim being coded. It stops it being paid, long after the desk has forgotten the encounter.
Between coding and billing
A correctly coded claim submitted under the wrong payer rules is rejected on a technicality that has nothing to do with the coding.
Between billing and AR
Claims that are neither paid nor denied are the easiest to lose. Nothing flags them, because nothing went wrong — they were simply never answered.
Between denials and everything upstream
A denial worked and won is revenue recovered once. A denial whose cause is removed is revenue that stops being lost.
Questions practices ask before they choose
What is revenue cycle management?
Revenue cycle management covers everything between a patient booking an appointment and the practice being paid in full for it: eligibility, registration, coding, claim submission, payment posting, denials and outstanding balances. It is described as a cycle because a failure at one stage reappears as a cost at a later one.
Do we have to take all of these, or can we start with one?
Either. Practices commonly start with the discipline causing the most immediate loss — often denials or aged AR — and extend the scope once that is stable. What is included is set by the service agreement.
What is the difference between medical billing and medical coding?
Coding translates clinical documentation into standardised code sets, which determines what the claim is worth. Billing builds, submits and follows that claim through the payer until it is paid. Coding sets the value; billing collects it. They fail in different ways and are measured differently.
What is the difference between a rejection and a denial?
A rejection is a claim the payer never accepted for processing, usually because of a formatting or data error; it can be corrected and resubmitted. A denial is a claim that was processed and refused, and it has to be appealed or written off. They are counted, worked and prevented differently, which is why reporting that merges them hides the actual problem.
How is AR management different from denial management?
Denial management works claims the payer has refused, and removes the cause so the same denial stops recurring. AR management works everything still outstanding — including claims that were never denied, just never answered — prioritised by value, age and how likely recovery is before timely-filing limits close them out.
Why does credentialing affect revenue if the billing is correct?
An unenrolled or lapsed provider cannot be reimbursed regardless of how well the claim is coded and billed. Because the resulting denials look like billing errors, the cause is often traced late.
Do we need to change our EHR or practice management software?
No. Our team works within your existing electronic health record, practice management, clearinghouse and payer portal software. We review your current technology setup during onboarding and determine the most secure and efficient working arrangement.
How do we find out which of these is costing us most?
That is what a revenue assessment is for. It reviews the cycle end to end rather than the single stage where the symptom appeared, because the stage where revenue is lost and the stage where it is noticed are rarely the same.
Not sure which of these is costing you most?
A revenue assessment reviews all 8, end to end, and shows you where the reimbursement is going.