Upload your Zirve account statement, reconcile bank and e-invoice data in one table
Upload Zirve's standard Excel report or open a direct connection. iFinances recognizes the debit/credit columns and matches lines against your bank statement and e-invoices. Every difference is listed with 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
You reconcile your Zirve account statement against bank and e-invoice (e-Fatura) data in one table. Accounting practices and SME finance teams on Zirve stop merging four sources by hand.
Zirve ships as separate packages. The account statement comes from the commercial package (Ticari Paket SQL). The 120 and 320 subledgers come from the general ledger package (Genel Muhasebe Paketi SQL). Those are the detailed ledgers behind receivables and payables.
Bank entries sit in their own module, and the counterparty's statement arrives as a PDF by e-mail. Merging four sources by hand in a spreadsheet is the slowest task of the period close. iFinances brings them into one table.
You upload the statement, invoice lists and receipt records exactly as Zirve exports them. Or a read-only direct connection to the Zirve database on your server is opened, chosen together at setup. Your bank statement and e-invoice data sit next to them either way.
The engine matches lines by FIFO, meaning the oldest open invoice is cleared first, or by invoice-specific clearing. It splits partial payments, allocates lump-sum payments and applies a cent tolerance. Foreign-currency items are compared at the TCMB (Central Bank of Türkiye) rate. Example: a transfer of TRY 48,250.00 is allocated to invoices FT-2026-0412 and FT-2026-0418, with the reason written down.
Every unmatched line lands on an exception list with a written reason and waits for your approval. iFinances never writes to Zirve, never creates vouchers and never closes a line on its own. The counterparty uploads their own statement through a secure link, with no account to create.
What data comes from this system?
Five data types are exported from the commercial and general ledger sides of Zirve as Excel files. Each one is loaded into its own iFinances template.
Customer and vendor statement
The account movement table in the commercial package is exported to Excel as an account statement report. In reconciliation it is the primary record of your side. Debit and credit lines, document dates and document numbers are matched against the counterparty statement and bank movements.
Sales invoice list
Sales invoices in the commercial package are reported as a list and loaded into the outbound invoice template. The list shows which invoice each debit line on the statement comes from. Example: a debit line of TRY 12,400.00 is tied to invoice FT-2026-0412 and checked against the e-invoice.
Purchase (inbound) invoice list
Purchase invoices are loaded into the inbound invoice template. That includes inbound e-invoices transferred from the e-invoice module into the commercial package. In vendor reconciliation the list is compared with the invoice list your supplier sends. It is also cross-checked against the e-invoice data held at the tax authority (GIB).
Receipts and payments
In Zirve, receipts and payments reach the account ledger through cash and bank vouchers. These records are loaded into the payments template. The engine allocates each receipt to open invoices by FIFO or invoice-specific clearing, splitting partial and lump-sum payments. Your actual bank movements come from the statement downloaded from your bank, not from Zirve's bank module.
Account master list
Account cards with name, tax number (VKN) and currency are loaded into the bulk company list template. The name is matched to bank narrative text with Turkish-character folding. Example: a transfer described as 'POYRAZ METAL SAN' is tied to the Poyraz Metal Sanayi card. The tax number is the identity key when sending reconciliation letters.
How do you get the file?
If you take the file route, the flow is short. You export the report from Zirve to Excel and upload it to iFinances. An unrecognized column is asked about, never guessed.
- 1
Open Reports in the account module
You open the account (Cari) module in the commercial package and choose Reports. For a single account, the statement print button produces a statement with date and transaction-type filters. For several counterparties, you run the statement report under Reports with a date range. Menu names can differ between builds.
- 2
Export the detailed statement to Excel
You choose the detailed account statement report and limit the date range to the reconciliation period. Example: 07/01/2026 to 09/30/2026. You check that the opening balance is visible on the report and save the file as xlsx. Legacy xls or CSV also works, since iFinances recognizes the format from the content.
- 3
Export invoice and voucher lists
You export the sales and purchase invoice reports and the cash/bank voucher lists with the same date range. All three files must cover the same period. That is what lets iFinances show, with a reason, which invoice or voucher a statement line came from.
- 4
Export the subledger if needed
You open the subledger report (Muavin) in the general ledger package. The subledger is the detailed movement list of one account in the chart of accounts. You export the 120 and 320 sub-accounts the same way. Any gap between the commercial statement and the subledger is better seen before reconciling.
- 5
Upload the files to iFinances
You upload each file to its template. The templates are statement, outbound invoices, inbound invoices, payments, bank statement and company list. The reader recognizes column names and the debit/credit sign convention, and asks about anything it cannot recognize. Matching starts as soon as the upload finishes, and the exception list is built.
Zirve → Upload · columns recognised ✓ · 1,284 lines
Connection path
Both routes are ready for Zirve. One route is uploading Excel files. The other is a read-only direct connection to the database on your own server. Which one you use is agreed during setup.
Zirve does not publish a public REST or SOAP API, the standard doorway through which programs request data. Zirve's data lives in a Microsoft SQL Server database. The commercial and general ledger packages use separate databases. The integration module posts commercial documents to the general ledger as vouchers, immediately or monthly in bulk.
In practice, external systems connect to Zirve in one of two ways. The first is read-only access to the database on your server through a SQL Server login. The second is a third-party API layer or integrator product installed on the server.
Those products need a license and a commercial agreement, with no self-service developer portal. Table and field names are not publicly documented by Zirve, so they are confirmed for each installation.
iFinances works with Zirve on both routes. On the file route you export the standard Excel or CSV report yourself. No external access to your server is opened. On the direct route, a read-only SQL Server login from your installation reads the Zirve data in place.
Credentials come from your own setup and stay with you. Because the commercial and general ledger databases are separate, which side is read is settled during setup. Most companies start on the file route, since it needs no extra license, server access or reseller coordination. On both routes iFinances only reads and never writes a record into Zirve.
Things to watch
The commercial statement and the subledger differ
The statement comes from the commercial package, the 120/320 subledger from the general ledger, in separate databases. Bulk posting, or a voucher never created for lack of an account code, makes the two totals differ. Example: the statement may show TRY 96,500.00 while the subledger shows TRY 84,100.00. Decide which file is your side, or upload both and let iFinances flag the gap.
Debit/credit columns and sign convention
Zirve statements usually show debit and credit in two columns, sometimes one amount column with a running balance. iFinances recognizes the layout from the content. Still, check on the first upload that invoices are on the debit side and receipts on the credit. Accounts with reversed balances deserve a separate look before reconciliation.
Column shift on Excel export
Zirve's August 2024 release notes mention fixing alignment problems when exporting some reports to Excel. On an older build, check that the header row and columns line up before uploading. Example: if a date appears under the 'Document No' header, export the file again. iFinances does not guess at a misaligned header, it asks you.
Foreign-currency accounts and rates
A foreign-currency statement may show TRY and currency amounts together, and you choose the column at upload. iFinances matches across currencies at the TCMB rate, not the daily rate table entered in Zirve. Example: an invoice of EUR 10,000.00 is compared with a TRY transfer at the TCMB rate. Exchange-difference lines that appear as separate documents are listed as explainable differences.
Inbound e-invoices versus commercial records
The Zirve e-invoice guide says inbound e-invoices are recorded by transferring them into the commercial package. Invoices in the commercial scenario are accepted or rejected from the pending-approval list (Onay Bekleyenler). An inbound invoice that was not transferred or accepted is not part of your commercial records. Upload e-invoice data separately, so iFinances flags invoices at the tax authority that your books lack.
Frequently asked questions
Export the account statement, invoice lists and receipt records from Zirve to Excel and upload them to iFinances. Add your bank statement and e-invoice data. The engine matches lines, lists unmatched ones with a reason and waits for your approval. At the end, a reconciliation letter with a per-currency summary is produced as a PDF.
Open the account module, then run the statement report under Reports with your date range. For a single account the statement print button also works. Save the file as xlsx. Legacy xls or CSV also works, because iFinances recognizes the format from the content.
Yes, the direct connection is ready. Zirve has no public API, so the connection uses read-only permission on your SQL Server database. The file route is equally ready and needs no extra license or server access. Which route you use is chosen together during setup.
Any Zirve package whose standard report can be exported to Excel. That includes the commercial package, the general ledger package, the small-business package and the accounting-practice package. The commercial package supplies the account statement, and the general ledger package supplies the 120/320 subledger.
It does not matter. You send the counterparty a secure link. They upload their own statement or Excel, with no software to install and no account to create. iFinances matches the two statements line by line and lists the differences for both sides to see.
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