All use cases

Prepare a reconciliation act in SBIS against 1C

Signing the act closes the period, yet the balance gap isn't broken into rows. The agent merges SBIS and 1C line by line before you sign anything.

Medium · 25 min · once a quarter

What you get

a Google Doc · once a quarter

Reconciliation with Supplier A, Q2
96 rows in the statement, 91 matched.
no. 1042 of 14.05   240,000  we have it, they don't
no. 1077 of 30.06   118,000  status "rejected"
no. 1081 of 30.06    36,000  amounts differ by 6,000
The 388,000 gap is fully broken down, row by row.
Two rows we can fix on our side, the third has to be
agreed with the counterparty.

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

Who it fits

  • The counterparty works through SBIS and sends their own statement: it needs a line-by-line check, not a total.
  • The statement is agreed over several rounds and you need to see what changed between versions.

When it won't work

Settlements run in several currencies or through agency schemes — line matching will invent discrepancies.

How the agent does it

1

Pick the counterparty

Name the period. If the counterparty has already sent their statement, attach it: the agent reconciles both sides row by row, not just your data against SBIS.

2

Collect and match

The agent builds the statement in SBIS, reads the document statuses and merges the rows with 1C postings, marking whose row is missing and in what status.

3

Break down the gap

A gap that isn't broken into specific rows becomes your loss the moment you sign. Look separately at documents still in "sent" status.

What you set

You'll need SBIS and 1C. From you: the counterparty, the period and the statement the counterparty sent, if you already have it.

What you'll need

СБИССБИС

Starter prompt

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

Prompt for the agent

Generate a reconciliation statement with [counterparty] for [period] in SBIS and check it against the settlements in 1C. Match line by line: date, document, debit, credit. Collect separately the lines that we have and the counterparty doesn't, that the counterparty has and we don't, and those that match on the document but differ on the amount. Don't level out differing balances by fudging: the discrepancy must break down into specific lines, and if it doesn't, say so. Take the document's SBIS status into account: sent, signed, rejected, cancelled — an unsigned document cannot be treated as agreed. Output the statement in the standard form, a line-by-line discrepancy sheet indicating the side and the status, and the closing balance from both sides.

Open in chat
Check the result

Review the reconciliation statement. List: — lines matched by amount without a matching document number or date; — documents in "sent" or "rejected" status that you counted as agreed; — the part of the balance discrepancy that didn't break down into specific lines; — offsets, prepayments and refunds recorded by the two sides in different periods; — lines that got into the statement from another contract with the same counterparty. Say what can be fixed on our side before signing and what will have to be agreed with the counterparty.

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

Related use cases