month-end-prep

Preparing for month-end closing

Month-end closing usually turns into an evening with three open tabs where nothing reconciles, and a couple of receipts have gone missing. This skill walks you through the reconciliation step by step: it catches transactions without a category, duplicates, and missing source documents, and at the end it writes a human-readable summary — "here's how much we earned and why" — rather than an accounting memo that no one will ever read.

Quick start

Connect ~~бухгалтерия (1C/MySklad) and at least one source ~~платежи (YooKassa, Tinkoff, bank statement), then say "let's close the month." Claude will walk you through each checklist item, pausing for your input at every confirmation point.

If there's no connector, Claude will switch to a CSV export — it won't silently skip a single step.

Workflow

Go through the steps in order. Each step has a completion state; don't move on to the next one until the current one is closed.

Step 1 — Agree on the month being closed

Ask the owner which month we're closing. Default to the previous calendar month if they haven't specified. Confirm before pulling data.

Step 2 — Pull the P&L and the transaction register from accounting

Request from ~~бухгалтерия:

• Profit and loss statement (P&L) for the month being closed (revenue, cost of goods sold, gross profit, operating expenses, net profit)
• Transaction register: every income and expense line

Flag right away:

• Transactions without a category — any line with the category "No category"/"Unallocated" or empty
• Needs clarification / For review — the accounting system's own flag

Show the count ("14 transactions without a category") and list them so the owner can assign them to categories before continuing. Do not move forward with open transactions without a category unless the owner explicitly says "skip for now".

See reference/quickbooks-reconcile.md — reconciliation with accounting data (1C, etc.): matching fields and notes.

Step 3 — Pull in acquiring payouts and statements

Request payout reports from ~~платежи — YooKassa, Tinkoff, SBP, bank statement, whichever are connected — for the same calendar month.

Match each payout with the bank receipt in the accounting system:

• Matched — the amount and date agree within 2 days → mark as reconciled
• Discrepancy < 0.50 ₽ — rounding/fee; record it, but do not mark it
• Discrepancy ≥ 0.50 ₽ — mark it with the delta amount
• There is a payout, but no receipt in the accounting system — mark as "not in accounting"
• There is a receipt in the accounting system, but no payout — mark as "not in acquiring/bank data"

See reference/paypal-settlements.md — the field structure of statements and payout reports (YooKassa, Tinkoff, bank).

Step 4 — Find suspicious duplicates

Scan the transaction register for likely duplicate debits or credits. Mark a transaction as a suspicious duplicate when all three:

• The same amount (within 0.01 ₽)
• The same supplier or customer
• Posted within 5 calendar days of each other

Show the marked pairs to the owner. They decide which one is legitimate (for example, a weekly recurring subscription) and which is a real duplicate to be deleted.

See reference/gotchas.md — common false positives and how to distinguish them.

Step 5 — Verify source documents (connector ~~хранилище / Desktop)

If the connector ~~хранилище (Yandex Disk, etc.) or Desktop is available, scan the folder with source documents (ask the owner for the path; by default ~/Documents/Первичка) for the month being closed.

For every expense transaction in the accounting over 2,000 ₽ without an attached document:

• Check whether there is a suitable source document file (act, invoice, receipt, UPD) — by amount ± 0.50 ₽ and date within 3 days
• Found → mark as “document present”
• Not found → mark as “no source document”

List the missing documents. The owner can attach a file or mark “document not required” (for example, a regular automatic payment without an act).

If the connector is unavailable, ask the owner to confirm which expenses he has source documents for — do not skip this step silently.

Step 6 — Owner confirmation point

Show the summary before moving on:

Операции без статьи:        X из X разнесено
Расхождения по зачислениям: X помечено, X закрыто
Подозрительные дубли:       X помечено, X снято
Недостающая первичка:       X открыто

Ask: “Are you ready to write the P&L summary and export the closing package?”

Do not proceed to Steps 7–8 without explicit confirmation.

Step 7 — Write the P&L summary

Write the month’s analysis in plain language — the kind the owner would show his wife or accountant, not an internal memo from a CFO. Target — 150–250 words.

Structure:

1. Headline — one sentence: “March closed at X ₽ net, +/− Y% versus February.”
2. Revenue — what drove the result; name the products, services, or clients if the data show concentration.
3. Gross margin — held, grew, or compressed, and the main reason.
4. Key expenses — any line item that moved more than 10% versus the previous month or went outside the norm; one sentence for each.
5. Bottom line — net profit versus the previous month; ask whether they have a target benchmark for comparison.
6. On watch — 1–3 things to watch in the next month.

Avoid jargon; explain anything that is not commonly used (“m/m” = month over month).

See reference/examples/pl-narrative.md — a worked example.

Step 8 — Export the closing package

Create two files:

close-packet-[ГГГГ-ММ].xlsx — three sheets:

• ОПиУ — P&L data from accounting, formatted
• Сверка — matched and flagged transactions side by side
• Задачи — all open flags (no category, no source documents, etc.)

close-packet-[ГГГГ-ММ]-summary.pdf — one page:

• Month and business name at the top
• Key figures (revenue, gross margin %, net profit)
• P&L summary from Step 7
• Number of open tasks, if any

Save both to the Desktop (or to the path specified by the owner). Confirm the file locations.

See reference/close-packet-format.md — column specifications and PDF layout.

Approval gates

• Never run reconciliation for a month that has already been submitted for reporting. Confirm that the books are still open before pulling data.
• Never delete or change a transaction in the accounting system directly. Show the flags; the owner makes the changes in their own accounting system.
• Always stop at Step 6 before issuing the result. Unresolved flags must be confirmed or explicitly skipped.

Graceful degradation

No connector	Fallback
~~бухгалтерия	Ask for a CSV export from accounting (P&L + transaction details)
~~платежи	Ask for a CSV of settlements from the acquiring personal account or a bank statement
~~хранилище / Desktop (source documents)	Ask the owner to confirm the status of source documents for each flagged expense

Reference files

• reference/quickbooks-reconcile.md — reconciliation with accounting data (1C, etc.): field matching, pagination, common data issues
• reference/paypal-settlements.md — structure of settlement reports and statements (YuKassa, Tinkoff, bank)
• reference/close-packet-format.md — xlsx column specifications, PDF layout, file naming rule
• reference/gotchas.md — false duplicates, split transactions, edge cases of an incomplete month
• reference/examples/pl-narrative.md — a worked example of the P&L summary