AC1 OHIP Error Code: What It Means and How to Fix It

You open your monthly remittance advice and see it: AC1. No obvious explanation, no clear next step. If your first instinct is to call your EMR vendor and report a system glitch, you are not alone, and that instinct will cost you somewhere between two and four hours of wasted administrative time, and potentially the claim itself.

Here is what AC1 actually means, why it keeps appearing, how to fix it correctly the first time, and how to stop it from repeating across your patient panel.

What Is the AC1 OHIP Error Code?

AC1 is an explanatory code that appears on your Ministry of Health Remittance Advice (RA) or Error Report. The Ministry's Remittance Advice Explanatory Codes document defines it plainly: "Maximum reached."¹

In practice, this almost always means a major consultation code has already been billed and paid for the same patient within the preceding 12 months, and the current claim has exceeded that frequency cap under the OHIP Schedule of Benefits.

A few important distinctions worth keeping in mind:

AC1 is an explanatory code, not a blanket outright rejection. The claim may have been paid in part, adjusted, or denied entirely. You need to read the full RA line item and the dollar amounts to understand the financial impact.
AC1 is a frequency-based rule, not a clinical judgment about the service you provided.
AC1 does not mean your billing software malfunctioned. The Ministry's adjudication system applied a rule and flagged the breach. The system worked exactly as designed.

The most common misread is assuming it is a technical transmission failure and resubmitting the identical claim. That triggers a second AC1, a second wasted billing cycle, and in some cases pushes the claim past Ontario's three-month stale-date submission deadline, converting a recoverable error into an unrecoverable financial write-off.²

When AC1 Appears: Root Causes for Ontario Physicians

AC1 does not appear at random. It fires because a specific billing rule limit has been exceeded. The root causes fall into three categories.

1. The legitimate frequency cap

A prior major consultation code was billed and paid for this patient, and the 12-month window has not yet reset. The new claim is valid clinically, but the billing code choice is wrong. The fix is a code adjustment, not a dispute.

2. The intake and referral triage gap

Front desk or intake staff treat every incoming referral form as a brand-new consultation. Patients being re-referred for chronic disease monitoring or longitudinal follow-up are booked under the default "New Consultation" appointment type. The system treats them as clean initial encounters despite prior billings within the rolling 365-day window. When this pattern is behind the rejection, AC1 will appear repeatedly across distinct patients, not just one.

3. EMR macro and template auto-population

Encounter note shortcuts, macro buttons, or order sets tie the closing of an encounter directly to a comprehensive initial consult code. If your clinical template defaults to a full consultation without prompting you to choose between initial, repeat consult, or assessment, high-volume recurring rejections are the predictable result. The physician or billing staff never sees the error upstream, only when the RA lands.

We have seen AC1 repeat in practices with three to five coding staff because nobody owned the audit trail connecting the appointment type to the fee schedule code being submitted.

Step-by-Step Remediation Workflow

Step 1: Stop the resubmission reflex

Before touching anything in your billing software, confirm you are looking at AC1 on the remittance advice. Do not re-click submit. Do not open an IT support ticket. Do not call the Ministry's service support line to report a system error. The system is not broken.

Step 2: Pull the 12-month claim history for that patient

Cross-reference the patient's file against all billed dates of service for the preceding 365 days. You are looking for a prior major consultation code that was already paid. If one exists and the diagnosis is the same or related, the correct path is a code downgrade, not a dispute.

Step 3: Determine whether this is a coding issue or a potential system error

Two scenarios change your path entirely:

Scenario A, Legitimate frequency cap: The prior consultation and the current one address the same clinical problem. The Ministry's rule applied correctly. Downgrade the code to a repeat consultation (e.g., A006, A036) or an appropriate assessment (e.g., A003, A004, A033, A034) based on the OHIP Schedule of Benefits, and resubmit on the next cycle.

Scenario B, Distinct diagnosis, possible system error: The rejected consultation has a clearly unrelated diagnostic code from the prior paid visit. MOH Bulletin #4736 identified a known system issue where claims submitted for an additional consultation by the same provider to the same patient, but with a different diagnosis, were incorrectly rejected.⁴ If your claim history matches that pattern and the service dates fall on or after October 1, 2019, with the original rejection occurring between November 1, 2019 and January 31, 2020, you may be entitled to file a Remittance Advice Inquiry (RAI) for the full consultation value rather than accepting a downgraded payout.

Step 4: File the RAI correctly if warranted

If your claim qualifies for an RAI, sequencing matters. The single most common mistake practices make is rebilling an alternate code in the standard EDT file before filing the RAI. Once an alternate claim pays out, the original consultation claim is effectively settled in the claims database. An RAI filed afterward will be flagged as already resolved, and you forfeit the differential.

When filing via eSubmit on the Ontario OPS BPS Secure Portal, attach the documentation to the exact accounting number, claim date, and RA payment run on which the reduction occurred. A general inquiry without those anchors will expire without manual review.

