Sepidar, Holoo or Hamkaran System: Which Tier Fits You
If you are choosing accounting software and stuck between the familiar names in the Iranian market, this is for you. Rather than declaring a winner, I will describe where each family sits and give you the criteria that have actually decided these projects for the businesses I have worked with.
Why "which is best" has no answer
I have seen companies abandon software that was perfectly suited to a different business. The problem is rarely product quality; it is a mismatch between operational size and system complexity. A distributor with three warehouses suffocates inside a package designed for a shop, while a small retailer buying a multi-branch system spends months on implementation and ends up using a tenth of it.
The right question is: given my document volume, user count and the reports I genuinely need, which tier of system fits?
Three tiers of the market
Tier one — lightweight packages. Products such as Holoo sit here, aimed at shops, trades and small trading companies. Their strengths are simplicity, fast setup and a low entry cost. After a short training session a user can raise invoices, run inventory and pull a trial balance.
Tier two — small and medium business products. Sepidar System, part of the Hamkaran System group, belongs here. These products are more serious about accounting structure and internal controls, offer specialised modules such as payroll, production and contracting, and have meaningful user permissions and change logs.
Tier three — enterprise and ERP systems. Hamkaran System's enterprise line and its peers target organisations with multiple companies, branches, cost centres, complex costing and supply-chain integration. The difference is not only feature count: implementation method, project duration and the demands on your internal team all change.
No tier is inherently better. Choosing the wrong tier — above or below your needs — is a cost you pay for years.
Comparison by decision dimension
| Dimension | Lightweight (e.g. Holoo) | SME product (e.g. Sepidar) | Enterprise (e.g. Hamkaran System line) |
|---|---|---|---|
| Target business | Shop, trade, small trading firm | SME with a finance team | Large, multi-entity organisation |
| Time to go live | Days | Weeks | Months |
| Depth of chart of accounts | Limited | Four levels with floating analytics | Multi-dimensional |
| Production costing | Weak or absent | Basic to moderate | Full |
| Payroll | Simple | Standard, with statutory filing exports | Full, with job grading |
| Permissions and audit trail | Limited | Adequate | Detailed and auditable |
| User-built reporting | Minimal | Moderate | Strong |
| Internal team needed | Almost none | One power user | Implementation team and key users |
Read this as a map of tiers, not a scorecard for products. Every vendor sells several editions, and what is missing from a base package may exist higher up the range, so always compare at edition level rather than brand level.
The criteria that actually decide it
Current tax compliance
The first filter today is whether the software can issue and submit electronic invoices and track their status, including corrective and cancellation invoices, the unique tax number, and a loadable quarterly transaction report. The requirements are set out in the taxpayer system guide.
Chart of accounts and analytical dimensions
If you later want profit by project, branch or product line and the data structure will not carry it, the only remedy is rebuilding past entries. Run your future reporting scenarios during the demo. Design principles are in designing a chart of accounts.
Data ownership and the exit path
Ask what happens if the relationship ends: in what format and at what level of detail is your data returned? Cheaper packages typically export less, which raises the cost of any future migration. The practical method is in migrating to new accounting software.
Local support
Outside the largest cities this can matter more than the product. An active local partner, a defined response time and on-site training are the difference between a three-week rollout and a six-month one. Call two of that partner's existing customers in your own area before deciding.
Never judge from the vendor's sample data. Load one real month of your own documents and run the whole cycle: invoice, submission, receipt, sales return, month-end close.
Which profile, which tier
| Business profile | Signals | Suggested tier |
|---|---|---|
| Single-location shop | One store, one or two users, no production | Tier one |
| Growing trading company | Several warehouses, sales team, product margin reporting | Tier two |
| Small manufacturer | Costing, raw material and finished goods stores | Tier two |
| Contractor | Contracts, progress billing, guarantees, withholding tax | Tier two with specialist module |
| Multi-entity group | Consolidation, branches, budgeting, many cost centres | Tier three |
If you are not sure the gap is software at all, weigh the process and staffing options before comparing any product.
An eight-step selection checklist
- List the monthly and annual reports you need, and name the consumer of each.
- Estimate current and three-year volumes of documents, users, warehouses and branches.
- Turn your tax and sector obligations into knockout criteria.
- Compare at least three options within the appropriate tier, not one from each tier.
- Demo with real data across a complete operating cycle.
- Get a written three-year cost of ownership from every vendor.
- Put data ownership, full export rights and support response times in the contract.
- Schedule go-live at the start of a fiscal year, or at least a quarter.
Common mistakes
Choosing on licence price, when the licence is often less than half the three-year cost. Buying modules that "might be useful one day", which lengthen implementation and training. Ignoring the quality of existing data, so that a polluted customer list simply moves to a new home. And the most expensive of all: deciding without the person who will use the system daily. Your accountant should be in the demo, hands on the keyboard.
If you would like the requirements analysis and vendor comparison done before you sign, I am glad to help.
Key takeaways
- The question is not which product is best, but which tier matches your size and complexity.
- E-invoicing and statutory reporting capability is a knockout criterion, not a bonus.
- Your chart of accounts and analytical structure determine what you can report three years from now.
- Check the exit path and data ownership before you enter, not when you want to leave.
- Three-year ownership cost and local support quality outweigh licence price.
Frequently asked questions
Which option suits a very small shop?
How does Sepidar differ from Hamkaran System's enterprise products?
Can I move to a bigger system later as I grow?
How should I compare prices?
Have a question? Just ask
One short call is usually enough to know where you stand. If I miss you, I will call back.