The process

One process. The whole system hears it.

From a request on site to a closed cost — eleven stages, every one of them a real ASIEL module.

Site material request
MR-2026-0418
Site-01 requests 500 m³ of C40 concrete for the seventh-floor pour.
32,500.000 OMR
Site engineer
Approved against budget
APR-2026-0912
Checked against budget line C-120 before approval, not after.
32,500.000 OMR
Project manager
Available stock reserved
RSV-2026-0301
Inventory reserves what is genuinely on hand; the rest becomes a purchase.
Warehouse keeper
Purchase order
PO-2026-0774
An approved order commits budget — and posts no journal entry.
32,500.000 OMR
Procurement
Goods receipt
GRN-2026-1180
Arrival at SITE-01 is the moment the books move.
32,500.000 OMR
Site receiving
Quality inspection
QC-2026-0455
The batch is inspected before issue. A rejection stops the issue rather than following it.
Quality inspector
Issued to the project
ISS-2026-0902
The issue charges cost code C-120 directly.
32,500.000 OMR
Site store
Supplier invoice
BILL-2026-2207
Matched against the order and the receipt before it is cleared for payment.
32,500.000 OMR
Accounts payable
Journal entry
JV-2026-3341
The entry is the consequence of the operation, not a separate step someone types.
32,500.000 OMR
ASIEL
Payment
PAY-2026-0688
Released from treasury in a payment run, on the supplier’s terms.
32,500.000 OMR
Treasury
Closed
Closed against the project, and traceable line by line to where it came from.
Finance

Eleven stages, one document travelling between them — and nothing re-entered at any of them.

Transaction impact

One approval. Five consequences. Nothing re-entered.

Approving one purchase order changes the commitment, the expected stock, the cash forecast and the supplier exposure — and posts no journal entry, because the books move on receipt.

Purchase order approvedPO-2026-077432,500.000 OMR

Project commitment
Commitment on C-120 rises
increase of 32,500.000 OMR
No journal entry
Incoming inventory
500 m³ expected at SITE-01
No journal entry
Cash forecast
Outflow expected within 30 days
decrease of 32,500.000 OMR
No journal entry
Supplier exposure
Total commitment to the supplier updates
No journal entry
Accounting
No entry yet — the books move on receipt
No journal entry

Entered once

Enter it once. ASIEL connects the rest.

The project, the cost code, the warehouse and the branch are typed on the site request — and then appear by themselves on the order, the receipt, the issue and the entry.

Typed once

Site material request

MR-2026-0418

Project: PRJ-2026-014
Cost code: C-120
Warehouse: SITE-01
Branch: MCT

Muscat Heights — Phase 2 · Site engineer

Purchase order
PO-2026-0774
- ProjectPRJ-2026-014
- Cost codeC-120
- WarehouseSITE-01
- BranchMCT
Inherited — nobody typed it again
Goods receipt
GRN-2026-1180
- ProjectPRJ-2026-014
- Cost codeC-120
- WarehouseSITE-01
- BranchMCT
Inherited — nobody typed it again
Issue to project
ISS-2026-0902
- ProjectPRJ-2026-014
- Cost codeC-120
- WarehouseSITE-01
- BranchMCT
Inherited — nobody typed it again
Journal entry
JV-2026-3341
- ProjectPRJ-2026-014
- Cost codeC-120
- WarehouseSITE-01
- BranchMCT
Inherited — nobody typed it again

Operations centre

Everything in flight — and what is stuck, and why.

Six operations at different stages on one screen: what is waiting on a decision, what is blocked, and who it is waiting on.

1Blocked

2Awaiting a decision

2In progress

C40 concrete — Muscat Heights
Received, awaiting invoice
PO-2026-077432,500.000 OMRthe transaction this page follows
Reinforcement steel — eighth floor
Awaiting approval
Waiting on: Project manager
MR-2026-042118,900.000 OMR
Concrete pump — monthly hire
Blocked: supplier is on hold
Waiting on: Supplier management
PO-2026-07814,250.000 OMR
Insulation — site store
Quality inspection
GRN-2026-11837,640.000 OMR
Supplier invoice — electrical works
Three-way match complete
BILL-2026-221123,180.000 OMR
Subcontractor certificate — reinforcement
Awaiting consultant approval
Waiting on: Consultant
IPC-2026-00624,900.000 OMR

