Upload a bank statement and an invoice register — the system compares the amounts for every counterparty and shows where they disagree.
Work that takes days by hand — done in seconds.
The system matches money paid against invoices received, counterparty by counterparty, and singles out those with a difference.
No card, no payment. Every feature is open and unlimited.
Money paid out
482 225 000
Invoices received
530 268 948
Difference
−48 043 948
1.37 bn
UZS of turnover tested on real data
142
automated checks after every change
6
real bank files — the reference set
On real data: 1.37 bn UZS turnover, 152 payments, 159 invoices, 35 counterparties.
Two files are needed: the bank statement and the invoice register exported from e-invoicing. You can select both at once.
Formats: .xls, .xlsx, .csv. Upload the bank's own file as it is, without editing it.
Choose Excel / CSV files
.xls · .xlsx · .csv
After the upload the first thing you see is not the result but the CHECK: which sheet from which file, how many rows were read, and whether that matches the file's own total.
The balance equation validates the file itself: if opening balance + credits − debits does not equal the closing balance, the system SAYS SO instead of quietly showing a result.
Balance equation — opening balance + credit − debit = closing balance
The table shows, per counterparty: how much money moved, how much is invoiced, and the difference. The last column spells out in words what to do about it.
The result can be exported to Excel, and a reconciliation act can be prepared for a single counterparty.
Both belong to the same company, but the money flows the other way. Each has its own colour so they never get mixed up.
Outgoing reconciliation
Money paid ↔ Invoices received
You paid. Did the supplier issue an invoice? Whoever did not shows up here.
Incoming reconciliation
Money received ↔ Invoices issued
Money came in. Did you issue an invoice? Whoever has not paid shows up here.
Each one came from a real problem in a real file — not to pad a list.
Opening balance + credits − debits = closing balance. If debit and credit are swapped, the file's own total will NOT notice — this equation will, and it says so.
opening · in · out · closing balance
An unfamiliar bank layout is learned once and recognised automatically next time. The memory is shared — every new user makes the system stronger for everyone.
The unpaid invoice balance is split into 0–30 / 31–60 / 61–90 / 90+ days. FIFO: incoming money closes the oldest invoices first.
The official two-sided document for a single counterparty: date, document, debit, credit, with balance and turnover rows. In Excel, ready to print.
On seven months of real data — 1.37 bn UZS turnover, 152 payments, 159 invoices, 35 counterparties. The system found differences the accountant had MISSED:
Company names are fictional — the figures come from a real test.
Every feature is open and unlimited. No card, no payment, no trial period.
Free
For everyone — solo accountants and teams alike
The product is still young. If a paid plan appears later, we will announce it in advance — your account will not be locked silently.
None of this exists yet. It is written as a direction, not as a promise.
Automatic stock-balance calculation by IKPU product codes.
Flagging tax risks in advance and building the balance sheet automatically.
A direct link to the bank and e-invoicing instead of Excel (1C Client-Bank, camt.053).
No. Never. It reads only what the file says and shows the difference. Fixing it is your decision.
Currently recognised: Hamkorbank, Ipoteka / ASBT and several generic layouts. An unfamiliar layout is learned once and recognised automatically next time.
Only you. Every account runs in its own workspace — no other user sees your companies or your amounts.
No — everything is free and unlimited for now: reconciliations, companies and users are all unrestricted. No card, no trial period, just sign up. If a paid plan appears later, it will be announced in advance.
They move into their own category and out of the main table. But they are NEVER deleted — the TOTAL at the top always stays the full amount.
Excel (.xls, .xlsx) and CSV. You can upload the bank's own file as it is, without editing it.
Yes. For a single counterparty it builds the official two-sided act: date, document, debit and credit columns plus the balance row. It downloads as an Excel file.
The uploaded file itself is not stored — it is only read. If you press Save, the result table is kept in your own workspace.
Upload the bank statement and invoice register of your messiest client. Whether there is a difference — you will know in a minute.