All use cases

Reconcile a bank statement against 1C entries

The statement and 1C are forty thousand apart, and nobody knows where. The agent matches operations line by line and names every mismatch.

Medium · 20 min · once a month

What you get

a breakdown in the reply · once a month

412 of 418 operations matched. Six did not:
14.03  Supplier A       120,000  in bank, not in 1C
16.03  Romashka LLC      45,000  in 1C, not in bank
21.03  Supplier B        18,500  amounts differ by 500
Total discrepancy: 143,500 ₽.
Two more rows matched on amount alone (number and
date disagree), look at those first.

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

Who it fits

  • Month-end close, when the bank balance and the 1C balance disagree and you need the exact rows.
  • Several current accounts and a steady flow of small payments, impossible to check by eye.

When it won't work

The period's postings haven't been entered yet, so there is nothing to reconcile against.

How the agent does it

1

Open up access

The agent reads the statement and the postings directly, nothing to export. Just tell it the period and which accounts are in scope.

2

Run the reconciliation

Operations are matched on three attributes at once: amount, date and payee. An amount-only match does not count as a match.

3

Work through the gaps

Before you hand the list to the accountant, ask the agent to review itself: some gaps are a shifted payment date rather than a real error.

What you set

You'll need 1C and the bank: Tochka or a statement in 1C format. From you: the period and the list of accounts, if there are several.

What you'll need

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

Starter prompt

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

Prompt for the agent

Reconcile the bank statement [Tochka / Alfa / Sber, or the attached file] against the postings in 1C for [period]. Match operations by amount, date and payee. Collect separately: receipts and payments not posted in 1C, postings with no bank operation, amount discrepancies within a single operation, likely duplicates. Don't force pairs: if an operation matched only by amount but not by payee or date, put it in "needs a decision", not in the matches. Output an XLSX: a "Discrepancies" sheet linking to the operation number and source document, a "Matched" sheet and a total line (how many operations and what amount did not reconcile).

Open in chat
Check the result

Review your reconciliation. List: - operations matched on fewer than all three attributes; - discrepancies explained by a shifted payment date rather than an error; - payees that have several similarly named records in 1C; - rows where the payee was inferred from the payment description rather than from the bank details; - the total discrepancy amount and which rows make it up. Don't fix 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