The documentation package that actually supports an AC1 appeal includes:³

The specific referral request letter from the referring physician, with date and distinct diagnosis clearly stated
The full consultation note, highlighting the assessment, management plan, and diagnostic formulation showing the encounter addressed an unrelated condition
The written opinion communicated back to the referring provider (dated letter or fax transmission confirmation, a consultation is not payable under Ontario regulations without this)
If defending an unrelated diagnosis: a one-page clinical summary demonstrating that the current problem is clinically distinct from the previously treated condition

AC1 vs. Code 32 vs. Code 40: Getting the Diagnosis Right Before You Fix It

Misidentifying which explanatory code actually applies will completely alter your operational next steps, and if you apply the wrong fix, the claim will be permanently rejected, stale-dated, or clawed back.

| Dimension | AC1, Maximum Reached | Code 32, Claimed Previously | Code 40, Allowed Only Once | |---|---|---|---| | Core meaning | A time-delimited frequency cap has been breached (e.g., one consultation per 12 months) | A literal system duplicate exists for the exact same code, patient, and day | A strict structural limit, either a lifetime maximum or a mutually exclusive service | | Trigger entity | Often a single specialist attempting a new consult before the time window resets | Same provider inadvertently double-submitting a file or day sheet | Same or different provider doing clinically incompatible work | | System visibility | Catches errors spanning months of patient history | Catches clerical batching or entry errors on the same date of service | Catches breaches of hard-coded medical policy guidelines | | Fix | Downgrade to repeat consult or appropriate assessment and resubmit | Verify if first submission was paid; if yes, write off second as administrative duplicate | Cannot be resolved by code-swapping; requires formal RAI with clinical notes proving extraordinary exception |

If you treat a Code 32 (duplicate) like an AC1 and swap the fee schedule code, you are now billing the Ministry for two different clinical services on the same day when you only performed one. That creates unintentional audit exposure for over-billing. If you treat an AC1 like a Code 32 and throw the claim away as a duplicate, you leave legitimate revenue on the table permanently.

For a broader look at how billing rule misalignments accumulate into revenue gaps, what medical school did not teach you about OHIP and medicare billing covers the structural knowledge gaps most Ontario physicians carry without realizing it.

Money you already earned, still unpaid

Recovery is separate work from ongoing billing. Charging only a percentage of what we recover, we review the backlog, correct what your documentation supports, and resubmit. Recent engagements have recovered five- and six-figure amounts, including rejected claims well past the 3-month stale dated deadline going back into 2023.

The alternative is usually your evenings or admin blocks, not billable clinic time. No setup or service fees. Every dollar recovered is money already written off, you keep most of it, and you pay nothing if nothing comes back.

“These claims weren’t chased up on. These claims have been stale dated. You add up the volume of money in there and it’s a consequential sum.”

Dr Sanjay Acharya, on what the recovery review found

Request a claims recovery review

When a Cluster of AC1 Errors Signals a Practice-Wide Problem

A single AC1 error usually reflects an isolated patient history scenario. A cluster of AC1 rejections across distinct patients in the same billing cycle points to an upstream breakdown in encounter classification, and it demands an audit, not individual claim-by-claim fixes.

The first thing to audit is your EMR's intake-to-billing rule map.

Pull an audit log comparing each patient's chart history against the fee schedule code submitted:

Filter all claims rejected under AC1 for the billing cycle
Cross-reference the service date with the last billed date of service in that patient's master profile
Verify the default billing trigger: was the code manually keyed by the physician, entered by a billing clerk, or auto-generated when a staff member clicked "Check-out" on an appointment slot that hardcodes a consultation code?

If the appointment setup defaults all referred encounters to initial consult codes without an automated lookback check or a required staff prompt asking whether the patient was seen within the last 12 months, your system will produce AC1 errors every single billing cycle until someone changes the rule.³

| Diagnostic step | Immediate action | Long-term safeguard | |---|---|---| | Claim recovery | Down-code rejected initial consults to repeat consultations or appropriate assessments; resubmit | Set billing software alerts to flag consultation codes billed within 365 days of a prior claim | | Intake reconciliation | Audit staff triage protocols; ensure repeat referrals are tagged "Follow-up / Re-assessment" not "New Patient" | Add a hard field to the intake workflow: "Has this patient been seen by our specialty in the past 12 months?" | | Cross-coverage check | Determine if rejections occur on shared patients across associates billing under the same specialty number | Coordinate group billing rules for inpatient rounds and shared outpatient consultations |

For practices running shared call schedules or multidisciplinary teams, patients seen by a colleague within the past 12 months will reject if coded as a major consult by a second provider unless the diagnosis is clearly, documentably distinct. That coordination gap is one of the more expensive blind spots we see in group practices.

