How do you actually reconcile accounts in Paraşüt? If your business runs its invoicing, collections, and customer accounts on Paraşüt — one of the best-known cloud pre-accounting platforms in Türkiye — the question comes up every month-end and certainly at year-end. (In Türkiye, "pre-accounting" — ön muhasebe — means the day-to-day commercial records such as invoices, receivables, payables, and cash that sit in front of statutory bookkeeping.) The first half of the answer is simple: Paraşüt's official user guides define clear steps for sending account statements and matching bank statements. The second half is what most guides skip: where those steps end, and which part of the work still lands on you.
This article does two jobs. First, it walks through Paraşüt's reconciliation workflows step by step — statement sending, bank reconciliation, and the Kolaymutabakat integration for bulk sending — sourced from the official guides. Then it draws an honest line: sending a statement is not the same as reconciling line by line. We also cover what happens when the balances differ, and how to automate that part of the work.
One thing up front: this is not a "Paraşüt versus something else" piece. Paraşüt describes itself as a web-based pre-accounting program and it does that job well. iFinances is not a pre-accounting competitor; it is a reconciliation and financial-intelligence layer that sits on top of whatever software you already use. The two work together, not instead of each other.
Customer account reconciliation in Paraşüt: the official workflow
According to Paraşüt's official guide, account reconciliation is built around sharing the account statement with your counterparty. In outline:
- 1. Create the statement. The account statement for the customer or supplier is prepared for the date range you choose.
- 2. Send it. The statement goes out by email, either as a PDF attachment or via a "Customer Screen" link.
- 3. Wait for the response. The counterparty checks the balance against their own records; they confirm if they agree, or reply if they don't. The process the guide describes is a manual reconciliation that proceeds through back-and-forth comments.
There is no automatic matching step in this flow; the guide page does not describe such a function. What you send is a dump of the movements in your own ledger. How the counterparty compares that dump with their records — the real labor of reconciliation — stays outside the process. Reading a statement correctly is a skill of its own, too: debit and credit run in mirror image on the two sides, so your receivable is their payable. Our guide on what an account statement is and how to read it covers that foundation.
Bank reconciliation in Paraşüt: upload, map, approve one by one
On the banking side, the official guide describes this flow:
- 1. Upload the statement. The Excel statement downloaded from online banking is loaded into the system.
- 2. Map the columns. Four columns — transaction date, description, amount, and balance — are defined by hand.
- 3. Approve the suggestions. The system suggests similar records; each transaction is closed one at a time with "Match" and "Approve" actions.
The guide page does not describe automatic bank feeds or bulk auto-matching. For a business with a low monthly transaction count, this flow works perfectly well. As volume grows, the math changes: you have to run a separate suggest-check-approve loop for every row, and the effort scales linearly with the number of rows. That is not a Paraşüt-specific gap — the same arithmetic applies to any tool that ties statement matching to manual approval.
Bulk sending and BA/BS: the job moves to Kolaymutabakat
When you want to send reconciliations to hundreds of counterparties at once, the official answer sits outside the product. Per the guide, Paraşüt users are directed to the third-party Kolaymutabakat.com integration for current-account, BA/BS (a monthly purchase/sales cross-reporting format whose filing requirement was abolished in September 2024), and cross-border reconciliations, with a 25% discount exclusive to Paraşüt customers. In other words, bulk reconciliation sending is an integrated external service, not a built-in feature.
One currency note belongs here: the Ba-Bs filing requirement itself was abolished by General Communiqué No. 565 on the Tax Procedure Law (Official Gazette dated 25.09.2024, no. 32673), starting with the September 2024 period — BA/BS is no longer a return filed with the tax administration. BA/BS reconciliation nevertheless remains an option in vendors' product menus. We covered what took the cross-check's place in Türkiye abolished the Ba-Bs forms: what replaces cross-checking.
Two observations complete the picture. First, "reconciliation" does not appear as a feature on Paraşüt's pricing page. Second, this is a positioning choice rather than an oversight: Paraşüt was acquired in 2019 by DST Teknoloji — the group that includes Mikro Yazılım and Zirve Yazılım — and the announcement highlighted that it had moved the pre-accounting of more than 11,000 SMEs to the cloud in five years. The product's center of gravity is pre-accounting; reconciliation is a side need solved through ecosystem partners. That is a category observation, not a criticism — we mapped the same pattern across all product groups in can your accounting software do reconciliation?
The distance between "one-click reconciliation" and the real process
Paraşüt's current-account product page promises reconciliation "in one click"; the mechanism the page describes is emailing the account statement. That distance is not unique to Paraşüt. Most tools sold as "reconciliation software" in Türkiye are, in practice, balance-notification and confirmation-collection tools; we unpacked the two categories in does it send letters, or does it actually match?
Why does this matter so much? Because reconciliation is two different jobs sharing one name. The first job is notification: "our ledger says your balance is X — do we agree?" The second job is verification: comparing both sides' records line by line to find out whether X is right, and if not, why. Sending a statement solves the first job. If the counterparty says "agreed," the process ends there — but if they say "our balance is different," the second job begins, and the tools for that job do not live inside a pre-accounting program.
When the balances differ: the work that stays manual
The scenario is familiar: you sent the statement, and the counterparty reported a different balance. The difference is a single number, but there may be hundreds of rows behind it. In our experience, most differences come from a handful of recognizable patterns: an invoice the other side never booked or booked late, duplicate entries, period shifts, one-sided returns or discounts, FX asymmetries, and partial payments applied to the wrong invoice. We examined all of these in the balances don't match: 9 causes of reconciliation differences.
Partial payments are the thorniest part: which invoice a given transfer closed, and for how much, is harder than it looks — and when the two sides close items under different assumptions, the line level can disagree even while the balances match. Why payment-invoice matching is hard digs into FIFO and partial-payment scenarios in depth.
At this point the most common reflex is to fall back to Excel: two statements side by side, VLOOKUP, manual highlighting. With few counterparties and low row volume, that method works. Once foreign-currency items, partial payments, and high transaction volume enter the picture, it turns into an hours-long process where things slip through.
Paraşüt + iFinances: keep your software, add a layer
The gap we have described so far — the line-by-line analysis that starts after the sending — is exactly the job iFinances solves. And you don't need to give up Paraşüt to get it. The flow works like this:
- 1. Export. Download your account statement from Paraşüt as Excel/CSV, along with bank statements and e-invoice lists if you have them.
- 2. Upload. Load the files into iFinances; the counterparty's statement comes in just as easily.
- 3. Let the engine match. The matching engine pairs rows automatically: it recognizes FIFO and partial-payment scenarios, works with official TCMB (Central Bank of the Republic of Türkiye) exchange rates on foreign-currency items, and produces an explainable reason for every match — you can see which row matched which, and why.
- 4. Read the difference report. Unmatched items are listed one by one; anomalies such as missing invoices, duplicate entries, and amount mismatches are flagged. The difference is no longer a single number but an addressable list of rows.
- 5. Generate and archive the letter. The reconciliation letter is produced from the system, and signed copies are kept in the archive.
This design is a deliberate choice: iFinances keeps no ledgers, issues no invoices, and files no returns. Your pre-accounting stays in Paraşüt — or whichever program you use — while iFinances runs on top as the reconciliation and verification layer. Not "replace your software," but "add a layer on top of it."
If you'd like to download an account statement from Paraşüt and see how the process runs on your own data, get in touch — we can set up the flow together in a short demo. If you're wondering what iFinances is and isn't, what is iFinances? is a good starting point, and for the full picture of the concept, what is reconciliation? the complete guide is always open.
Frequently Asked Questions
Does Paraşüt have a reconciliation feature?
According to Paraşüt's official guide, account reconciliation is handled by emailing the account statement as a PDF attachment or via a Customer Screen link, and reconciliation is not listed as a feature on the pricing page. For bulk current-account and BA/BS reconciliation, users are directed to the third-party Kolaymutabakat integration. Line-level automatic matching and difference analysis require a separate reconciliation layer.
How do you do bank reconciliation in Paraşüt?
You upload the Excel statement downloaded from online banking, then manually map four columns: transaction date, description, amount, and balance. The system suggests similar records, and each transaction is closed one by one with Match and Approve steps. That is the process the official guide describes; it does not mention automatic bank feeds or bulk auto-matching.
Can Paraşüt and iFinances be used together?
Yes. iFinances is not a pre-accounting program; it is a reconciliation layer that sits on top of the software you already use. You export your account statements and bank records from Paraşüt as Excel/CSV and upload them to iFinances, where automatic matching, the difference report, and the reconciliation letter are produced. Your Paraşüt setup stays exactly as it is.
Can you send bulk reconciliations from Paraşüt?
Per the official guide, Paraşüt users are directed to the third-party Kolaymutabakat.com integration for bulk current-account, BA/BS, and cross-border reconciliations, with a 25% discount exclusive to Paraşüt customers. That service solves letter sending and response collection; when a balance comes back different, the line-by-line analysis is still a separate job. Note: the Ba-Bs filing requirement itself was abolished by General Communiqué No. 565 starting with the September 2024 period; BA/BS reconciliation nevertheless remains an option in vendor product menus.
