Sign in or create a free account to save this Card to your Deck.

Performance Card · Evidence of progress

Review days sales outstanding against a baseline

COLLECTIONS SHOULD BE MEASURED FROM A BASELINE.

Days sales outstanding describes time from sale to collection and can reveal receivables problems. Changes must be interpreted against payment terms, customer mix and actual receivable records. The standard is repeated observable capability under comparable conditions. Intent, documentation, or tool adoption alone does not establish performance.

Expanded teaching

Expanded teaching

The observable standard

Days sales outstanding describes time from sale to collection and can reveal receivables problems. Changes must be interpreted against payment terms, customer mix and actual receivable records. Performance means the capability produces a repeatable result under comparable conditions, not merely that a policy, dashboard, checklist, or tool exists.

What to measure

How does DSO compare across consistent periods, and what other conditions changed? Track billing timeliness, days sales outstanding, overdue balances, reconciliation completion, duplicate or exception rate, cost per transaction, cash visibility, forecast accuracy, and lag between operational activity and financial recording. Define the sample, period, baseline, and person authorized to judge the standard.

What does not count as evidence

Intent, training completion, software adoption, a single successful case, or a manually repaired exception cannot establish systemic capability.

Improvement cycle

Establish a baseline and review the underlying unpaid invoices before attributing an improvement to AI. Compare the observed result with the baseline, identify meaningful variation, test one improvement at a time where practical, and review whether the change remains effective under normal operating pressure.

Where AI belongs

AI can extract and match records, prepare reminders, detect anomalies, summarize approved financial data, and route exceptions. It should not autonomously move money, approve invoices, determine tax treatment, invent missing transactions, or replace qualified financial review.

Measurement limits

Metrics can reveal delay, error, variation, and progression without explaining every cause. Use them to select questions for investigation and add human context before consequential decisions.

Diagnostic inquiry

Questions to ask, not conclusions

What repeated observable evidence would show that “Review days sales outstanding against a baseline” is working at the required operating standard?

Questions that distinguish possible explanations

  • How does DSO compare across consistent periods, and what other conditions changed?
  • What upstream condition, control failure, or missing information could produce the same symptom?
  • If you take the proposed next action, what observable result will tell you whether it helped? Proposed action: Establish a baseline and review the underlying unpaid invoices before attributing an improvement to AI.

Practical application

Practical application

Establish a baseline and review the underlying unpaid invoices before attributing an improvement to AI. Use a recent, bounded sample instead of hypothetical data. Name one accountable owner, record the current baseline, define the acceptance or completion standard, and run the change through a normal operating cycle. At review, decide whether to keep, revise, expand, or stop the intervention based on evidence. Escalate immediately where privacy, security, legal, customer-harm, or material financial risks cannot safely wait for the test cycle.

Ask Atria

Talk through this Card

Talk it through with us

If this Card describes your week, a free conversation is the fastest way to see what it means for your company and what to do next.

Book a free conversation