Reconcile Business Records And Results

The problem

Discrepancies between systems, vendors, and reports often result in aggregate adjustments that hide underlying operational risks. Relying on date and amount matching alone leads to unexplained variances, timing errors, and failed audits.

What it does

• Analyzes discrepancies between source systems, vendor statements, and physical counts to identify root causes.
• Establishes authoritative data sources and stable business identifiers for one-to-one or many-to-many matching.
• Builds an item-level variance register with clear ownership, classification, and required actions.
• Converts manual reconciliation tasks into repeatable business controls with documented evidence and sign-off workflows.

Why this beats prompting it yourself

Generic prompts often attempt to force totals to match or suggest vague "data cleaning" steps. This skill enforces strict financial control logic, including cardinality checks, bridge populations, and segregation of duties, ensuring every material difference is evidenced rather than ignored.

Use cases

• Reconcile Shopify orders against Stripe settlements and ERP invoices.
• Validate WMS book inventory against physical cycle counts and 3PL records.
• Manage payment settlements, refunds, and chargeback bridges.
• Verify data integrity during system migrations or parallel runs.

Known limitations

This tool is read-only and cannot post journal entries, modify source systems, or release payments. It requires structured source reports or data exports to function effectively.