Reconcile your Nebim V3 account statement against bank and e-invoice data
Your Nebim V3 account statement, invoice and payment reports are compared with three sources in iFinances. The counterparty's statement, the bank statement and e-invoice data sit in one table. Open items become visible before month-end.
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
You reconcile your Nebim V3 account statement line by line against counterparty, bank and e-invoice (e-Fatura) data. It is for accounting managers and group controllers. You see which payment settled which invoice, with a written reason. Nebim V3 is the system of brands that run retail and wholesale side by side. Store tills, card POS settlements, wholesale customers, dealers and vendors all live in one system.
So even when the Nebim balance agrees, which line was settled by which payment remains a separate question. Example: account 120 (trade receivables) shows a balance of TRY 48,250.00, but which transfer settled invoice FT-2026-0412? iFinances answers that question for every line with a written rationale, and you make the decision. Nothing is written back to Nebim; iFinances keeps no books and creates no settlement entries.
What data comes from Nebim V3?
The six datasets below reach iFinances from the Nebim V3 finance side. There are two routes. You upload the standard report as Excel or CSV, or a direct connection is set up. Which route to use is agreed at setup.
Customer and vendor account statement
Debit, credit and balance movements per counterparty from the Customer and Supplier Management application. This is the backbone of the reconciliation. iFinances compares it line by line with the statement the counterparty sends. Where sub-customer activity rolls up into a parent account, export at the level the counterparty uses.
Sales invoice list
Wholesale, retail, export and instalment sales invoices. Nebim V3 keeps each as a separate document type. iFinances checks the list against the purchases on the counterparty's statement. It also checks it against e-invoice data held by GIB (Türkiye's tax administration). An invoice the counterparty never booked, or one issued twice, shows up here.
Purchase invoice list
Supplier invoices such as wholesale purchases, expense purchases and imports. iFinances compares them with the supplier's statement and with the inbound e-invoice data. An invoice the supplier issued that nobody entered in Nebim is flagged as a missing invoice.
Payments and collections
Cash receipts and disbursements, card payments, incoming and outgoing bank transfers. Cheques and promissory notes collected through the bank also arrive in this list. iFinances proposes which payment settled which invoice, using FIFO or invoice-specific settlement. Partial payments are split, bulk payments are allocated across invoices, and every proposal carries a written reason.
Bank movements
Bank vouchers that Nebim V3 created from MT940 files or its online banking service. MT940 is the standard file format banks use to deliver statements. You can upload these vouchers, but they have already passed through a posting rule inside Nebim. For independent evidence, upload the bank's own statement as the third source.
Counterparty master list
Customer, retail customer and vendor cards with tax number, legal name and currency. The tax number is the VKN for companies or TCKN for individuals. You upload the list once. A shortened bank-description name such as "POYRAZ METAL SAN" is then linked to the right counterparty. The similarity matching tolerates Turkish characters. Reconciliation letters also reach the right addressee.
How do you export the statement from Nebim V3?
The file route has four steps. Open the report, choose the Grid layout, save as Excel or CSV, upload to iFinances. On the direct route these steps are configured once at setup.
- 1
Open and filter the report
You open the account statement report under Customer and Supplier Management. You choose the account code or account group and the date range, for example 07/01/2026 to 07/31/2026. Nebim V3 can store report filters; save the month-end filter once and reuse it every period.
- 2
Choose the Grid layout
You select Grid as the report type. Nebim V3 reports come in Grid, Pivot and Form layouts. Matching needs Grid, which shows one row per document. Pivot gives totals and drops document numbers. Check that date, document number, description, debit, credit and currency columns are visible.
- 3
Save as Excel or CSV
You pick Excel or CSV as the save format. Nebim V3 saves reports as Excel, PDF, HTML, TXT, CSV, MHT and Image. PDF and image formats cannot be matched. Reports run through Nebim V3 Web Report are saved the same way.
- 4
Upload to iFinances
You upload the file to the matching template: account statement, sales invoices, purchase invoices, payments or bank statement. iFinances reads the file by content, not by extension. Legacy xls, CSV encoding and delimiter, and hidden sheets are handled automatically. Column headings and the debit/credit sign convention are recognized. Anything unrecognized is put to you as a question, never guessed.
Nebim V3 → Upload · columns recognised ✓ · 1,284 lines
How is the direct connection set up?
What Nebim V3 exposes technically, and the two routes iFinances uses into it.
Nebim V3 exposes data in several ways. Nebim V3 Integrator is a separately licensed REST service that runs on the customer's own IIS server. REST is a standard way for two applications to talk over the internet. A Connect call opens a session, and RunQuery and RunProc run queries defined in the database. Nebim V3 data can also be read directly from its MS SQL Server database. The Data Send/Receive module moves data between Nebim databases, and the Data Warehouse can be queried from Excel.
On the iFinances side the Nebim V3 connection is ready, and both routes are available. The first route is the file: you upload the standard report as Excel or CSV. The second route is the direct connection. The Integrator's REST service or a read on the V3 database is configured once at setup. Data then arrives every day without anyone running a report. Server address, license and credentials come from your own Nebim installation. Which route to set up is agreed together at setup. The rule is the same on both: iFinances only reads from Nebim and never writes to it.
Things to watch in Nebim V3
One company, two cards
Nebim V3 keeps wholesale customer, retail customer and vendor cards separately. A company you both buy from and sell to may be on two cards. Export the statement from both cards and upload both. iFinances joins the same tax number into one counterparty. Upload only one, and half of the counterparty's statement stays open.
Sub-customer level
Sub-customer movements roll up into a parent account in Nebim. Dealers and franchisees may live as business partners in a separate database. Export at the level the counterparty uses. Example: if the counterparty sends a statement per store, export per sub-account too. If the levels differ, the balance agrees but the lines do not.
Grid, never Pivot
A Pivot report gives totals and carries no document numbers. Matching needs the Grid layout. A user-specific report design may hide columns. If debit and credit are two columns or one signed column, iFinances detects the sign convention. Without document numbers, matching relies on amount and date only, and proposals get weaker.
A Nebim bank voucher is not a statement
Movements imported via MT940 or the online banking service are posted to counterparties by a rule in Nebim. If the rule chose the wrong account, the error is now inside Nebim too. Take the third source from the bank itself. iFinances reads the bank's own statement directly, including HTML tables saved with an xls extension.
Foreign-currency documents
Nebim documents carry an exchange-rate field. A statement can be exported in Turkish lira or in the document currency. Know which one you exported and keep it consistent with the counterparty. Example: a EUR 10,000.00 invoice settled by a TRY transfer. iFinances then uses the TCMB (Central Bank of Türkiye) rate. The rate used and the resulting difference appear in the match rationale.
Frequently asked questions
Nebim V3 e-Mutabakat gets the counterparty to confirm the balance by email or portal. iFinances works one layer down. It matches the counterparty statement, bank statement and e-invoice data against Nebim records line by line. Unexplained differences are shown with a reason. A confirmed balance does not mean every line is explained; the two can run side by side.
Not on the file route. Standard report output is enough; no extra module, license, IIS server or database access is needed. On the direct route you need the Integrator license or read access to the V3 database. That access comes from your own installation. Both routes are ready; the choice is made together at setup.
No. Whatever system the counterparty uses, they upload their own statement through a secure link you send them. No account or software is needed. Excel, CSV and legacy xls files are recognized by content and their columns are mapped.
Account reconciliation applies where a counterparty statement exists: wholesale customers, dealers, suppliers and group companies. Individual sales at the till have no counterparty statement. The control there is different: do card POS settlements and till takings agree with the bank statement? That belongs to bank reconciliation.
Nebim V3 can hold each company in its own database. You upload each company's statement under its own name. Balances between group companies then appear from both sides as an intercompany reconciliation. Any line that does not agree is flagged in both ledgers.
Other integrations
Same engine, different source. If your system is not listed, the file route still works.
Related content
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