Review Supplied Business Reversals

The problem

Business reversals like refunds, chargebacks, and cancellations often leave messy trails across multiple systems. Relying on fragmented emails, trackers, and screenshots leads to duplicate recoveries, accounting errors, and incomplete closures.

What it does

• Decomposes original actions and intended reversals into a structured register.
• Cross-references evidence from supplied files, exports, and reports to identify documentation gaps.
• Flags duplicate recovery risks where multiple reversal paths (e.g., bank recall vs. credit note) exist simultaneously.
• Generates residual-action checklists and human validation scenarios for authorized reviewers.
• Organizes complex ownership, dates, and evidence requirements into a clear governance draft.

Frameworks & tools

Analyzes documentation from ERP, CRM, and accounting exports. Works with spreadsheets, emails, and screenshots supplied via the Read tool.

Why this beats prompting it yourself

Generic prompts often miss downstream effects like tax treatment, inventory restoration, or access removal. This skill enforces a strict multi-point verification protocol that surfaces hidden conflicts and residual exposures without assuming completion.

Use cases

• Reviewing high-value ecommerce order cancellations to ensure fulfillment stops match refund status.
• Auditing duplicate supplier payment recoveries to prevent simultaneous bank recalls and credits.
• Verifying account closure documentation to ensure access removal and billing stops align.
• Preparing reversal crosswalks for finance teams before month-end period closes.

Known limitations

Cannot access live systems or execute transactions. Analysis is limited strictly to user-supplied materials or data accessible via the Read tool.