All posts
Billing & RCM8 min readBy The Velano Team

How Guardian EOBs Are Processed (Step-by-Step)

Guardian dental explanation-of-benefits processing works best when the office runs one repeatable workflow: verify claim status, open the full EOB, match it to the…

Guardian dental explanation-of-benefits processing works best when the office runs one repeatable workflow: verify claim status, open the full EOB, match it to the original claim, post the ledger, and route any exception before billing the patient. The friction is rarely the form itself. One payer notice can trigger posting decisions, patient-balance changes, documentation requests, and appeal work all at once — and when those handoffs are unclear, statements go out too early and the front desk gets pulled into billing cleanup.

This guide is for office managers, billers, practice owners, and DSO operations teams who want a cleaner posting workflow. It covers what the EOB means, how to pull it in Guardian Anytime, which fields drive posting, and how to handle the common exceptions — predetermination, coordination of benefits, and requested-information letters — before they turn into rework.

Key takeaways

  • The EOB is a posting document, not just a patient notice. Read the whole thing, not only the payment amount.
  • Guardian Anytime shows claim status for the past 30 days by default and adds an EOB button once a claim is paid.
  • The fields that matter most are the submitted ADA code, the alternate code, tooth/arch notation, the payment outcome, and the remarks.
  • Predetermination, COB, and requested-information letters change whether you can post or must hold the claim.
  • The strongest workflow uses one review sequence and one escalation rule before any balance is finalized.

What a Guardian dental EOB tells your team

A Guardian EOB explains how the payer processed the submitted claim and what that result means for posting and patient responsibility. Guardian issues the EOB after services are provided and processed, and its glossary is built around field-by-field interpretation — which makes the EOB the reference point for ledger decisions, patient communication, and follow-up.

ADA guidance on reading an EOB adds an important warning: remark codes are often where bundling, least-expensive-alternative-treatment (LEAT), downcoding, and documentation requests appear. That's exactly why staff should read the full EOB rather than the payment line alone.

A repeatable Guardian EOB workflow

Use the same review sequence every time — it creates one auditable standard instead of letting each biller decide differently.

CheckWhat the team confirmsWhy it matters
StatusPaid claim, letter request, or pending itemStops staff posting from the wrong screen
Payment logicSubmitted code, alternate code, remarksCatches downcoding, bundling, and LEAT issues
Exception reviewCOB, predetermination, attachments, limitationsPrevents premature statements and rework
Next actionPost now, hold, appeal, or document follow-upKeeps each EOB in one queue

The full office workflow:

  1. Open claim status in Guardian Anytime. Claims from the past 30 days display automatically under Claims, then Claim status.
  2. Locate the claim outcome. When the claim is paid, an EOB button appears beside it.
  3. Check for requested-information signals. A Letter button means information was requested; open it for the details sent to patient and provider.
  4. Match the EOB to the original claim. Compare submitted CDT codes, tooth numbers, service dates, and billed fees against the practice record before posting anything.
  5. Review payment logic. Confirm whether the claim paid as submitted, paid on an alternate code, applied plan limitations, or shifted balance responsibility.
  6. Post the insurance payment and adjustment. Record the insurer payment, any contractual write-off, and the remaining patient balance per the EOB.
  7. Document the exception if the EOB changed the expected outcome — downcoding, bundling, missing documents, COB, or predetermination mismatch.
  8. Assign the next action. Close the claim only if the ledger, notes, and patient balance match the EOB and no follow-up letter, appeal, or rework remains.

The Guardian EOB fields that drive posting

Guardian's glossary defines the fields most relevant to posting. The Submitted/ADA Code field shows the ADA code billed and the service description. An Alternate Code appears when benefits were based on a different code than the one submitted — a signal to review for downcoding first. Tooth notation uses adult teeth 1–32, child teeth A–T, and arch markers such as UR, UL, LL, LR, UA, LA, and FM.

Guardian EOB fieldMeaningPosting action
Submitted ADA codeOriginal CDT code billedMatch to the claim
Alternate codeDifferent code used for benefitsReview downcoding first
Tooth / arch notationLocation processedConfirm the right procedure
Payment and patient shareAmount Guardian paid and amount leftPost payment and balance
Remarks / letter triggerWhy the claim changed or pausedRoute to follow-up