This is a demonstration that simulates progress. The Operations Centre in the product is driven by real transactions.

Traceability

Every number in ASIEL has a source.

Pick any component of the project’s actual cost and follow the documents that produced it — from the issue back to the journal entry.

Project actual cost482,350.000 OMRMuscat Heights — Phase 2 · PRJ-2026-014

Material — 5 documents

ISS-2026-09022026-06-18
Material issue
500 m³ of C40 concrete issued to C-120
32,500.000 OMR
GRN-2026-11802026-06-17
Goods receipt
Received into SITE-01
32,500.000 OMR
PO-2026-07742026-06-09
Purchase order
Raised on Al Wadi Trading Co.
32,500.000 OMR
BILL-2026-22072026-06-21
Supplier invoice
Three-way matched: order, receipt, invoice
32,500.000 OMR
JV-2026-33412026-06-17
Journal entry
Dr Inventory, Cr GRNI
32,500.000 OMR

Construction

From tender to handover.

Eleven phases of a project’s life, each owned by a module — and the transaction this page follows sits inside them.

Tender
An invitation is registered with its dates, documents and bonds.
Estimation
Priced from resources and outputs, not a percentage added to a cost.
1,180,000.000 OMR
Bill of quantities
The approved BOQ is what every later certificate is measured against.
Budget
Opened against cost codes — and checked before every request is approved, not after.
1,000,000.000 OMR
Procurement
This is where this site’s transaction happens: the concrete ordered, and received.
32,500.000 OMR
This is where the transaction this page follows happens
Site
Daily reports, hours and equipment — the source of actual cost, not a summary of it.
Subcontractors
Contracts with their bonds and retention, certified the way the main contract is.
67,250.000 OMR
Interim certificate
Measured against the BOQ, and handed to receivables as an invoice.
412,600.000 OMR
Variations
Approved, priced and taken into the budget — never appearing first in the final cost.
48,900.000 OMR
Cost and margin
Committed, actual and forecast on one cost code — and the margin follows from them.
482,350.000 OMR
Handover
Handover, defects liability and retention release — the project closes rather than stops.

Manufacturing

From demand to a finished batch — and where it came from.

Nine steps, and only two of them move the books: when material is issued, and when the finished batch is received.

Batinah Aluminium Works

Forecast demand
Expected demand for aluminium façades next quarter, from orders and forecast together.
1,200 unitsNo journal entry
Material requirements
On hand against the bill of materials — a shortfall becomes a purchase, not a surprise on the floor.
MRP-2026-W25No journal entry
Production order
The order commits material and work-centre capacity — and posts no journal entry.
PRD-2026-0318400 unitsNo journal entry
Material issued
This is where the books first move: raw material out, work in progress in.
ISS-2026-1142Raw material → work in progress
Work centre
Operations recorded against the routing: run time, downtime, and who performed it.
No journal entry
Shop floor
Production reported from the floor itself, not typed up from a sheet afterwards.
No journal entry
Quality inspection
Inspected before receipt. A rejection stops the batch and is recorded with its reason.
QC-2026-0912No journal entry
Finished goods received
The books move again: work in progress out, finished goods in at their cost.
FG-2026-0455392 unitsWork in progress → finished goods
Order cost
Material, labour and overhead on one order — and the variance against standard is shown, not inferred.
No journal entry

Where did this batch come from?

SupplierSUP-0771Aluminium billet supplier
Raw material batchLOT-AL-2026-00886063 billet — mill certificate attached
Goods receiptGRN-2026-2210Received into the works store
Production orderPRD-2026-0318Aluminium façades — 400 units
Rejected batchQC-2026-0912-R8 units rejected: coating thickness out of tolerance — reworked
Finished batchFG-2026-0455392 units accepted
CustomerDN-2026-0663Delivered on one delivery note

Oman

Built around how business works in Oman.

Three-decimal Rials, tax treatments kept apart, Arabic first, and Fawtara — stated as facts about the software.

Omani Rial
Three decimal places in every amount, every entry and every report — nothing rounded on the way.
Value added tax
Treatments kept apart from one another: zero-rated, exempt, out of scope and reverse charge.
Arabic first
Interface, documents and reports in Arabic, right to left — with English beside it.
Branches and companies
More than one company under a group, each with its own books, branches and fiscal year.
Fawtara
Invoices prepared, submitted and followed — including a rejection and the reason for it.
Audit and control
Every entry has a source, every permission has a holder, and nothing leaves the audit log.

