BUILD ENGINE · EVIDENCE REVIEW · 24 OCTOBER 2026

What works today.
What it still takes to call it complete.

A practical capability review for a Saudi construction ERP built on Odoo 20 and React. This report separates features we have from acceptance we have proved.

Can we claim “full Saudi accounting, full CRM, full Sales, full Purchase, and all DGA portal connections”? No. That wording overstates the tested system. We have useful, integrated product slices and a broad Saudi accounting staging addon. Production accounting, full story acceptance, field workflows and official portal connections remain incomplete.

The honest status

The current Build Engine backlog contains 164 user stories. A story becomes DONE only after its full acceptance criteria pass. A partial feature is useful, but does not count as half a completed story.

50 / 164DONE · 30.5% fully acceptance-verified
102 / 164PARTIAL · 62.2% have an incomplete implementation
2 / 164MISSING · 1.2% need implementation
10 / 164BLOCKED · 6.1% need access or a decision

The 62.2% PARTIAL figure is a classification share, not an overall completion score. Under ADR0014, React is the required end-user UI. BE-109/BE-110 now have React RFI workflows but remain PARTIAL pending live role and project/company boundary acceptance. See the story-by-story traceability.

Build Engine feature status

Filter the table by area. “Verified” refers only to the named, synthetic QA scenario. It does not mean the entire business area has reached production acceptance.

Saudi books, chart and tax setup

QA configured

One accounting_ksa addon extends native Odoo accounting with the Saudi localization. The isolated training company uses SAR and an sa chart with 233 accounts and17 tax definitions.

  • Verified company readiness, balanced synthetic general entries and role-restricted finance API.
  • Customer invoices and vendor bills in the demo remain drafts.
  • No live ZATCA onboarding, invoice submission, accountant sign-off, opening-balance migration or statutory filing has passed.
  • Custom report access still needs review for project/journal restrictions. Arabic source-string coverage is99.9%, not legal/linguistic approval.

Evidence:202 accounting addon tests passed across339 combined Odoo cases (two conditional accounting skips; one optional construction skip). Current demo sample: SAR137,000 debit=credit and SAR13,000 posted-only profit.

Reports, assets and budgets

Staging checks passed

Twelve report endpoints and QWeb renders were exercised. Real PDF and XLSX exports were downloaded; the sample profit and loss and workbook figures were inspected.

  • Income statement: SAR25,000 revenue−SAR12,000 expenses=SAR13,000 sample profit.
  • Sample asset SAR36,000 with36 depreciation periods; project budget SAR120,000.
  • Bank reconciliation client screens loaded for finance role.
  • Custom report bundle is not an audited substitute for every Odoo Enterprise report. Accountant confirms statutory layouts, close, VAT and audit treatment.

Tested in the isolated be_theme_qa_20261024 database. Report evidence · Native JSON-2 API permission checks.

Banking, payments and OCR

Partial / manual UAT

Bank-file parser families and a native reconciliation screen exist. UI render and search passed; full match/post/reversal flow, repeat-file dedupe, live bank feed, payment rails and bank certification are not verified.

  • One upstream browser reconciliation tour is not collected as a passing test.
  • Arabic/English local OCR tools are packaged; real invoice extraction accuracy was not accepted.
  • PDF output is visually correct for the sample, but Latin numbers are not searchable/extractable in the current runtime. Accessible/searchable PDF is open.
  • Payment/check configuration and automatic collection jobs need finance-controlled UAT. Imported jobs start inactive.

Evidence: client actions, feature boundaries, rendered PDF preview.

Six local AI specialists

Connection smoke passed

CRM, sales, purchasing, accounting, analyst and coordinator profiles reached local qwen3.8:27b. Advice records include their source links. Finance access gates financial context. The model has no native business-write tools.

  • All six profile connection checks returned a response; business-move count stayed at five before and after.
  • Smoke checks do not prove answer accuracy, full CRM workflow coverage or approval behaviour.
  • Existing React approval-based agent workflows remain a separate service and acceptance surface.

See actual local model evidence and ADR0013.

CRM

Present; not full

