The enterprise tier of NERAX
NERAX Business brings the entities, branches and warehouses of a group onto the double entry core that already runs on nerax.ir, and adds the controls, consolidation and accountability a board asks for.
Group console, consolidated
Sample view Trailing twelve monthsConsolidated revenue
0 million Toman
Entities on one ledger
5
Intercompany eliminated
2,310 M
Entities and balances
Consolidation journal CJ 1042
The group, drawn as the mark
Consolidation journal CJ 1042 Sample
2,310 M
Sample view: the figures in this console are drawn for this page. The layout follows the consolidated reporting the Business tier produces from the same journals as the entity books.
In production today, on the core platform
Business is not a separate product with separate promises. It stands on the core platform that is live today, and every panel below can be opened and checked on nerax.ir.
Sales, purchases, payments and reversals post balanced journals in one transaction. A posted document is reversed, never deleted.
Illustrative journal, drawn for this page.
Customers and suppliers, invoicing with partial payments, and document numbering kept separately for each business.
Illustrative invoice, drawn for this page.
Stock across multiple warehouses, transfers between them, stock cards, and production orders that consume materials and produce finished goods.
Illustrative stock levels, drawn for this page.
An assistant that answers over the business data of that business and proposes actions. Nothing financial is posted without a person confirming it first.
Illustrative exchange, drawn for this page.
Internal messaging and video meetings inside the same system as the books, with a simple mobile panel for daily work.
Sales and profit reporting, and a complete export of the business data in one file whenever the owner asks. Passwords and secrets are never part of an export.
These are built for Business groups in phase two, and they are listed separately on purpose. Nothing in this section is live today, and keeping that distinction visible is part of the offer.
One account for the holding and its entities. Group reports are produced from the same journals as the entity books, with intercompany entries eliminated in the consolidation itself, not adjusted later in a separate file.
Design diagram for the phase two tier.
Granular roles per entity, approval chains for payments and journals above limits the group sets itself, and separation of duties: whoever raises a document cannot be its final approver.
The raiser is blocked from the final step by the system, not by policy.
An exportable history of documents, approvals, access and exports for each entity, kept for the period written into the agreement.
A documented, versioned API and document events for the group systems, with integration work for banking, commerce and logistics scoped into the engagement.
Planned surface, shown as designed for phase two.
Business groups run in their own deployment and database, on the documented PostgreSQL path, with maintenance windows and data residency agreed in writing.
Foreign currency accounts, recorded exchange rates and revaluation, designed in phase two for groups that trade across borders.
Rates are recorded at posting; revaluation runs at period close.
Named contacts on both sides, and response and recovery targets set per client in writing. This page advertises no blanket numbers, because a number that is not in your agreement is not a promise.
Controls are listed one by one, at their true stage. Security here is described by what the system does, not by seals we have not earned.
NERAX holds an issued Enamad electronic trust symbol for the core platform, displayed on nerax.ir. The Business tier claims no certification it has not undergone; where a client audit requires evidence, the governance pack is the evidence.
Stated at true stageThe core product was built bilingual from its first day. Readiness is stated here at its true stage, in the same way as everything else on this page.
Persian, right to left and set in Vazirmatn, and English, left to right, in one product, over one chart of accounts. A group does not keep a second system for its second language.
The Moadian foundation is built: invoice data models, automatic drafts created from a sale, and a settings wizard. Live submission activates for each business after that business completes its own tax portal registration.
Multi currency ledgers and revaluation are designed into the Business tier. Reporting periods and calendars follow the fiscal settings of the group itself.
Migration is run as a project with gates, by named people. A group does not move to the next phase until the current one is signed off.
A working session with your finance lead. The entities, the current systems and the reporting the board needs are mapped, and the scope is written down before anything is priced.
Your current books are audited for structure, opening balances and history. The plan states what moves, what is archived and what stays behind, with dates attached.
NERAX Business runs beside your current system for one full reporting cycle. Every figure is reconciled between the two before anyone relies on the new books.
The consolidated reports are presented against the parallel run. Go live happens on the signature of the group, and the old system stays readable for the retention period.
Training for administrators and finance teams is part of the third and fourth phases, in Persian or English, using your own chart of accounts as the teaching material.
Write down the shape of the group. A person reads every request, and the reply proposes a time for a working session, not a sales call. Pricing is scoped per group structure after the briefing and agreed in writing. This page publishes no figures, because a figure without your structure behind it would be invented.
Your request is with the NERAX Business desk. A person reads every request, and the reply proposes a time for a working session.
