month-heads-up

Pre-end-of-month summary

The most expensive money surprises happen in the last week of the month, when it's already too late to change anything. This skill runs on the 25th and shows the next 30 days in advance: where the thinnest week is and which two things are worth doing right now to get through it calmly.

Make a warning summary before the end of the month. Pull forecast data on money and give the owner a clear picture of "here's what the next 30 days look like" with specific things to watch.

Argument breakdown:

• --horizon (default: 30) — forecast window in days (30 or 60)

Step 1 — Current cash position

Following the skill's workflow cash-flow-snapshot:

1. Pull from ~~бухгалтерия (1C/MoySklad) the current cash balance and receivables.
2. Pull from ~~платежи (YuKassa/Tinkoff/bank statement) the credited balance and pending credits.
3. Add up into total available + incoming cash flow.

Step 2 — Upcoming obligations

1. Pull from ~~бухгалтерия recurring expenses (salaries, subscriptions, rent) that fall within the next 30 days.
2. Pull all invoices that are overdue or due within the next 14 days.
3. Flag any payment that will drop the balance below the comfortable buffer (by default: < 150,000 ₽ or the owner's average monthly expense per accounting × 0.5).

Step 3 — Cash flow forecast

1. Forecast the net flow over 30 days: current balance + expected receipts − known obligations.
2. Find the tightest week (with the lowest forecast balance).
3. Flag if the forecast goes negative in any week.

Step 4 — Two things to keep an eye on

Output no more than two specific, actionable items to keep an eye on:

• Which invoice(s) to send for payment right now (remind the debtor)
• Which expense(s) to postpone or renegotiate

Format:

Сводка перед концом месяца — {текущая дата}
Горизонт: ближайшие {X} дней

Денег сегодня: {сумма} ₽
Прогноз на конец периода: {сумма} ₽
Самая напряжённая неделя: {диапазон дат} — прогноз {сумма} ₽

ДВЕ ВЕЩИ НА КОНТРОЛЕ
1. {пункт} — {почему важно} — рекомендуемое действие: {действие}
2. {пункт} — {почему важно} — рекомендуемое действие: {действие}

Connector failures

If ~~бухгалтерия is unavailable — stop: cash forecasting requires accounting as a source of truth. If there is no ~~платежи — build the forecast only from accounting data and note “acquiring is not connected — receipts via acquiring are excluded from the forecast.” The same applies if the bank statement is unavailable.

Approval gates

• Never initiate payments or send emails/messages automatically. Show the data and actions so the owner can do them himself.
• Never forecast revenue that is not confirmed in accounting or acquiring. Use only conservative estimates.

Example (illustrative, data are conditional)

Input: the skill started on the 25th, horizon 30 days.

Output:

Сводка перед концом месяца — 25.04
Горизонт: ближайшие 30 дней

Денег сегодня: 310 000 ₽
Прогноз на конец периода: 95 000 ₽
Самая напряжённая неделя: 12–18.05 — прогноз 40 000 ₽

ДВЕ ВЕЩИ НА КОНТРОЛЕ
1. Счёт «Вектору» на 120 000 ₽ просрочен 12 дней — закрывает провал недели
   12–18.05 — действие: отправить напоминание сегодня.
2. Закупка упаковки на 60 000 ₽ запланирована на 14.05 — ложится на тонкую
   неделю — действие: перенести на 22.05 после поступления от «Вектора».

(All numbers are conditional, to illustrate the format.)

Conclusion

Show the formatted summary and offer to prepare draft payment reminders for all flagged overdue invoices.