React has a CRM screen; native Odoo CRM holds the Saudi demo opportunity. UI flows, validation, filters and responsive layouts passed the documented preview/browser suite.

  • CRM epic:9 PARTIAL,1 MISSING,0 DONE.
  • Live authenticated React rehearsed seven screens read-only; draft edits/creates are not full production role/tenant integration.
  • Government/private lead handling, complete Etimad discovery flow, automatic bid ingestion, qualification agents and end-to-end human approval remain open or blocked.

See epic status and test scope and limits.

Sales

Present; not full

React office workspace and native Odoo support sales opportunities/quotations and draft sales documents. The KSA demonstration links a sample lead, quotation and project BOQ.

  • Sales AI/proposals epic:2 PARTIAL,7 MISSING,1 BLOCKED (the story epic includes AI proposal obligations, not a claim that base Odoo lacks sales).
  • Mocked/browser draft tests do not complete every live authorization, approval, margin, contract and invoice lifecycle story.
  • Native demo quotation is not sent or confirmed.

Purchase and suppliers

Present; not full

Native Odoo RFQs/purchase records and a React purchasing workspace exist. A synthetic RFQ is connected to demo BOQ lines.

  • Procurement epic:7 PARTIAL,3 MISSING.
  • Full tender/three-way approval, subcontract workflows, live supplier response, purchase-receipt-to-site quantity/cost reconciliation and role acceptance remain open.
  • Demo RFQ remains draft; no supplier message is sent.

Construction ERP core

Substantial modules; incomplete stories

Odoo has project/task, BOQ, tender, contract, variation, daily-log, materials, progress, quality and maintenance modules plus a themed native workspace. The QA database contains a synthetic fit-out project and linked examples.

  • Project/scheduling epic:6 PARTIAL,4 MISSING.
  • Quality epic:3 PARTIAL,5 MISSING,1 BLOCKED.
  • Native slices now include equipment custody, submittal revisions/decisions, owner project-risk and finance snapshots, and confirmed BOQ-to-sales-line analytic linkage; they remain PARTIAL pending the full story acceptance gates.
  • External submittal portal review, drawing-version/change-impact integration, advanced schedule/resource control, project commercial reconciliation and subcontractor portal acceptance remain open.
  • Native RFI backend workflows exist; their React user journeys remain open. DMS permission findings and final project-wide security/production gates remain open.

Native RFI roles, assignment, date, audit and Arabic/English screens passed. See RFI acceptance.

Field mobile and offline

Incomplete

The native theme and office React views adapt to phone widths. A separate site PWA has queues, but that does not establish full field-sync acceptance.

  • Offline epic:8 PARTIAL,0 MISSING.
  • Conflict resolution, durable reconnect, photo/object storage and site-data permission scopes have open acceptance.
  • No claim of reliable offline approvals, 48/72-hour operation or secure field attachment workflow.

DGA standards and government services

Not certified / not all portals connected

DGA is a regulator/standards authority for digital-government agencies, not one universal ERP gateway. Its 2025 basic digital-transformation standards state a scope of all government agencies. We have not completed a DGA standards assessment or obtained a certificate. Applicability to this contractor product must be assessed against the customer, contract and agency requirements.

  • Etimad: no API subscription/key in this workspace. The official portal uses product subscription and approval, an application, credentials, sandbox testing and production access.
  • Balady: an official open-data API document is public. That does not prove permit/transaction access; no authenticated construction-service integration passed.
  • Ejar/Wafi and other services: no verified scoped integration, approved credentials or sandbox acceptance in this build.
  • ZATCA: Saudi localization/EDI dependency is installed; simulation onboarding and document submission were not tested. Zero Fatoora calls.

Keep separate the DGA standards assessment, Etimad subscription and each service's API access, permits, and workflow approval.

Operations, identity and deployment

QA only; production open

Current feature evidence is from local isolated QA. The React/Odoo office app is running, but neither the Account KSA addon nor the complete construction test suite has been rolled through production companies.

  • No migration plan exists for databases with overlapping accounting addons already installed.
  • Production OIDC/JWKS, object storage, secure per-tenant credential binding, disaster recovery, restore tests, SLO/load tests and full audit retention remain open.
  • Custom report SQL and private/project rule interaction require deeper review before rollout.

Comparison with established systems

