Accounting & Receipts

Go to the Paraşüt card under the Accounting category in Settings → Integrations and click Set Up. Then:

• Enter your Paraşüt Firma ID (Company ID) (found in your Paraşüt dashboard URL after /companies/).
• Enter your Paraşüt login email and password.
• Test the connection, then Save to finish.

Your login credentials are stored encrypted. This is your own Paraşüt account; Mindora does not open or manage it, it only triggers the receipts you issue from within the app.

To issue a legal e-SMM through Mindora, your Paraşüt account must have e-SMM (GİB) authorization activated. This generally involves obtaining a digital fiscal seal/signature and completing the e-SMM application through Paraşüt.

This activation happens on the Paraşüt side. Since the exact steps and pricing can change over time, follow Paraşüt's e-SMM activation flow. Until activation is complete, issuing from Mindora produces a sales invoice instead of a legal receipt (see below).

If you issue a receipt before e-SMM activation is complete, Paraşüt creates a Sales Invoice (Satış Faturası) instead of a legal freelancer receipt. A Sales Invoice is not a legal e-SMM.

If you see a Sales Invoice in Paraşüt instead of an e-SMM, your e-SMM activation is not yet complete. To start issuing legal receipts, first finish the e-SMM activation in Paraşüt.

Yes. Your Paraşüt login credentials and your clients' TC Kimlik numbers are encrypted with AES-256-GCM before storage; passwords are never kept in plain text. This ensures KVKK (Turkey's data protection law) compliance.

Your Paraşüt credentials are used only to authenticate with the Paraşüt API, that is, to issue receipts on your behalf. This is your own Paraşüt account; you can always manage the account and its data from the Paraşüt panel as well.

e-SMM can only be issued for sessions with a Paid status. Open the payment detail of the session, scroll to the e-SMM Makbuzu (e-SMM Receipt) section, enter the client's TC Kimlik No (you can check Remember for future receipts), and click Issue e-SMM.

The receipt is created in your own Paraşüt account; you can then view it as a PDF or send it to the client. The TC Kimlik No you enter is stored securely and can be reused for future receipts.

You set the default receipt settings on the Paraşüt integration setup screen, and later update them via Edit Settings (Ayarları Düzenle). Both have a Receipt Defaults (Makbuz Varsayılanları) section with these fields:

• Service Name (Hizmet Adı): the service description shown on the receipt; for example, Psychotherapy Session.
• VAT Rate (KDV Oranı %): typically 0% for healthcare services in Turkey.
• Withholding Rate (Stopaj Oranı %): varies by the payer's situation; usually 0% for individual clients.

These values prefill every receipt by default. The rates can differ based on you and your client's situation; consult your accountant for the correct rates.

You can send the issued receipt via WhatsApp (Web) or email (Gmail), in a Standard or Friendly tone; a message template is ready to use. In the send flow, the relevant app (WhatsApp Web or Gmail) opens first, then a Yes, I sent it / No, I did not confirmation window appears; your answer is logged in the payment history.

For manually uploaded receipts, only those in the Ready status can be sent.

After a receipt is issued, the session's payment information is locked to keep data consistent between Mindora and Paraşüt; you will still see a warning if you try to edit it.

If there is an error in an issued receipt, the correct path is to refund the payment and issue a correction receipt. See the next section for details.

No. You issue the receipt (and, when needed, the correction receipt); Mindora does not issue receipts on its own in the background. This is by design, because a receipt is a legal document and you should control which session it covers and with what details.

The same principle applies to sending: Mindora opens WhatsApp or email with the recipient details and message text prefilled, but you decide to send; no message goes out without your knowledge.

In the future, these steps may become configurable through automation rules; for example, you could choose to have the system issue and send the receipt automatically, or only issue it and leave the sending to you.

Yes. An e-SMM legally requires the recipient's (client's) TC Kimlik number, so it is requested when you issue the receipt.

• Validation: the TC Kimlik number must be exactly 11 digits and pass a validity check; if it's wrong, confirm it with the client.
• Reuse: if you tick Remember on first entry, it auto-fills for the same client's future receipts.

Entered TC Kimlik numbers are stored securely (encrypted with AES-256-GCM).

To issue a correction receipt, the session must be refunded first. Once the payment is refunded (status Refunded or Partially Refunded), an Issue Correction Receipt option appears in the e-SMM section.

When you confirm, the original receipt in Paraşüt is cancelled automatically. Both the original and the correction receipt remain visible in the payment history for auditing purposes.

For in-person (manual) payments, Mindora cannot verify that the money was actually returned, so it does not create an automatic Correction Pending badge. In that case, issue the correction receipt through the GİB portal or your accountant, and optionally upload it to Mindora using the manual upload feature.

Yes. If you issue your receipts through the GİB portal, your accountant, or other software, you can upload them to Mindora; this does not require the Paraşüt integration. In the payment detail of the session, click Upload Receipt and upload the file (PDF, JPG, or PNG). This way, all your receipts stay in one place alongside the relevant session.

An uploaded file first goes to Uploading, then Verifying for a security scan, then Ready. Only receipts in the Ready status can be sent to the client.

You can later update the receipt with Replace Receipt or remove it with Delete Receipt. Note: deleting only removes it from Mindora. A receipt you issued through Paraşüt or the GİB must be cancelled there separately; Mindora does not cancel receipts in external systems.

The Accounting Tracking Screen gives you a bird's-eye view of your receipt workflow; instead of checking each session one by one, you see all pending and issued receipts in one place. It opens from the Accounting toggle on the Payments page (only when Paraşüt is connected). It has two tabs:

• Pending: sessions awaiting a receipt action (SMM Pending and Correction Pending).
• Issued: your full receipt history (receipt number, type, amount, issue date).

Using the Issue Receipt button in the table, you can open the receipt modal directly without going into the session detail.

Even when viewing the regular payments table, you see a badge next to each session showing its accounting status:

• Receipt Pending: the session is paid but no SMM has been issued.
• Correction Pending: the session was refunded and a correction receipt is needed.
• Receipt Complete: all required receipts have been issued.

For unpaid, free, or link-sent sessions, accounting does not apply, so no badge is shown.

Yes. Using Export on the Payments page, you can download your payment records as CSV or Excel; it includes fields such as client, session date, amount, payment status, and channel. You can filter by date or client first, then export to prepare the set of records you will share with your accountant.