Reconcile your SAP Business One statement against bank and e-invoice data
SAP Business One statements, invoice and payment lists are matched in iFinances against bank and e-invoice (e-Fatura) data. Everything sits in one table with a written reason per match. The connection is ready. File upload or direct connection is chosen together at setup.
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 your SAP Business One statement is reconciled against bank and e-invoice data. It is written for CFOs, accounting managers and internal auditors who need the line behind a balance difference. SAP Business One's Internal Reconciliation only clears debit and credit items inside its own ledger. The counterparty's statement, the bank's movements and the e-invoices cleared by GIB (Turkish Revenue Administration) sit outside SAP.
iFinances compares these three outside sources with your SAP records in one table. It matches invoice FT-2026-0412 (TRY 48,250.00) to the March 12, 2026 transfer and writes the reason. Unmatched lines fall into an exception list and wait for your approval. iFinances keeps no books, writes nothing back to SAP Business One and never closes a line by itself.
What data comes from this system?
Excel exports from SAP Business One's standard reports load directly into iFinances templates.
Customer and vendor statement
Every debit and credit movement for one business partner in the period. The source is the partner's Account Balance window or the General Ledger report run by business partner. It is compared line by line with the counterparty's statement. The items behind any balance difference are found here.
Sales and purchase invoices
A/R Invoice (sales) and A/P Invoice (purchase) records. SAP stores them in the OINV and OPCH tables. Each line carries document number, partner code, posting date, due date and amount. iFinances compares this list with the e-invoice list and flags e-invoices that never reached the ledger.
Credit memos and returns
A/R Credit Memo and A/P Credit Memo records (ORIN and ORPC tables). The counterparty often books a return on another date or for another amount. For example, a TRY 3,600.00 return is dated February 28 in your books and March 5 in theirs. iFinances links the credit memo to its invoice and recomputes the remaining balance.
Incoming and outgoing payments
Incoming Payments (receipts, ORCT) and Outgoing Payments (OVPM) lists. Each record carries the invoices it settled and the payment means (transfer, check, credit card, cash). The list loads into the iFinances payments template and is matched against real movements on your bank statement. A payment cleared in SAP with no bank counterpart surfaces as an exception.
Business partner list
Business Partners master data (OCRD table). It carries partner code, legal name, tax ID (VKN) and currency and loads into the bulk company template. A shortened bank description such as 'POYRAZ MTL SAN' is matched to this list by name similarity. The suggestion waits for your confirmation.
How do you get the file?
On the file route, you export the standard SAP Business One report to Excel and upload it. Columns and the debit/credit sign are recognized from the file content.
- 1
Open the partner statement
In Business Partners > Business Partner Master Data, you find the partner. You click the golden arrow next to Account Balance to open the Account Balance window. For several partners at once, run Financials > Financial Reports > Accounting > General Ledger by Business Partner.
- 2
Show all transactions
You select every movement in the period, not just open items. Items cleared through Internal Reconciliation leave the open-item view but stay on the counterparty's statement. You keep the date range identical to the agreed period, for example 01/01/2026 to 03/31/2026. You select local currency (TRY).
- 3
Export to Excel
You export the report and save it as xlsx. There is no need to rename headers, reformat dates or move the currency column. iFinances recognizes them from the file content.
- 4
Add invoice and payment lists
For the same period, you export the A/R and A/P Invoice, Credit Memo and Incoming/Outgoing Payments lists separately. For aging, you can add Customer Receivables Aging under Financials > Financial Reports > Accounting > Aging. Vendor Liabilities Aging sits in the same place. iFinances takes each file into its invoice, return and payment template.
- 5
Upload to iFinances and verify
You upload each file to its template. If a column is not recognized, iFinances asks instead of guessing. In the upload summary you compare row count, period and totals with the footer of the SAP report. If total debit is TRY 1,284,500.00, both sides must show the same figure.
SAP Business One → Upload · columns recognised ✓ · 1,284 lines
Connection path
SAP Business One can be connected in two ways. Which one is used is chosen together at setup.
The primary route is the Service Layer, SAP's REST-based web interface (OData v4, at /b1s/v2). Other routes are the DI Server (SOAP, an XML web service) and read-only database queries. The database is SAP HANA or MS SQL. There is no ready-made statement endpoint. The statement is derived from journal entry lines (JournalEntryLines) filtered by partner code.
SAP Business One is a closed installation and every company hosts its own server. External access is opened through VPN or your approval, and the integration user needs an SAP user license. Credentials come from your own installation, so file versus direct connection is decided together at setup. Whichever route is chosen, iFinances only reads, writes nothing to SAP Business One and closes no lines.
Things to watch
Three currencies, one correct column
SAP Business One stores movements in local, system and partner currency, and the chosen column changes the balance. A EUR 10,000.00 invoice shows TRY 372,500.00 at the document rate and a different figure at today's rate. Export the statement in local currency and keep the foreign amount as a separate column. iFinances performs cross-currency matching at the TCMB (Central Bank of Türkiye) rate.
Internal reconciliation is not reconciliation
Internal Reconciliation only clears debit and credit items inside SAP's own ledger. It does not prove the counterparty sees the same item. An open-items-only export leaves the counterparty's settled invoices unmatched and creates false differences. Export the whole period.
Debit/credit columns and sign
Reports usually show amounts in separate Debit and Credit columns, sometimes in one signed column. On the vendor (A/P) side the direction is the reverse of the customer (A/R) side. iFinances recognizes the sign convention from the file and asks when it is ambiguous. Still, check in the upload summary that total debit and credit agree with the SAP report footer.
Payments on account and advances
A receipt taken without an invoice reference (payment on account) waits in SAP as a separate item. The counterparty has usually applied it to an invoice already. For example, a TRY 25,000.00 advance has settled invoice FT-2026-0388 on their side. iFinances proposes a FIFO allocation (oldest invoice first), writes the reason, and the decision stays yours.
No Türkiye e-invoice data in standard SAP
Standard SAP Business One has no Türkiye e-invoice (e-Fatura) or e-Arsiv integration. That data sits in the add-on's user-defined fields (prefixed U_) or in the integrator's portal. Export the real GIB-side list from your integrator portal. Upload it to the inbound and outbound invoice templates separately. Do not mix it with the SAP invoice list.
Frequently asked questions
Yes, the connection is ready. You either upload the Excel exports from SAP, or the same records are read directly. Direct reading goes through the Service Layer or a read-only database query. Which route applies is decided together at setup. Credentials come from your own installation. In both cases iFinances only reads and never writes to SAP.
No. Internal Reconciliation clears debit and credit items within your own ledger. The counterparty's books, the bank statement and the e-invoices cleared by GIB are outside that operation. Reconciliation compares your record with those independent outside records. iFinances does exactly that and shows each difference with its reason.
The file route is version-independent. Excel files from 9.3 and 10.0 installations on SAP HANA or MS SQL are read the same way. Column headers may differ between the English and Turkish interface. iFinances recognizes them from content and asks about any field it does not know.
Each SAP Business One company (CompanyDB) produces its own export. In iFinances each company is set up as a separate organization. For intercompany reconciliation, the two companies' mutual statements are matched. Company A's account 120 (trade receivables) meets company B's account 320 (trade payables). Branch information that arrives as a column is kept on the line.
No. Whatever system the counterparty uses, they upload their own statement through the secure link iFinances sends. There is no software to install and no account to create. The reconciliation letter and the signed-copy archive are produced in the same flow.
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