The revenue impact of unresolved billing rule misalignments like these is covered in depth in our piece on the true cost of DIY OHIP billing. The short version: practices handling their own claims often carry 5–10% in annual revenue leakage from patterns exactly like recurring AC1 clusters that nobody is tracking month-over-month.

Preventing AC1 Rejections Going Forward

Prevention comes down to three operational habits:

Weekly claims review with a 365-day lookback. Before submitting consultation codes, your billing process needs to confirm whether a major consultation was billed and paid for that patient within the rolling year. This does not require sophisticated software, it requires someone owning the check. If nobody owns it, it does not happen.

Quarterly Schedule of Benefits refresh. OHIP fee schedule rules change. Which codes trigger AC1, what the frequency caps are, and which specialty codes carry specific restrictions can all shift. A quarterly read of updated MOH materials keeps your default codes aligned with current rules rather than last year's rules.²

Appointment type to fee code mapping audit. If your EMR auto-populates a fee schedule code based on appointment type without a physician confirmation step, you are one default setting away from producing a cluster of AC1 errors every billing cycle. That mapping is worth reviewing with your billing team at least once a year.

For Ontario specialists managing higher-complexity billing environments, understanding which AI and billing tools are right for your practice is a useful companion read for building the oversight infrastructure that catches these patterns before the RA arrives.

If this is useful in your practice, you can start with a Free OHIP billing review.

Frequently Asked Questions

Is AC1 a rejection or just a notice?

AC1 is an explanatory code on your remittance advice, not automatically a full outright rejection. The claim may have been paid in part, adjusted, or denied at nil depending on context. Always read the full RA line item and the claim amount before deciding your next step. The financial impact varies significantly depending on how the Ministry adjudicated the specific encounter.

Can I appeal an AC1 error?

Yes, in specific circumstances. If you believe the frequency cap was incorrectly applied, particularly if the rejected consultation addressed a clearly unrelated diagnosis from the prior paid visit, you can file a Remittance Advice Inquiry with OHIP within the appeal window. The key is sequencing: file the RAI before rebilling an alternate code in your standard EDT submission. If an alternate code pays first, the original claim is treated as settled and you lose the differential. Attach the exact accounting number, claim date, and RA payment run date to your eSubmit inquiry so the assessor can match your documentation to the claim record.

Why does AC1 keep happening to the same patient?

Likely causes include: your billing software not flagging prior consultations within the 365-day window, front-desk staff booking all returning referred patients under "New Consultation" appointment types, or an EMR template that auto-populates an initial consult code at checkout without a review step. Audit your appointment type to fee code mapping first. If the same patient triggers AC1 more than once, something in your workflow is systematically producing the wrong code for that encounter type.

Does AC1 affect my payment percentage or future OHIP billing status?

AC1 itself does not affect your billing licence or your payment rates. However, a recurring pattern of AC1 errors, especially across multiple patients in the same specialty code, can attract closer scrutiny during a Ministry claims review. Correcting the upstream workflow now is the right call for both revenue recovery and compliance hygiene. If you want to understand how OHIP billing audits work and what signals draw attention, what medical school did not teach you about OHIP and medicare billing is worth reading.

How do I know whether to downgrade the code or file an RAI?

It comes down to diagnosis. If the rejected consultation addresses the same or related clinical problem as the prior paid visit within the 12-month window, the Ministry's rule applied correctly. Downgrade to a repeat consultation or appropriate assessment code and resubmit. If the rejected consultation addresses a clearly distinct, unrelated condition with a different diagnostic code, and the original rejection occurred within the specific date windows referenced in MOH Bulletin #4736, you have grounds for an RAI. Document the clinical independence of the two encounters clearly, the referral letter, the consultation note, and the written report back to the referring physician are your three core pieces of evidence.

If you are seeing AC1 errors on your remittance advice and want to know whether they reflect an isolated coding adjustment or a pattern worth auditing across your full claims history, we are glad to take a look. Book your free OHIP billing review with the Physicians First team, we will show you exactly where the leakage is and what it is costing you.

References

Ministry of Health, Ontario. "Remittance Advice Explanatory Codes/Messages." April 2026. https://www.ontario.ca/files/2026-04/moh-remittance-advice-explanatory-codes-en-2026-04-07.pdf
Ministry of Health, Ontario. "Diagnostic Codes, Ontario Health Insurance Plan." March 2026. https://www.ontario.ca/files/2026-03/moh-diagnostic-codes-en-2026-03-13.pdf
Opsmed. "OHIP Rejection Code Lookup, 429 Codes, Free, No Signup." April 2026. https://opsmed.ca/ohip-rejection-codes/
MDBilling Support. "AC1, Rejection (AC1 Error), Maximum Reached." October 2025. References MOH INFOBulletin #4736 regarding known Ministry system errors causing AC1 rejections on legitimate same-provider, different-diagnosis consultations. https://support.dr-bill.ca/en/articles/9237577-mdbilling-ac1-rejection-ac1-error-maximum-reached