Clienta cloud · Hesabfa REST · no Windows agent
Hesabfa cloud accounting integration
Enter the sale once. Let the same document land in Hesabfa.
Clienta is cloud software. Hesabfa is cloud software too. Without a bridge, sales types twice, cannot see a balance, and a CRM invoice is not a finance document. The marketplace connector closes that gap: catalog and parties come from accounting, issued invoices go to Hesabfa, and credit and stock appear on the customer record.
This page explains how the connection works. It is not a substitute for the in-product guide. Setup is done by the Hesabfa business owner and a workspace admin together. Salespeople only see the result on invoices and the finance card. Didar, CRM24 and Vtiger all sell the same bridge because demand outruns the technical friction.
How the model works
This is not full accounting sync. Hesabfa’s API is built for CRM and shops: contacts, items, sales invoices, receipts and stock. The ledger and tax e-invoicing are not in this connector, and Clienta does not claim them. Tax e-invoicing stays inside Hesabfa.
Hesabfa → Clienta
Active items and services sync with code, sell price and stock. Account remainder and credit limits are read onto a person or company. Hesabfa price is the source of truth.
Clienta → Hesabfa
A person or company is linked or created as a Hesabfa contact. Only issued documents are sent. A quote becomes a draft; an invoice becomes confirmed.
Without a connector
Didar announced a free Hesabfa connection, CRM24 sells it as a one-time fee, and Vtiger lists Hesabfa beside Sepidar and Holoo. The pain is the same: sales in CRM, accounting in Hesabfa, nothing in the middle — even though both are already on the internet.
Hesabfa is on the internet. If Clienta repeats Sepidar friction here, it loses to Didar. The connection has to come up in under thirty minutes or it stays “later”.
If matching is a spreadsheet exercise, invoices fail on unknown items. Clienta pulls items from the API so Hesabfa remains the code source of truth.
Individuals and companies have required fields. The connector maps the person or company to a Hesabfa contact before the document.
In Iran a sales invoice has consequences. A serious product has roles: sales raises the quote, finance or an admin posts the official invoice.
Many Hesabfa customers also run WooCommerce. Hesabfa allows only one hook URL. If Clienta silently takes it, the shop sync dies.
What the connector does
Remainder, credit, connection status and send live where the salesperson works — not in a separate IT panel.
If posting would push the remainder past Hesabfa credit, the document is not created. Finance is not told after the fact.
Active items and services enter the workspace catalog. New items are created by finance in Hesabfa and synced again.
Hesabfa has no separate quotation entity. A Clienta quote becomes a draft sales invoice; the official invoice becomes confirmed.
You can allow only the workspace admin to send official invoices, or anyone who can issue an invoice in Clienta.
Changes are read with getChanges so WooCommerce is not displaced. A live hook is only used if you confirm the replacement.
Marketplace
A workspace admin adds Hesabfa from the marketplace. Ordinary members do not get that button. After adding it you are not connected yet — the app is only enabled so you can paste the API key and login token.
Invoices
You build the invoice in Clienta, check synced lines and issue it. After send, the Hesabfa number stays on the document and CRM editing closes.
Deal
Hesabfa has no deal entity. The Clienta board moves selling forward; when the opportunity is won, the invoice is built from those lines and sent if you configured auto-send.
Sales reports
Report drift usually comes from two catalogs and two customers, not from missing charts. The connector unifies that source so the Clienta pipeline and the Hesabfa invoice speak the same lines.
Setup at a glance
A salesperson usually cannot open Hesabfa finance settings. This order is what the in-product guide explains in more detail. If the business is active, it usually takes 15 to 30 minutes.
Sign in as the business owner, open finance settings and the API page, and make sure the API is on. If it is off, Clienta shows “API is disabled”.
Copy both from that page. The login token replaces username and password. Do not enter the owner password in Clienta.
A workspace admin adds Hesabfa from the marketplace. Until the app is added, the connection tab is hidden.
Paste the key and token on the connection tab. If the fiscal year name appears, you are on the right business. An expired subscription shows up here, not as a vague “API is broken”.
Agree currency, warehouse receipt and issuer role with finance, then sync items. Sending invoices now makes sense.
Architecture
The Clienta server POSTs directly to the Hesabfa REST API. That is why setup is simpler than on-premises Sepidar. Keys live only on the backend, encrypted. Live sync uses getChanges polling; the hook is an optional accelerator.
The sync queue, issued invoices and encrypted keys. The business-owner password is never stored.
Every method is POST and JSON. Rate limit 240 requests a minute. A unique id stops a duplicate post within 24 hours.
Fiscal year, Contact, Item, Invoice. Tax e-invoicing and the ledger stay here.
If you are told the change hook is already set for another system, do not tick replace unless you want WooCommerce or that system disconnected. Clienta polling still works without the hook.
Daily work
The Hesabfa card on an issued invoice has the send button. If an item is unmapped, the customer is missing or credit is full, the message is clear. After success, the invoice stays locked in CRM.
Product honesty
Who does what
Turns the API on and creates the key and token in finance settings. Without those the Clienta form errors. They also create new items in Hesabfa.
Adds the app, pastes the keys, sets who may send official invoices and runs the first item sync. Ordinary members do not get those jobs.
After connection, only Clienta. They raise quotes, see balances and issue invoices if the role allows. Hesabfa is not on their desk.
FAQ
Hesabfa has a cloud REST API at api.hesabfa.com. Clienta connects with an API key and login token. Items and balances are read; an issued quote is written as a draft and an issued invoice as confirmed.
No. Hesabfa is on the internet. The Clienta server reaches the Hesabfa API from the cloud. That is the main difference versus on-premises Sepidar.
In Hesabfa, sign in as the business owner and open Settings → Finance settings → API. The apiKey is unique per business and the loginToken replaces a password. Official docs: hesabfa.com/help/api.
Usually one of these: the invoice is still a draft, a line is not mapped to a synced item, the customer is unmapped, credit is full, the API is off, the business expired, or the 240-request limit was hit. The Clienta error names the cause.
No. After send, the official invoice is locked in CRM. Correction and voiding happen in Hesabfa. Deleting in Clienta does not remove the Hesabfa document. That limit is intentional so finance keeps the document.
The Hesabfa API can create items, but this Clienta version does not, so finance keeps codes and stock. The accountant defines the item in Hesabfa and Clienta syncs it.
The Hesabfa change hook is a single URL. Clienta polls by default. Do not tick replace-hook unless you have coordinated with the shop.
It is not stored. Only the API key and login token live on the Clienta server, encrypted. They are not shown again in the browser. To change business, reconnect.
Open the 14-day trial, add Hesabfa from the marketplace and paste the keys with the business owner. The step-by-step guide lives inside the product.