Paraşüt in the Zervanor Engine: e-Fatura, e-Arşiv and Reminders

Paraşüt is where the paperwork lands — every sale eventually needs an invoice, an e-Fatura or e-Arşiv, and someone chasing the ones that go unpaid. Most teams do that by hand: copy the order in, cut the invoice, download the PDF, send it, then remember to follow up next week.

Zervanor is the automation engine behind vertical SaaS products, and Paraşüt is modelled in it as a versioned connector pack — the ledger work above becomes workflows a product can run for its users. Here is what the engine covers.

What the Paraşüt connector does

The Paraşüt connector covers the real accounting surface — verified against Paraşüt’s official JSON:API v4 over OAuth2, 34 actions and polling triggers:

• Invoicing: Create Sales Invoice, Pay Sales Invoice, Cancel Sales Invoice, Convert Estimate to Invoice, Get Sales Invoice.
• e-Documents: Create e-Fatura, Get e-Fatura PDF, Create e-Arşiv, Get e-Arşiv PDF, Create e-SMM — the compliant Turkish document set, end to end.
• Contacts, products & purchases: Create Contact, List Contacts, Create Product, List Purchase Bills, Create Purchase Bill, Pay Purchase Bill.
• The trigger that starts a flow: Sales Invoice Created — polled, so a new invoice can kick off the rest of a workflow.

It’s agent-ready, so an AI agent can read an order, decide which document to cut, and act — not just shuttle data.

4 accounting automations worth building

1. Marketplace order → e-Fatura → customer SMS. When an order lands on Trendyol, Hepsiburada, N11 or Çiçeksepeti, normalize it, cut the matching e-Fatura in Paraşüt, and text the customer the invoice link — zero manual steps. This is the flow Turkish sellers ask for most.

2. Overdue invoice → reminder, automatically. Poll for invoices past due and send a polite SMS or email reminder before they age further — the collections chase your accountant does by hand, on a schedule.

3. Payment received → e-Arşiv/e-Fatura, cut instantly. When a payment lands (Papara, a POS, a bank event), issue the compliant document and file it — no end-of-day backlog.

4. Return → return invoice. When a return comes in, cut the matching return invoice and notify the customer — closing the loop accounting usually chases manually.

What the engine already runs

Each of these is modelled against the live connector catalog, trigger and steps included:

• Trendyol Order → Paraşüt e-Fatura → Netgsm SMS — the flagship order-to-invoice-to-SMS flow.
• Hepsiburada Order → Paraşüt e-Fatura → Netgsm SMS — the same play for Hepsiburada sellers.
• Paraşüt Overdue Invoice → Netgsm SMS Reminder — automation #2 above, modelled end to end.
• Papara Payment → Paraşüt e-Fatura → Netgsm SMS — payment-triggered invoicing.

Selling on İdeaSoft, N11 or Çiçeksepeti? Those Paraşüt chains are live templates too. On a different SMS provider? Verimor and Turkcell e-Şirket are ready alternatives — or just describe your flow in plain language and Zervanor assembles it against your real connectors, showing every step before it runs.

Why finance teams pick Zervanor

The whole chain runs as a single workflow execution, and the agents that handle the reading, judging and drafting run in the same runtime as the workflow itself.

See the full Paraşüt connector reference for all 34 actions, or start with the flagship template above.

FAQ

Does it issue real e-Fatura / e-Arşiv? Yes — Create e-Fatura, Create e-Arşiv and Create e-SMM are real actions against Paraşüt’s official API, with PDF retrieval. No scraping, no unofficial access.

Do I need to write code? No. Deploy a template or describe the flow in chat. Any step is editable in the visual builder if you want to open it.

How does Zervanor connect to Paraşüt? Through Paraşüt’s official JSON:API over OAuth2, with credentials you connect once.