Reconcile your ETA account statement line by line
Upload ETA:SQL and ETA:V.8-SQL reports as Excel, or connect directly to the database. iFinances matches statement, invoice and bank lines in one table. Every match carries a written reason.
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
Upload your ETA account statement (cari ekstre) as Excel or connect directly. Reconciliation is then prepared in one table. This page is for finance managers, accountants and group finance teams whose Turkish books are kept in ETA. The account statement, the invoice list and the bank movements are matched in the same table. Every open line gets a written reason and waits for your approval.
ETA is a Turkish commercial and accounting product family that runs on an open MS SQL Server database. Its ETA:SQL and ETA:V.8-SQL editions are common in accounting practices and small to mid-sized companies. Receivables, Invoicing, Bank and Cash are separate modules with separate vouchers. So one TRY 48,250.00 collection leaves traces in three places. iFinances only reads those lines, never writes to ETA and never closes a line on its own.
What data comes from ETA?
ETA's modules map onto the data types used in reconciliation as follows. Table names are taken from ETA's own technical notes and sample queries.
Customer and vendor account statement
The account statement is the main reconciliation file. ETA keeps these lines in the CARHAR (account movement) table and account master data in CARKART. The Receivables module statement report lists the lines with debit, credit and running balance columns. iFinances compares this statement line by line with the one the counterparty sends and produces the difference list.
Invoice list (sales and purchase)
Sales and purchase invoices share the FATFIS header table, separated by voucher type. Line items live in FATHAR. iFinances uses the invoice number (FT-2026-0412), date, amount and due date to match payment and e-invoice (e-Fatura) lines. Outbound and inbound invoices are loaded through separate templates.
Payment and collection records
ETA has no single payment table. Collections and disbursements sit separately in account movements, cash vouchers and bank vouchers. The iFinances payments template gathers them into one list. It then allocates them to open invoices by FIFO (oldest invoice closes first) or by invoice-specific clearing. A TRY 100,000.00 bulk transfer, for example, is split across three invoices, each part with a written reason.
Bank movements
The Bank module holds account cards in BANKHESAP and bank vouchers in BANKAFIS and BANKAHAR. iFinances compares the ETA bank movement report with the real statement you download from the bank. That surfaces movements booked in the ledger but missing at the bank. A TRY 12,400.00 transfer received by the bank but never posted appears in the same list.
Cheque and promissory note movements
The Cheque/Note module works separately with the CSNKART and CSNHAR tables. No separate cheque/note report is uploaded to iFinances, though. The movement that affects the account balance already appears in the account statement. Reconciliation runs on that line. For a post-dated cheque, the statement date and the date the funds reach the bank can differ. Such a line may land on the exception list when compared with the bank statement.
Journal vouchers and chart of accounts
The General Ledger module works with journal vouchers. The Turkish uniform chart of accounts loads automatically when a company is created. The ledger-side file uploaded for reconciliation is the account statement, not the journal vouchers. Before exporting, compare accounts 120 (trade receivables) and 320 (trade payables) with the statement in ETA. That way a reversed balance is caught on your own side first.
How do you get the file?
If you take the file route, the flow is short. The local team saves the ETA report as Excel and uploads it to iFinances. Columns and the debit/credit sign are recognized from the file content.
- 1
Open the account statement report
You open the Receivables (Cari) module in ETA:V.8-SQL and follow Reports, Movement Reports, Statements (Ekstreler). You select the date range of the reconciliation period, for example 01/01/2026 to 06/30/2026. Then you pick the account card in question. The opening balance must be visible in the report, because matching starts from it.
- 2
Save the report in Excel format
You choose Excel as the output format on the report screen. ETA reports can also be saved as Word, PDF, HTML, txt and rtf, but reconciliation needs Excel. In the report design, switch off printer elements such as page headers and page numbers. That keeps the file clean.
- 3
Add the invoice list and the bank report
You take the invoice list from the Invoicing module the same way. From the Bank module you take the movement report for the relevant account. Save sales and purchase invoices as separate files. Loading them into the outbound and inbound invoice templates then takes one step.
- 4
Upload the files to iFinances
You pick the matching template in the setup wizard and drop the file. iFinances recognizes xlsx, legacy xls and CSV from content and sees hidden sheets. If it cannot identify a column, it does not guess, it asks you. Matching starts as soon as the upload finishes and the exception list appears.
ETA → Upload · columns recognised ✓ · 1,284 lines
Connection path
Both routes are ready for ETA. You upload Excel files, or a direct connection is opened to the ETA database. Which one you use is agreed during setup.
ETA keeps its data in an open MS SQL Server database and presents that as a product feature. The built-in SQL editor and the Dynamic Excel Connection let users write free queries against that data. Access runs over ODBC / OLE DB, the standard Windows database drivers, with a read-only SQL login. ETA has no REST or SOAP service, that is, no interface called over the internet. So the direct route runs through the database.
On the file route, the Excel reports exported as described above are uploaded. No external access to your ETA server is opened. On the direct route, a read-only SQL login created in your own installation is used. Account, invoice and bank movements are read into the same templates. The credentials come from your installation and stay with you. On both routes iFinances only reads, never writes to ETA and never closes a line on its own.
Things to watch
Special vouchers do not move the account balance
If the card balance and the statement balance disagree, check special vouchers first. According to ETA's official Q&A document, movements entered through special vouchers do not change the account balance. Check for special voucher entries before exporting the reconciliation file. Otherwise two ETA reports will not even agree with each other.
Zero-amount invoices may be missing from the statement
Invoices of TRY 0.00, such as free-of-charge deliveries, may not reach the account statement. The cause is the Account Record for Zero-Amount Invoice parameter in Invoice General Parameters being off. If the counterparty shows that invoice on its statement, iFinances flags it as a missing invoice. The reason is written next to it. The source of the difference is an ETA parameter, not a reconciliation error.
Payments are not in one table
One collection can leave traces in four places in ETA. Account movement, cash voucher, bank voucher and the Cari II payment-matching record. Load the same payment from two reports and TRY 48,250.00 appears twice. It is then flagged as a duplicate. Feed the payments template from one source, usually the collection and disbursement lines of the account movement report.
Multi-currency account cards and FX differences
ETA can track several currency accounts on one account card. Exchange rates live in the shared ETA_MASTER database, not in the company database. Note which currency the statement was exported in. iFinances uses the TCMB (Central Bank of Türkiye) rate for cross-currency matching. FX difference lines are shown with their own reason.
Excel export can fail on a component error
If the Excel output fails, the cause is usually a Windows component. ETA's official document notes that on 64-bit systems the error can occur even after Etaexcel.reg has been run. OLEXLSF.DLL must then be re-registered. Apply that repair first and involve ETA support if the problem persists. On the direct route this step never comes up.
Frequently asked questions
Yes, the connection is ready. ETA exposes an open MS SQL database. The direct route runs through a read-only SQL login created in your own installation. The file route is equally ready. You upload the Excel output of ETA reports, and no external access to your server is opened. Which route you use is agreed during setup.
For account reconciliation, one file. The account statement for the counterparty and period in question, saved as Excel. For the bank and e-invoice sources too, ask for the invoice list and the bank movement report. Download the bank statement yourself. The accountant changes nothing in ETA and installs nothing.
The file route is version-independent. Excel output from ETA:SQL, ETA:V.8-SQL and V.11 / V.11 Pro reports can be loaded. Customized report designs with added or removed fields are fine. Columns are recognized by name and content, and any unknown column is queried rather than guessed.
They do different jobs. ETA's payment matching links an invoice to a collection inside your own ledger. Reconciliation compares your ledger with the counterparty statement, the bank statement and e-invoice data. iFinances brings those three external sources into the same table as your ETA data. Every difference is listed with a written reason.
No. You send the counterparty a secure link. They upload the statement from their own system through it and need no software or account. iFinances matches the two statements and, if required, generates the reconciliation letter as a PDF.
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