Epic Hospital Billing and RCM Support
An outside billing team can work inside your Epic environment when your Epic team grants named, role-based accounts under a signed BAA. We work your assigned queues, check UB-04 and CMS-1500 claims, post remittances and report from your data.
Written by Salman Saeed, CEO and Co-Founder · Reviewed by a Certified Medical Coder · Last reviewed October 2026
In short: we work in your Epic environment with named accounts, role-based access, two-step login and a signed BAA. We take the queues you assign, check facility and professional claims, and report from your own data.
What is Epic and who uses it?
Epic is the electronic health record (EHR) software made by Epic Systems Corporation. Hospitals, health systems, clinics and specialty groups run it, and its billing work sits in modules that a billing team learns separately from the clinical screens.
Epic's health systems page describes integrated software that connects hospitals, clinics, post-acute care and a health plan. Its acute care page states that 3,300 hospitals and 73,000 clinics use Epic.
Epic's site names acute and inpatient care, primary care, more than 60 specialties, emergency and urgent care (the ASAP application), retail clinics, long term care and rehab. One build can hold a hospital, its clinics and its physician groups together.
This page covers how we work inside a client's Epic environment, mostly for hospitals and large groups. It makes no claim about any relationship with Epic Systems Corporation.
Which Epic billing modules should a billing team know?
Epic groups its billing and front-end tools under Access & Revenue Cycle. Epic's page for that area lists scheduling, referral management and authorization, price estimates, electronic coverage verification and revenue cycle automation.
Your Epic team tells us which billing applications are live in your build and which security templates control them.
Epic's patient financial experience page says statements can show a combined self-pay balance for hospital and professional charges. Both pieces must agree before a statement goes out.
How do we get set up inside your Epic?
Access rules for the whole company are on our security page. The same controls apply in Epic as in any client system: HIPAA training and NDAs for all staff, encrypted backups on our side, and a dedicated compliance officer.
What do we do inside Epic?
We work the revenue cycle steps your team assigns, in the order a claim travels. Claims go out within 24 hours of charge entry, and denials are worked within 48 hours.
- Review charges for missing or mismatched codes, modifiers, diagnoses and demographics before the claim leaves
- Check UB-04 facility claims for bill type, revenue codes, patient status, condition and occurrence codes, authorization and payer-specific rules
- Check CMS-1500 professional claims for rendering provider, place of service and modifiers
- Clear claim edits and submit through your clearinghouse
- Post ERA 835 remittances and reconcile them against deposits
- Work denial queues, appeals and A/R follow-up by payer and age
- Send patient statements and work patient balances
- Flag charge capture, coding and registration patterns back to your team
Claims leave Epic for a clearinghouse that your organization already uses, and we work with that connection instead of replacing it.
We also prepare dispute data for out-of-network claims. See out-of-network billing and IDR and the federal IDR process.
Which reports do we pull from Epic?
We pull reports by purpose and ask your Epic team to share the version that fits your build, because report names vary.
| Purpose | Question it answers |
|---|---|
| Charge lag | How many days pass between the date of service and a charge reaching billing |
| Discharged not final billed | Which finished encounters have not produced a bill, and what is holding them |
| Claim status | Which claims are waiting, rejected, in review or paid |
| A/R aging by payer | Where dollars are sitting, by payer and by age bucket |
| Denial trends | Which denial reasons repeat, by payer, department and provider |
| Payment variance | Where payers paid less than the contracted or expected amount |
DNFB means discharged not final billed.
What billing quirks come with an Epic hospital?
We do not attribute defects to Epic. These checks come from CMS and federal rules that matter when a hospital and its physician groups bill from one record.
| Check | Rule and source | What we look at |
|---|---|---|
| Which form | CMS Claims Processing Manual Chapter 25 calls the UB-04 a uniform institutional provider bill. Chapter 26 says professional and supplier paper claims to Medicare use the CMS-1500. | Facility charges and physician charges for one visit sit on the right claim type |
| Type of bill | Chapter 25, FL 4: a four-digit code showing facility type, care type and a bill frequency digit | The frequency digit on replacement and late-charge claims |
| Revenue codes | Chapter 25, FL 42: each charge in FL 47 needs a revenue code, and code 0001 is entered on the total line | Revenue code and HCPCS pairing on each line |
| Modifiers | Chapter 26, Item 24D: the CMS-1500 can carry up to four modifiers per line | Modifier order and what falls off if a fifth is added |
| Electronic format | Chapter 24 lists the X12 837 institutional and professional claims and the 835 remittance as HIPAA transactions | That the claim type matches the transaction sent through the clearinghouse |
| Remittance format | Chapter 22: CMS requires the ASC X12 835 version 5010A1 for electronic remittance advice | Posting of CARC and RARC codes and adjustment amounts |
| Filing limit | 42 CFR 424.44: Medicare claims must be filed within 1 calendar year after the date of service | Old unbilled accounts surfaced in the DNFB report |
Other payers differ, so we read each payer's own manual before applying a Medicare rule to a commercial claim.
How we handle billing in Epic
We work inside your Epic environment under your security rules, in the queues you assign, with named accounts, a signed BAA and two-step login. We report from your own data and flag problems back to your team with examples.
We align each EHR, clearinghouse and payer portal workflow with verified team experience, standard claim validation, reconciliation controls and performance monitoring.
To see how this would fit your hospital or group, book a call. You can also read about our hospital and facility billing and revenue cycle management services.
- Epic: Our Software · Epic Systems Corporation
- Epic: Health Systems and Clinics · Epic Systems Corporation
- Epic: Access and Revenue Cycle · Epic Systems Corporation
- Epic: Patient Financial Experience · Epic Systems Corporation
- Epic: Acute and Inpatient Care · Epic Systems Corporation
- Epic: Specialties · Epic Systems Corporation
- Medicare Claims Processing Manual, Chapter 25: Completing and Processing the Form CMS-1450 Data Set · CMS
- Medicare Claims Processing Manual, Chapter 26: Completing and Processing Form CMS-1500 Data Set · CMS
- Medicare Claims Processing Manual, Chapter 24: General EDI and EDI Support Requirements · CMS
- Medicare Claims Processing Manual, Chapter 22: Remittance Advice · CMS
- 42 CFR 424.44 Time limits for filing claims · eCFR
We check every rule, code and deadline against the official source. See our editorial policy.
Common questions
Straight answers from the team that does the work.
Ask a billing lead directly. A 20-minute call, Monday to Friday, 9am to 5pm Eastern.
01Can an outside billing company work inside Epic?
Yes, when the hospital or group allows it. Your Epic team creates named user accounts for the outside team and assigns security templates, after a business associate agreement is signed. You grant, limit and remove the access. We work the queues you assign.
02What access does a billing partner need in Epic?
Billing and follow-up access for the queues and reports in scope, set by role-based security templates your team approves. Each person has a named account with two-step login, and nobody shares a login. We ask for billing and follow-up access only.
03Which Epic reports matter for denial and A/R tracking?
We look for reports on charge lag, discharged not final billed, claim status, A/R aging by payer, denial trends and payment variance. Report names vary by build, so your Epic team shows us the version that fits your setup and agree the reporting format at setup.
04How do claims move from Epic to the clearinghouse and payer?
Epic prepares the claim, a clearinghouse your organization already uses carries it to the payer, and acknowledgments and remittances come back the same way. We work with your existing connection. Medicare Chapter 24 lists the 837 institutional and 837 professional claims as HIPAA transactions.
05How does Epic post ERA and 835 remittances?
Posting rules are set in your Epic build, so we follow your configuration. CMS requires the ASC X12 835 version 5010A1 for electronic remittance advice. We post payments, record CARC and RARC adjustments, reconcile against deposits and send unclear items to the denial queue.
06What billing mistakes are common with charge capture, modifiers and demographics?
We check for missing or late charges, a modifier on the wrong line, a fifth modifier on a CMS-1500 that holds four, and registration data that does not match the payer record. These are general claim checks we run on every account, not a verdict on any software.
07Is Epic data safe with an offsite billing team under a BAA?
We sign a business associate agreement with every client before access begins. All staff complete HIPAA training and sign NDAs, every system uses two-step login, backups are encrypted and automatic, and a compliance officer oversees it. Your team controls the accounts. Details are on our security page.
08Does Epic produce UB-04 institutional claims as well as CMS-1500 professional claims?
Hospitals bill facility services on the UB-04 and physician services on the CMS-1500, What your build produces depends on your setup, so we confirm with your Epic team and check each claim against the form rules in Medicare Chapters 25 and 26 before it goes out.
09How do we pull NSA and IDR dispute data out of Epic?
We ask your Epic team for the claim, charge, payer, service date and remittance data a dispute needs, then match it to the notice, the payment timeline and the original remittance. We never pull anything your account role does not allow. Rules and deadlines are on our federal IDR process page.
10How long does it take to move billing to a new vendor while staying on Epic?
The EHR stays in place, so the move is mostly access, queue ownership and report setup. The time depends on your security review, how fast accounts are approved and how many queues transfer. Scope is agreed at setup and written down with your team, so both sides know which queues move first.
11Is there a billing company that works in Epic?
Yes. Nucleus Align works in your Epic environment on the queues you assign, checking facility and professional claims, posting remits and working denials and A/R, with claims out within 24 hours of charge entry and denials worked within 48 hours, and you keep your own system.
12Can Nucleus Align work in Epic without sharing a login?
Yes. Each person on our team gets a named Epic account of their own under a business associate agreement, with two-step login. You can limit or end access whenever you decide. That keeps every action traceable to one person, and you decide when access ends.
Running Epic? Talk to us.
A 20-minute call about your payers, volume and setup. Monday to Friday, 9am to 5pm Eastern.