reconciliation

Reconciliation

Important: This skill assists with reconciliation workflows but does not provide financial advice. All reconciliations should be reviewed by qualified financial professionals before sign-off.

Methodology and best practices for account reconciliation, including GL-to-subledger, bank reconciliations, and intercompany. Covers reconciling item categorization, aging analysis, escalation, and the deliverables that package reconciliation work: reconciliation memos, vendor correspondence, AP discrepancy trackers, and supervisor review packs.

Read Reconciliation Standards before you build — the cross-cutting output discipline, applied as checks on your own work (not a template): reconcile within the account's materiality threshold and show the computed difference (tight for cash/bank, looser for estimate-heavy accounts like accruals — it need not be exactly $0); tie support to the official GL / trial-balance figure that ties to the ERP, and show the difference; use live formulas, never hardcoded balances; cover the complete population; label each material figure disclosed-vs-derived with its source and period, and never present a guess as disclosed; document the inputs, methodology, exceptions above threshold, and a definitive conclusion — cross-tie related accounts for reasonableness (e.g., AR vs revenue given the payment terms) and propose the most-likely cause of each exception; and never guess silently — state the assumption you took wherever the inputs left a choice open. Apply the treatment the task calls for and don't impose structure it doesn't need; the sections below add the type-specific mechanics.

Structure precedence — apply before the methodology

The user's requested deliverable structure and any supplied template are authoritative. The formats below are examples of content, not required tabs or layouts.

• Preserve exact tab count, names, order, template rows/columns, headers, and formulas when specified. Do not insert a cover, README, requirements checklist, controls sheet, source index, copied source-data tab, memo, reviewer-notes tab, or exception tab unless explicitly requested or already present in the template.
• Keep the requirements checklist and detailed analysis in working notes. Put only requested output into the workbook.
• "Audit-ready," "controller-ready," "professional," and "reusable" never expand scope. Achieve those qualities with formulas, labels, and concise notes inside the requested tabs.
• If the request says "only," "exactly," "do not add/rename/delete/reorder," or "template exactly as supplied," treat that as a hard failure boundary. Do not apply a standard format that conflicts with it.
• When no layout is prescribed, choose the smallest structure that fully satisfies the request. Add a separate schedule or memo only when its content cannot fit clearly in an already-required tab and the user has not limited the structure.