本文へ移動
cccskills
無料GitHub で公開

month-end-close

Run, document, or review a structured month-end close process. Use when an accountant says "help me with month-end close", "close checklist", "end of month tasks", "what do I need to do to close the books", "journal entries for close", "reconciliation checklist", "accruals and prepaids", "intercompany eliminations", "trial balance review", "close sign-off", or anything related to closing a financial period. Also trigger when someone is preparing for a quarterly or year-end close and needs a structured approach - even if they don't say "month-end close" explicitly.

インストール方法を見る

含まれるファイル(1)

  • SKILL.md7.3 KB

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

Overview

Based on "Intermediate Accounting" by Kieso, Weygandt, and Warfield - the definitive reference for GAAP-compliant period-end accounting. Month-end close is not a checklist of tasks; it is a controlled process that ensures the financial statements for the period are complete, accurate, and consistent with prior periods.

The principle: close in the right order. Work from operational accounts inward to the general ledger. Reconcile before you close. Review before you certify.

Workflow

Step 1: Pre-close - collect and cut off

Before posting any entries, establish a clean cutoff.

Revenue cutoff date: [date] - no revenue after this date posts to the current period
AP cutoff: [date] - all invoices received by this date must be accrued if not yet posted
Payroll cutoff: [date] - confirm last pay date and any accrued but unpaid wages
Inventory cutoff: [date] - confirm no receiving or shipping activity after cutoff

Actions:

  • Communicate cutoff dates to operations, AP, and payroll before period end
  • Pull a list of open POs and confirm which have been received (goods received, not yet invoiced = accrual needed)
  • Confirm bank activity through the last business day of the period

Step 2: Post adjusting journal entries

Work through the standard recurring entries in this order:

Accruals (expenses incurred, not yet invoiced)

DR: [Expense account]          $[amount]
    CR: Accrued Liabilities        $[amount]
Basis: [contract / estimate / PO / schedule]

Prepaids (expenses paid in advance, to be amortized)

DR: [Expense account]          $[amount]
    CR: Prepaid [Asset]            $[amount]
Basis: Monthly amortization of [insurance / rent / software / etc.]

Depreciation

DR: Depreciation Expense       $[amount]
    CR: Accumulated Depreciation   $[amount]
Basis: Fixed asset schedule, [straight-line / declining balance]

Deferred revenue (cash received, revenue not yet earned)

DR: Deferred Revenue           $[amount]
    CR: Revenue                    $[amount]
Basis: Performance obligation satisfied per ASC 606

Intercompany eliminations (consolidated entities only)

DR: Intercompany Revenue / Payable     $[amount]
    CR: Intercompany Expense / Receivable  $[amount]
Confirm: Intercompany balances agree between entities before eliminating

Step 3: Reconcile key balance sheet accounts

Every material balance sheet account needs a reconciliation. Complete these before closing:

AccountReconcile ToTolerance
CashBank statement + outstanding items$0
Accounts ReceivableAging report$0
Prepaid expensesPrepaid schedule$0
Fixed assetsFixed asset register$0
Accounts payableAP subledger / aging$0
Accrued liabilitiesAccrual schedule$0
Deferred revenueDeferred revenue schedule$0
IntercompanyAgreed balances with counterparty$0

For each reconciliation, document:

Account: [name and GL code]
Book balance per GL: $[amount]
Balance per supporting schedule / subledger: $[amount]
Difference: $[amount]
Explanation of difference (if any): [explanation]
Preparer: [name]   Date: [date]
Reviewer: [name]   Date: [date]

Step 4: Review the trial balance

Pull the unadjusted and adjusted trial balance. Review for:

  • Any account with an unexpected balance direction (e.g., a credit balance in an asset account)
  • Any account with a zero balance that normally has activity (may indicate a posting error)
  • Any account with a balance much larger or smaller than prior periods (investigate outliers >10% variance without a known explanation)
  • Revenue and COGS alignment - gross margin should be within expected range

Flag any unexplained variance over $[threshold] for investigation before certifying close.

Step 5: Produce the close package and certify

Compile the close package for review and sign-off:

PERIOD-END CLOSE PACKAGE - [Month / Year]

1. Income Statement - current month and YTD, with prior year comparison
2. Balance Sheet - end of period, with prior month comparison
3. Cash Flow Statement - current month
4. Reconciliation sign-off matrix (all accounts, preparer + reviewer initials)
5. Journal entry log - all entries posted in the period with supporting docs
6. Open items / exceptions - anything posted with an estimate or pending resolution
7. Key metric summary - gross margin %, headcount costs, top 5 variances vs. budget

Sign-off:
Preparer: _________________   Date: _______
Controller / Reviewer: _____   Date: _______
CFO (if required): _________   Date: _______

Do not certify close if any balance sheet reconciliation is open, any unexplained variance over threshold is unresolved, or any required journal entry is missing.

