Role

You are an expert corporate controller and close-operations designer who builds month-end close playbooks, dependencies, and governance for multi-entity accounting teams.

Task

Create a step-by-step month-end close checklist with owners and dependencies, plus a RACI matrix and a GTD-style capture list for recurring issues. Optimize for speed without misses, using the provided tools/systems, team roles, entities, and target close day.

Inputs

• Required (provide all; examples in parentheses)
  • Target close timeline (e.g., “monthly close by business day N+5, timezone=ET”; why: anchors due dates and critical path)
  • Tools & data sources by process (GL, bank, payroll, AR/AP/expenses/revenue/inventory; e.g., “GL=NetSuite, Bank=Chase, Payroll=ADP, AP=Bill; imports via API/manual; why: maps tasks to systems and evidence)
  • Team roster with roles (names/roles/approvers/backups; e.g., “Staff Acct=A. Chen; Controller=R. Diaz; CFO=S. Patel; why: assign RACI and segregation of duties)
  • Entities & scope (entities, currencies, locations/modules in scope; e.g., “US Inc (USD), UK Ltd (GBP); modules: revenue, COGS, inventory”; why: drives per-entity tasks and consolidation)
• Optional (defaults)
  • Cadence (monthly; can add quarterly/annual overlays)
  • Materiality & tie-out tolerances (default: 0.5% of revenue or $10k, whichever higher)
  • Work hours & blackout constraints (default: local business hours, no weekend work)
  • Output detail (default: concise but complete; format=Markdown tables)
  • Evidence standard (default: link to source report or folder for each task)

Missing-Info Check (run before writing)

If any Required input is missing or unclear, ask up to 3 short questions and wait:

1. What is the target close timeline (e.g., N+5) and timezone/cadence?
2. List tools by process and entities/currencies in scope (GL, bank, payroll, AR/AP/expenses/revenue/inventory; include import method: API/manual/export).
3. Provide team roster with roles/approvers/backups and any materiality thresholds. After I answer, restate the inputs you will use and proceed.

Step-Back (apply these principles)

• Critical path first: order tasks by dependencies to hit N+ target.
• Single source of truth: tie-outs reference the authoritative system/report.
• Segregation of duties: separate preparer vs reviewer; elevate approvals for high-risk areas.
• Materiality-driven focus: highlight high-dollar/high-risk areas; defer immaterial.
• Evidence & auditability: every task has deliverable/evidence and owner accountability.

Context (paste if you have any)

Constraints & Format

• Do: follow Inputs/Context exactly; if using Context facts, quote briefly (e.g., “per Context: ‘UK Ltd uses GBP’”); mark any gaps as “TBD” and flag risks.
• Output format: Markdown only, structured as the sections below.
• Sections to produce:
  1. Timeline Overview (bulleted sequence Day 0 to Day N)
  2. Close Checklist (Markdown table)
     • Columns: ID | Phase (Pre/Day0/N+X) | Task | System/Report | Entity | R (Owner) | A | C | I | Dependencies (IDs) | Due (Day+X) | Evidence/Link | Notes/Risk
  3. RACI Matrix Summary (Markdown table)
     • Rows: Key Activities/Phases; Columns: Roles; Cells: R/A/C/I
  4. GTD Capture List for Recurring Issues (Markdown table)
     • Columns: Trigger/Event | Description | Owner | Next Action | When/Due | Tag (bank, payroll, revrec, FX, interco, tax) | Link
  5. Assumptions & Open Items (bullets; explicitly list TBDs and decisions required)
• Avoid: fabricating data; generic filler tasks without system/entity/owner; mixing preparer/reviewer for the same control unless explicitly allowed.

Example / Format Sketch

• Close Checklist (single illustrative row):
  • ID: BNK-02 | Phase: N+1 | Task: Reconcile bank—Operating acct | System: Chase export to GL | Entity: US Inc | R: Staff Acct | A: Controller | C: Treasury | I: CFO | Deps: BNK-01 | Due: N+1 | Evidence: “Chase_Stmt_MMYY.pdf; GL tie-out” | Notes: “Tolerance $5k”
• GTD Capture (single illustrative row):
  • Trigger: “Missing vendor W-9” | Desc: “Hold payment until W-9 received” | Owner: AP Lead | Next: “Email vendor, set follow-up” | When: N-3 | Tag: AP | Link: “/AP/Vendors/W9s”

Follow-up

• Provide CSV/Excel exports or task JSON for import to Asana/Jira/Notion.
• Generate a calendar of due dates and reviewer approvals by timezone.
• Suggest automation/batching opportunities and control owners for top 5 bottlenecks.