Payer Paper Trail

The problem in detail

Billing staff submit claims and then have no way to verify whether the payer actually processed them. Reps give conflicting or unverifiable answers by phone, emails go unreturned, and failures only surface weeks later as aged receivables. Staff burn hours re-calling the same payers with nothing durable to show for it, and withheld revenue piles up.

Proposed product

A claim follow-up tracker built around the phone call rather than the clearinghouse. For each outstanding claim, staff log a call in under 30 seconds: payer, rep name, call reference number, what was promised, and the date promised. The tool then watches that promise — if the check or EOB hasn't landed by the promised date, the claim resurfaces on a daily chase list with the full prior history on screen, so the next rep is quoted their colleague's own words and reference number. After a configurable number of broken promises, it assembles a ready-to-send escalation packet: a chronological call log, claim details, and a pre-filled state Department of Insurance prompt-pay complaint. Dashboards show aged claims by payer and which payers break promises most, so the office can target its limited follow-up time.

Why now

The evidence shows no sharp trigger: this is a long-standing problem, and the category is already crowded — Datarovers' Denials 360 advertises timestamped claim notes, automated payer-callback reminders and auto-generated appeal letters, and Amperos automates the payer call itself. What is genuinely open is the per-payer broken-promise record and the state Department of Insurance prompt-pay complaint, where Pennsylvania's rules require a provider to have contacted the insurer first, making a chronological call log a prerequisite for escalation.

Smallest useful version

A web app for a single billing office: manually add outstanding claims (CSV import of an aging report), log calls with promise dates, get a daily chase list of broken promises, and export a formatted call-history complaint document. No payer integrations or clearinghouse connection at first — the value is the enforced paper trail and the resurfacing, not automated status lookup.

Potential ways to charge

• Solo tracker — free: one user, up to 50 open claims, call logging and daily chase list, no export (free tier to earn the paid step; no comparable price in the evidence)
• Billing office — £59 per month: unlimited claims, up to 5 users, broken-promise chase list, payer scorecard, call-history export (typical for comparable small-business SaaS; evidence contains no pricing)
• Practice group — £179 per month: multi-location, pre-filled DOI prompt-pay complaint packets for your states, aged-claim dashboards by payer, CSV/PM-system import mapping (typical for comparable tools)
• Outsourced RCM vendor — £450 per month: multi-client workspaces, per-client reporting for the AR calling team, API access (typical for comparable tools; the ~200 AR caller vacancies suggest buyers who staff this work at scale)

Routes to early customers

• Employers posting AR caller vacancies on Indeed — roughly 200 listings surfaced; the hiring manager owns exactly this workflow
• Outsourced US RCM and medical billing firms whose staff phone payers all day, approached directly as multi-client buyers
• Practice-manager and medical-billing groups and professional associations where the manual call-log advice in industry how-to guides circulates
• Publishers of provider-facing follow-up guides (the ones telling billers to record date, rep name and call reference number) as content partners or referrers

Main risks

• Incumbents already cover the core: Denials 360 offers timestamped notes, callback reminders and auto-generated appeal letters, so a lightweight call tracker may be seen as a feature, not a product.
• Offices may simply use the notes field in their existing PM/RCM system; no surfaced evidence shows anyone complaining that current software fails at this.
• The riskiest assumption is untested — payers may ignore a quoted call reference and complaint threat just as they ignore phone chasing, so logging discipline collapses.
• DOI complaint rules and forms vary state by state (Illinois and Pennsylvania differ), so the escalation feature needs meaningful per-state build work before it is useful nationally.
• AI call-automation entrants such as Amperos attack the problem by removing the call entirely, which could make manual logging obsolete for the same budget.

Questions to test first

