Controllers own the close, the controls, and the accuracy of the financial record. The prompts in this article are built specifically for that scope, not for analysis or strategic narrative, but for the operational and documentation tasks that define the controller's day.
These prompts are most useful in general purpose AI tools where the controller is drafting documentation, preparing sign-off materials, or writing responses to audit questions. Replace every bracketed item with your specific numbers, account names, and context. The more specific the input, the less revision the output requires.
Close Management Prompts
Close status report for CFO
Write a close status update for the CFO for [period], suitable for a brief daily update during the close cycle. Format as three sections: (1) Completed today — list tasks completed. (2) In progress — list tasks in progress with expected completion. (3) Blockers — list any items blocking close completion with the owner and expected resolution date.
Current status: [paste task list with status]
Blockers: [list any blockers]
Expected close completion date: [date]
Close cycle timeline, post-mortem
We completed the [period] close in [X] days. The original target was [Y] days. Using the following task completion log, identify the three tasks that caused the most delay, the root cause of each delay, and a specific change to the close process that would prevent each delay in the next cycle.
Task log: [paste task names, planned completion day, actual completion day]
Draft close process improvement memo
Draft a close process improvement memo following the [period] close. The memo should: identify the two or three most significant inefficiencies observed, propose a specific change for each, identify the owner of each change, and set a target for the next close cycle. Write in a direct, action-oriented style suitable for distribution to the accounting team.
Issues observed: [list]
Context: [any relevant background]
Prepare close day timeline for the team
Create a close day timeline for [period]. The close involves the following tasks: [list tasks with owner roles and dependencies]. The target close date is day [X] after period end. Build a day-by-day task schedule from day 1 through day [X], assigning each task to the earliest possible day given its dependencies, and flagging any tasks that are on the critical path to close completion.
Reconciliation Prompts
Reconciliation sign off summary
Write a reconciliation sign-off summary for the controller's review package for [period]. Include the following accounts: [list account names]. For each account, the summary should state: the GL balance, the reconciling items (if any) with amounts and expected resolution dates, the reviewer's name and date, and a sign-off status of Clear, Clear with items, or Escalate.
Account data: [paste balance and reconciling item detail for each account]
Escalation memo for aged reconciling item
Draft an escalation memo for the following reconciling item that has remained unresolved for [X] periods: Account: [name]. GL balance: [amount]. Sub-ledger or expected balance: [amount]. Difference: [amount]. History: [describe what has been done to resolve it and why it remains open]. The memo should recommend a resolution path — correcting entry, write-off, extended investigation — and state what approval is needed to proceed.
Intercompany reconciliation dispute note
Entity [A] records an intercompany [receivable/payable] of [amount] with entity [B]. Entity [B] records [receivable/payable] of [amount] with entity [A]. The difference is [amount]. Known reasons for the difference: [list]. Draft an intercompany dispute note that documents both positions, explains the difference, proposes the correcting entry, and identifies which entity should post the correction and why.
Journal Entry Review Prompts
Non standard journal entry sign off review
Review the following non-standard journal entry for appropriateness before sign-off. Entry details: Date: [date]. Preparer: [name/role]. Debit: [account, amount]. Credit: [account, amount]. Description: [paste description]. Supporting documentation: [describe what was attached].
Assess: (1) Is the accounting treatment correct for the described business purpose? (2) Is the description specific enough for audit? (3) Is appropriate supporting documentation attached? (4) Are there any aspects of this entry that would warrant escalation to the CFO? Provide a recommended action: Approve, Approve with amendments, or Escalate.
Journal entry description rewrite
Rewrite the following journal entry description to meet audit documentation standards. The current description is: [paste current description]. It is inadequate because: [explain — e.g. too generic, no business purpose stated, no reference to source document]. The business purpose of the entry is: [explain]. The rewritten description should be specific, reference the source document or approval, state the business purpose clearly, and be written in a way that an auditor reviewing it with no prior context would understand.
Journal entry population risk assessment
I am reviewing the journal entry population for [period] prior to close sign-off. The following entries have been flagged as requiring controller review: [list entries with date, preparer, accounts, amount, description]. For each flagged entry, assess the risk level (Low/Medium/High) based on the account sensitivity, preparer, timing, and description. For any High risk entry, recommend the specific additional information or documentation required before I approve it.
Control Documentation Prompts
Control narrative, full format
Draft a control narrative for the following control. Use a format suitable for SOX documentation or internal audit review.
Control name: [name]
Control objective: [what risk does this control address]
Control type: [preventive / detective / both]
Frequency: [daily / weekly / monthly / quarterly]
Performed by: [role, not name]
Reviewed and approved by: [role]
Procedure: [describe in step-by-step detail what the control performer does]
Evidence retained: [what documentation is kept as evidence the control operated]
Exception handling: [what happens when the control identifies an exception]
For period [date]: performed by [name] on [date], reviewed by [name] on [date]. Exceptions: [none / describe].
Control deficiency response
Draft a management response to the following control deficiency identified during [internal audit / external audit / self-assessment]: Deficiency description: [paste]. Root cause: [explain]. Impact assessment: [describe what could go wrong if this deficiency is not remediated]. Remediation plan: Owner: [role]. Actions: [list specific steps]. Target completion: [date]. Monitoring: [how will you confirm the remediation is effective]. Write in a tone that acknowledges the finding fairly and demonstrates a credible, time-bound remediation commitment.
ICFR design documentation
Draft an ICFR (Internal Control over Financial Reporting) design description for the following control process: [describe the process, e.g. month-end accrual review]. The documentation should cover: (1) the financial reporting risk being addressed, (2) the control activities in place to address that risk, (3) who performs each activity, (4) the frequency, (5) the evidence of operation, and (6) how exceptions are handled. This description will be provided to the external auditor as design-level ICFR documentation.
Audit Preparation Prompts
PBC response mapping table
Create a PBC response mapping table for the following audit requests. For each request, identify the document name that satisfies it, the location where the document is stored, and the preparer. Format as a table with columns: PBC reference, Request description, Document name, Location, Preparer, Status (Ready / In Progress / Pending).
PBC requests: [paste list of audit requests]
Audit finding risk assessment for management response
We have received the following draft audit finding from the external auditor: [paste finding]. Before drafting the management response, assess: (1) Is the finding factually accurate? (2) Is the risk characterization appropriate — are there mitigating factors the auditor may not have considered? (3) What is the most credible and proportionate remediation response? (4) Is there any aspect of the finding that warrants a rebuttal rather than acceptance?
Provide your assessment, then draft a management response that addresses each point.
Audit committee pre meeting briefing note
Draft a briefing note for the controller to present to the audit committee before the [period] external audit. The note should cover: (1) Summary of the period's financial reporting — any significant judgments, estimates, or accounting policy applications that the committee should be aware of. (2) Status of prior audit findings — are remediation actions on track? (3) Any new accounting standards or regulatory changes effective this period. (4) Known audit risk areas and how the team has prepared for them.
Context: [paste relevant details]
