Platform Architecture

Twelve product layers

Asaan Hesab is not a single application. It is twelve interlocking layers that together form a complete enterprise operating system.

Layer 1
Core ERP
Accounting, sales, purchasing, inventory and CRM on one shared ledger.
Layer 2
Financial Engine
Cash, bank, multi-currency, accounts payable and receivable, and budgeting.
Layer 3
Operations Engine
Warehouses, goods in transit, production, project and service management.
Layer 4
Industry Modules
Sector workflows purpose-built for Afghanistan and the wider region.
Layer 5
Workflow & Approval Engine
Dynamic approval chains, delegation and task routing across roles.
Layer 6
Intelligence Layer
Business intelligence, forecasting and continuous KPI tracking.
Layer 7
AI Layer
Voice commands, fraud detection and strategic recommendations.
Layer 8
Security Layer
Strict document integrity protocol (no hard delete) and a complete audit trail.
Layer 9
Communication Layer
Customer, supplier and agent portals plus automated WhatsApp messaging.
Layer 10
Integration Layer
POS hardware, e-commerce, banking and payment system APIs.
Layer 11
Customization Layer
No-code builder for forms, reports and custom fields.
Layer 12
Infrastructure Layer
Offline-first synchronization, disaster recovery and multi-device support.

Design Philosophy

The five foundational principles

Every screen, rule and report in Asaan Hesab is built on these five commitments.

Simple for staff
A field agent or cashier can complete their work without knowing a single accounting concept. The system handles the double-entry behind the scenes.
Powerful for accountants
Complete double-entry bookkeeping, precise traceability and strict correction rules deliver an audit-grade financial record.
Intelligent for executives
A BI panel that surfaces the state of the business and its bottlenecks instantly, without drowning you in reports.
Built for Afghanistan
Local currencies (AFN, USD, PKR, IRR, CNY), Hawala and Saraf ledgers, weak-connectivity operation and local units of measure are built in, not bolted on.
Future-ready architecture
Ready for AI, voice assistants, APIs, cloud and mobile integration from day one.

System Rules

These rules are enforced by the core and cannot be switched off. They are what separates an ERP from a bookkeeping app.

Document integrity protocol
No posted document can ever be deleted from the system. Hard delete is banned. Changes are made only through a reversal, a cancellation or a credit note — each requiring a stated reason.
Segregation of duties
Purchase request, approval, goods receipt (GRN), invoice and payment are split across separate permissions so that no single person can complete a fraudulent cycle alone.
Full audit trail & history
Who changed what, when, from which IP and device — stored with the old value, the new value and the stated reason.
Standard document lifecycle
Every document follows the same status path, so any user can read the state of any record anywhere in the system.
3-way matching engine
Payment cannot be approved until the purchase order, the goods receipt note and the supplier invoice have been cross-checked by quantity and amount.