Wolvox account statement reconciliation, line by line
For groups whose Turkish entity keeps its books in AKINSOFT Wolvox. The statement, invoice register and bank entries reach iFinances by Excel export or direct read-only connection. Matching, the exception list and the confirmation letter are produced in iFinances, nothing is written back to Wolvox.
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
This page explains how the Wolvox account statement (cari ekstre) is reconciled line by line with the counterparty. It is for group controllers and local finance teams whose Turkish entity runs AKINSOFT Wolvox. Manual line-by-line comparison ends, and every difference comes with a written reason. Wolvox keeps the subledger (customer and supplier accounts) in one database and General Accounting in another.
iFinances puts the Wolvox statement, invoice register, bank entries and the counterparty's Excel file in one table. The engine matches the lines and writes a reason next to each match. A typical reason reads "invoice FT-2026-0412, TRY 48,250.00, cleared by the wire of March 12, 2026". Missing invoices, duplicates and unexplained differences wait for your approval, never cleared by iFinances on its own.
What data comes from this system?
The local team exports these six data sets from Wolvox. Each one loads into the matching iFinances template.
AR/AP subledger statement
The subledger statement lists every debit and credit between the entity and one customer or supplier. Wolvox stores these movements in the CARIHR table and builds the date-ranged statement report from it. The entity's lines are matched one by one against the counterparty's statement. Value date, the day the bank values the money, is usually missing, so matching uses the document date.
Invoice register (sales and purchases)
Invoice headers sit in FATURA and lines in FATURAHR. The sales register is compared with the customer's purchase list, the purchase register with the supplier's sales list. Document number (FT-2026-0412), date, account code, net and gross amount are enough. The VAT breakdown and document exchange rate sit in side tables and are not needed.
Payments and receipts
Payments and receipts are told apart in the subledger by a transaction type code. Cash entries come from KASAHR and bank entries from BANKAHR. Cheques and notes sit in CEK_SENET and enter the statement when collected, so no separate template is needed. iFinances matches payments to invoices and can split a TRY 100,000.00 bulk payment across three invoices.
Bank entries as booked
Wolvox keeps bank definitions, accounts and movements in separate tables (BANKA_ADI, BANKA_HESAP, BANKAHR). It also has a module that imports the statement received from the bank. Reconciliation uses two layers, the bank entries booked in Wolvox and the bank's own statement. iFinances takes both and shows the gaps and duplicates between them as the third source.
e-Invoice status fields
An e-invoice (e-Fatura) is an invoice sent electronically through the Turkish Revenue Administration. Wolvox has no separate e-document table, the status sits in fields on the invoice record. Include those fields in the export and the file shows which documents were e-invoices and which e-archive. iFinances cross-checks the e-invoice list from your provider against the ledger and the bank statement.
Counterparty master data
The CARI table carries account code, legal name, tax number (VKN) and currency. Loaded as a bulk company list, it locks each counterparty to its Turkish tax number. It also feeds name-similarity suggestions, linking bank text "POYRAZ METAL SAN" to "Poyraz Metal Sanayi A.S.".
How do you get the file?
If you take the file route, the flow has four steps. The local team runs the report in Wolvox, exports it to Excel and uploads it to iFinances.
- 1
Run the detailed account transaction report
You run Ayrintili Cari Hareket Raporu, Wolvox's detailed account transaction report, for the account and period. Use the same period as the counterparty, for example January 1 to June 30, 2026. Keep the opening balance line in the report. From release 8.25.07 the report grid also carries a transaction type detail column.
- 2
Export the grid to Excel
You right-click the report grid and choose Excel from the Export menu. Save the file as it comes, do not rename columns, remove the header row or reformat numbers. iFinances recognizes the format from the content, so xlsx, legacy xls and CSV are all accepted.
- 3
If needed, pull tables through the SQL Monitor
When the standard report lacks a column, you run a query in Wolvox's SQL Monitor. A typical query is SELECT * FROM CARIHR. You export the result to Excel from the right-click Export menu. This gives every field, and your Wolvox permission level must allow running queries.
- 4
Upload to iFinances and confirm the column mapping
You upload the file to the account statement, invoice list or payments template. iFinances detects column names, Turkish headers included, and the debit/credit sign convention. Any unrecognized field is asked about, never guessed. Add the bank statement and e-invoice list for the same period, and three-way matching starts.
Akınsoft Wolvox → Upload · columns recognised ✓ · 1,284 lines
Connection path
Both routes are ready for Wolvox. The first is file upload, the second a direct read-only connection to the entity's own database server. Which one is used is agreed at setup.
Wolvox data lives in a Firebird 2.5 or MS SQL database on the entity's own server. Read-only SQL access is opened there through a standard driver such as ODBC, without needing AKINSOFT's permission. A separate Wolvox SDK exists, but it needs an SDK license and has no command for line-level invoices. There is no public REST API, meaning a web service that serves data, and no cloud edition.
iFinances works either way, and the SDK is only an option for companies already holding a license. On the file route the local team uploads the Wolvox Excel or CSV export, no VPN needed. On the direct route, iFinances reads subledger, invoice, cash and bank movements with a read-only login you create. The credentials come from your installation and stay with you, and iFinances only reads Wolvox, never writes.
Things to watch
Transaction type codes and debit/credit direction
Wolvox stores what a movement is as a numeric transaction type code. Reports may show debit and credit in separate columns or one amount column with the direction encoded. iFinances detects the sign convention from the file and asks when it is unclear. A cash-sale invoice settles on the same document, so that settlement must not reappear in the payments file.
Foreign-currency accounts and document rates
The account currency sits in the account's currency definition, the invoice rate in a per-document rate table. Do not mix a TRY-equivalent statement with a foreign-currency one, especially for intercompany balances in EUR. It compares a EUR 10,000.00 invoice with TRY 385,400.00 received at the TCMB (Central Bank of Türkiye) rate. The FX difference is shown on its own line.
Subledger and general ledger live in different databases
Wolvox General Accounting, with journal vouchers and the chart of accounts, runs in a separate database. Integration vouchers carry subledger movements into the ledger. When they lag, accounts 120 (receivables) and 320 (payables) drift from the subledger statement. Reconcile on the ERP statement, and have the local team check the GL difference inside Wolvox.
Version differences and report columns
Column names and counts in Wolvox 8 and Wolvox 9 report grids can differ. The transaction type detail column, for instance, was added in release 8.25.07. iFinances recognizes columns by content rather than name, so a version change rarely causes trouble. When it does, a one-time confirmation is requested on the mapping screen.
Booked bank entries are not the bank statement
Bank entries in Wolvox are already posted to the books, while the bank's statement is an independent source. Uploading only one of them hides duplicates and gaps. Take the statement from the bank and the entries from Wolvox separately. A TRY 12,500.00 receipt sitting at the bank but not yet booked in Wolvox surfaces this way.
Frequently asked questions
Yes, the connection is ready. The direct route uses read-only access to the entity's own Firebird or MS SQL database. The file route is equally ready, the local team exports Excel or CSV and uploads it. Which route is used is chosen at setup. On both, iFinances only reads and never writes to Wolvox.
No. Neither the file route nor the database route needs an SDK, a license or developer credentials. A standard report export or a read-only database login is enough. The SDK only comes up for companies that already hold a license and prefer that path.
Wolvox 8 and Wolvox 9 report exports are accepted, and the file route is version-independent. Columns are recognized by content rather than name, so column differences between versions rarely matter. If an unrecognized field appears, iFinances does not guess, it asks you.
Yes. Counterparty reconciliation runs on the ERP subledger statement, no journal vouchers or chart of accounts are needed. Adding the invoice register, payments and bank statement completes the three-way cross-check. If General Accounting is also in use, have the local team confirm accounts 120/320 agree with the statement.
No. The counterparty's software does not matter. iFinances sends them a secure link, they upload their own statement as Excel, and no account is created. The Wolvox statement and their file are matched in the same table. The difference list and confirmation letter are produced as PDF, which covers the usual intercompany case too.
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