Reconcile your BizimHesap account statement against counterparty, bank and e-invoice
Your BizimHesap account statement is matched line by line against the counterparty, the bank and e-invoice data. The connection is ready. File upload and BizimHesap's own direct link both work.
Lines ready for matching
Columns, signs and dates recognised; on one table with bank and e-invoice.
Whichever route you choose, the same matching engine runs.
Illustrative screen · sample data
This page explains how to reconcile your BizimHesap account statement against the counterparty, the bank and e-invoices. It is for the finance manager or accountant who needs to see which lines create the balance difference.
The difficulty is not BizimHesap itself but the counterparty's records, which are not in your BizimHesap panel. A supplier shows invoice FT-2026-0412 for TRY 48,250.00 as open, while you paid TRY 30,000.00 against it. iFinances puts both statements in one table, proposes linking that payment to the invoice and writes the reason. It does not post entries, does not keep books and never closes a line without your approval.
What data comes from BizimHesap?
Four data types can be taken from BizimHesap for reconciliation. Anything not on this list does not come from the system.
Account statement
This is the main input. The Account Statement from a customer or supplier card lists invoices, collections, payments and returns by date. Each line carries debit, credit and running-balance columns. iFinances matches these lines against the counterparty's statement and shows which items make up a TRY 2,150.00 difference.
Customer and supplier master list
You export BizimHesap's customer and supplier cards to Excel with name and tax number (VKN). That list goes into iFinances' bulk company template, and iFinances proposes links from bank-statement sender names to it. 'POYRAZ METAL SAN.' and 'Poyraz Metal Sanayi' count as similar once Turkish characters are folded. You approve every link.
Collection and payment lines
You do not need a separate payment file, and BizimHesap's programming interface has no payment endpoint anyway. iFinances reads those lines, marked by type, as payments and matches them FIFO, oldest invoice first. One transfer of TRY 100,000.00 is allocated across three invoices. A partial payment of TRY 30,000.00 leaves the rest of the invoice open.
Sales and purchase invoice lists
You download sales and purchase reports from the BizimHesap Reports screen as Excel or CSV. They are used to cross-check e-invoice data and the counterparty's invoice lines by document number. If FT-2026-0412 appears in all three sources with the same amount, the match reason gets stronger. The programming interface has no endpoint that reads invoices, so the list comes only from the report export.
How do you get the file?
If you take the file route, the job is short. You take BizimHesap's standard export and upload it to iFinances, with no setup required.
- 1
Open the account card and choose Account Statement
You open the card of the customer or supplier in BizimHesap. On the card screen you choose Account Statement and enter the date range that covers the reconciliation period. You press Prepare Report. Start the range at the period start, say January 1, 2026, so the opening balance enters the table.
- 2
Download the statement as Excel
You choose Excel as the output format. BizimHesap produces the statement as PDF and Excel, and reconciliation needs Excel. In a PDF an amount like 48,250.00 turns into text and cannot be matched line by line. You do not need to rename the file or edit the column headers.
- 3
Optionally take the invoice reports
You download the sales and purchase reports from the Reports screen as Excel or CSV. If you also reconcile against e-invoices, these lists strengthen document-number matching. They are optional, and the account statement alone is enough for statement reconciliation.
- 4
Upload to iFinances
You drop the file into the company's data area, and iFinances reads the format from content. It works out column names and the debit/credit direction and asks about any field it cannot recognize. From the same screen you send the counterparty a secure link. They upload their own statement there without opening an account.
BizimHesap → Upload · columns recognised ✓ · 1,284 lines
Connection path
First what BizimHesap offers technically, then the two connection routes iFinances uses.
BizimHesap runs in the cloud, so there is no direct database access. Its only technical route is the B2B API, a web service that answers requests with JSON over HTTPS. The official developer documentation is narrow and covers adding orders and invoices, products, warehouses and stock. Endpoints that read the customer list and the statement appear only in community projects, not in official documentation.
On the iFinances side the BizimHesap connection is ready, and both routes work. On the file route you upload the account statement and, optionally, the invoice reports as Excel or CSV. The direct route reads the B2B API with an access token, a key issued from your own panel. The route is chosen together at setup, and the file route is often the more predictable one.
Things to watch
Some lines may have no document number
The Excel statement has a document number column, but some lines may leave it empty. Statement lines in the programming interface carry no document number at all. On an empty line iFinances matches on date and amount, and the reason says so. The reason reads, for example, 'March 12, 2026, TRY 48,250.00, no document number'.
The bank statement does not come from BizimHesap
BizimHesap's programming interface has no endpoint for bank, cash, checks and notes or journal entries. Take the bank leg directly from your bank as Excel. iFinances recognizes bank-specific templates and HTML tables saved as .xls from their content. Keeping the three sources independent is what makes the comparison meaningful.
Sign convention and virtual POS collections
Debit and credit columns point different ways for a customer card and a supplier card. iFinances derives the direction from the file and asks when it cannot be sure. A virtual POS collection may reach the bank as a daily total, handled under the lump-sum rule. A TRY 10,000.00 sale can land as TRY 9,820.00, with the fee shown as a separate item.
Date range and opening balance
If you export only the last month, the opening balance appears as a single line. That line matches nothing on the counterparty's side. Start the range from the date the previous reconciliation closed, say January 1, 2026. Using the same range as the counterparty shortens the exception list.
Exchange rates may be missing from the file
The programming interface has no exchange-rate endpoint, and the Excel statement may not show the rate applied. iFinances matches across currencies with the official TCMB (Central Bank of Türkiye) rate. The FX difference between a EUR 1,000.00 invoice and a TRY 38,450.00 payment is flagged separately. Posting that difference in BizimHesap remains your job.
Frequently asked questions
The connection is ready and there are two routes. On the file route you upload the Excel statement from BizimHesap, with nothing to install. On the direct route the B2B API is read with an access token from your own account. The route is chosen together at setup. Results stay in iFinances, and nothing is written back to BizimHesap.
No. BizimHesap keeps your own records and can email a statement to the counterparty. Comparing the statement they send back with yours line by line is a separate job. So are splitting partial payments, explaining the difference and archiving a signed reconciliation letter. iFinances does that job, and your software does not change.
No. The counterparty receives a secure link and uploads their own statement as Excel, CSV or legacy .xls. They install nothing and open no account. Which program they use does not matter, because iFinances identifies the format from content.
Yes. You upload the outbound and inbound e-invoice (e-Fatura) lists. All three sources are cross-checked in one table by document number and amount. Take the list from your integrator or the tax authority portal, not from BizimHesap. That keeps the e-invoice leg independent.
No, line-level matching needs Excel or CSV, and BizimHesap produces both. In a PDF, amounts such as 48,250.00 and dates turn into text and cannot be read reliably. If the counterparty only sent a PDF, asking for the Excel copy is the shortest route.
Other integrations
Same engine, different source. If your system is not listed, the file route still works.
30 minutes. With your own data.
Live demo. No commitment.
- Live demo — the system, not slides
- No prep, instant walkthrough
- A tailored quote in your inbox