Reconcile your Mikro account statement with bank and e-invoice data in one table
Upload the Excel reports Mikro already produces, or connect to Mikro directly. iFinances matches each line and writes a reason for every difference.
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 export the Mikro account statement (Cari Hesap Ekstresi) to Excel, and iFinances reconciles it line by line. Finance teams and group controllers with a Turkish entity stop hunting for differences across spreadsheets.
In Mikro, invoices, collections and posted bank entries all live in one account-movement table. At month end the statement is exported and compared with the counterparty's statement in a spreadsheet. Add the bank statement and the e-invoice (e-Fatura) list, and the work spans three files. iFinances puts all three sources in one table, matches the lines and explains each open item in writing.
What data comes out of Mikro?
Each item is a standard Mikro report or list. The Turkish name is what your local team will recognize.
Account statement (Cari Hesap Ekstresi)
The statement comes from Mikro's account-movement table with date, document, debit, credit and running balance columns. In iFinances it is your side of the ledger, account 120 (trade receivables) or 320 (trade payables). It is compared line by line with the counterparty's statement. Example: both balances show TRY 48,250.00, but invoice FT-2026-0412 exists only on your side.
Sales invoice list
Mikro has no invoice header table. An invoice is a set of rows in the account movements, keyed by document series and number. The e-invoice identifier, called ETTN, sits in a separate e-invoice transactions table. iFinances cross-checks the list against the counterparty's incoming invoices and the e-invoice data. Keep the series and number columns in the export.
Purchase invoice list
Supplier e-invoices arrive through the integrator and are tracked in Mikro's incoming invoice list. iFinances matches this list against the supplier statement and your payment records. Example: a TRY 12,400.00 supplier invoice appears in the e-invoice list but was never posted to account 320. It shows in the exception list as "not in ledger".
Payments and collections
Collection, disbursement and memo entries share the account-movement table with invoices and differ only by document type. iFinances matches them against the counterparty statement and the actual cash movement on the bank statement. Example: a TRY 20,000.00 collection dated March 15, 2026 is in the ledger but never reached the bank. Only the three-way comparison shows this.
Bank entries
Mikro keeps bank account cards and imported online bank movements in their own tables. Posted bank entries sit among the account movements. For reconciliation the authoritative source is the bank's own statement, and Mikro's bank entries represent the ledger side. A transfer posted twice, or a transfer with no narrative, is found in the gap between the two.
Counterparty master list
Account cards in Mikro carry the legal name, tax number (VKN) and address. They can be exported as a list. Uploaded as a bulk company list, it lets iFinances suggest which counterparty a bank narrative belongs to. Example: bank narrative "POYRAZ METAL SAN TIC" is paired with card "Poyraz Metal Sanayi ve Ticaret A.S." Turkish-character folding handles spelling variants, and a person approves the suggestion.
How the files are produced
On the file route your team runs a standard Mikro export and uploads it to iFinances. Nothing is installed on the Mikro server and no API application is filed.
- 1
Run the account statement report
Your team opens the statement report. Mikro's support center lists it as Cari Hesap Ekstresi (044117) or its detailed variant (044118). They select the account, the period and the currency. A document-level view is all reconciliation needs. The line-detail option lists stock items under every invoice and only inflates the file.
- 2
Export to Excel or CSV
Your team exports the report output as Excel or CSV. Column order does not matter and nothing needs to be renamed. Export options vary by Mikro version, and whichever is available works. iFinances identifies the file by its content.
- 3
Repeat for invoices, payments and bank entries
Your team exports the sales and purchase invoice lists, the collection and disbursement records and the bank entries. All cover the same period. Each comes from its own report screen. They also download the bank's own statement from online banking. iFinances reads bank statements with bank-specific templates.
- 4
Upload to iFinances
You upload each file to its template, from the local office or from a shared-service center abroad. The reader identifies the format from content, not the extension. xlsx, legacy xls, CSV and HTML tables saved as xls all work, including Turkish-encoded CSV. Column names and the debit/credit sign convention are detected. Any unrecognized field is asked about rather than guessed.
- 5
Review the exceptions
You open the exception list, read the written reason for each suggestion and approve or reject it. The engine has matched the lines as soon as the upload finished. If the counterparty statement is still missing, you send the counterparty a secure link. They upload their own file and need no account or software.
Mikro Jump / Fly → Upload · columns recognised ✓ · 1,284 lines
Connection path
Two separate questions. What technical access does Mikro offer, and how does iFinances use it?
Mikro's official API documentation describes a REST/JSON interface. That is a standard way for programs to request data over a network. It is served by a Windows service on the customer's own server. Jump Bulut is reached through a separate API gateway. Calls authenticate with an API key, company code, user code, working year and a daily password digest. The account card list has a dedicated endpoint. Account movements, payments and bank entries are read through a database method called SqlVeriOkuV2. Access is licensed, subject to an application to Mikro, and pricing is not public.
On the iFinances side the Mikro connection is ready and both routes are available. On the file route the Excel or CSV exports described above are uploaded and matching runs on them. On the direct route the same records are read through Mikro's REST/JSON interface and the SqlVeriOkuV2 database read. The API key and the company and user codes come from your own Mikro installation. The route is chosen together at setup. On either route iFinances reads only, writes nothing to Mikro and clears nothing on its own.
What to brief your local team on
Confirm the currency of the export
The Mikro statement shows either TRY or foreign-currency columns, depending on the currency chosen at report time. On a foreign-currency account the TRY balance can be 0.00 while EUR 12,500.00 is still open. Agree with the local team which currency the statement is exported in. Compare with the counterparty in the same unit. For cross-currency items iFinances applies the TCMB (Central Bank of Türkiye) rate and shows the FX difference separately.
Do not let anyone flip debit and credit
Mikro reports give debit and credit in separate columns with a running balance. Some lists use a single signed amount column instead. iFinances detects the convention from content, so the export should be uploaded as produced. The counterparty's statement is the mirror image of yours, and the engine already accounts for that.
Ask for document-level, not line-level
The statement report has a line-detail parameter that dumps stock items under each invoice. A 300-row statement becomes 3,000 rows while totals stay the same. Reconciliation is done at document level, so ask for the export with the detail off.
Keep the document series and number
Mikro identifies an invoice by document series and number inside the account movements. The e-invoice ETTN is kept in a separate table. Those two columns are the reliable bridge to the e-invoice list. Whatever report the invoice list comes from, they should stay in the file.
Older versions export differently
Mikro Run, Jump, Fly and Jump Bulut may share report codes, but export options vary by version. Older installations can produce legacy xls or an HTML table saved with an xls extension. iFinances recognizes all of these from content. Avoid a manually tidied workbook with hidden sheets and merged header cells. The raw export is the better upload. Document type code lists are not in the public documentation. On the direct route they are confirmed against live data.
Frequently asked questions
Four exports as Excel or CSV for the period. The account statement (Cari Hesap Ekstresi) for each counterparty in scope. The sales and purchase invoice lists. The collection and disbursement records. Add the bank's own statement and the e-invoice list from the integrator. The local team already produces these reports at month end.
It can. The connection is ready and both routes are available. You can upload the standard Excel or CSV exports. Or Mikro can be read directly through its REST/JSON interface and its database read method. The route is chosen together at setup, and direct access follows Mikro's own licensing and application terms.
Not for the file route. It uses report exports that any Mikro user can produce, with no API key, license or server access. For the direct route, yes. Mikro's API is licensed and subject to an application, and we go through that step together at setup.
Yes. Every match and every exception carries a written reason. A reviewer who does not read Turkish can still follow why two lines were paired. The local team uploads the files and the exception list is reviewed centrally.
Mikro's reconciliation features send a balance confirmation to the counterparty. iFinances works on the lines underneath that balance. It matches the statement, the bank statement and the e-invoice data in one table. It allocates partial and bulk payments and lists open items with a reason. The reconciliation letter is produced from that result. The two complement each other.
No. iFinances keeps no ledger, writes no record into Mikro and never clears a line by itself. The output is a list of suggested matches with reasons. Corrections and postings stay in Mikro and with your team.
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