Saudi SMB finance intelligence
From Qoyod records to a tenant-safe finance command center.
Build a trusted foundation for Saudi SMB financial intelligence: connect Qoyod, normalize financial data, enforce roles and tenant isolation, then prepare for Zakat, forecasting, banking, and anomaly detection.
No write-backCanonical recordsArabic/English foundation
Qoyod connected
Riyadh Trading Co.Finance overview
Qoyod connectedImport status
42 created · 8 updated · 0 failed
Forecasting plannedDesigned for Saudi accounting teams moving from records to intelligence
Saudi SMB accounting contextArabic and English readyRead-only Qoyod importTenant-safe routingZakat-ready data directionPostgreSQL RLS foundation
Why this foundation matters
Advanced intelligence is only as reliable as the financial data beneath it.
Milestone 1 keeps the scope focused: one connector, one tenant-safe data path, and a dashboard that already feels like a product.
Scattered accounting data
Owners and accountants need one normalized view across accounts, contacts, invoices, payments, and ledger rows.
Limited cash visibility
Forecasting is only useful after revenue, expense, and cash movement data is clean and repeatable.
Zakat complexity
Milestone 1 preserves relevant source fields without claiming a completed Zakat calculation engine.
Banking mismatch
Bank feeds and reconciliation arrive later, using the same canonical transaction layer.
Product workflow
A clean path from login to normalized dashboard output.
The app structure is built to scale into later banking, Zakat, ML, and reporting work without rewriting the foundation.
Connect
Start with Qoyod as the first read-only accounting integration.
Normalize
Map source records into tenant-scoped canonical finance tables.
Inspect
Review KPIs, transactions, import status, and clear empty states.
Expand
Add banking, Zakat, forecasting, and anomaly detection after M1 is safe.
Operational dashboard
Built for finance scanning, not decorative analytics.
Overview cards, recent transactions, Qoyod status, import health, and planned intelligence modules are visible without pretending later milestones are finished.
Review transactionsRevenueSAR 49.8K
ExpensesSAR 7.6K
Import status42 created · 8 updated
ZakatPlanned module
Integration roadmap
Qoyod is active first. Other connectors stay clearly planned.
This prevents Milestone 1 from becoming a connector backlog and keeps the canonical data model clean.
Canonical finance layerMilestone 1 data model
QoyodLeanZohoXeroQuickBooksDaftraWafeq
Security and tenancy
Tenant isolation and role control are visible product features.
The dashboard experience reflects the same permission model that protects integrations and financial records.
Tenant context
Every dashboard page loads tenant context before reading data.
Role checks
Owner, admin, accountant, and viewer actions are shaped by server-side permissions.
Database isolation
PostgreSQL RLS policies are part of the foundation, not a later hardening task.
Milestone discipline
View planned connectorsFuture modules are prepared, not over-promised.
Zakat, Lean Open Banking, Zoho, Xero, QuickBooks, Daftra, Wafeq, forecasting, and anomaly detection remain planned placeholders until ownership and milestone scope are confirmed.
FAQ
Milestone 1 scope
Is Qoyod the only active connector?
Yes. Qoyod is the only active Milestone 1 connector. Lean, Zoho, Xero, QuickBooks, Daftra, and Wafeq stay planned.
Does this calculate Zakat?
No. Milestone 1 keeps Zakat as a planned module while preserving useful tax and source fields.
Is Arabic supported?
Yes. Public pages, auth pages, dashboard navigation, and RTL/LTR layout support Arabic and English.
Is this production complete?
Not yet. The foundation is structured for real auth, PostgreSQL persistence, and live Qoyod credentials to be wired next.