Fina
Property management from the Ejar lease to collected rent and closed repair jobs
-
At a glance
Sector
Real estate
Platforms
Web · iOS · Android · WhatsApp
Modules
9
Integrations
8
Screens
4
Total duration
22 weeks
Fina brings buildings, units and tenants into one platform, registers leases on the Ejar network, and generates rent schedules collected through SADAD, mada and Apple Pay, with bank transfers matched automatically. It chases arrears with WhatsApp reminders, routes repairs to technicians under an SLA, issues owner statements and e-invoices for commercial units, and flags likely late payers before the due date.

-
Challenge
-
01
Leases live in Ejar and payments in spreadsheets, so owners learn who paid and who is late only at month end.
-
02
Bank transfers arrive without a clear reference, and accountants match them to tenants and instalments by hand.
-
03
Arrears are chased through scattered calls with no documented sequence, and grow before they reach a formal notice or an enforcement request.
-
04
Repair requests come by phone and WhatsApp, with no record of time to fix or parts cost per unit.
Who it is built for
-
Owner
A clear monthly statement and the net income paid on time
-
Property manager
Occupancy, collection, arrears and renewals on one board
-
Tenant
Pays, requests repairs and views the lease from the phone
-
Technician
Today’s jobs with location and parts, and photo proof of completion
-
Accountant
Automatic bank matching and tax invoices for commercial units
-
Modules
What the system does
Connected modules working on one set of data.
-
01
Properties & units
Buildings, units, amenities and the national address of each unit
-
02
Leases & Ejar
Create, register, renew and close leases through Ejar
-
03
Schedules & collection
A schedule per lease, collected via SADAD, mada and Apple Pay
-
04
Bank reconciliation
A virtual IBAN per lease and automatic transfer matching
-
05
Arrears follow-up
Stepped WhatsApp reminders, then a documented notice and a file ready for enforcement
-
06
Maintenance
Tenant-app requests, technician dispatch, SLAs and spare parts
-
07
Owner statements
Income, expenses, management fees and the owner’s net payout
-
08
Meters & e-invoicing
Sub-meter readings and e-invoices for commercial units
-
09
Portfolio dashboards
Occupancy, collection, arrears ageing and renewals
Where the AI works
-
AI · 01
A model scores the risk of each instalment being late before it falls due, from payment history, transfer patterns and open repair requests, so early reminders go only to those who need them.
-
AI · 02
A private in-Kingdom language model drafts each renewal offer with a proposed rent based on local comparables and the rent rules in force, for the manager to review before it goes out.
-
AI · 03
Smart matching links each bank transfer to the right lease and instalment from name, amount and reference, even with spelling variants or partial payments.
-
AI · 04
Repair requests are classified from text and photos into plumbing, electrical or AC, with a suggested priority and likely parts.
-
Screens
The system as the client's team and customers use it.



