Upload your DİA account statement, reconcile against bank and e-invoice data
DİA's standard Excel exports load straight into iFinances. Both file upload and a direct connection through DİA's web service API are ready. We choose the route together during 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
Upload your DİA account statement and reconcile it against counterparty, bank and e-invoice (e-Fatura) records. Accounting managers and CPAs on DİA stop comparing lines by hand and get a written reason per difference.
The counterparty's statement, the bank's transaction file and the tax authority's (GİB) e-invoice records all sit outside DİA. iFinances brings them into one table next to your DİA statement and matches the lines. For example, a TRY 48,250.00 transfer is matched to invoice FT-2026-0412 with a written reason, awaiting your approval. iFinances writes nothing back to DİA and keeps no books, so corrections are still made in DİA.
What data comes from DİA?
Standard lists and reports from DİA's receivables, invoice, bank and cash screens map directly onto iFinances templates. A template is the column layout iFinances expects for each data type.
Customer and vendor account statement
DİA's Account Statement report (report code scf1110a) lists debit, credit and running balance movements for one counterparty. It is run with a date range and an opening-balance option. In iFinances this file is your side, meaning account 120 (receivables) or 320 (payables) in DİA. It is compared line by line with the counterparty's statement, and unexplained differences land on the exception list.
Sales invoice list
The Invoice List screen (scf2220) holds the invoices you issued. In DİA purchase and sales invoices share one list and are separated by a type field. iFinances loads this list into the outbound invoice template and matches it against receipts. If invoice FT-2026-0412 for TRY 48,250.00 is missing from the counterparty's statement, it is flagged as missing.
Purchase (inbound) invoice list
These are the supplier invoices you filter by type on the same Invoice List screen. They load into the inbound invoice template and match against the supplier's statement and your payments. Compared with the tax authority's e-invoice list, invoices never entered into DİA become visible. An e-invoice that arrived but was never posted to account 320, for example, appears on the exception list.
Receipts and payments
Receipt and payment slips, cash transactions and card collections sit on separate DİA screens. You upload them as lists into the payments template. iFinances allocates each payment to invoices by FIFO, meaning oldest invoice first, or by invoice reference. A TRY 100,000.00 bulk transfer is split across three invoices, and a partial payment keeps its open remainder.
Bank account movements
Account movements and bank vouchers from DİA's bank module (bcs) are your bank entries as recorded in DİA. The real statement downloaded from your online banking is placed next to them. That reveals transactions never entered, entered twice or entered with a different amount. TRY 12,500.00 at the bank but TRY 12,050.00 in DİA is flagged as an amount difference.
Counterparty master list
Account codes, legal names and tax numbers (VKN) load into the bulk company template. iFinances compares these names with the free-text descriptions on bank lines. The comparison folds Turkish characters, so "YILDIZ" and "Yildiz" count as the same name. Deciding which transfer belongs to which account remains your decision.
How do you get the file?
On the file route you export the report or list from DİA to Excel and upload it. The reader recognizes format and columns from content. On the direct route the same lists are read through the web service, without these steps.
- 1
Run the Account Statement report
You run the Account Statement report (scf1110a) in DİA with the period's start and end dates. Keep the opening-balance option on so the period-start carry-forward is in the file. Save the result as Excel. iFinances recognizes this file as your side of the statement.
- 2
Split the invoice list by type
You apply the period date filter on the Invoice List screen (scf2220). Filter sales and purchase invoices separately by type and export each as its own Excel file. iFinances expects outbound and inbound invoices in separate templates, so this split keeps the upload simple.
- 3
Export bank movements and payment vouchers
You export the bank module's movement list and the receivables module's receipt and payment vouchers. Also download the bank's own statement from your online banking. iFinances recognizes that statement through a bank-specific template.
- 4
Upload to iFinances and confirm the mapping
You drop each file into its template slot, the upload area reserved for that data type. iFinances identifies xlsx, legacy xls, CSV and hidden sheets from content. It maps column names and the debit/credit sign convention automatically. Anything it cannot recognize is asked, never guessed, and matching starts once you confirm.
DİA → Upload · columns recognised ✓ · 1,284 lines
Connection path
DİA is cloud-hosted, so there is no direct database access. Its only outward technical path is the web service API, the interface that hands data to other programs.
DİA offers a REST web service API (v3), meaning an interface that returns data over standard HTTPS calls. The receivables, invoice, bank, ledger and e-document modules each expose list services. Standard reports can also be retrieved through the API as Excel, PDF or JSON. There is no SOAP interface and no direct database connection.
Access has two parts, an API key issued by DİA on application and your own DİA login. The login means the username, password, company code and period code of your own DİA installation. That user needs web-service permission, and DİA meters every call on a credit basis. Both routes are ready, the choice is made together during setup, and iFinances never writes to DİA.
Things to watch
No opening balance, no matching period start
The Account Statement report adds the opening balance through a separate option. Run without it, the file starts with in-period movements only. A January 1 carry-forward of TRY 35,000.00 is then missing and the balances disagree by that amount. Always run the report with the opening balance.
Purchase and sales invoices share a list
DİA keeps purchase and sales invoices on one Invoice List screen, separated by a type field. An unfiltered export mixes both directions. iFinances asks about an unrecognized direction, but two type-filtered files is the cleanest route.
List screens and reports do not return the same columns
DİA's list screens return the columns shown on that screen. A report's output depends on the chosen report design. Pull from a list one month and a report the next, and the column layout changes. iFinances recognizes columns from content, but using the same source every period speeds up mapping approval.
Which rate on foreign-currency accounts?
DİA is multi-currency and its rate table holds several rate columns. The file does not always show which rate produced the local-currency amount on a line. iFinances converts such lines at the TCMB (Central Bank of Türkiye) official rate and shows the difference separately. A EUR 10,000.00 invoice valued at two rates can differ by TRY 4,100.00, shown as a rate difference.
Company and period boundaries
Every DİA report is pulled for one company and one fiscal period. At year end the old period's closing carry-forward and the new period's opening line can share one file. The same movement then appears twice, so take only one side at the boundary. iFinances flags the duplicate but leaves the decision to you.
Frequently asked questions
Yes. The DİA connection is ready and both routes are available. You upload the Excel or CSV files exported from DİA. Or iFinances reads the data directly through DİA's web service API. The direct route needs an API key from DİA, a web-service-enabled user and the company and period codes. The route is chosen together during setup.
No. Whatever system the counterparty uses, it uploads its own statement through the iFinances secure link. No account or software is needed. You upload your DİA statement and both sides meet in the same table.
Yes. You can upload the e-invoice and e-archive lists from DİA's e-document module. The list downloaded from the tax authority portal works too. iFinances compares that list with the DİA invoice list. It flags e-invoices never entered into DİA, and DİA entries that have no e-invoice.
No. iFinances keeps no books, creates no entries and never closes a line on its own. It produces match proposals with written reasons. Corrections, vouchers and clearing in DİA are done in DİA, by you.
The safest route is one file per counterparty. When the file carries an account code or name column, the lines can be split by counterparty. Whether DİA's bulk-statement output includes that column depends on the report design. For large volumes we try it together during the call. Counterparty statements arrive one account at a time.
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