Reconcile your Logo statements against bank and e-invoice data in one table
Statements, invoice lists and bank entries from Logo Tiger or GO are matched line by line in iFinances. Every match carries a written reason your group controller and auditor can read. The connection is ready and both routes work. Upload the exports, or read Logo directly.
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
Reconcile the Logo Tiger or GO statement against the counterparty statement, the bank statement and e-invoice (e-Fatura) records. Finance leads of Turkish subsidiaries and their group controllers get a match list with written reasons. Nobody lines up three or four spreadsheets by hand at month end.
Logo keeps receivables, payables, invoices, bank, cash and check records in one MS SQL database. The raw material for a reconciliation is already there. The difficulty is the comparison. The account 120 (trade receivables) statement in Logo, the customer's statement and the bank statement sit apart.
iFinances takes the Logo statement as an uploaded export or reads it through a direct connection. The engine ties a 48,250.00 TRY transfer dated March 12, 2026 to invoice FT-2026-0412 and writes the reason. Unmatched lines go to an exception list and every proposal waits for your approval. iFinances never writes back to Logo, keeps no books and clears no line on its own.
What data comes from Logo?
Logo holds all six data types a reconciliation needs. Which one you upload depends on the reconciliation you run. A statement reconciliation needs only the statement, a bank reconciliation also needs the bank vouchers.
Customer or vendor statement
Logo's Cari Hesap Ekstresi (account statement) report exports a date range with debit, credit and balance columns. In iFinances this statement is your side, your view of account 120 (receivables) or 320 (payables). It is matched line by line against the counterparty's statement and the bank entries.
Sales invoices (outbound)
Sales invoices in Logo carry invoice number, date, account, amount and currency. A typical line reads FT-2026-0412, March 12, 2026, 48,250.00 TRY. iFinances matches this list against collections and the customer's statement. An invoice that was paid but still looks open is isolated here.
Purchase invoices (inbound)
Supplier invoices sit in the same structure in Logo. The inbound list enters a three-way comparison with the vendor statement and outgoing payments. A supplier invoice never booked, or booked twice, surfaces here.
Payments and collections
Logo keeps payments and collections together with their clearing movements. Check and promissory-note movements arrive as they appear on the statement. iFinances ties each payment with FIFO, meaning the oldest invoice clears first, or to a specific invoice. A 30,000.00 TRY partial payment is split, and a 125,000.00 TRY bulk payment is allocated across invoices.
Bank entries
Logo's bank module records bank accounts and bank vouchers. iFinances compares these vouchers against the real statement you download from the bank. A transfer that never reached the ledger, a duplicated bank entry or an unidentified transfer shows up here.
Account master list
Names and tax numbers (VKN) from Logo's account cards are uploaded as a bulk company list. A shortened name in a bank narrative, such as POYRAZ METAL SAN TIC, is compared against this list. The comparison ignores Turkish character differences and proposes a match. You confirm it.
How do you get the file?
On the file route you run the standard report in Logo and save it as Excel or CSV. Then you upload it to iFinances. It takes five steps.
- 1
Filter the account statement report
You open the Cari Hesap Ekstresi (account statement) report under Logo's account reports. You set the date range, for example January 1 to March 31, 2026, and the account. Menu names differ between Tiger and GO. The report name and the filter logic are the same.
- 2
Set the report unit to Ms Excel or Table
You pick Ms Excel or Table in the report units field on the report screen. The field lists Screen, Printer, Ms Excel, MS Access, Ascii File, HTML File, PDF File and Table. Depending on the version, Ms Excel saves CSV or XLS, and Table saves xls, txt or html. iFinances reads both from content, not from the extension.
- 3
Create an Excel file from the account list with F12
You press F12 on the account list screen, or double-click the icon in the top-left corner. In Create Excel File you pick the folder and the columns, then confirm. The option differs by product and version, so verify it once on your installation. If it is missing, take the data through the report unit.
- 4
Upload the file to iFinances
You pick the data type on the upload screen, for example Account Statement, and drop the file. iFinances identifies the format from content, not from the extension. xlsx, legacy xls, CSV and hidden sheets are read as they are. Column names and the debit/credit sign are detected, and any unrecognized field is asked, never guessed.
- 5
Request the counterparty's statement by link
You generate a secure upload link in iFinances for your customer or supplier. The counterparty opens the link and uploads its own statement, with no account to create. Once both sides and the bank are in one table, matching starts.
Logo Tiger / GO → Upload · columns recognised ✓ · 1,284 lines
Connection path
Logo offers several technical routes. In iFinances the file upload and the direct route that fits your product version work together. The choice is made at setup.
The Logo product family exposes four technical access routes. The first is the Logo Objects REST Service installed on your own server. REST is a standard interface through which applications exchange data over a network. The service serves account cards, account vouchers, sales and purchase invoices, bank vouchers, cash-desk and check transactions.
The REST service exists only on Tiger 3, Tiger 3 Enterprise, Tiger Wings and Tiger Wings Enterprise. GO 3, GO Plus, Tiger Plus and Start do not support it. The ClientId and ClientSecret, the access keys the service requires, come through Logo's reseller channel. There is no public developer portal.
The second route is the Logo Objects COM interface, which runs on desktop products including GO 3. The third is the only route common to every product. Logo's MS SQL Server database is read directly with a read-only user, one that can only read. The account, invoice, payment, bank, cash, check and e-invoice status tables live there.
The fourth is file-based transfer through Logo XML templates. Exchange rates and e-invoice status have no separate REST resource. Those two are readable only in the database.
On the iFinances side the Logo connection is ready and both routes are available. On the file route you run the report above and upload it. On the direct route the product version decides the technical path. Tiger releases with REST support use REST, and every Logo product can use read-only database access.
Credentials such as the database user or the ClientId come from your own installation and reseller. The route is chosen together at setup. Whichever route you choose, the file upload stays in use. The counterparty statement and the bank statement always arrive from outside Logo. iFinances only reads, writes nothing back to Logo and never clears a line on its own.
Things to watch
Debit and credit columns
Logo's account statement gives debit and credit in separate columns. Some report designs show the balance in one signed column instead. iFinances detects the sign convention from content and asks when it cannot be sure. Check which column is debit before you upload, because a sign read the wrong way flips every match.
The Excel unit's output format depends on the version
The Ms Excel unit saves CSV on one version and XLS on another. iFinances identifies the format from content, not from the extension. For CSV it detects utf-8 and cp1254, the Turkish Windows encoding, and the delimiter automatically. If Turkish characters still look broken, re-export from the Table unit as xls.
Report designs change the columns
Report design in Logo is open to users, so columns can be added or removed. A column deleted from a design may still appear in the Excel export. Statements pulled by two users with two designs do not carry the same headers. Export from one standard design and you stop remapping columns every month.
Foreign-currency accounts
For foreign-currency accounts Logo stores the TRY equivalent and the transaction currency separately. Exporting your statement and the counterparty's in the same currency lowers the exception count. iFinances matches across currencies at the official TCMB (Central Bank of Türkiye) rate. The FX difference is shown separately. As an example, a 10,000.00 EUR invoice paid with 412,500.00 TRY is compared at the official rate.
Product and version differences
The Tiger and GO families share one database structure. Menu names, report lists and REST support differ by product and version. A menu path found in Tiger 3 may not be in the same place in GO 3. Verify the export steps once on your own version and write them down.
Frequently asked questions
Yes. The connection is ready and both routes can be used. The local team exports Logo's standard report as Excel or CSV and uploads it. Or Logo is read directly. That means REST where the version supports it, or read-only database access on every Logo product. The route is chosen together at setup.
Yes. The file route works the same on every Logo product, including GO 3. The group system is not involved. iFinances works on the Logo export, the counterparty's statement and the bank statement. The one difference concerns direct connection. GO 3 does not support the REST service, so it uses read-only database access.
Logo produces the statement, debt tracking and aging from its own ledger. Reconciliation compares that ledger with the counterparty's ledger, the bank and the e-invoice records. Those three sources live outside Logo. iFinances performs the comparison, attaches a written reason to each match and produces the reconciliation letter. The number reported to the region carries its evidence. Logo stays.
Every match carries a written reason and every open difference sits on an exception list. Reconciliation letters are kept with their signed copies. Counterparty statements arrive through a secure upload link, so the confirmation comes from the counterparty itself. The auditor follows that trail without the local team rebuilding it from e-mail. iFinances certifies nothing itself.
xlsx, xlsm, xlsb, legacy xls, CSV and HTML tables saved with an xls extension. Hidden sheets are read, and encoding and delimiter are detected automatically. iFinances identifies the format from content, not from the extension. It asks about any column it cannot recognize.
Yes. The team can upload weekly or daily exports. The engine matches incoming data and updates the exception list. At month end the region sees only the unresolved lines, not the whole month.
Other integrations
Same engine, different source. If your system is not listed, the file route still works.
Related content
- How to export a customer or vendor statement from SAP, Logo, Mikro and Netsis
- Can accounting software do reconciliation?
- The balance matches, the lines don't
- Credit balances in receivables, debit balances in payables
- Reconciliation types: statements, bank, e-invoice
- Supplier statement reconciliation
- All integrations
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