Reconcile the Luca customer statement against bank and e-invoice data
The customer statement you export from Luca is matched in iFinances against counterparty, bank and e-invoice data. Records stay in Luca. iFinances only matches and explains each 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
Luca reconciliation means matching your Luca customer statement against the counterparty statement, bank and e-invoice data. This page shows accountants, accounting managers and CFOs which Luca file to take and how to upload it. The gain is simple. Every open line is read from a list with a written reason, not hunted in a spreadsheet.
Luca is the cloud accounting family of TURMOB, the Turkish union of chartered accountants. On the accountant side, Luca MMP keeps the general ledger with vouchers and a chart of accounts. On the business side, Luca Koza and Luca Net KOBI handle receivables, invoicing and cash. That split makes reconciliation hard. The business sees a customer statement. The accountant keeps the account 120 (trade receivables) or 320 (trade payables) statement. The two are posted by different people on different dates.
iFinances brings the three sources into one table. You upload the Excel or CSV file exported from Luca. Column names and the debit/credit sign are recognized from the content. Any unknown field is asked, not guessed. The engine links each payment to an invoice and writes the reason. Example: a transfer of TRY 48,250.00 cleared invoice FT-2026-0412. The limit is clear. iFinances writes nothing into Luca, keeps no books and never closes a line on its own. The connection is ready and there are two routes. You upload a file, or a direct connection is set up. Which one to use is decided together at setup.
What data comes from Luca?
Luca's standard reports map one to one onto the iFinances upload templates. The same data arrives as an uploaded file or over the direct connection. Your ledger side is loaded through the invoice lists and the payment records. The account statement is the reference for the balance and period check.
Account statement and customer statement
In Luca MMP you take the account statement for account 120 (receivables) or 320 (payables). The report lists voucher lines with debit and credit columns. In Luca Koza and Net KOBI the Customer Statement and Account Movement reports do the same job. Your side of the reconciliation is the set of movements in this statement. The statement balance is the control figure you compare with the total in the upload preview. Example: if Luca shows TRY 312,480.00 on August 31, 2026, the preview should show the same. Make sure the report covers the whole period and every movement of the counterparty.
Sales and purchase invoice lists
In Luca Koza, the sales and purchase invoices in the Invoice menu form the invoice base. In Luca MMP, invoices reach the ledger through Excel Invoice Import and the Smart Integration Point. Those two tools move data into Luca and do not export an invoice list. If your accountant runs MMP, export the invoice list from your e-invoice (e-Fatura) integrator as Excel. The list loads into the outgoing and incoming invoice list templates in iFinances. Invoice number and document date come from this list. So a payment can be linked to a specific invoice instead of FIFO. Missing-invoice and duplicate flags are also produced against this list.
Collections and payments
In Luca Koza and Net KOBI, Collection and Payment Transactions under Finance Management carry the cash movements. In Luca MMP the same data sits in receipt and disbursement vouchers. These records load into the payments template in iFinances and serve two jobs. First, the ledger payment is verified against the bank statement. Then it is allocated to open invoices by FIFO (first in, first out) or invoice-specific clearing. Example: one transfer of TRY 100,000.00 is split across invoices FT-2026-0388 and FT-2026-0401.
Bank movements
The Bank Integration screen in Luca MMP pulls daily statements from partner banks. In Luca Net, the Bank Statements module works with CSV uploads. Luca Koza has Bank Accounts and Bank Movements screens. For iFinances the cleanest source is the bank's own statement. The bank-specific templates and the generic bank template exist for that file. The bank movement recorded in Luca represents the ledger side. In three-way matching, the ledger entry, the bank statement and the counterparty statement are compared on one line.
Customer and vendor master list
In Luca Koza and Net KOBI, the Customer Account Card screen holds company names and tax numbers. In Luca MMP the same data sits in Chart of Accounts Customer Definition. This list loads into the bulk company list template in iFinances and serves two purposes. Counterparty statements are attached to the right company by tax number (VKN). Unlabeled bank transfers are suggested to a company by name similarity. Example: the bank text "POYRAZ METAL SAN" is matched to the card "Poyraz Metal Sanayi A.S.". iFinances proposes, and the decision stays with you.
How do you get the file?
The file route has four steps. You save the Luca report as Excel or CSV, upload it to iFinances and confirm the column mapping. On the direct route the same steps are configured once at setup.
- 1
Decide which Luca product you export from
You choose the source first. If your accountant uses Luca MMP, take the account statement for account 120 or 320. If the business runs Luca Koza or Net KOBI, use the Customer Statement report. Both show the same transactions with different columns. iFinances reads both. Still, use the same report every period. That shortens cut-off discussions.
- 2
Select the full period and account range
You set the report date range to the whole reconciliation period. Example: July 1, 2026 to August 31, 2026. Make sure the opening balance is in the file or at hand. Check that every movement of the counterparty is in the file. If some are left out, lines the counterparty sees are wrongly flagged as missing. For foreign-currency accounts, make sure the currency amount is also in the file.
- 3
Save as Excel or CSV
You pick a report that gives Excel or CSV output. Some Luca reports offer only Word or PDF. iFinances recognizes xlsx, xlsm, xlsb, legacy xls and CSV from the content. Encoding and delimiter are detected automatically, and hidden sheets are read. There is no need to edit the file by hand. Report headers above the column row and subtotal rows are stripped.
- 4
Upload to iFinances and confirm the mapping
You upload the file and check the preview. iFinances recognizes column names and the debit/credit sign. Any field it cannot identify is asked, not guessed. The preview shows row count, period and balance total. You compare with Luca and confirm. You also upload the counterparty statement and the bank statement for the same period. The counterparty can upload its own file through a secure link. No account or software is needed on its side.
Luca → Upload · columns recognised ✓ · 1,284 lines
Connection path
First the technical paths Luca offers, then the two connection routes iFinances uses.
Luca is mostly file-based. Excel Data Import, Excel Invoice Import and Chart of Accounts XML/CSV import mainly move data into Luca. In Luca Koza, the REST API, a web service for reading data, is open only to named partners. The e-document web service is granted after an integration application and a confidentiality agreement. The TURMOB e-Birlik integration key serves TURMOB services only. As a cloud service, Luca gives no direct database access. These findings are based on vendor documentation. Access terms can be changed by Luca Yazilim and TURMOB.
On the iFinances side the Luca connection is ready, and both routes are available. The first is the file route. You upload Luca's standard export, and iFinances recognizes the content and matches it. This works on every Luca subscription. The second is a direct connection. If your account holds the Koza REST service or the e-document web service, it is configured at setup. Data then arrives without anyone downloading a report by hand. That access comes from your own Luca account and from the terms set by Luca Yazilim and TURMOB. iFinances has no partnership with either. How much a direct connection covers depends on the services your account holds. The file route has no such limit. Which route to set up is decided together at setup. Reconciliation works the same way on both.
Things to watch
MMP and Koza show the same data differently
For the same counterparty, the Luca MMP account statement and the Luca Koza customer statement can look different. MMP is organized by voucher logic, Koza and Net KOBI by business logic. The column sets differ. Choose your reconciliation source once and use the same report every period.
Sign convention and reverse balances
You see a credit balance in account 120 or a debit balance in account 320. This usually comes from a payment posted to the wrong account. Luca's tool for listing and correcting reverse-balance accounts can generate a corrective entry for such lines. If the entry is posted before period end it appears in the statement, otherwise it does not. iFinances recognizes the sign convention from the content. It lists the open line with a written reason and does not clear it.
Accountant posting lag
An invoice dated August 28, 2026 in the business may reach the ledger on September 3, 2026. Luca MMP is usually in the accountant's hands, and entries are posted days later. Document date and posting date diverge. Lines near period end show up in the following month's statement. iFinances puts such a line on the open list with the reason "cut-off". You do not hunt for it in a spreadsheet.
PDF and Word output cannot be matched
Some movement reports in Luca offer only Word and PDF output. iFinances reads xlsx, xls, xls files that are actually HTML tables, and CSV. PDF and Word reports are not uploaded. If you hit a screen without an Excel option, use an Excel-capable report with the same data.
Exchange-rate source on foreign-currency accounts
In its bank integration, Luca converts foreign-currency accounts to TRY. It uses the TCMB (Central Bank of Türkiye) rate of the transaction date. Voucher lines carry a rate field. If the file has only the TRY amount, the currency amount is lost. Cent-level differences then appear against the counterparty's EUR 10,000.00 statement. Make sure the currency amount is also in the file. iFinances matches across currencies at the official TCMB rate.
Frequently asked questions
The reconciliation tools inside Luca tied to TURMOB services were built around the Ba-Bs forms. Those forms were abolished from the September 2024 period by VUK General Communique No. 565. iFinances reconciles lines, not forms. The counterparty statement, your ledger record, the bank movement and the e-invoice data are matched in one table. Every open line carries a written reason.
Ask your accountant for the period's invoice and payment records and the 120/320 account statement as Excel files. You upload them to iFinances yourself. The accountant does not need to use iFinances. The counterparty can upload its own statement through a secure link. Nobody has to install additional software.
The connection is ready and both routes are available. Luca has not published a general read API open to third parties. Its REST and web services are granted under agreements, and there is no direct database access. A direct connection uses whichever service access your own account holds. The file route works on every subscription. We decide together at setup.
Not necessarily. Invoices processed into Luca through its e-document portal or Smart Integration Point appear on the ledger side. Exporting the e-invoice list directly from your own integrator as Excel is often more complete. iFinances loads it into the outgoing and incoming invoice list templates. An invoice that never reached the ledger is flagged as a missing invoice.
iFinances does not clear them. If there is a matching candidate, it is proposed with its reason. Otherwise the line stays on the open-items list with a written reason. The corrective entry is posted in Luca by the accountant. See our article on credit balances in receivables and debit balances in payables for the detail.
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