Ledger, bank statement and e-invoice compared on one table. A written reason next to every match. Eight types of reconciliation, one method.
Lines, not totals: three sources recorded one event; the engine folded the name difference.
iFinances proposes, you approve; a match you have not approved never becomes final.
Illustrative screen · sample data
Reconciliation is checking, line by line, whether two sources recorded the same transaction the same way. Invoice FT-2026-0412 for TRY 48,250.00 in account 120 (trade receivables) must match the customer's statement. iFinances matches your ledger, bank statement and e-invoice (e-Fatura) list on one table, line by line. Finance teams get a short exception list with a written reason on every open item.
The hard part is that the two sources write the same transaction differently. A customer sends TRY 125,000.00 in one transfer that your ledger splits across three invoices. A dollar invoice is booked at another rate, a return is a credit note on one side only. A spreadsheet lookup returns blank on all of these, and the work piles up at month end.
iFinances puts ledger entries, bank statement and e-invoice list on one table and matches them line by line. Each proposal carries a written reason, such as "FT-2026-0412 settled by TRY 48,250.00 transfer, March 14, 2026". Accepting, rejecting or correcting the proposal is your decision. iFinances does not keep books, does not create entries and never closes a line on its own.
One comparison is not enough. iFinances tests the same line across four sources and six dimensions, then puts the result in front of you with its reasoning.
Open items, due dates and who is waiting on what sit in one list. You see it without waiting for month-end.
Invoice, payment, bank and ledger are compared for the same line. The difference two sources cannot see surfaces here.
The reasoning behind every decision, and who approved it and when, is kept. The audit file accumulates on its own through the month.
The owner, the finance director and the auditor look at the same data. Each of them is answering a different question.
“Where is my money, and who has not paid?”
Sees which invoices are still open and which collections actually landed, without waiting for month-end. An overdue balance is noticed the day it happens, not weeks later.
“How many days will the close take?”
Because reconciliation is spread across the month, nothing piles up at month-end. Invoice, payment, bank and ledger are verified from four sides; the team spends its time on decisions, not on investigation.
“Who made this decision, and why?”
The reason behind every match is written on the day the decision is made. Who approved it, when they approved it and where the signed letter sits are visible on one screen.
Eight types, one engine. Where you start depends on where your data lives. All of them compare the same three sources from a different angle.
Whichever type you choose, iFinances applies the same three rules.
Ledger, bank and e-invoice are compared on the same table, not in separate screens. A receipt that agrees between bank and ledger but has no e-invoice is an exception. A two-source reconciliation cannot see it.
A balance confirmation looks at one number. An invoice overstated by TRY 10,000.00 and a TRY 10,000.00 receipt booked twice cancel out in the balance. Every invoice, every payment and every bank movement is matched individually. An agreeing balance is a result, not evidence.
The engine presents each proposed match with a written reason. Accepting, rejecting or correcting it is your decision. iFinances never closes a line on its own and never posts to your ledger. The reason is written that day and stays as it was for the auditor.
iFinances compares the invoice, the payment, the bank movement and the ledger entry at the same time. It makes reconciliation continuous, and it verifies and automates your financial processes.
Poyraz Metal · FT-2026-0412 · 48,250.00
Matched across four sources · waiting for your approval
Illustrative screen · sample data
A line is checked against four sources, not two: invoice, payment, bank, ledger. The difference two sources cannot see becomes visible here.
It does not wait for period end. Data is matched the day it arrives, and the difference reaches you that same day.
Every match carries its reason in writing. No black box: no line becomes final until you approve it.
Invoice-to-payment matching, bank collection checks and letter generation run as a flow, not by hand.
iFinances does not keep your books, issue invoices or vouchers, or create entries. The decision to close and the ledger entry stay in your own system.
Internal audit asks for a written reason behind every match. The counterparty wants to confirm the balance. Both jobs are built on the matched lines.
As data arrives, four checks run at once. You do not wait for month end; a difference reaches you the day it appears.
The bank statement is uploaded and transfers are matched to candidate invoices.
Incoming and outgoing e-invoice lists are compared.
The account statement is uploaded and line-by-line matches with the counterparty are proposed.
Only the differences you have already worked remain.
Which payment settles which invoice is identified. Partial and bulk payments are split across line items.
Every movement on the statement is tied to the right counterparty account. Fees, commission and value dates become their own line items.
Duplicate entries, missing documents and unusual amounts are flagged as soon as they break the pattern.
Advances that stay open too long, transfers with no description and entries left on one side only are prioritized.
Illustrative examples · sample data
All four checks produce a list of differences. No line closes by itself; your team makes the call and gives the approval.
Benchmark: in APQC data the monthly close takes ~4.8 days in the top quartile and ~6.4 days at the global median. Source: APQC Open Standards Benchmarking.
Connections are ready for all fourteen systems, including SAP, Logo, Mikro and Netsis. You upload the standard Excel or CSV export, or we connect through REST, SOAP, database or file service. Which route you use is decided together during setup, and both feed the same engine.
All integrationsComparing two sources that recorded the same transaction line by line, then explaining the differences. Sources can be your ledger and a customer statement, bank and account 102, or e-invoices and ledger. An agreeing balance is not enough. You show which lines agree and why the others do not.
No. Most products sold as e-reconciliation send a balance-confirmation letter and collect the reply. They compare two balances, not the lines behind them. iFinances matches the lines first, extracts the open items and generates the letter on top of that result.
At least at month end, preferably as data arrives. A difference takes minutes to investigate on the day it arose and hours under closing pressure. Continuous reconciliation spreads the work across the month, and only the remaining exceptions are worked at month end. In the APQC (American Productivity & Quality Center) benchmark the top quartile closes in 4.8 days.
The accounting and finance team inside the company, the external accountant or auditor outside it. The software prepares the matching and the exception list, the decision stays with a person. The counterparty takes part too. It uploads its own statement through a secure link and needs no account or software.
Yes, more than ever. General Communique No. 565 on the Tax Procedure Law abolished the Ba-Bs forms from the September 2024 period. The tax authority already gets this data from e-invoices. What disappeared is the filing that made two companies compare their books. Seeing that a counterparty booked the same documents now means line-level reconciliation over statements and e-invoice data.
No. iFinances does not keep books, issue documents or create entries. It works alongside the ERP or accounting software you already use. It reads the data you export, matches the three sources and shows the open items with reasoned proposals. The clearing decision and the ledger entry stay in your system.
Live demo. No commitment.