FloQast vs. AuditBoard for Dental Support Organizations

Dental insurance claims can sit unpaid for 30, 60, or 90 days depending on the payer, and a downcoded or partially denied claim often needs a resubmission before it's fully resolved. An aging report at the DSO level that doesn't break out by payer and by location hides which specific relationships are actually the problem. Reconcile claims aging by location and payer monthly, and flag any bucket where the aging is trending worse than the prior period.

A management fee charged from the DSO's management company to each practice entity needs to eliminate cleanly when the group's financials consolidate, and a fee schedule that changes location by location, or an entity structure with a dental service organization model layered on top, makes that elimination easy to get wrong. Reconcile the management fee intercompany balance every close, not just at year end, so a mismatch shows up while it's one month's worth of noise instead of a full year's.

Production-based or collections-based doctor compensation typically runs on a formula tied to numbers that live in the practice management system, not the general ledger, and a true-up done quarterly or annually means a doctor's pay can swing significantly when the correction finally lands. Reconciling the compensation accrual against actual production monthly, even on a smaller scale than the full formal true-up, keeps that swing from becoming a surprise for the doctor or the business.

Recurring reconciliations for claims aging, management fee eliminations, and compensation accruals, repeated the same way at every location, is exactly what FloQast's checklist model handles well: the same reconciliation structure rolls forward location by location, with a reviewer who can see at a glance which sites closed clean and which are still open.

As a DSO grows past a handful of locations, brings on outside capital, or starts preparing for a sale, owners and lenders increasingly want documented evidence that reviews actually happened at the location level, not just that the consolidated numbers tie out. AuditBoard's controls library holds that evidence: who reviewed each location's close, on what cadence, and whether segregation of duties held between whoever bills insurance and whoever posts the resulting cash.

• If claims aging and management fee reconciliations are the recurring mess every close, start with FloQast.
• If a lender, private equity partner, or acquirer's diligence team has started asking for documented location-level review evidence, bring in AuditBoard.
• If doctor compensation true-ups are the source of the most disputes, fix that reconciliation cadence directly; the platform matters less than catching the gap monthly instead of annually. MeetMyCFO's AI CFO, Frank, can flag which location's claims aging has moved the wrong direction before the group-level close hides it inside an average.

A patient credit balance from an overpayment or an insurance overpayment that never gets refunded sits as a liability that grows quietly across dozens of locations if nobody reviews it on a schedule. Reconcile credit balances by location monthly, and set a policy for how long a credit sits before it's either refunded or escheated under your state's unclaimed property rules, which you should confirm with counsel since those rules vary by state. A DSO that never reviews this account tends to discover a much larger balance than expected the first time an outside party asks about it.

Say a single location's claims aging shows a growing balance with one specific payer, its management fee elimination is off by a small amount from the prior month, and its doctor compensation accrual hasn't been trued up in two quarters. Reconciled separately, each of those three items points to a specific, fixable cause: a payer relationship worth escalating, a fee schedule change that wasn't reflected in the intercompany entry, and a compensation formula overdue for its update. Combined into one location-level variance with no breakdown, the same three issues just look like the location is having a bad month, which is a much harder thing for a group controller to act on.