An invoice on its way to Fawtara

OM1100472093 · demonstration data

Created
The invoice is the result of a sale, not something typed on a separate screen.
Validated
Checked before it is sent: registration, tax treatment, and totals against lines.
Queued
Submission is asynchronous — an outage delays an invoice rather than losing it.
Submitted
Sent to Fawtara, and waiting for its answer.
Rejected
A rejection is shown with the reason as given — on the invoice itself, not in a log somebody has to find.
Accepted
After correction and resubmission — and the invoice carries its real status at every step.

ASIEL prepares the invoice, submits it, and shows Fawtara’s answer as given. No accreditation or approval is claimed here.

Modules

Fifty modules, eight domains, and real dependencies between them.

Pick a domain to see its modules and what it connects to — taken from the module catalogue itself, not drawn for the page.

1General Ledger
2Accounts Receivable
3Accounts Payable
4Cost Accounting
5Treasury Management
6Banking & Reconciliation
7Budgeting & Forecasting
8Fixed Assets
9Financial Consolidation
10Oman Tax & Fawtara

Connected to

Sales
- Sales Managementdepends on Accounts Receivable
- Customer Credit Managementdepends on Accounts Receivable
Procurement
- Procurementdepends on Accounts Payable
Construction
- Project Budget Controldepends on Budgeting & Forecasting
Manufacturing
- Manufacturing Costingdepends on Cost Accounting

These are taken from the module catalogue itself — the same dependencies the system enforces when a module is activated.

Industries

Which of the fifty are yours?

Fifty is an impressive number and an unhelpful one. Pick your kind of business to see what it actually starts with — a starting point, not a template that is applied.

The project is the unit of profit, and cost is measured against it line by line from tender to handover.

28Construction Project Management
31BOQ Management
32Project Budget Control
33Subcontractor Management
34Progress Billing & IPC
35Variation Orders & Claims
16Procurement
21Inventory Management
1General Ledger
2Accounts Receivable

A starting point rather than a template that is applied: modules are enabled one at a time, according to what you actually buy.

Roles

Same ASIEL. Different responsibility.

Pick a role: the cards two people share stay and move to their new place, and the rest change. Not five screens — one screen that knows who is looking at it.

Chief executiveWhere the company stands, and what threatens it.

Cash1,284,600.000 OMRAcross all accounts
Revenue3,940,200.000 OMRYear to date
Margin18.4%After charged cost
Live projects7Two near closure
Open risks3One above threshold
Receivables612,750.000 OMR84,300 of it overdue

Security and control

Every claim here names what enforces it.

Eight capabilities, each stated with the mechanism that actually enforces it — and what is not in service today is not listed.

Undeclared is refused
Every endpoint declares the permission it needs. One that declares nothing is refused, not opened.
Enforced byA global guard on every request, and a test that scans every handler
Permissions declared in code
Permissions are declared in code and reconciled to the database on every boot — none is granted without a definition.
Enforced byA permission registry reconciled at boot, refusing any key a handler enforces and nobody declared
The subscription gates access
A module the tenant has not bought opens for nobody, whatever their role — decided from the permission key itself.
Enforced byThe module derived from a permission key’s first segment, refused as MODULE_NOT_ENTITLED
Tenant isolation in the database
Enforced in the database itself, not only in code — a query with no tenant established returns nothing.
Enforced byRow-level security policies on every tenant-owned table
An audit trail nothing leaves
The database refuses to delete an audit event — for every role, including the database owner.
Enforced byA database-level constraint that refuses DELETE
Segregation of duties
Whoever raises a document does not approve it — nor reach it through a delegation, nor as an escalation target. If excluding them empties the step, raising is refused rather than auto-approved.
Enforced byThe approval chain excludes the submitter on every route, each one asserted by a test
Sessions that can be ended
A session expires on its term and is revoked immediately on request — and the first reason recorded is never overwritten by a blander one.
Enforced byIssue, expiry and revocation under test, and every session revoked on a password reset
Lockout after failed attempts
Failed attempts are counted and recorded, and the account locks at the configured limit — and the counter survives the refusal that caused it.
Enforced byA counter written in a unit of work separate from the transaction that refuses the attempt

What is checked before a single row is read

