All use cases

Stay ahead of a cash gap and keep a payment calendar

Every Monday you decide which invoices go out and which can wait. The agent lays payments out by day and finds the day the money runs short.

Medium · 15 min · once a week

What you get

a table in the reply · once a week

Payment calendar, 15-21 April
Mon 15   balance 2,100,000   due     640,000
Tue 16   balance 1,460,000   due   1,380,000
Thu 18   balance    80,000   payroll 1,150,000
Short on 18 April by 1,070,000 ₽.
The gap disappears if the 1,200,000 from Romashka LLC
arrives on time. We found no such date in the contract:
it is placed from their past payment behavior.

A sample on made-up data; your numbers will be your own.

Who it fits

  • Monday morning, deciding which invoices go out for payment this week and which ones wait.
  • Several accounts and dates that never move: taxes, payroll, leasing instalments.

When it won't work

Upcoming payments aren't recorded anywhere, so a calendar built from past charges alone shows nothing.

How the agent does it

1

Gather the obligations

Make sure invoices due and their deadlines are entered in 1C. Name the payments that cannot be moved and the minimum balance you keep on the account.

2

Build the calendar

The agent takes balances from the bank, spreads the obligations across dates and looks for the first day when the accounts fall short.

3

Question the inflows

A gap usually appears or vanishes because of one optimistic inflow line. Ask the agent where it got that date from.

What you set

You'll need Tochka and 1C. From you: how many days ahead we plan, which payments cannot be moved and the minimum balance to keep.

What you'll need

Точка
1С:Предприятие

Starter prompt

Copy the prompt or open it straight in a chat with the agent.

Prompt for the agent

Build a payment calendar for [horizon: a week / two weeks / a month] based on account balances and the obligations in 1C. Lay out the outflows by day: invoices due with their deadlines, taxes and contributions, payroll, loans and leasing, recurring payments. Mark which payments cannot be moved. Include expected customer receipts as a single inflow line per day and only where the contractual payment date has already arrived; don't count sales reps' promises or "they usually pay by Friday". Find the first day the balance drops below the [minimum balance] and show the shortfall. Output a day-by-day calendar and a list of payments that are candidates for moving, with a new date.

Open in chat
Check the result

Review the calendar. List: - inflow lines placed on a date that isn't in the contract; - payments without a deadline that you spread across days at your own discretion; - fixed-date obligations that ended up in the "move" list (those must not be touched); - partially paid invoices: what amount is left and which day you placed it on; - the gap day and the shortfall: which rows it is made of. Separately, say whether the gap disappears if the largest expected payment is removed.

A second prompt: the agent uses it to review its own work and show what's left for you.

Related use cases