Reconciling your Paraşüt account statement: invoices, payments and bank in one table
Upload Paraşüt's standard Excel exports. iFinances matches every line against bank, e-invoice and counterparty data and writes a reason for each open item.
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
You reconcile your Paraşüt account statement against counterparty statements, bank statements and e-invoice (e-Fatura) records in iFinances. This page shows a CFO or controller which Paraşüt files to export and how each line is matched. The gain is clear. At period end you see which invoice is still open and which transfer settled what, with a reason.
Paraşüt is a cloud pre-accounting application. Sales and expense invoices, cash and bank accounts and e-document submission are managed in one screen. Small and mid-sized Turkish businesses and e-commerce sellers use it widely. The difficulty comes from that simplicity.
Paraşüt has no journal entries and no chart of accounts. Payments are not a standalone list, they sit under the invoice. The customer statement is produced as a PDF for sending to the counterparty. At period end the counterparty's statement, the bank's statement and the Paraşüt records live in three separate places.
iFinances puts those three sources in one table. It matches invoices to payments using FIFO (oldest invoice first) or invoice-specific clearing. It splits partial payments and allocates lump-sum payments. Foreign-currency items are compared at the TCMB (Central Bank of Türkiye) rate. Every proposal carries a written reason, approval stays with you, and iFinances writes nothing back to Paraşüt.
What data comes from this system?
The lists Paraşüt exports to Excel map directly onto iFinances upload templates. Column sets vary by Paraşüt version, and the reader asks you about any field it does not recognize.
Customer and supplier list
Customer and supplier cards export from Paraşüt with name and tax number. In iFinances they load as the bulk company list. The tax number (VKN) is the key that binds counterparty statements and bank movements to the right company. A bank line reading 'POYRAZ METAL SAN' is proposed for the card 'Poyraz Metal Sanayi A.Ş.' automatically.
Sales invoices
The sales invoice list exports with invoice number, date, customer and amount. In iFinances it loads as the outbound invoice list. Each line is compared with the purchase side of the customer's statement and with e-invoice data. Example: invoice FT-2026-0412 for TRY 48,250.00 should appear as a credit of TRY 48,250.00 on the customer's statement.
Expense and purchase invoices
The expense list exports with supplier, date and amount. It loads as the inbound invoice list and is matched against the sales invoices on the supplier's statement. An invoice found at the supplier but never entered in Paraşüt is flagged as a missing-invoice anomaly. An anomaly, meaning a record that breaks the expected pattern, is listed with its reason.
Collections and payments
Paraşüt keeps no standalone payment list. Each collection or payment appears in an account's transaction history and on the invoice it settles. You export the transaction history for a date range and load it with the payments template. Example: a transfer of TRY 60,000.00 dated March 12, 2026 is split automatically across invoices FT-2026-0398 and FT-2026-0412.
Cash and bank account movements
Paraşüt supports cash and bank accounts in lira, US dollars, euros and pounds sterling. Each account's movements export as a separate file. That file is Paraşüt's view of the bank, not the bank's own statement. A TRY 1,250.00 bank fee never entered in Paraşüt surfaces as an unexplained difference.
e-Document submission status (in the API)
Paraşüt submits sales invoices as e-invoice or e-archive documents and records the submission status. That status is readable only through Paraşüt's API, the interface programs use to exchange data. iFinances' e-invoice reconciliation does not depend on that field. The e-invoice data from your integrator is placed next to the Paraşüt invoice list. An invoice found on one side only becomes an open item.
How do you get the file?
On the file route, you take Paraşüt's standard export and upload it to iFinances. Column names and debit-credit sign conventions are recognized automatically. On the direct route the same records are read through the Paraşüt API, and these steps fall away.
- 1
Export sales and expense invoices to Excel
In Paraşüt, open the invoice list under Sales (SATIŞLAR). Use the import/export button at the bottom of the page (İÇE/DIŞA AKTAR), then choose export and download. Repeat for the expense records under Expenses (GİDERLER). Pick a wide date range, because unpaid invoices from earlier periods form the opening balance.
- 2
Export cash and bank transaction history
On each cash or bank account page, filter the transaction history by date range. Use the export button to download it as Excel. If you run several accounts, export each as its own file. The cash-bank report under Reports gives totals only, and line-level reconciliation needs the account's own transaction history.
- 3
Export the customer and supplier list
Export the customer and supplier lists through the same button. Upload this file once and refresh it only when new companies are added. Check that the tax-number column is populated, because company matching relies on it.
- 4
Add the counterparty's and the bank's statements
Obtain the account statement the counterparty sends you as Excel or CSV. The statement download button in Paraşüt produces a PDF, and that document is for sending to the counterparty. You can also send the counterparty a secure link, and they upload their statement themselves with no account. Upload the statement from your online banking with the bank template, legacy .xls formats are recognized as well.
- 5
Upload to iFinances and answer what it asks
Drag and drop the files into iFinances. The reader identifies the format from content and maps column names and the debit-credit sign automatically. It does not guess an unrecognized field, it asks you. When the upload completes, matched, partially matched and open lines are listed with their reasons.
Paraşüt → Upload · columns recognised ✓ · 1,284 lines
Connection path
First the technical path Paraşüt offers, then the two connection routes iFinances supports.
Paraşüt exposes a REST API (v4). A REST API is the standard interface programs use to read each other's data over the internet. The data format follows the JSON:API 1.0 standard, and the official specification is published openly as OpenAPI/Swagger 2.0. Authentication is OAuth2, access tokens expire after two hours and are renewed with a refresh token.
Actual access requires an active Paraşüt subscription. Client credentials are requested by e-mail from the Paraşüt support team, there is no self-service developer portal. The API returns customer and supplier cards, sales and purchase invoices, invoice-linked payments, cash-bank movements and e-document status. No resource exists for cheques and promissory notes. Journal entries and a chart of accounts are outside the product's scope.
There is no single endpoint that returns an account statement. The statement is derived by combining the invoice and payment endpoints. Direct database access is not offered.
iFinances supports both routes into Paraşüt, and both are ready. On the file route you upload the Excel exports described above. On the direct route, data is read through the Paraşüt REST API in a read-only flow you authorize. The subscription and client credentials come from your own Paraşüt account. The route is chosen together during setup.
Things to watch
The customer statement downloads as PDF
The statement download button in Paraşüt produces a PDF intended for the counterparty. Line-level reconciliation uses the invoice lists and the cash-bank transaction history exported as Excel. iFinances builds the account statement from those files itself, so do not upload the PDF. If the local team forwards you the PDF, ask for the exports instead.
Payments are not a standalone list
Collections and payments live under the invoice and in the cash-bank movements. One movement may settle several invoices, and Paraşüt's invoice-linked view can differ from the FIFO clearing iFinances derives. Example: Paraşüt books TRY 60,000.00 against FT-2026-0412, while iFinances starts from the oldest invoice FT-2026-0398. iFinances shows its own clearing with a reason, and the decision stays with your team.
No journal entries, no chart of accounts
Paraşüt is pre-accounting. There is no trial balance for account 120 (trade receivables) or 320 (trade payables). There is no journal or voucher number. The statutory ledger sits with an external accountant, and any gap between the two arises in the transfer. For a check against the statutory books, obtain the accountant's account statement. Reconcile it against the Paraşüt records as a separate reconciliation.
Exchange rates are embedded in the document
Paraşüt supports lira, dollar, euro and sterling accounts. The rate is stored on the invoice or movement, not in a separate rate table. Confirm at upload which columns hold the foreign-currency amount and the lira equivalent. iFinances matches cross-currency items at the TCMB rate. Any gap against Paraşüt's document rate is reported as an FX difference, not an unexplained one.
Paraşüt's bank reconciliation is not the bank's statement
Paraşüt's bank reconciliation screen (BANKA MUTABAKATLARI) matches an uploaded bank statement against Paraşüt records. For unmatched lines it prompts the user to create new entries. Afterwards the bank movements in Paraşüt resemble the bank statement. They are still a copy edited by the local team. For three-way reconciliation, upload the bank's own statement separately. Movements never entered in Paraşüt only become visible that way.
Local-language files, English review
The exports arrive with Turkish column headings and Turkish number formats such as 48.250,00. The reader recognizes them from content, so nobody renames columns before upload. Matched, partially matched and open lines can be reviewed by a group reviewer who reads no Turkish. A disputed line still needs a local reader with the underlying document.
Frequently asked questions
iFinances adds the independent third check. Paraşüt's statement sends your own view to the counterparty, and its bank reconciliation helps post bank movements. iFinances compares the counterparty's statement, the bank's statement and the Paraşüt records in one table. It writes a reason per match, flags missing invoices and duplicates, and archives the signed reconciliation letter.
iFinances reconciles the Turkish entity's data and pushes nothing into either system. The Paraşüt exports, bank statements and counterparty statements are matched in iFinances. The group sees the results, the exception list and the letters. Posting to the group ERP stays with your local accountant. For intercompany balances, each side uploads its own statement and differences are listed with reasons.
The minimum set is three files. These are the sales invoice list, the expense records list and the cash and bank transaction history. Add the counterparty's statement for counterparty reconciliation and the bank's own statement for bank reconciliation. The customer and supplier list is uploaded once. All are standard Paraşüt exports, no custom report or add-on is required.
Yes, the connection is ready and both routes are available. The local team uploads the standard Excel exports, or iFinances reads the Paraşüt REST API read-only. The direct route needs an active Paraşüt subscription and client credentials from Paraşüt support, from your own account. Both routes use the same matching engine, and the choice is made during setup.
It makes no difference. Whatever software the counterparty runs, they send their account statement as Excel or CSV. They can also upload it through the secure link iFinances generates. The reader identifies the format from content and maps the debit-credit direction and date fields automatically. Ambiguous fields are queried. The counterparty installs nothing and opens no account.
You decide, against the source document, and iFinances corrects no record on its own. Paraşüt is the pre-accounting record and the statutory ledger sits with the accountant. The gap usually comes from entries skipped, duplicated or dated differently during the transfer. Reconcile the accountant's statement against the Paraşüt records separately. Lines found on one side only are listed with reasons.
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