Finance without manual reconciliations

The agent reconciles statements against 1C, builds the P&L, tracks receivables, and prepares reporting — accurate and on time.

Try for free
1С собери P&L за май из 1С
1С

EBITDA 1,87 млн ₽ — +21% к апрелю при росте выручки на 11%

Операционку удержали на +3%, поэтому почти весь прирост ушёл в прибыль.

P&L · май

File · XLSX
Разбор по статьям

Bank statements, 1C, and e-docs — reconciled automatically

All integrations
Точка
Сбербанк
Альфа-Банк
Т-Банк
1С
МойСклад
Диадок
Контур
ЮKassa

Reconciliation on autopilot

Matches bank statements, invoices, and 1C entries, finds discrepancies and duplicates, flags anything off.

P&L и движение денег — в Telegram
Платёжный календарь на неделю
Сверка Диадок ↔ 1С за неделю
Контроль кассовых разрывов

P&L and reporting in minutes

Builds profit and loss, margins, and trends from 1C and spreadsheets — a finished report for leadership, no manual assembly.

Собери P&L за май по подразделениям

Свёл из 1С и таблиц. Маржа и прибыль по подразделениям — в готовом своде для руководства.

P&L · май — по подразделениям

Document · XLSX

Receivables under control

Tracks overdue invoices, ranks debtors, and sends reminders to clients and managers on schedule.

Дебиторка по срокам
контроль

Source docs and budgets

Parses incoming documents, checks details and amounts, compares actuals to budget, and highlights variances.

Счета и акты по шаблонам компании
Сверка НДС перед сдачей отчётности
Напоминания должникам по дебиторке
Выгрузка проводок в Google Sheets
Build a P&L for [period] broken down by business unit using 1C data. For each unit: revenue, direct costs, gross profit, overhead, profit before tax. Next to it — the share of total company revenue. Allocate indirect costs only by the rule [by revenue / by payroll / by floor area]. If no allocation base is set, don't spread them evenly — put such costs on a separate line "not allocated". Build the report on the accrual basis: from sales documents, not from cash receipts. Output an XLSX: a "P&L" sheet with units in columns, a "Details" sheet linking to the documents behind each line item, and a "not allocated" line with its total.
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.
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.
Prepare a reconciliation statement with [counterparty] for [period] using 1C and Diadoc data. Match every UPD and VAT invoice from EDI against a posting in 1C by number, date and amount. Collect the discrepancies: a document exists in Diadoc but isn't posted in 1C, is posted in 1C but never arrived via EDI, amounts or the VAT rate differ, the document was cancelled or replaced by a corrected one. Don't stop at a matching number: different contracts can share the same numbers — also check the contract and the amount, otherwise move the row into "needs a decision". Output the statement in the standard form broken down by dates and documents, a separate discrepancies sheet and the opening and closing balances — per our data and per the EDI documents.
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.
Build a payment calendar for [horizon: a week / two weeks / a month] based on account balances and the obligations in 1C. Lay out the outflows by day: invoices due with their deadlines, taxes and contributions, payroll, loans and leasing, recurring payments. Mark which payments cannot be moved. Include expected customer receipts as a single inflow line per day and only where the contractual payment date has already arrived; don't count sales reps' promises or "they usually pay by Friday". Find the first day the balance drops below the [minimum balance] and show the shortfall. Output a day-by-day calendar and a list of payments that are candidates for moving, with a new date.
Every morning at [time] send a Telegram summary of the accounts [list of accounts] for the previous day. Format: opening and closing balance for each account and in total, total inflow and outflow, the three largest receipts and the three largest payments with payee and description. In a separate block — unusual operations: a payment above [threshold], a new payee never paid before, a payment on a weekend, a fee higher than usual. If there were no operations — say exactly that, don't resend the previous summary and don't fill the gap with average values. Keep the message within one screen: no tables and no explanations of why the balance changed.
Check the attached invoice [PDF / photo / EDI document] before sending it for payment. Cross-check against 1C: tax ID, tax registration code, bank account and bank — against the supplier record; the subject, prices and amount — against the contract and this supplier's previous invoices; whether the same invoice has already been paid or is already in the queue. Take the details from the body of the invoice, not from the email or the sender's signature. If a field is unreadable or missing in 1C, write "not verified" and don't substitute the value from a previous invoice. At the end: what matched, what differed, whether there is a duplicate, and a verdict — pay, clarify or reject, with a one-line reason.

FAQ

Where data is stored and how access is protected — covered separately: security overview

Yes, via API. It reads entries, statements, invoices, and reference data, reconciles them, and builds reports. It supports standard configurations; access follows your permissions.

It doesn't execute payments. It prepares registers, reconciliations, and reports for approval, while the decision and signature stay with your finance team. Routine off, control on.

It matches amounts, dates, payees, and purposes line by line. It catches duplicates, underpayments, and stray charges, flags the doubtful, and explains each gap.

Access is granted narrowly to the areas you choose, and every action is logged. The agent works inside your perimeter on the rights you give — nothing leaves without your consent.

Ready-made use cases

All use cases
Build a P&L by business unit with an AI agent

You know the company's profit. Which line of business brings it in you still work out by hand in Excel. The agent splits it straight from 1C.

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.

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.

Build an EDI reconciliation statement with a counterparty

The counterparty sent their statement and the totals disagree. The agent merges Diadoc documents with 1C postings and shows whose document dropped out.

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.

Stay ahead of a cash gap and keep a payment calendar

Every Monday you decide which invoices go out and which can wait. The agent lays payments out by day and finds the day the money runs short.

Get a recurring cash-flow report on schedule

Your morning starts with the bank client and three tabs of balances. The agent posts yesterday's summary to Telegram and flags what stands out.

Verify details and amount on an incoming invoice

Invoices land in chat from different managers, and one person sends them all to the bank. The agent checks each against the 1C record and contract.

Build a cash flow statement for the period

The report shows profit, the accounts show nothing. The agent lays out how much the business itself earned and how much went into kit and loans.

Measure receivables turnover by counterparty

You changed the payment terms, but nobody checked whether customers actually pay faster. The agent shows average payment days by month and by client.

Run debtor reminders on a schedule

Payment reminders get remembered a month after the due date. The agent writes three letters of rising firmness and sends them on schedule.

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.

Triage incoming EDI documents with AI

Dozens of documents sit in Diadoc, some unsigned simply because nobody got to them. The agent checks each one against the order in 1C.

Assemble the monthly closing document package

Some acts came through EDI, some by email, some never came at all. The agent assembles the package per customer and names exactly what's missing.

Guides on this topic

Close the month faster and error-free

Connect 1C in minutes and hand reconciliations, reporting, and receivables to the agent — so your team can focus on analysis and decisions.

Try for free