Why pilots tell the truth

In pilots, reality shows up fast: real receivables, real stakeholders, and real edge cases.

Learning 1: data quality decides automation

The most common issues are simple:

  • incomplete debtor data
  • inconsistent invoice references
  • missing payment information
  • mismatched status definitions between ERP and process

The fix is not “more fields”. It is an OS principle: validation, normalization, and clear events.

Learning 2: timing matters more than escalation intensity

Many processes escalate too late or too mechanically. The OS layer needs timing as a control variable: which channel when, with what spacing, and with which exceptions.

Learning 3: tone must exist as policy

“Let’s send a reminder” does not scale. Tone is policy: by segment, jurisdiction, and state. That requires templates, approvals, and clear rules.

Learning 4: escalation needs guardrails

Automation without guardrails creates risk. In pilots, three guardrails proved essential:

  • Stop rules when conflict indicators appear
  • Approvals before legal steps
  • Audit trail for every decision

Takeaway

Pilots validated our OS approach: a unified state model, clear events, and governance make debt recovery faster and controllable.