UserA live session, neither revoked nor expired
RoleWhat this person actually holds
ModuleHas the tenant bought this module?
PermissionThe permission declared on this endpoint
CompanyThe company the document belongs to
The rowAnd the database policy checks the tenant again

The same request, across another company’s boundary

Refused — and answered as not found rather than forbidden: the difference between those two answers would itself reveal that the document exists.

What is not listed here is left out deliberately: multi-factor authentication for workspace users is not in service today, and is not claimed.

Implementation

From setup to running, in a known order.

Ten stages, each before the next for a reason: the chart before any entry, cost dimensions before the first posting, roles before people.

Company and branches
The company, its branches, departments and stores — and the fiscal year everything after is measured against.
Chart of accounts
The chart, the account types and the control accounts — before any entry, because an entry is not corrected by deleting it.
Cost dimensions
Projects, cost centres and which dimensions are mandatory — the decision that fixes what your reports can answer later.
Customers and suppliers
The commercial registers, with payment terms, credit limits and tax details.
Items and stores
Items, units of measure and stores — and the valuation basis that will govern every issue after.
Opening balances
Balances enter as a balanced opening entry, not as figures written over the accounts.
Approval matrices
Who approves what, and above which threshold — with segregation of duties enforced rather than recommended.
Tax and Fawtara
Registration, treatments and codes, and the submission configuration for Fawtara.
People and roles
Roles and what they hold, then people — in that order, because a role is reviewed before it is handed out.
Go live
The first open period, and the first real transaction travelling from request to entry.

Why ASIEL

Arabic first
Right-to-left is structural in the design, not a stylesheet applied at the end, and English is a complete alternative rather than a partial translation.
One system, not fifty products
One ledger, one costing engine, one dimension model, one document store and one approval matrix serve every module.
Authorization evaluated per request
User, session, organisation, entitlement, permission, data scope and business state — six independent checks. Hiding a menu item is not one of them.
An audit trail that cannot be edited
Every change records the actor, the time and the before and after, in the same transaction that made it, and the database refuses to update or delete the record.
Built for contracting and manufacturing
The BOQ → interim certificate → variation chain, and the BOM → routing → MRP → costing chain — not bolt-ons to a general accounting package.

50 modules, one platform

The modules sit in eight domains, and each one knows what it depends on, so none can be switched on half-working.

Explore the modules

Designed in Oman, for Oman

Localisation is not a translated interface. It is the market’s particulars being part of the data model itself, rather than a setting adjusted after installation.

The Omani rial at three decimal places, with precision coming from currency configuration and never from a constant
Asia/Muscat as the default timezone, with storage always in UTC
Commercial registration and VAT numbers as fields on the organisation and the company
The governorate on the branch, because Omani reporting is requested by it
An Arabic, right-to-left interface as the baseline, with English as a complete alternative

Site material request
Approved against budget
Purchase order
Goods receipt
Issued to the project
Journal entry
Closed

One process.One platform.One financial result.

Book a demo

An Omani-built ERP for the modern enterprise

One process. The whole system hears it.

Site material request

Approved against budget

Available stock reserved

Purchase order

Goods receipt

Quality inspection

Issued to the project

Supplier invoice

Journal entry

Payment

Closed

One approval. Five consequences. Nothing re-entered.

Project commitment

Incoming inventory

Cash forecast

Supplier exposure

Accounting

Enter it once. ASIEL connects the rest.

Site material request

Purchase order

Goods receipt

Issue to project

Journal entry

Everything in flight — and what is stuck, and why.

Every number in ASIEL has a source.

Material issue

Goods receipt

Purchase order

Supplier invoice

Journal entry

From tender to handover.

Tender

Estimation

Bill of quantities

Budget

Procurement

Site

Subcontractors

Interim certificate

Variations

Cost and margin

Handover

From demand to a finished batch — and where it came from.

Forecast demand

Material requirements

Production order

Material issued

Work centre

Shop floor

Quality inspection

Finished goods received

Order cost

Where did this batch come from?

Built around how business works in Oman.

Omani Rial

Value added tax

Arabic first

Branches and companies

Fawtara

Audit and control

Created

Validated

Queued

Submitted

Rejected

Accepted

Fifty modules, eight domains, and real dependencies between them.

Connected to

Connected to

Connected to

Connected to

Connected to

Connected to

Connected to

Connected to

Connected to

Connected to

Which of the fifty are yours?