All use cases

Find duplicate payments and stray charges

Several people pay invoices, and now and then the same one goes out twice. The agent finds doubled payments and subscriptions everyone forgot.

Easy · 15 min · once a month

What you get

Looks doubled — 3 pairs:
05.04 and 08.04  Supplier A     180,000  invoice no. 121
12.04 and 12.04  Romashka LLC    46,000  invoice no. 87
Forgotten recurring charges:
Email service  3,900 a month, paid for 14 months
Possible overpayment: 226,000 ₽.
Two rows may be partial payments of one invoice —
only a call to the supplier will settle that.

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

Who it fits

  • Invoices get paid by several people, and the same invoice occasionally goes out twice.
  • Lots of recurring charges — services, acquiring, fees — and some haven't been needed for years.

When it won't work

You have many identical scheduled payments, rent or leasing: without an exclusion list the report is just those.

How the agent does it

1

Set the search window

Name the period and the window in days within which two identical payments count as suspicious. List the recurring charges that are not duplicates right away.

2

Run the search

The agent matches outgoing payments against postings and source documents in 1C and groups the findings by type of suspicion rather than into one pile.

3

Filter the false ones

Half of the "duplicates" usually turn out to be partial payments of one invoice. Filter those out before you call and ask for money back.

What you set

You'll need Tochka and 1C. From you: the period, how many days apart two identical payments look suspicious, and the list of recurring charges.

What you'll need

Точка

Starter prompt

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

Prompt for the agent

Check outgoing payments on the accounts for [period] against the statement and the postings in 1C. Find: payments with a matching payee and amount within [3 / 7 / 14] days, the same invoice or UPD paid by different payment orders, recurring payments that have no contract or acceptance certificate in 1C, and increases in the amount of a recurring payment. Don't treat scheduled recurring payments — [rent, leasing, payroll project] — as duplicates. Don't declare a payment a duplicate if the grounds differ: if the payment descriptions differ, move the pair into "looks similar, needs checking". Output a table: date, payee, amount, source document, suspicion type and the possible overpayment amount; at the end — how much money is worth reclaiming or cancelling.

Open in chat
Check the result

Review the list. List: — pairs where only the amount matched while the payee or the grounds differ; — partial payments of one invoice that you took for a double payment; — refunds and reversals that close a duplicate you found — such rows don't belong on the list; — payments whose grounds weren't found because the document isn't posted, not because it doesn't exist; — the total possible overpayment and which rows went into it. Mark what can be verified from the data and what requires a call to the supplier.

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

Related use cases