• Interview 10 billing offices or AR calling managers found via the Indeed vacancies: ask what they do with call reference numbers today and whether anything ever came of a logged promise.
• Run a 30-day manual pilot in one office using a shared spreadsheet plus a daily chase email, and measure whether logging discipline survives and whether promised payments land faster.
• Test the escalation claim: find two offices that have filed a state DOI prompt-pay complaint and ask what the log did to the outcome and timing.
• Show a mock payer scorecard (which payers break promises most) to five practice managers and ask whether it changes how they allocate follow-up time — this is the unclaimed angle.
• Price test the £59 and £179 steps against what they already pay for their PM/RCM system, to see whether this is an add-on budget or no budget at all.

Evidence and sources

The sources this assessment is based on. Evidence level: Indicative, counted from these sources as described in how ideas are assessed. Findings are what a source shows; anything the research only inferred is marked as an inference.

Research findings

• SupportsIndeed job listing (India, US RCM outsourcing)

  Shows: job-posting demand for manual payer calling

  An 'Accounts Receivable (AR) Caller' job posting describes the exact manual work the product targets: following up with insurers on pending, denied, rejected and underpaid claims and verifying claim status through payer portals, clearinghouses and outbound calls, requiring 2+ years US RCM experience. A related Indeed listings page shows roughly 200 AR caller/AR calling vacancies, indicating an entire labour category paid to phone payers by hand. Posting age shown as ~87 days at time of search; exact date not displayed.

• SupportsRCM vendor blog guide

  Shows: industry how-to guide describing the undocumented-call problem

  A provider-facing guide instructs billers that on every payer follow-up call they must record the date, the representative's name and the call reference number, saying this log becomes critical evidence later. That is precisely the data model the proposed tool captures in under 30 seconds, confirming the workflow exists and is currently handled by manual note-taking. Page age shown as ~236 days; no explicit publication date surfaced.

• SupportsState insurance department guidance (Illinois DOI; also Texas TDI, Oklahoma OID, 31 Pa. Code §154.18)

  Shows: regulatory mechanism for the escalation packet exists and is provider-facing

  Illinois DOI runs a provider complaint process explicitly covering prompt pay, where state law requires HMOs, insurers, IPAs and PHOs to pay claims promptly. Pennsylvania regulation requires providers to first contact the insurer about claim status and documentation before filing a department complaint — meaning a durable, chronological call log is effectively a prerequisite for escalation. This validates the product's DOI-complaint feature, though rules and forms vary state by state, implying meaningful per-state build work.

• Weakens the caseDenial management software vendor site

  Shows: competitive landscape — existing tools already offer call notes and follow-up reminders

  Datarovers' Denials 360 advertises timestamped claim notes and comments for audit, automated reminders for payer callbacks and follow-ups, timely-filing alerts and auto-generated payer-ready appeal letters. This overlaps substantially with the proposed tracker's core (call log + promise reminder + escalation packet), weakening pure differentiation; the unclaimed angle appears to be the broken-promise scoring by payer and the state DOI prompt-pay complaint output.

• Weakens the caseVendor roundup and healthcare software directory

  Shows: crowded category of denial/follow-up management products

  Elion's denials-management category lists many products, including Amperos, which performs automated payer follow-up, insurance-call and IVR navigation and payer-portal data collection — i.e. automating the call itself rather than logging it. A separate 2026 roundup lists ten denial management vendors (Availity, Experian Health and others). Incumbents and AI call-automation startups both compete for this budget, raising the bar for a lightweight call-log tool.

Where the problem was reported

Public posts in which people described this problem, grouped into one problem before research began.

• House insurance compensation advice · r/Insurance · 16 October 2026
• Meritain Health Denied Payments!! · r/Insurance · 14 October 2026
• Amica customer quotes? · r/Insurance · 14 October 2026
• Insurance lapse and plate revoked? · r/Insurance · 14 October 2026

Looked for, not found

• No first-person support complaint, app-store/G2-style product review, search-volume figure or public issue-tracker item was surfaced in which a billing office states that existing software fails to track payer call reference numbers and broken payment promises. Searches returned industry guides, vendor pages and job listings instead. Whether practice managers would pay for a standalone call-tracker rather than use their PM/RCM system's notes field is therefore untested — the strongest non-community signal found is indirect (job demand for AR callers).