All use cases

See what you owe suppliers and who to pay first

There's never enough for every invoice at once, and the queue gets rebuilt in a notebook weekly. The agent spreads payments across days by real balance.

Medium · 20 min · once a week

What you get

Payment plan, week of 15 April
Mon  Supplier A      420,000   12 days overdue
Tue  Romashka LLC    180,000   due today
Wed  Rent            250,000   cannot be moved
Fri  Supplier B      140,000   9 days of deferral left
The balance never drops below 300,000 on any day.
Two suppliers have no term in the contract — the agent
chose their place in the queue itself, check it.

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

Who it fits

  • There isn't enough money for every invoice, and the payment queue is rebuilt in a notebook weekly.
  • Several dozen suppliers, each with their own terms and deferrals — you can't hold that in your head.

When it won't work

Deliveries are entered into the books a week late — you'd be paying against documents not yet in the system.

How the agent does it

1

Set cut-off and accounts

The agent reads debts and balances directly, nothing to export. If you have several current accounts, name the ones you pay from or it pools them together.

2

Build the queue

The agent counts overdue days from the contract term rather than the delivery note date and spreads payments so the balance holds up every single day.

3

Check before the bank

Look at days where the balance only works if an expected inflow lands on time. And at rows where the agent picked the payment term for you.

What you set

You'll need MoySklad, 1C and Tochka. From you: the cut-off date, the accounts you pay from and the suppliers who must never be delayed.

What you'll need

МойСклад
Точка

Starter prompt

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

Prompt for the agent

Build a payables report for suppliers as of [date] using [MoySklad / 1C] data and the account balances from Tochka. For each supplier: the amount owed, which delivery documents it consists of, the payment term from the contract, days past due, the date and amount of the last payment. Take the term from the contract or the delivery terms. If the term isn't filled in — don't assume the usual 14 days, move the supplier into a "term not defined" list. Spread the payments across the days of [period] so that the balance covers each day. If it doesn't — show the day and the size of the gap instead of silently trimming the amounts. Output an XLSX: a "Payment queue" sheet with date, amount and the reason for the priority, a "Deferred" sheet and a total line — how much is due and how much money is available.

Open in chat
Check the result

Review the payment plan. List: — debts closed by a prepayment or an offset but still left in the calculation; — suppliers who have several records in the system, with the debt split between them; — rows where the payment term isn't filled in and the priority was set on your judgement; — days where the balance is only sufficient if the expected inflow arrives on time; — payments that can't be moved without approval — rent, taxes, payroll. Don't reorder anything silently: whatever you can correct yourself, show as a "proposed changes" list.

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

Related use cases