Revenue cycle automation: what to automate, in what order, and how to measure it
Updated
The five stages of the revenue cycle
HFMA groups its MAP Keys revenue cycle KPIs into five categories: patient access, pre-billing, claims, account resolution, and financial management. We use the same five stages here because they give your team and any vendor a shared vocabulary.
Patient access
Eligibility checks before the visit, prior authorization requests and status checks, insurance capture at registration. Insurance eligibility verification.
Pre-billing
Charge reconciliation against the schedule, missing-documentation flags, coding edits before the claim leaves. Claim denial automation.
Claims
Claim submission, clearinghouse rejection handling, claim status checks on a schedule. Claim denial automation.
Account resolution
Payment posting from remittance files, denial classification and routing, appeal packet assembly, underpayment detection. Claim denial automation.
Financial management
AR aging, denial trends, payer performance, and cash forecasting from source data. Revenue cycle reporting automation.
Start with the standard transactions
HIPAA requires covered entities to use national standards when they conduct certain transactions electronically. CMS lists them on its adopted standards page, and says any provider who accepts payment from a health plan must comply if they conduct those transactions electronically. Five of them carry most revenue cycle work.
| Transaction | Adopted standard (version 5010) |
|---|---|
| Eligibility and benefits | X12 270/271 |
| Prior authorization and referrals | X12 278 |
| Claims | X12 837 |
| Claim status | X12 276/277 |
| Remittance advice and payment | X12 835 |
Our view: build on these transactions through your clearinghouse first. They are stable, they leave an audit trail, and a change arrives as a versioned standard instead of a redesigned web page. Use browser automation only for a payer that offers no transaction or API for the task. Our healthcare RPA guide covers where that line falls.
What the CMS prior authorization rule changes
The CMS Interoperability and Prior Authorization final rule applies to Medicare Advantage organizations, state Medicaid and CHIP fee-for-service programs, Medicaid managed care plans, CHIP managed care entities, and Qualified Health Plan issuers on the federal exchanges. Commercial employer plans are not on that list, so confirm each payer before you plan around the rule.
Three parts matter for automation planning. Covered payers, other than exchange issuers, must send prior authorization decisions within 72 hours for expedited requests and seven calendar days for standard requests. Starting in 2026, they must give a specific reason for a denied authorization. From January 1, 2027, they must offer a Prior Authorization API built on FHIR.
Our view: the API date gives you a reason to design authorization workflows around a payer API where one exists and keep a fallback for payers without one. The denial reasons give you cleaner data to classify. Read the CMS fact sheet, dated January 17, 2024, and check for later changes before you commit a roadmap. See our prior authorization automation and HL7 and FHIR integration pages.
Track filing deadlines per payer
Medicare fee-for-service claims must be filed no later than the close of the period ending one calendar year after the date of service, under 42 CFR 424.44. Other payers set their own limits, and contracts vary. A claim filed after the limit risks denial, so a deadline calendar per payer belongs early in an automation project.
Rules can compute the deadline when a claim is created, watch open accounts against it, and alert a named person before it expires. Our claim denial workflow includes this tracking.
Baseline your KPIs before you build
Automation without a baseline leaves you arguing about results. HFMA's MAP Keys define the equations. Days in AR (FM-1) is net receivables divided by average daily net patient service revenue. Clean claim rate (CL-1) is the share of claims that pass edits with no manual intervention. Remittance denial rate (AR-5) tracks denials at the remittance.
Record three to six months of each on the published definition before go-live. After launch, compare on the same definition and the same payer mix. Our revenue cycle reporting workflow builds these numbers from source systems so they do not depend on one analyst’s spreadsheet.
Where people stay in the loop
Automate steps that follow fixed rules. Keep a person on coding judgment, appeal review, and patient balance conversations. Route anything the software cannot classify to a named queue instead of letting it fail quietly, and review a sample of automated decisions each month.
HIPAA and vendor requirements
Revenue cycle data is PHI from end to end. Any vendor that builds or runs your automation is a business associate and needs a signed BAA before it sees a record. Read our post on BAA requirements for automation vendors and on preparing automated systems for a HIPAA audit. Billing companies can start at our medical billing automation page.
Sources
- Adopted Standards and Operating Rules. CMS. Lists the HIPAA-adopted transactions and their X12 versions. Page updated March 16, 2026.
- CMS Interoperability and Prior Authorization Final Rule (CMS-0057-F) fact sheet. CMS. Covered payers, decision timeframes, denial reasons, and the API date. Fact sheet dated January 17, 2024.
- 42 CFR 424.44, Time limits for filing claims. Cornell Legal Information Institute, reproducing the Code of Federal Regulations. The Medicare fee-for-service filing limit.
- MAP Keys. Healthcare Financial Management Association (HFMA). Industry-standard revenue cycle KPIs with defined equations.
We read these pages on September 25, 2026. Passages that begin “Our view” are our own advice. This guide is general information, not legal or billing advice.
Common Questions
What is revenue cycle automation?
Software that performs repeatable revenue cycle steps under fixed rules: checking eligibility, requesting authorizations, submitting and tracking claims, posting payments, sorting denials, and building reports. Staff handle the exceptions and the judgment calls.
Which revenue cycle tasks should we automate first?
Start where your own denial and rework data points. Our view: eligibility and authorization are common first picks, because a fix there prevents a denial and a fix downstream repairs one. Pull 90 days of denials, group them by root cause, and automate the largest recoverable group.
Does automation replace billing staff?
It removes repetitive lookups, keying, and status checks. Coding judgment, appeal review, and conversations with patients about balances stay with people. We hold appeals for human review by default.
How do we measure whether it worked?
Baseline a defined set of KPIs before you build, then compare on the same definitions afterward. HFMA's MAP Keys publish equations for days in AR, clean claim rate, and remittance denial rate, so your numbers mean the same thing to an outside reader.
What does revenue cycle automation cost?
Our builds run $60,000 - $300,000 per workflow, and managed operation starts at $10,000+ / month. Clearinghouse and payer portal fees sit outside those ranges.
Not sure which stage to automate first?
Send us a denial export and your payer list. We will group the denials by root cause and name the workflow with the largest recoverable amount. Read the wider guide to healthcare workflow automation.
Start with a conversation, not a proposal.
A 45-minute call with a senior engineer. We will tell you honestly whether automation is the right answer for the workflow you have in mind.