Product
What Laftah actually does today
One system for the construction operating cycle -- projects, procurement, inventory, workforce, documents, finance, and reporting -- built as a modular monolith so every module shares the same data instead of syncing copies of it.
Projects & contracts
The operational context everything else hangs off of.
- Projects with customers, cost codes, and budget lines.
- Customer contracts and vendor subcontracts, each with their own value, status, and approval trail.
- Every cost, commitment, and invoice on a project traces back to it -- nothing is entered without a project to belong to.
Procurement
Requisition through receipt, with three-way matching.
- Purchase requisitions, RFQs, and purchase orders, routed through a configurable approval workflow.
- Goods receipt notes (GRNs) confirm what actually arrived against what was ordered.
- Supplier invoices match against received quantities before they're allowed to post -- a three-way match, not a rubber stamp.
Inventory
A real movement ledger, never a bare editable quantity.
- Warehouse-level stock, moved in and out through recorded transactions, with project allocation.
- Every quantity on hand is the sum of its movement history, not a number anyone can just overwrite.
Subcontractors
The vendor-side mirror of customer contracts.
- Subcontract agreements per project and vendor, tracked as their own commitment against project cost.
Workforce & timesheets
Labor hours become labor cost, on the record.
- Employees, timesheets, and a review/approval step before hours convert into project cost.
Documents
AI-assisted extraction, reviewed before it counts.
- Upload a supplier invoice and have its fields extracted automatically -- vendor, amounts, line items.
- Nothing from an extraction posts to the books unreviewed: a human confirms or corrects it first.
- Document classification and splitting for multi-invoice uploads.
Finance
A real double-entry ledger underneath everything else.
- Chart of accounts, journals, fiscal periods, and tax rates.
- Every journal entry is balanced -- debits equal credits -- before it's allowed to post, and a posted entry can't be edited; corrections are new reversing entries.
AP / AR & payments
Supplier and customer invoices, vendor and customer payments.
- Supplier invoices flow from PO match through approval to posting.
- Customer invoices bill against projects and contracts.
- Vendor payments and customer receipts allocate against specific invoices, tracked to the cent.
Project cost control
Budget vs. committed vs. actual vs. forecast -- computed live.
- Committed cost from approved purchase orders, actual cost from posted invoices and approved labor, forecast as the sum of both.
- No shadow ledger: every number here is derived from the same records finance and procurement already use.
Reporting
Trial balance, P&L, AP/AR aging, and project profitability.
- Standard financial reports read directly from the posted ledger -- the same numbers finance sees, not a separate summary.
Saudi e-invoicing readiness
A ZATCA integration boundary -- built honestly, not oversold.
- Every posted customer invoice gets a real ZATCA-format QR code and an internal hash chain, generated automatically.
- Live submission to ZATCA is not yet connected -- that requires real sandbox credentials this deployment doesn't have, and we won't claim compliance we haven't tested.
Multi-tenant security
Every record belongs to one organization, enforced everywhere.
- Role-based permissions, organization-scoped data access, and an audit trail on the actions that matter.
Procurement, in practice
Requisition through receipt, with three-way matching.
Purchase requisitions, RFQs, and purchase orders, routed through a configurable approval workflow.
Illustrative product view
Requisition through receipt -- every supplier invoice matches against what was ordered and received.
Documents, in practice
AI-assisted extraction, reviewed before it counts.
Nothing from an extraction posts to the books unreviewed: a human confirms or corrects it first.
Illustrative product view
Nothing from an extraction posts to the books unreviewed -- a human confirms or corrects it first.
Built for Saudi Arabia, built to grow with you
Laftah is a modular monolith by design -- not microservices, not a patchwork of disconnected tools. Every module reads and writes the same underlying data, so a purchase order, a timesheet, and a posted invoice all show up correctly wherever they matter, without a separate sync step to get wrong.