AR Leakage Map — the seven places value leaves the receivable.
This redacted replica shows how VitaCoreX maps every stage where an accounts-receivable dollar loses probability of recovery. The live version is delivered under NDA. This sample shares structure, rubric, and tone; specific values are replaced with marked redactions.
Executive summary.
Five observations tied to dollar magnitude the finance team can recognize. No recommendation in this section — recommendations live in Section 5 after findings are established.
- Total AR under review is $[REDACTED]M across [REDACTED] customer segments; [REDACTED]% sits past 90 days.
- Packet quality score averaged [REDACTED]/12 — the 9.0 threshold where counsel accepts a handoff without additional research is not being met.
- Escalation thresholds drift between [REDACTED] and [REDACTED] days depending on who owns the account; similar balances are treated differently.
- Dispute ledger has [REDACTED] open items; median age is [REDACTED] days, which silently extends the recovery window on every balance they touch.
- Write-off trend is up [REDACTED]% YoY — underlying driver is documentation timing, not customer creditworthiness.
Methodology.
Fourteen days broken into three phases: data intake (days 1–5), domain scoring (days 6–10), synthesis and readout (days 11–14). Read-only access only; no system writes, no customer contact.
- AR aging pulls reconciled to operator close — weekly snapshots across trailing 180 days.
- Statistically sampled packet audit — [REDACTED] balances drawn across aging buckets, segments, and amounts; each scored against a 12-item rubric.
- Escalation practice interview — one per owning-role (CSM, billing lead, collections lead) focused on observed behavior rather than policy on paper.
- Dispute ledger audit — median age, resolution rate, root-cause mix across the ledger.
- Counsel-readiness check — if this balance walked to counsel today, which fields would counsel demand we fill in before acting?
Findings across seven domains.
Each finding follows: Observation → Impact → Root cause → Recommendation. Same template the live deliverable uses.
Finding 3.1 — Aging visibility
Observation: aging is visible per-segment but not reconciled to write-off trend. Impact: finance cannot distinguish collection delay from bad-debt acceptance. Root cause: report pipeline stops at 90-day bucket. Recommendation: extend aging view through 365 days with trailing write-off overlay.
Finding 3.2 — Packet quality
Observation: [REDACTED]% of 90+-day balances lack a single source-of-truth invoice matched to an executed contract line. Impact: every customer challenge requires a research cycle averaging [REDACTED] days. Root cause: packet is generated at billing, not re-generated at escalation. Recommendation: regenerate fresh packet at each escalation threshold.
Finding 3.3 — Escalation discipline
Observation: thresholds drift [REDACTED]–[REDACTED] days by owner. Impact: identical-profile balances experience materially different timelines — fairness and compliance exposure. Root cause: no network-wide written policy; thresholds inherited informally. Recommendation: 45 / 75 / 120 unified thresholds with documented overrides.
Finding 3.4 — Dispute ledger hygiene
Observation: [REDACTED] open disputes, median age [REDACTED] days. Impact: silently extends recovery window on every touched balance. Root cause: no SLA for dispute close; no owner by default. Recommendation: 10-day SLA with named owner; weekly stand-up on the over-SLA tail.
Finding 3.5 — Counsel-handoff readiness
Observation: readiness averages [REDACTED]% against the 90% counsel requires. Impact: counsel delays or bills additional research hours — both slow recovery and erode margin. Root cause: no single handoff template. Recommendation: codify handoff template; measure readiness as standing KPI.
Leakage band — low vs. recoverable.
Range-framed, not single-point. Low end assumes partial adoption; high end assumes full workflow adoption with packet refresh discipline.
- Low-band 6-month recovery
- $[REDACTED]MPartial adoption, refresh every 60 days
- High-band 6-month recovery
- $[REDACTED]MFull adoption, weekly refresh, unified thresholds held
- DSO compression estimate
- [REDACTED] daysWeighted-average at the 6-month mark
- Write-off trajectory
- DecliningDirection, not magnitude — engagement-close measurement
90-day remediation roadmap.
The sequencing the diagnostic recommends. Not a quote — scope and price are negotiated separately. Published so the operator can evaluate fit before discussing commercial terms.
Days 1–30
Unified aging view, packet template, pilot segment
Extend aging report through 365 days with write-off overlay. Publish the packet template. Select [REDACTED] pilot segments by volume and aging profile. No network-wide rollout in this window — containment until the pilot validates.
Days 31–60
Dispute SLA, threshold policy, refresh cadence
Deploy 10-day dispute SLA. Publish unified threshold policy with override rubric. Launch weekly packet refresh cadence on the over-60-day tail.
Days 61–90
Counsel-handoff template, operator handback
Publish counsel-handoff template with readiness KPI. Begin handback of monitoring cadence to the operator team with VitaCoreX in observer role through engagement close.
Out of scope.
Scope is deliberately narrow. Items below are either operator-side, counsel-side, or a separate commercial engagement.
- No legal representation or legal advice. Items that become legal matters remain with the operator counsel.
- No debt-collection activity. No balance is contacted, assigned, or referred by VitaCoreX during the engagement.
- No customer contact of any kind. All customer-facing execution remains the operator’s role.
- No contract renegotiation. Contracts read for ambiguity only; renegotiation is a separate engagement.
- No PHI, PCI, or regulated-data handling on VitaCoreX-owned infrastructure — all workflow runs inside the operator environment.
- No warranty of specific recovery outcome. Section 4 band is a modeled range, not a guarantee.