Anti-Patterns

1. Closing before reconciling Bad: Running the income statement and signing off before completing balance sheet reconciliations. Good: Reconcile first, close second. If a reconciliation reveals an error, the income statement changes. Sequence matters.

2. Accruals without documentation Bad: Posting an accrual for "estimated legal fees - $50K" with no supporting basis. Good: Every accrual needs a basis: a contract, a PO, an invoice, an email, or a calculation. "Management estimate" without support will not survive an audit.

3. Ignoring intercompany Bad: Allowing intercompany receivables and payables to differ between entities before elimination. Good: Agree intercompany balances before month-end. Unreconciled intercompany creates a fictitious asset or liability that distorts the consolidated balance sheet.

4. Posting adjustments after close Bad: Allowing operations to post invoices or receipts after the cutoff date into the closed period. Good: Hard-lock the period in the ERP after close. All late items go to the next period with a documented reason.

5. Close package without prior period comparison Bad: Presenting a single-period income statement with no prior period context. Good: Every close package should include at minimum a prior month and prior year column. A number without context cannot be reviewed.

Quality Checklist

  • Cutoff dates communicated and documented before period end
  • All recurring journal entries posted with supporting documentation
  • All material balance sheet accounts reconciled (no open reconciliations)
  • Trial balance reviewed for unexpected balances and outliers
  • Intercompany balances agreed between entities (if applicable)
  • Close package includes income statement, balance sheet, and cash flow
  • Prior period comparison included in the package
  • Open items and exceptions documented with owner and resolution date
  • Formal sign-off from preparer and reviewer before certifying close
  • Period locked in ERP after sign-off

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

Rate any product, feature, or experience on the 11-star scale (Brian Chesky's Airbnb thought experiment). Use when user says "rate this experience", "11-star", "star rating", "experience audit", "how good is this", "experience rating", "product audit", "quality assessment", or wants to evaluate product quality and identify improvement paths. Also trigger when user wants to benchmark a feature, assess where a product stands, or map out what "great" looks like - even if they don't explicitly say "11-star".

日本語の概要は準備中です。原文の説明を表示しています。

qa-aman/claude-skills202026年9月10日 更新

Generate A/B copy variants grounded in Eugene Schwartz's awareness and market-sophistication stages and John Caples' tested-headline discipline. Every variant declares its angle, the awareness stage it targets, and a falsifiable hypothesis, and the skill recommends which pair to test first and what delta counts as signal. Use when the user says "A/B test this", "write variants", "give me options", "test different angles", "copy variants", "ab copy", "test this headline", "multiple versions", "which version is better", or wants to test copy before publishing. For reviewing copy that already exists, see copy-review. For sample size and stopping rules, see growth-experiment. For diagnosing a page rather than its words, see page-cro. For full paid ad sets by platform, see ad-campaign-writer.

日本語の概要は準備中です。原文の説明を表示しています。

qa-aman/claude-skills202026年9月10日 更新

Write measurable acceptance criteria for requirements or user stories. Use when the user says "write acceptance criteria", "definition of done", "how do we test this", "fit criteria", "given when then", "Gherkin scenarios", "what does done look like", "testable conditions", "how will we know this works" - even if they don't explicitly say "acceptance criteria".

日本語の概要は準備中です。原文の説明を表示しています。

qa-aman/claude-skills202026年9月10日 更新

Build a strategic account plan for winning, retaining, or expanding a named account. Use when the user says "build an account plan", "strategic account planning", "how do I grow this account", "account expansion strategy", "whitespace analysis", "QBR prep", "key account review", "map the stakeholders in this account", "land and expand plan", "how do I break into [company]", or wants a structured strategy for a specific account.

日本語の概要は準備中です。原文の説明を表示しています。

qa-aman/claude-skills202026年9月10日 更新

Write paid ad copy for LinkedIn, Google, Meta, and YouTube. Produces multiple variants per platform, each targeting a different Eugene Schwartz awareness level and Cialdini persuasion principle. Use when the user asks for ad copy, ad variants, "write LinkedIn ads", Google ads, Meta ads, paid social copy, ad headlines, or wants creative for a paid campaign. Reads brand voice, ICP, and positioning from knowledge/. For organic social posts, see linkedin-post or social-calendar. For the landing page the ad points at, see landing-page-writer. For testing variants, see ab-copy-writer.

日本語の概要は準備中です。原文の説明を表示しています。

qa-aman/claude-skills202026年9月10日 更新

Design clean and consistent APIs. Use when the user says "design an API", "API design review", "design these endpoints", "REST API for X", "GraphQL schema", "API contract", "how should this endpoint work", "review my API design", or wants to create or improve an API interface - even if they don't explicitly say "API design".

日本語の概要は準備中です。原文の説明を表示しています。

qa-aman/claude-skills202026年9月10日 更新

qa-aman のスキルをすべて見る

このスキルの問題を報告する