Fidar Accounting is the financial backbone of the ERP: every invoice, goods receipt or payment produces its own balanced journal entry through configurable rules, carrying analytic dimensions such as branch and cost centre. The module is in development, and this page explains its design openly.
On the roadmap · joining this module’s update list is free
This module is in development. What you read on this page is our design and plan for this module, not something you can use today. We publish its schedule and status on the roadmap.
Problem and solution
When accounting software is separate from sales and inventory, accountants re-key every invoice and delivery. Month-end is spent hunting differences, and the P&L arrives weeks late.
An invoice issued by sales is typed into the accounting package again, with a chance of error every time.
In Fidar’s design no module writes journals directly; each sends an “accounting intent” and the posting engine creates a balanced entry using account-determination rules.
Inventory value and COGS are estimated at period end.
Perpetual inventory valuation using FIFO, weighted average or standard cost, updated with every stock movement.
Bank statements are compared with the books in spreadsheets, and cheque status lives in a separate notebook.
Bank reconciliation with suggested matches and full lifecycle management for incoming and outgoing cheques, including Iran’s Sayad system.
After the month is closed, someone posts a back-dated entry and everything moves.
Fiscal period locks: once closed, no module can post into it, and posted entries are corrected only by reversal.
Capabilities
The best time to migrate accounting is the start of a fiscal year or quarter: you enter opening balances from the previous period’s closing trial balance and record new documents in Fidar from day one.
Review your chart of accounts beforehand. Many companies accumulate duplicate or unused accounts over the years; migration is a good moment to simplify.
Define account-determination rules once with your auditor or finance manager: which revenue account each product group posts to and which inventory account each warehouse uses. After that, entries are generated without manual work.
Document chain
Instead of re-keying, accountants review entries generated from operations — and can trace any number back to its source document.
Receivable, revenue and VAT.
COGS and inventory reduction with your valuation method.
Settles the receivable via bank, cash or cheque.
Matches the bank line to the recorded payment.
Integration
Because every Fidar module shares one database, an invoice and its journal entry are saved in a single transaction: both or neither. Differences between sales and the books simply can’t arise.
Reports
Standard statutory and management reports from release day, with Jalali or Gregorian periods.
Access
In accounting, access is more than security — it is internal control. Fidar enforces segregation of duties, amount limits and period locks in the system itself.
Security and user accessLeave your email and be first to try the beta of this module. If you have specific requirements, add them to the message so we can design for them.
Accounting is on Fidar’s roadmap, where we publish its status. Use the “Notify me” form on this page to be first to try the beta.
Accounting software keeps the books; an ERP runs every process on one dataset, with accounting as one of its modules. In Fidar, financial entries are generated automatically from sales, inventory and payroll. More in what is cloud ERP.
Integration with Iran’s Moadian e-invoicing system — issuing and submitting electronic invoices — is part of this module’s localization design.
No. Iranian tax rules change frequently, so every rate and table is configurable data with validity dates, checked against official sources before implementation.
No. Posted financial entries are never deleted or edited; corrections are made by reversal, and every action stays in the immutable audit log.
Yes. Contacts and deals already live on the shared core; when Accounting ships, the same customers and data flow into the books with no migration.
Quotations, orders, tiered discounts and field-sales routes.
Multi-warehouse, lots and serials, cycle counts and putaway.
Purchase requests, RFQs, orders and goods receipt.
Pivots, charts and drag-and-drop dashboards on all your data.
Start with CRM and Contacts; when Accounting ships, the same data goes straight into the books.