SuperAPI AI Directory
Partner中文AI newsFavorites
Skillsclose-month

close-month

General & other

View repository

Updated 10-15 19:47

About this skill

Close the month

The month is "seemingly closed" until in April it turns out that March money from acquiring never made it into the books, and half of the expenses are sitting without a category. This skill reconciles the books with acquiring and statements, puts all inconsistencies on the table, and produces a ready closing package — so that both you and the accountant have something to work with.

Run the month-closing process. Reconcile, flag discrepancies, describe the P&L in plain language, and export the closing package for the owner's archive (and their accountant).

Argument breakdown:

  • --month (default: previous calendar month) — format ГГГГ-ММ
  • --save-to (default files) — files (~~хранилище: Yandex Disk / Mail.ru Cloud), desktop (locally) or both

Step 1 — Reconciliation

Run the skill workflow month-end-prep:

  1. Pull all transactions from ~~бухгалтерия (1C/MySklad) for the month being closed.
  2. Pull incoming payments from each connected source ~~платежи (YuKassa, Tinkoff, SBP, bank statement) for the same month.
  3. Match accounting transactions with incoming payments by amount + date (±2 days).
  4. Output three categories of discrepancies:
    • Incoming payments without a match — money arrived via acquiring/SBP but did not make it into the books
    • Receipts in the books without a match — there is income in the books without a record in acquiring (cash? transfer by bank details? wrong category?)
    • Amount discrepancies — matched, but the amount differs (fees, split refunds)

Step 2 — Flag suspicious entries

Output in the same report:

  • Transactions without a category — entries in the books without a category
  • Suspicious duplicates — same amount, same counterparty, within 3 days
  • No source documents — transactions in the accounting records over ₽5,000 without an attached document (act, invoice, receipt, UPD)

For each one, recommend an action: assign to category X, delete the duplicate, attach the source document.

Wait for the owner to review the flagged items before writing the summary. Do not assign to categories or delete automatically.

Step 3 — P&L summary

After the owner's review, generate a P&L summary in plain language:

{Месяц ГГГГ} закрылся на {выручка} ₽ выручки ({+/-}{X}% к прошлому месяцу).
Главный драйвер: {статья/клиент}. Сильнее всего сдвинулось: {статья} {рост/спад}
{сумма} ₽, потому что {причина из операций}.

Маржа: {X}% ({+/-}Y п.п. к прошлому). {Комментарий по затратной части}.

Три заметных пункта:
1. ...
2. ...
3. ...

The figures are taken from the accounting records; why — from cross-reconciliation of large transactions, counterparty names, and deltas versus the previous month.

Step 4 — Export the closing package

Generate two files:

  1. close-packet-{ГГГГ-ММ}.xlsx — a workbook with multiple sheets:
    • Сверка — an accounting ↔ acquiring matching table with discrepancy rows highlighted
    • Помечено — without category / duplicates / no source document
    • ОПиУ — a formatted financial result report with a delta column versus the previous month
    • Оборотка — categories + ending balances (trial balance)
  2. close-packet-{ГГГГ-ММ}.pdf — a one-page summary: P&L summary + key figures + number of discrepancies

Save both to the selected --save-to. File name format: close-packet-2026-04.xlsx и т.п.

Connector failures

If ~~бухгалтерия is unavailable — stop: reconciliation requires the accounting records as the source of truth. If the source ~~платежи is unavailable (YuKassa/Tinkoff/bank), perform the reconciliation using the available sources and note “acquiring not connected — acquiring credits omitted from reconciliation” (or specify which one is missing). If all payment sources are unavailable — perform the analysis using the accounting records only and note this.

Approval gates

  • Never correct flagged items automatically. Always show the discrepancy, recommend an action, wait for the owner.
  • Never delete duplicates without explicit confirmation. Show both records side by side.
  • Saving the package is automatic, it goes to the owner's own disk/storage.

Example (illustrative, data is conditional)

Input: the owner says "close March". There are 142 transactions in the accounting, 1C and YooKassa are connected.

What the skill found:

  • 3 YooKassa credits totaling 58,000 ₽ were not included in the accounting (stuck as "not in accounting")
  • 11 transactions without a category totaling 84,000 ₽
  • 1 suspicious duplicate payment to a supplier (two lines of 12,000 ₽ over 2 days)

Output after review by the owner:

March closed at 1,240,000 ₽ in revenue (+8% vs February). The main driver is wholesale to "Vektor". Margin 31% (−2 pp: packaging became more expensive). Three items under control: assign the 11 transactions to categories, check the duplicate to the supplier, attach 2 acts.

Files: close-packet-2026-03.xlsx + close-packet-2026-03.pdf. (All numbers are conditional, to illustrate the format.)

Conclusion

Finish the run with a single summary paragraph: revenue, margin, remaining unresolved discrepancies (if any), paths to the saved package. If not all discrepancies are closed, list them so the owner can return to them.