A capability-family comparison, not a scored procurement benchmark. Vendor products vary by licensed edition, selected apps, integrations, geography, implementation quality and configuration. The “ours” column reports this codebase and its tests, not an equivalent completed production install.

CapabilityBuild Engine · current evidenceOdoo 20 EnterpriseProcoreSAP S/4HANA Cloud Public Edition
ERP / accountingBroad staging sliceSaudi base + custom 12-report engine, assets, budgets, import/reconciliation, OCR/treasury packages.202 accounting tests; no statutory/production sign-off.Vendor documentedOdoo documents native accounting, bank sync, budgets, assets and standard financial reporting; some report/localization reporting features are Enterprise-only. Licensed edition and KSA package must be confirmed.Integrated construction financeProcore describes project-cost/financial-management integration alongside the company’s accounting system; do not assume it replaces general-ledger ERP.Enterprise ERPSAP documents finance/procurement/project processes and a Saudi country version. Scope, contracts and fit are implementation-specific.
Saudi localization / ZATCAConfigured; no UATSAR + Saudi chart in isolated demo; customer invoices remain draft; no ZATCA onboarding/submission. Tax and Arabic invoice acceptance still open.Saudi modules documentedOfficial Odoo documentation lists Saudi accounting and Saudi EDI/localization modules. Installation alone does not validate live credentials, company setup or legal acceptance.Verify integrationProduct documentation reviewed here does not establish Saudi ledger or ZATCA filing coverage. Confirm local accounting integration with vendor.Saudi functions documentedOfficial SAP Help describes Saudi country-specific functions; verify the requested release, E-invoicing scope and customer integration.
CRM, sales, purchaseScreens + sample recordsExisting React and native Odoo; CRM9P/1M, procurement7P/3M, sales-AI/proposals2P/7M/1B. Not complete approval-to-cash or RFQ-to-pay acceptance.Native app familiesOdoo documents CRM opportunities-to-quotes, sales quotations/orders and RFQ/purchase management. Configure roles, accounting, approvals and integrations.Construction procurement contextConstruction commitments and project-cost workflows; ERP/accounting systems commonly remain connected for corporate books.Integrated ERP processesSAP product scope documents sourcing/procurement, sales, manufacturing and project/finance process integration.
Project execution / fieldNative modules; story gapsProjects, BOQ, RFQ, daily log, variations, quality, maintenance and tested RFI flow; advanced schedule, DMS, submittals, subcontractor portal and end-to-end field UAT incomplete.ERP project managementOdoo documents project/task/milestone, project visibility, activities, reporting and links to sales, timesheets and documents. Construction execution depth varies by add-ons/configuration.Construction-specialist focusProcore documents RFIs, drawings, submittals, daily logs, schedules, photos, permissions and project-financial workflows.Enterprise projectsSAP documents project management integrated with staffing, recording time, procurement, sales billing and finance. Verify field execution/document detail for the specific implementation.
Mobile / offlineResponsive; sync incompleteTheme and React phone layouts pass browser checks; offline story epic8PARTIAL. Durable data/photo sync and conflict workflows remain open.Verify app and scopeNot scored here. Ask for the exact Odoo mobile/offline apps and required workflows in a scenario-based demo.Field tools documentedMobile construction workflow breadth includes field records; test network-loss behavior and Saudi deployment/security requirements in a pilot.Deployment-specificNo offline parity claim evaluated; validate exact SAP mobile applications and connected/disconnected field cases.
Saudi public portal APIsNot connectedEtimad approval/subscription absent; Balady public open data is not a permit connector; no verified Ejar/Wafi integration; ZATCA simulation not tested.Must configure per serviceA country localization is not proof of every portal connection. Confirm each maintained connector, credentials, sandbox, and approved business role.Project platformNo universal DGA/Etimad/Balady/Ejar connector established in the reviewed product sources.Project integration requiredSaudi version/localization does not automatically grant access to each Saudi government service.
Scale / assurancePrototype/staging evidence494 named automated regression cases (491 pass,3 skipped) plus scoped real HTTP/browser/model smoke. No complete story acceptance, load/SLA, recovery or production security sign-off.Mature vendor baselineEnterprise support/hosting and service options depend on Odoo plan and deployment. Compare actual contract, SLA, support and data residency.Construction platformCompare local availability, data residency/security, accounting integration, implementation partner and total cost for your project profile.Enterprise deploymentCompare scoped process coverage, implementation services, integration architecture, local operations, hosting and total cost.

