All use cases

Build an overdue receivables report by counterparty

Every collections round starts with someone assembling the list by hand. The agent counts overdue days from contract terms and orders the queue.

Easy · 10 min · once a week

What you get

Call these first:
Romashka LLC   820,000 ₽   47 days overdue
Supplier A     310,000 ₽   21 days overdue
I. Smirnov      95,000 ₽    9 days overdue
Total overdue: 1,225,000 ₽ across 14 customers.
Two have no payment term in 1C — overdue days were
counted from the shipment date, so double-check those.

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

Who it fits

  • The weekly collections round, where the list is rebuilt by hand from exports every time.
  • You need to tell "pays late" apart from "stopped paying" — those are two different calls.

When it won't work

Contract payment terms aren't entered in 1C — there is no baseline to count overdue days from.

How the agent does it

1

Set date and threshold

Name the day the debt is measured on and the overdue point where calls start. If some customers have their own deferral, say so — otherwise they land on the list for nothing.

2

Build the register

The agent pulls shipments, payments and terms from 1C and separates chronic non-payers from customers who simply pay a week late.

3

Check before you call

A wrong figure quoted to a customer costs more than a day of delay. Look at rows where a payment wasn't linked to a specific invoice.

What you set

You'll need 1C and Diadoc. From you: the date the debt is measured on and how many overdue days put a customer into the queue.

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 receivables report by customer as of [date] using 1C data. For each customer: the amount owed, which documents it consists of, the payment term from the contract, days past due, the date and amount of the last payment. Count overdue days from the contractual term, not from the shipment date. If the term is not filled in — don't assume a standard 30 days, move the customer into a "term not defined" list. Sort by overdue amount. Flag separately those whose debt has been growing for three months in a row, and those who pay reliably but late. At the end — the total overdue amount and which five customers account for half of it.

Open in chat
Check the result

Review the summary. List: — debts closed by a prepayment or an offset but still left in the calculation; — customers whose payments weren't linked to specific invoices; — rows where overdue days were counted from shipment because the term is not filled in; — installment contracts where there is in fact no overdue amount; — the amount that must not be quoted to the customer until accounting confirms it.

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

Related use cases