- Home
- Features
Eleven modules that work together — the document starts on site and ends in the ledger
No module works in isolation. A material request becomes a purchase order, the purchase order a supplier invoice, the invoice a voucher, the voucher an entry. Here are the modules one by one.
E-signature approval on a chain you define
Material requests, purchase orders, payment requests, site reports, payslips, custody settlements and manual entries — every type has an approval chain in settings: who signs first and who next. Nothing executes until the last signature.
- The approvals inbox: what waits for your signature, and your documents returned for revision — in one place.
- A push notification and an email when it is your turn; everyone signs their slot from the phone.
- Rejection closes the document; "return for revision" sends it back as a draft to its author.
- The signature, name and approval date appear on the printed document.
- A payment request does not become a voucher before approval — approval here is not a formality.
Stock per item by a clear formula, and custody per site with a document
Item stock = receipts + adjustments − production components − direct issues − deliveries to sites. Quantities accept fractions, and every movement records who made it and when.
- Site custody: issued to site, consumed on site, returned to store, damaged — and progress is measured by what was delivered against the target.
- The install/dismantle cycle for scaffolding and signs: new install, dismantle, re-install, and the workshop as a third location.
- Stock counts with variances, a movement log, and allocation of products to projects.
- Material cost becomes a ledger entry automatically at a weighted-average purchase price, on the project's cost centre.
Products with bills of materials, and production orders that deduct components automatically
Every product has its components (how many metres, kilograms, pieces). A production order deducts components from the store, and the finished product is allocated to its project and delivered to site.
- Product stock = produced − issued to its projects.
- Components at project level too, for work made to order for each client.
- Production component cost is posted to the ledger at its price.
From the client PO to the progress bill to collection — with retentions computed
Client → client PO → project and site → delivery notes → progress bill → collection. The bill computes the advance and retentions automatically; cancellation is by credit note.
- Tax invoice with a QR code, integrated with the Zakat, Tax and Customs Authority (ZATCA).
- Release of retentions when due, and a printed statement on your letterhead sent to the client.
- Profitability per project: revenue against material cost and expenses.
- Aging: who is late and by how much, from each bill's due date.
The full purchasing cycle: the department requests, purchasing buys, goods arrive, documents are filed
Material request → purchase order → raw material receipt → supplier invoice (stock, non-stock or tax) and returns → payment requests and vouchers in installments tied to the order.
- A statement per supplier, and aging from open invoices.
- The AI assistant reads a photo of the supplier invoice and fills in the lines — you review and approve.
- A purchase order is paid in installments: every payment request links to the order and the remainder is computed.
Multiple cash boxes and bank accounts, and bank reconciliation that matches itself
Every cash box and bank account has an account in the chart. Documents that move money carry a "cash box / bank" field, and transfers between accounts with their fees post automatically.
- Bank reconciliation: paste the bank statement lines and the system matches them to the ledger (same amount within 7 days), or match manually.
- What is in the bank but not in the ledger (fees, interest) is posted straight from the line.
- Account movements with running balances, an opening balance per account, Excel and PDF export.
Automatic entries from every approved document — the accountant reviews instead of re-entering
A ready chart of accounts (assets, liabilities, equity, revenue, expenses) that you can edit; core accounts have a fixed "role" so entries find them even if you change the codes.
- Automatic entries for progress bills, collections, supplier invoices, vouchers, payslips and custody settlements — every entry linked to its document.
- Entries are never edited or deleted: cancellation is by reversing entry. Manual entries with approval when needed.
- Period closing: no entry can be dated inside a closed period, and the error reaches the document itself.
- Trial balance, consolidated statements (client, supplier or employee), aging, VAT return, income statement and opening balances.
Employee files and documents, and payslips that post their entry on approval
The file first, documents after: iqama, contract and papers; HR forms (leave, advance, start of duty); and payslips whose net is computed as you type.
- The AI assistant reads a photo of the iqama and fills in the details.
- A salary voucher from the approved payslip; employee custody linked to payment vouchers and settled with approval.
- A separate HR permission: whoever sees employee documents need not see the accounts.
What was done today, in pictures, in the project file
The supervisor uploads the site report from the phone: photos, what was installed or executed, and notes. The manager reviews and comments from wherever they are, and reports stay with the project rather than in a WhatsApp group that gets deleted.
- The daily management report: all sites on one page.
- A PDF from photos — generated on the device, for documents sent to the client.
- Tasks, follow-up and a task board for the team.
Installs on the phone and the laptop, and tells you when a document is waiting
A web app that installs without an app store (PWA). Screens designed for the phone from the start, dark and light themes, Arabic and English with one toggle.
- Push notifications on the phone and the computer even with the app closed, and emails with document links.
- An end-of-day summary by email to whoever you choose in settings.
- PDF printing on your letterhead, Excel export from every table, and search across everything.
A database and a URL for your company alone
Not an account on a shared system. Every client has its own database project and its own URL (such as atlas.yourcompany.com), with your company's logo on printed documents.
- The first account created is the owner; everyone else needs an email on the company domain or to be added by name, and waits for approval.
- Roles: owner, admin, editor, HR, approval-chain manager — everyone sees what concerns them.
- Backups to your own Google Drive, and a "data health" page that checks the database.
- A log of every action: who did what and when.
Photograph the paper and the system reads it and fills it in — you review before saving
A document scanner built into the phone, AI reading that only copies what is on the paper and never computes or infers, and an assistant that answers from your database. Every user has a daily quota, and nothing is saved without review.
- Camera scan onto any document: automatic crop, flatten and compress, attached as a PDF or image to the document.
- Reads a supplier quotation or invoice, or a client PO, from a photo or PDF and fills in the lines as written, checking the total.
- Reads an iqama, ID or passport to open the employee file, with Hijri and Gregorian dates.
- An assistant for daily questions (balances, last purchase price, what is running out, production capacity) answered from your numbers with a detail card.
- Tasks from a plain sentence or from meeting minutes, a project summary, a written weekly report from the dashboard numbers, and plain-language search.
- An e-signature from a photo of your signature on a blank sheet, cleaned up and placed on the approval line.
Want to see it running on your own work?
A demo online or at your office in Riyadh — with one of your live projects.