monthly-closing-statements – Other skill for AI agents

Monthly Closing & Statements

What it is: The month-end checklist, the reconciliations it depends on, and the statements it produces.

Overview

Works out the smallest useful Monthly Closing & Statements setup for the business in front of it, then

builds it only when asked. The default output is a short recommendation, not a

spreadsheet. Artifacts - CSV, SQL DDL, JSON Schema, Notion mapping - are produced on

request, from one field list so they cannot drift apart.

Say this plainly at the start: the reconciliations are the hard part and reconciliations support reliable statements. A trial balance can be prepared during reconciliation and is not proof of completeness, valuation or recognition. Statement preparation also requires accounting judgments and review; unresolved material items must follow the entity's documented close/sign-off policy.

This skill produces an empty template. It does not close your books, does not calculate

your trial balance and does not draw a balance sheet. It records the checklist, the

answers and the period figures so the close is repeatable and the next person can see

what was still open.

Layer: Layer 8: Close & Analyse. Fits: Growth stage. Table code: n/a.

When to Use This Skill

• monthly closing checklist
• month-end reconciliation tracker
• trial balance preparation record
• monthly financial statements pack
• month-end analysis record

Also use it when the user says "the month-end checklist, the reconciliations it depends on, and the statements it produces", or describes the same process happening in a

spreadsheet, a document or someone inboxes.

Do not use it for: statutory filing, tax computation, or legal advice. This skill produces

empty templates only - it never holds or processes real employee or customer data.

How It Works

Follow the shared execution contract. The module-specific rules below define only domain fields, decisions, calculations, and safety constraints.

Step 1 - Identify intent

Read the request and pick the intent before asking anything.

• "set up" or "build" or "create" -> the user wants artifacts; go to Step 2.
• "our process is ..." or "it is in a sheet" -> the user wants to move an existing process; capture it, then Step 2.
• "is this right" or "review" or "audit" -> the user wants a check, not a build; answer from what they share.
• "how do I ..." -> advice question; answer directly and offer the build only if it helps.

Ask only if this is the highest-value missing fact; otherwise proceed without an opener:

> Q: What does your month-end close involve today, and how long does it take?

Step 2 - Ask only what is missing

Treat ambiguous replies as unanswered and ask which explicit option the user means. Record unknown values as Unknown; Unknown is not zero. A record must not be Done when a required check fails.

Skip anything the user already answered, in any earlier message. Ask the rest one at a

time, and stop as soon as the remaining answers would not change the output.

• Close - Who prepares and who reviews? / How long does it take? / Fixed target date?
• Reconciliations - Cash, bank, parties, inventory, TDS, VAT? / Which is the hard part?
• Adjustments - Depreciation? / Accruals and prepayments? / Provisions in use?
• Output - Trial balance, profit and loss, balance sheet? / Management reporting? / Any filing?
• Outcome - What do you need? / A closing checklist, a template or both?

Never invent an answer. If the user does not know, record it as unknown and carry on.

Step 3 - Hold the internal context

Hold the answers in this shape. It stays internal - it is not shown to the user unless

they ask, and it never carries a value the user did not give.

module: monthly-closing-statements
intent: null            # setup | advice | review | fix | build | convert | export
scale: null             # Starter | Growth | Scale, only if the answer changes it
areas:
  "Close": null
  "Reconciliations": null
  "Adjustments": null
  "Output": null
  "Outcome": null
requested_outputs: []   # csv | sql | json | notion | xlsx - requested formats only
confirmed_facts: []     # only what the user actually said
open_questions: []      # the unanswered ones, in the order worth asking

Step 4 - Recommend the smallest workflow

Build an already requested artifact without asking again. For advice-only requests, give a short recommendation and offer the relevant artifact.

Recommended approach: One closing record per month that carries every reconciliation as an explicit answer before any statement is drawn, then the period figures and a short written read on the position, so the close is repeatable and the next person can see what was still open.

Why this one: The statements are the easy part. They require accounting judgments as well as reconciled inputs, and a trial balance built on unreconciled balances is just arithmetic on top of errors. Putting the gates in the record is what stops a month being reported while cash, inventory or tax is still unagreed.

Workflow: Sales and purchase entries completed → Receipts and payments completed → Cash and bank reconciled → Party ledgers reconciled → Inventory reconciled → Statutory liabilities reconciled → Receivables and payables reviewed → Depreciation and adjustments recorded → Trial balance prepared → Statements prepared → Period analysed

