Find clients who haven't paid in over 30 days
Before the call round you need to know who is merely late and who has moved the date twice. The agent matches Bitrix24 promises against 1C receipts.
Medium · 20 min · once a week
What you get
Promised and unpaid — snapshot of 17 March Romashka LLC — 780,000 ₽, promised 24 Feb, +22 days Sergeev — 145,000 ₽, the date was moved twice Vektor LLC — 300k ₽ paid of 900k, partial Unmatched: 2 payments came from a different legal entity — check the link by hand, and quote no debt figure to the client before accounting confirms it.
A sample on made-up data — your numbers will be your own.
Who it fits
- The manager is certain the client is about to pay — the promise was made three weeks ago.
- Receivables keep growing, and the debtor list is assembled from two systems by hand.
When it won't work
Payment promises live in the manager's head and never reach CRM — nothing to reconcile.
How the agent does it
Set the snapshot
Name the date and the threshold in days — it should match what managers treat as a normal delay. Say where a payment promise lives in your CRM.
Reconcile with facts
The agent reads promises in CRM and receipts in 1C and links them by the payer's legal details. A stranger's payment that happens to match is not attributed.
Verify the amounts
The manager walks into the client conversation with this list. A debt figure named wrongly ends that conversation.
What you set
Bitrix24, 1C. From you: the snapshot date, the threshold in days, and where a payment promise is recorded: a comment, a task or a separate field.
What you'll need
Starter prompt
Copy the prompt or open it straight in a chat with the agent.
Reconcile the payment promises from Bitrix24 deals against actual receipts in 1C as of [date] and find clients with no payment for longer than [N] days. For each: the promised date and amount, who recorded it and when, what actually arrived, how many times the deadline was pushed, the date of the last conversation, the owning manager. Link client and payment by legal details. If a payment arrived without a link to a deal — don't assign it to the nearest one by amount, move it into "unidentified payments". Don't reconstruct promises that aren't in CRM by logic: write "agreement not recorded". Sort by amount. For each client propose the next step: a call, an email, escalation or handover to receivables collection.
Open in chatCheck the reconciliation of promises and payments. List: — clients whose payment came from a different legal entity and therefore didn't match; — payments assigned to a deal by a matching amount rather than by a document; — clients where the promise was reconstructed from correspondence rather than recorded in CRM; — cases where the payment was partial and the client formally met the condition; — amounts that can't be quoted to the client until accounting confirms them; — clients on deferred payment or instalments whose due date hasn't arrived yet. Propose the next steps yourself; escalation and handover to receivables collection only through me.
A second prompt — the agent uses it to review its own work and show what's left for you.