← BillabexCONTENT HISTORY

Update to Billabex

Snapshot Sep 30, 2026 · 22:57 UTC · version 2.0.0

Collection source: not recorded for this historical snapshot.

WHAT CHANGED · RULE-BASED ANALYSIS

First saved snapshot

No earlier snapshot is available to establish a change.

Compare saved observations

Download comparison JSON
Full technical diff · 0 changed fields
Full snapshot data
{
  "name": "analyze-receivables-statistics",
  "description": "Calculate useful Billabex receivables statistics from customer balances, invoices, communications, and tasks. Use for portfolio KPIs, outstanding totals, overdue rates, payment follow-up activity, customer concentration, or management reporting.",
  "included_files": [],
  "skill_md_contents": "---\nname: analyze-receivables-statistics\ndescription: Calculate useful Billabex receivables statistics from customer balances, invoices, communications, and tasks. Use for portfolio KPIs, outstanding totals, overdue rates, payment follow-up activity, customer concentration, or management reporting.\n---\n\n# Analyze Receivables Statistics\n\n1. Resolve the organization with `list-organizations` only when needed.\n2. Use `list-customer-balances` for account exposure and `list-invoices` for invoice counts, amounts, payment status, and overdue status. Use `list-communications` and `list-account-tasks` only when the requested statistics require them.\n3. Continue through every relevant page before calculating a portfolio-wide result. If complete pagination is not practical, label the result as a partial sample.\n4. Calculate only metrics supported by retrieved fields. Never infer a payment date, recovery rate, trend, or historical comparison from current-state data alone.\n5. Present the requested KPIs first, followed by concentration risks, notable exceptions, the covered period, and the calculation basis.\n\nKeep this workflow read-only. Respond in the language of the user's latest request. Copy proper names exactly. Never expose technical identifiers. Use natural business vocabulary and avoid internal terminology.\n"
}

SHA-256: dfa0606676998d5638e625b07c5e2819d417acd4e3080148581bee8ec4336d59