If the remarks mention bundling, LEAT, downcoding, or a documentation request, treat that as workflow direction, not boilerplate.

How to pull the EOB from Guardian Anytime

Open claim status in Guardian Anytime, locate the claim, and select the EOB button shown on paid claims. The portal signal tells you the next action:

Portal signalWhat it usually meansNext team action
EOB buttonClaim paid and EOB availableOpen it, compare to the claim, post only after review
Letter buttonGuardian requested informationHold posting, open the letter, route to documentation follow-up
No EOB yetClaim pending, outside the default view, or unavailable onlineRecheck status, widen the date range, use the phone workflow

Save the EOB in the same place every time so it can be tied back to the ledger and any later appeal. Guardian also notes that Managed Dental Care claims aren't viewable in Guardian Anytime, so route those directly to the phone workflow.

When the EOB doesn't match the estimate

When a Guardian EOB doesn't match the treatment estimate, stop posting and trace the gap to coding, plan rules, timing, or COB. Run this checklist before changing the balance:

  • Reconfirm the exact CDT code and tooth number submitted.
  • Check whether Guardian paid on an alternate code.
  • Review remarks for documentation requests or limitation language.
  • Confirm whether a predetermination existed and was still valid.
  • Check whether coordination of benefits changed the expected payment path.
  • Hold patient billing until the team knows the balance is final.

If these exceptions keep repeating, the office usually has an upstream workflow problem rather than a posting-speed problem.

How predetermination and COB change things

A processed predetermination stays valid for 12 months unless benefits change, and requests typically process within 28–30 days unless more information is required. When a major-service claim pays differently than expected, confirm whether the predetermination was current and whether the final treatment matched what was submitted.

Coordination of benefits adds another layer: one plan is primary, others are secondary, and the secondary determines benefits after considering what the primary paid. That means the first EOB may be a checkpoint, not the final posting event — hold patient billing until the sequence is clear.

Common mistakes to avoid

  • Posting from claim status alone instead of opening the full EOB.
  • Ignoring the alternate-code field when the plan paid on different logic.
  • Skipping tooth or arch verification and posting the right dollars to the wrong procedure.
  • Treating a Letter button like a paid-claim event instead of a documentation task.
  • Finalizing patient responsibility before COB is complete.
  • Using different note formats by office or biller, so appeals and audits take longer later.

For teams posting across carriers, the same control points carry over to the Aetna EOB process, how BCBS EOBs are processed, and the Cigna EOB workflow. The fix is usually simple: one checklist, one note template, one escalation path, and one shared definition of when a claim is actually done — the same discipline that catches EOB posting errors and underpayments.

How Velano helps upstream

Many Guardian EOB exceptions begin before the claim is ever posted — a missing subscriber ID, a wrong date of birth, an incomplete callback reason, or an after-hours question that never got captured. Velano doesn't post EOBs, file appeals, or do billing. It's an AI receptionist for dental practices that answers every inbound call and text 24/7 and books directly into your PMS.

Where it helps: Velano collects cleaner information during the first patient interaction — subscriber ID, date of birth, plan, and the reason for the call — and writes it into Open Dental, Eaglesoft, Denticon, and other systems, so the billing team works from accurate intake instead of fixing it after the claim. It answers overflow and after-hours so insurance questions don't get lost in voicemail, and it gives callers a natural next step instead of another hold loop. Cleaner intake usually means cleaner claim follow-up downstream — and it pairs with the upfront work of verifying Guardian dental coverage before the visit.

The bottom line

The right Guardian EOB workflow is the one your team can run the same way every time without leaking revenue or creating rework: open the full EOB, verify codes and tooth notation, post only after checking remarks, and hold the claim when letters or COB are involved. When the same missing details keep showing up before the claim is even posted, the bigger win is upstream — cleaner intake and a phone that always gets answered.

See Velano answer a live call for your practice.

Stop losing patients to voicemail.

See how Velano answers every call, books into your PMS, and follows up — so patients show up.