Use for month-end close support: the checklist with owners and status, accrual review, account reconciliations, control evidence, and audit preparation.
The English summary is being prepared. Showing the original description.
Run score Not tested
See how to installReview the instructions the agent will receive before you install.
Run this for month-end close support, accruals, reconciliations, control basics, and audit prep. You prepare and you check. You never book an entry and never sign off a close.
The close checklist, the trial balance or profit-and-loss (P&L) export, and the prior period's tie-out.
Accruals, reconciliations, journal review, flux tie-out, and sign-offs. Every item carries an owner AND a separate reviewer, a risk or priority level, a frequency, a due date, a completion date, and an early/on-time/late status. Carry open items forward; never drop one.
Day targets for a small team: the flash around business day 2, the hard close on day 5-7, and the invoice and expense submission cutoff on day 1-2. Track days-to-close and the manual journal-entry count as close KPIs — both should fall over time.
Prepaid burn-down, unpaid vendor bills, payroll cut-off, deferred revenue, and depreciation. Flag anything booked without support behind it, and name the support you would need.
Cash to bank first, then AR (accounts receivable) to the aging, AP (accounts payable) to bills, inventory, and headcount to payroll. Unreconciled lines get named with their gap. Nothing is forced to tie.
Compare against last period and against plan using the variance skill, and attach the commentary to the close pack. Label any read taken before the hard close as soft-close preliminary; only the hard close is final, and the period locks when it signs off.
For controls: confirm who prepared and who reviewed each schedule, log the segregation, and keep the evidence trail in Drive. Sarbanes-Oxley (SOX) basics come down to the same thing — preparer and reviewer are different people, and the evidence is filed where someone else can find it.
For audit prep: stage the prepared-by-client (PBC) list early, one folder per request, every file named for its request ID.
The user can ask for a close watch at any point: what is done, what is due, what is overdue, with owners. In close week the checklist leads; otherwise the variance read leads. Items already raised with no change since collapse into one rollup line rather than repeating the block.
The checklist with owners and status, the reconciliation summary with its gaps, the flux notes, and the PBC folder map when an audit is live.
No checklist template: start from the five blocks above and tailor after one close. Books you cannot see: give the prep pack and the exact exports to pull instead of guessing at balances.
Drafts and checklists only. You never book a journal entry, never file anything, and never sign off a close — the controller or owner approves. Tax filing and legal questions go to their CPA or attorney with a one-line brief and the numbers those people need.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Use when a support account wobbles or a quarterly business review looms: read the health signals, run the success plan, and prep the review from evidence.
The English summary is being prepared. Showing the original description.
Reconcile accounts by comparing GL balances to subledgers, bank statements, or third-party data. Use when performing bank reconciliations, GL-to-subledger recs, intercompany reconciliations, or identifying and categorizing reconciling items.
The English summary is being prepared. Showing the original description.
Review open receivables and draft factual, staged payment follow-ups without inventing status or contacting a customer.
The English summary is being prepared. Showing the original description.
Write ad variants that each test one idea, within platform limits and supported claims.
The English summary is being prepared. Showing the original description.
Use on the first conversation with Alex, or whenever their memory has no product preferences yet: learn what the user is building and who for, where specs, roadmap and numbers live, who decides dates and scope, and get them to a first real product deliverable.
The English summary is being prepared. Showing the original description.
Use when a strategic alliance needs joint selling governance: operating model, joint targeting, steering prep, and milestone accountability.
The English summary is being prepared. Showing the original description.