LAFTAH

LAFTAH · لفتة

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, BOQ lines, and budget lines.
  • Customer contracts and vendor subcontracts, each with their own value, status, and approval trail.
  • Variation orders, client payment applications, and subcontract claims, kept separate from the tax invoice.
  • 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

Invoices can be entered by hand. Extraction is reviewed before it counts.

  • Supplier invoices can be entered without an external extraction service.
  • When the document service is connected, extracted vendor, amounts, and lines stay in review until a person confirms them.
  • A confirmed review is locked so a later extraction cannot overwrite it.

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 supplier invoices, stock issues, and certified subcontract claims. Forecast final cost includes the remaining budget from the same engine.
  • 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.

LAFTAH · purchase orders

Illustrative product view

Running

POVendorStatus
PO-1042Approved
PO-1041Received
PO-1040Draft
PO-1039Received

A draft is not a commitment. It stays off project cost until the order is approved.

Documents, in practice

Invoices can be entered by hand. Extraction is reviewed before it counts.

When the document service is connected, extracted vendor, amounts, and lines stay in review until a person confirms them.

LAFTAH · document review

Illustrative product view

Running

The vendor is read from the document and held for review. It does not post by itself.

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.

Product · LAFTAH