Step 5 - Build only on request

Once the user asks for it, derive the fields from the confirmed context and emit the

requested artifacts. For machine-readable text, keep prose outside the data; for files,

provide a usable link. Report material validation failures or limitations separately.

**A selected Notion output is rendered by notion-manual-import, so route the

Notion step there.** When the user selects Notion, hand that step to

[notion-manual-import](https://github.com/sickn33/agentic-awesome-skills/blob/main/skills/notion-manual-import/SKILL.md): it holds the CSV, the property

mapping, the import steps and the verification checklist, and it renders the Field

Reference below instead of defining a table of its own. Do not restate the mapping

here and do not improvise the import steps. Manual CSV and mapping outputs need no

connection. For requested workspace changes, follow the shared contract: verify actual

tool access and the target before writing. A user saying "connected" is not tool evidence.

Never ask for a Notion password or token.

Closing Number,Period Start,Period End,Entries Completed,Cash Reconciled,Bank Reconciled,Party Ledgers Reconciled,Inventory Reconciled,TDS Reconciled,Other Statutory Liabilities Reconciled,Receivables Reviewed,Payables Reviewed,Depreciation Recorded,Accruals & Prepayments Reviewed,VAT/Tax Account Reviewed,Trial Balance Prepared,Financial Statements Prepared,Revenue,Gross Profit,Net Profit/Loss,Receivables Outstanding,Payables Outstanding,Working Capital,Cash Flow Position,Financial Position,Open Adjustments,Closing Date,Prepared By,Reviewed By,Status,Notes,Closing ID
CL-2026-08,2026-08-01,2026-08-31,Complete,Yes,Yes,Yes,Yes,Yes,Yes,Yes,Yes,48200.00,Yes,Yes,Yes,Yes,4820000.00,1542400.00,612000.00,486200.00,394800.00,,1284500.00,"Solvent, working capital thin against a 42 day collection cycle.",3,2026-09-05,Synthetic Preparer,Synthetic Reviewer,In progress,Three accruals still open; statements marked draft until cleared.,

CREATE TABLE monthly_closing_statements (
  closing_number VARCHAR(255),
  period_start DATE NOT NULL,
  period_end DATE NOT NULL,
  entries_completed VARCHAR(100) NOT NULL,
  cash_reconciled VARCHAR(100) NOT NULL,
  bank_reconciled VARCHAR(100) NOT NULL,
  party_ledgers_reconciled VARCHAR(100) NOT NULL,
  inventory_reconciled VARCHAR(100) NOT NULL,
  tds_reconciled VARCHAR(100) NOT NULL,
  other_statutory_liabilities_reconciled VARCHAR(100) NOT NULL,
  receivables_reviewed VARCHAR(100) NOT NULL,
  payables_reviewed VARCHAR(100) NOT NULL,
  depreciation_recorded NUMERIC(14,2),
  accruals_prepayments_reviewed VARCHAR(100) NOT NULL,
  vat_tax_account_reviewed VARCHAR(100) NOT NULL,
  trial_balance_prepared VARCHAR(100) NOT NULL,
  financial_statements_prepared VARCHAR(100) NOT NULL,
  revenue NUMERIC(14,2) NOT NULL,
  gross_profit NUMERIC(14,2) NOT NULL,
  net_profit_loss NUMERIC(14,2) NOT NULL,
  receivables_outstanding NUMERIC(14,2),
  payables_outstanding NUMERIC(14,2),
  working_capital NUMERIC(14,2),
  cash_flow_position NUMERIC(14,2),
  financial_position TEXT,
  open_adjustments INTEGER CHECK (open_adjustments >= 0),
  closing_date DATE,
  prepared_by VARCHAR(255),
  reviewed_by VARCHAR(255),
  status VARCHAR(100) NOT NULL,
  notes TEXT,
  closing_id BIGINT GENERATED BY DEFAULT AS IDENTITY PRIMARY KEY,
  created_at TIMESTAMP DEFAULT NOW(),
  updated_at TIMESTAMP DEFAULT NOW()
);

CREATE INDEX idx_monthly_closing_statements_status ON monthly_closing_statements (status);

{
  "$schema": "https://json-schema.org/draf

… (full content is in the download package)