-
Architecture
Independent services, in-Kingdom data, and integrations over documented APIs.
Channels
- Tenant app: iOS & Android
- Technician app: Jobs, parts & photos
- Manager console: For managers & accountants
- Owner portal: Statements & payouts
Edge
- API gateway: Routing & rate limits
- Identity: Nafath & per-portfolio roles
Services
- Lease service: Units, leases & renewals
- Billing & collection: Schedules, invoices & reminders
- Reconciliation: Transfer & IBAN matching
- Maintenance service: Requests, SLAs & parts
- Owner ledger: Statements, fees & payouts
AI
- Late-payment model: Risk per instalment
- Renewal drafting LLM: Private in-Kingdom model
- Payment matcher: Links transfers to leases
- Request triage: Classifies text & photos
Data
- PostgreSQL: System of record & ledger
- Redis · BullMQ: Reminder & job queues
- Object storage: Leases & photos in-Kingdom
Integrations
- Ejar: Lease registration
- SADAD · mada · Apple Pay: Payment channels
- Bank API: Virtual IBANs & statements
- ZATCA Fatoora: E-invoicing
- WhatsApp Business: Reminders & notices
Connections
- Tenant app to API gateway
- Technician app to API gateway
- Manager console to API gateway
- Owner portal to API gateway
- API gateway to Identity
- API gateway to Lease service: REST
- API gateway to Billing & collection
- API gateway to Maintenance service
- API gateway to Owner ledger
- Billing & collection to Reconciliation
- Reconciliation to Owner ledger
- Lease service to Renewal drafting LLM
- Billing & collection to Late-payment model
- Reconciliation to Payment matcher
- Maintenance service to Request triage
- Lease service to PostgreSQL
- Billing & collection to Redis · BullMQ: jobs
- Owner ledger to PostgreSQL
- Maintenance service to Object storage
- Lease service to Ejar: API
- Billing & collection to SADAD · mada · Apple Pay
- Reconciliation to Bank API: statements
- Billing & collection to ZATCA Fatoora: e-invoice
- Billing & collection to WhatsApp Business
Stack
- Next.js
- NestJS
- React Native
- PostgreSQL
- Redis · BullMQ
- Python · FastAPI
- Docker
- Kubernetes
-
Workflow
From lease to owner statement
-
01
Create the lease & send it to Ejar
Property managerLease service · Ejar
-
02
Tenant approves via Nafath
TenantEjar · Nafath
-
03
Generate schedule & virtual IBAN
AutomaticBilling · Bank API
-
04
Risk-based reminder before the due date
AutomaticLate-payment model · WhatsApp
-
05
Collect & reconcile
Tenant, then automaticSADAD · mada · Bank API
-
06
Tax invoice for commercial units
AutomaticZATCA Fatoora
-
07
Arrears follow-up & notice
Collections officerBilling · WhatsApp
-
08
Month close & owner payout
AccountantOwner ledger · Bank API
-
Data & API
The core entities and relations, and a live example from the API.
Party
- iduuidPK
- roleenum(owner,
tenant) - national_idtext
- cr_numbertext
- nametext
- phonetext
- vat_numbertext
- ibantext
Property
- iduuidPK
- owner_iduuidFK
- nametext
- citytext
- districttext
- national_addresstext
- typeenum(residential,
commercial, mixed)
Unit
- iduuidPK
- property_iduuidFK
- codetext
- typeenum
- area_m2numeric
- roomssmallint
- meter_idstext[]
- statusenum(vacant,
leased, maintenance)
Lease
- iduuidPK
- unit_iduuidFK
- tenant_iduuidFK
- ejar_numbertextunique
- starts_ondate
- ends_ondate
- annual_rentnumeric
- frequencyenum
- virtual_ibantext
Instalment
- iduuidPK
- lease_iduuidFK
- due_ondate
- amountnumeric
- vatnumeric
- statusenum
- paid_attimestamptz
- late_probreal
Payment
- iduuidPK
- instalment_iduuidFK
- channelenum(sadad,
mada, apple_pay, transfer) - amountnumeric
- bank_reftext
- matched_byenum(auto,
manual) - received_attimestamptz
WorkOrder
- iduuidPK
- codetextunique
- unit_iduuidFK
- categoryenum
- priorityenum
- technician_iduuidFK
- sla_due_attimestamptz
- partsjsonb
- statusenum
OwnerStatement
- iduuidPK
- owner_iduuidFK
- periodtext
- collectednumeric
- expensesnumeric
- mgmt_feenumeric
- net_payoutnumeric
- paid_attimestamptz
- Party 1—∞ Property
- Property 1—∞ Unit
- Unit 1—∞ Lease
- Party 1—∞ Lease
- Lease 1—∞ Instalment
- Instalment 1—∞ Payment
- Unit 1—∞ WorkOrder
- Party 1—∞ OwnerStatement
/v1/leases
Create a lease and send it to Ejar for registration
Request
{
"unit_id": "unt_narjis_a204",
"renewal_of": "lea_01JF3B8X2K",
"tenant_id": "pty_01HX9P4D7M",
"starts_on": "2026-12-15",
"ends_on": "2027-12-14",
"annual_rent": 60000.00,
"frequency": "monthly",
"channels": ["sadad", "mada", "apple_pay", "transfer"]
}
Response
{
"id": "lea_01JGQ7W2NC",
"status": "pending_ejar_approval",
"ejar": { "request": "EJR-2026-7741203", "awaiting": ["tenant_nafath"] },
"virtual_iban": "SA62 8000 0000 6080 1427 7310",
"schedule": { "instalments": 12, "first_due": "2026-12-15", "amount": 5000.00 }
}
Webhook event · payment.matched
{
"event": "payment.matched",
"lease": "lea_01JF3B8X2K",
"instalment": "12/12",
"channel": "transfer",
"amount": 5000.00,
"currency": "SAR",
"matched_by": "auto",
"confidence": 0.98,
"at": "2026-11-15T08:14:09+03:00"
}
-
Integrations
-
Ejar
Lease registration, renewal and termination
-
SADAD
A SADAD bill per instalment
-
mada · Apple Pay
In-app payments through a payment gateway
-
Bank API
Virtual IBANs and daily statements
-
ZATCA Fatoora
E-invoices for commercial units
-
Nafath
Tenant and owner sign-in with the national SSO
-
National Address
Property national address checks
-
WhatsApp Business
Payment reminders and repair updates
-
Security & compliance
- Data, leases and backups hosted inside the Kingdom.
- National Cybersecurity Authority Essential Cybersecurity Controls (ECC).
- Personal Data Protection Law (PDPL) alignment, with ID numbers and IBANs masked in screens and logs.
- Data isolated per owner and portfolio, with role-based access for managers, accountants and technicians.
- Payments through PCI DSS-compliant gateways; card data is never stored.
- Maker-checker on owner payouts and IBAN changes.
- Immutable audit trail for every lease, payment and notice.
-
Delivery plan
Clear phases with measurable deliverables.
-
01
Discovery & portfolio audit
- Workshops with property, collections and maintenance teams
- Inventory of properties, units and live leases
2 weeks -
02
UX & architecture
- Tenant and technician app prototypes tested with users
- Ledger and reconciliation design
3 weeks -
03
MVP build
- Properties, leases and payment schedules
- Tenant app, collection and reminders
7 weeks -
04
Integrations
- Ejar, SADAD, mada and Apple Pay
- Bank, ZATCA Fatoora and National Address
4 weeks -
05
Maintenance, owners & models
- Technician app, SLAs and parts
- Owner statements and the late-payment and renewal models
4 weeks -
06
Migration & go-live
- Migrate leases and opening balances
- Phased launch by property
2 weeks
- Total duration
- 22 weeks
- Team
- Project manager, business analyst, 3 backend and frontend engineers, 2 mobile engineers, an ML engineer, QA and DevOps.
Performance
- 95%+ Transfers matched to a lease automatically
- < 24h Owner statement sent after month close
- < 4h Technician on site for an urgent request
- 99.9% Availability