Vendor feature descriptions are linked below. Cells describe published product scope, not performance or a recommendation. We have not installed/evaluated Procore or SAP. We have not run a licensed Odoo Enterprise comparison against this addon.

“DGA connection” and portal integrations mean different things

DGA’s published 2025 Digital Transformation Basic Standards specify scope: all government agencies. The page cannot serve as a blanket claim that a private construction ERP is “DGA connected” or certified. If a ministry, public owner or contract imposes controls on a supplier, map the exact obligations and evidence to that customer.

Etimad's official developer portal describes product review, subscription request and approval, registered application, API credentials, sandbox sample testing and then production URL. This workspace has no Etimad subscription or keys. Balady publishes an open-data API document, which gives no evidence that transactional permits are enabled for this app. Treat each portal as a separate service integration and confirm allowed products/scopes with its operator.

لا نستطيع أن نقول إن النظام كامل أو متصل بجميع بوابات الجهات الحكومية. لم يكتمل اعتماد المحاسبة السعودية أو اختبار زاتكا، ولا تتوفر مفاتيح اعتماد اتيماد. كما أن معايير هيئة الحكومة الرقمية تخص الجهات الحكومية بحسب نطاقها المنشور. لكل بوابة اعتماد وواجهة ونطاق اختبار مستقل.

Etimad

Not onboarded Request the relevant API product, get its subscription approved, register the application, test its sandbox and obtain production access. See official portal steps in Etimad Get Started and Subscriptions.

Balady

Open-data API documented; service APIs unverified Review the official open-data API guide; confirm the exact permit/service integration separately.

ZATCA / Fatoora

No simulation acceptance Native Saudi EDI dependency exists. Owner-authorized onboarding, certificate lifecycle, invoice/credit-note tests and reconciliation evidence are still required.

Ejar, Wafi and bank services

Not connected Confirm an available official service/product, contract, scope and credentials, then implement and test each adapter.

What to do next

Follow the requested delivery order and validate each vertical flow before widening the rollout. See the full implementation plan.

1. Finance and connected business workflows

Reconcile KSA chart, tax, accounting policy and opening balances with a Saudi accountant. Then prove the connected Odoo flow: qualified CRM opportunity → tender/award → project/approved BOQ → customer quote/order → purchase/receipt/vendor bill → project analytic cost → customer invoice/payment and reports.

2. Complete construction controls

Finish project schedule/resource controls, BOQ revisions and variations, site inventory, quality/safety, submittals, document revisions, contracts, equipment and workflow gates. Keep role, company and project checks inside every change.

3. Offline and field delivery

Prove durable assigned-data sync, atomic/idempotent apply, conflict resolution, attachments, Excel imports/exports and archive packs after the agreed soak; keep final approvals online unless a safe offline signature model is accepted.

4. Evaluated AI workflows

Build source-linked, Arabic/English business suggestions with confidence, role-scoped context, audit/replay, and human approve/edit/reject feedback. Agents must never send bids or post financial entries autonomously.

5. Saudi portal integrations

For each selected Etimad, Balady, Ejar/Wafi, ZATCA or bank service, secure the named product, owner, permission, credentials and sandbox, then test it independently. Do not claim generic DGA connectivity.

6. Final security and production gate

Complete cross-tenant/project access review, identity and secrets checks, object-store isolation, backup/restore, dependency scanning, load/soak, incident response and tenant-by-tenant migration/rollback before production customer data.

Evidence and sources

Local repository status is current as of 31 October 2026. Vendor pages describe vendor product scope and may change; they are not independent evaluations. Government sources support the stated authority/API scope.

Build Engine QA evidence

Real English profit and loss page in isolated synthetic Saudi QA, showing SAR 13,000 net profit
Real native Odoo20, synthetic isolated QA company. Posted-only sample: SAR25,000 revenue, SAR12,000 expense, SAR13,000 net profit. This screenshot proves the rendered demo report, not a customer close or audited Saudi filing.
AI LOGIC · نسخة AI Logic، نُسخت في 17 نوفمبر 2026 من namaa-react-ksa.ngrok-free.app/demo.html