01Exposure
Finance
- Candidate
- $239
- Reviewable
- $239
- Confirmed
- $0
A figure the board can ask about. Candidate, reviewable, submitted, and confirmed stay four separate numbers, each still attached to its findings.
The finance viewReimbursement intelligence for dental groups
Were we paid correctly?
Bitewing answers it for every claim your group adjudicates, with the source line, the expected amount, and the payer route attached. Your team decides.
EOB linePayer routeGoverning schedule$239 under expected
The ledger
Thousands of lines. One of them is wrong.
Every claim line was paid against a contract. Most are right. Bitewing checks all of them and finds the underpayments your team can prove, with the source line still attached.
Five places
Today the answer lives in five places. Drag to see it in one.Tap to see it in one.
The fee schedule in a spreadsheet. The EOB in a scanned PDF. The contract in a binder. The payer in a portal. The question in an inbox. Bitewing reads them together and keeps each one attached.
Today
Five places to look for one answer. Nobody can check every claim.
With Bitewing
Finding 8291-ESample · No PHI
$890 expected$651 allowed$239 under expected
- Fee scheduleExpected $890
- EOB lineAllowed $651
- Contract amendmentSchedule version active on DOS
- Payer portalPayer A · Network partner
- Inbox threadReview owner · Central RCM
Review-readyHuman decision
One record. Every source behind it. A person decides what happens next.
DragTap
Every source
Every source your group already keeps, converging on one record.
Dental groups reconcile reimbursement across claims, remittance, fee schedules, contract terms, payer routing, and location-specific systems. Those sources rarely arrive in one reviewable record. Bitewing connects the relevant context and keeps each finding tied to the line behind it.
Select a sourceSee what each one contributes to the sample finding.
Sample data · No PHI · Logos are trademarks of their owners · Connector availability is confirmed per deployment
Four steps
Four steps. One finding your team can stand behind.
No new queue. No new owner. Bitewing reads what you already keep, compares it, attaches the proof, and hands the decision to a person.
- Step 01
Connect what you already keep
Claims, remittance, fee schedules, and contract context. Read-only to start.
- Step 02
Compare every allowed amount to its contract
Actual allowed against the expected allowed on the service date, on the route that priced the claim.
- Step 03
Attach the evidence. Hold what is missing.
Every finding carries its source line, its comparison, and its review state. A missing source becomes a named request.
- Step 04
Your team decides
Approve, hold, or ask for more. Nothing moves until a person says so.
The gap
The gap comes last.The evidence comes first.
Once the source line, the expected allowed amount, and the contract period are in place, the difference is arithmetic. Open each one below. Then see what happens when a source is missing.
Finding 8291-ESample · No PHI
Remittance · ERA 835 · sample excerptLocation 14
Claim8291-E
Service date2026-03-12
ProcedureProcedure A
Billed charge$1,180
Allowed amount · this line$651
Plan paid$512
Patient responsibility$139
Adjustment · Sample adjustment$529
The actual allowed amount is read from this remittance line. Nothing is keyed in by hand, and the line stays attached to the finding so a reviewer can open it before trusting the number.
Review-ready · human decision
The context
The full context travels with the finding.
Every finding carries its source line, its allowed comparison, and its review state. When a required source is missing or in conflict, the finding stays held. Never pushed. Never hidden behind a confidence score.
Sample · No PHI
Four jobs
Recover what you can prove. Stop chasing what you can't.
One source-backed finding becomes a finance figure, a queue row, a contract pattern, and a payer packet. Only the provable bucket moves forward. The rest stay held and auditable.
Finding8291-ERoutePayer A · Network partnerScheduleActive on DOSExpected$890Allowed$651Difference$239 under expectedReviewReady · 41 days left
02Next action
RCM
- Queue
- Review-ready
- Owner
- Central RCM
- Evidence
- Complete
A queue with no mystery rows. Ready, held, and exactly which source is still missing. Blocked work never reaches the ready list.
The review queue03Pattern
Contracting
- Route
- Network partner
- Schedule
- 2026-01-01 → 2026-07-01
- Expected
- $890
The route and the schedule version that priced the claim, so a repeated shortfall becomes a contract conversation instead of a hunch.
Contract readiness04Packet
Payer relations
- Source
- Remittance line
- Comparison
- $890 vs $651
- Difference
- $239 under expected
Source line, comparison, and review state assembled into something a person can send.
The payer packetWhat gets pursuedOnly the first row moves forward. The rest stay held and auditable.
- Review-ready
Everything needed to prove it is attached.
Can move forward after team review.8291-E lives here - Needs evidence
An underpayment is likely, but a fact needed to prove it is still missing.
Held back with a specific evidence request. - Monitor pattern
The row is not ready for action, but the payer, source, or procedure pattern should stay visible.
Feeds payer and source review without entering the ready queue. - Not actionable
Paid as expected, out of time, or ruled out by a reviewer.
Suppressed from export but remains auditable.
One claim
Bring one claim. We will show every source behind it.
A 15-minute intro. Bring a reimbursement question. We will walk one complete example, source by source, or show exactly what would be missing before your team acts.
BAA available before PHILeast-privilege accessEncryption in transit and at restRead-only start