Skip to content
EstateFlow
QistFlow

The plot-file payment engine: schedules, reminders, recovery, transfers.

QistFlow runs the money-over-time side of plot and off-plan sales. It composes any payment plan (booking, confirmation, allocation, periodic installments, balloons, possession), generates a dated schedule per file, posts every payment against it, applies penalties automatically and turns overdue files into recovery lists. Transfers carry the remaining schedule forward under an atomic lock, so a file can never be sold twice.

features
12features
modules
13modules
screens
5screens
webhooks
12webhooks
File GV2-0417 · Plot 14-C
36-month plan · Category B · 10 Marla
Inst. 7 · 05 Aug
PKR 85,000 · paid
Inst. 8 · 05 Sep
PKR 85,000 · paid
Inst. 9 · 05 Oct
PKR 85,000 · due
Balloon · 05 Dec
PKR 500,000 · scheduled
Balance
PKR 2,975,000 · 0 days overdue
Next reminder: 02 Oct on WhatsApp
§ 01Why teams switch

Thousands of files, one spreadsheet, no penalties

  • Schedules are worked out per customer by hand and disagree with the agreement
  • Late-payment surcharge is applied inconsistently, then disputed
  • Recovery is random phone calls, not a list with owners and outcomes
  • A file gets transferred with dues pending, or worse, sold to two buyers
BeforeWith QistFlow
On-time collectionReminders when someone remembers Three reminders per installment with a pay link
PenaltiesManual, inconsistent Applied by rule after grace, shown on the statement
RecoveryNo list, no ownership Monthly list per officer, outcome per row, recovery % measured
TransfersFraud risk Locked, dues-checked, deed auto-generated
§ 02 Features & mechanism

How each part of QistFlow actually works

12 features from the product documentation. Select one to read what it does, the mechanism behind it, the data it holds, the state before and after, and what it connects to.

12 features
Feature 01 of 12

Multi-phase payment-plan engine

Does / why

Down payment, confirmation, allocation, N periodic installments (monthly/quarterly/half-yearly), balloons on set months and a possession charge, defined per project and category.

Mechanism

Admin defines plan components per project and category: down payment %, confirmation, allocation, N periodic installments at a frequency, balloons on specific months, possession charge. The engine turns the template into a formula.

Data

Plan template, unit price, category, down payment, installment count/frequency, balloon months and amounts, possession charge, start date.

Connects to

Booking, Schedule generation, Accounts, Documents.

Before

Plans worked out by hand per customer.

After

A consistent plan attached to the file at booking.

Modules

13 modules, switched on per role. Admins configure rules; everyone else sees only what applies to them.

  • Payment-Plan Engine
  • Schedule Generation
  • Due/Paid Ledger
  • Receipts & Online Payments
  • LPS / Penalty
  • Balloon & Possession
  • Defaulter Management
  • Recovery-Officer Workflow
  • WhatsApp/SMS Reminders
  • Customer Statements
  • Refunds & Cancellations
  • File Transfers
  • Duplicate / Fraud Detection
§ 03 How it runs

One file, start to finish.

A realistic sequence from the documentation, with the state before and after each step. Names and numbers are illustrative.

On mobile

Recovery-officer app (assigned list, call, log outcome, mark collected, offline); customer app (schedule, pay, receipts, statement); dealer portal.

  1. 01

    Booking confirmed

    Plot 14-C, 10 Marla, Category B. The agent selects the 36-month plan: 20% down, 34 monthly installments, two balloons in months 12 and 24, possession charge at month 36.

  2. 02

    Schedule generated

    Thirty-eight dated rows are written to the file. The agreement prints the same schedule. The customer sees it in the app.

  3. 03

    Reminders run

    Three days before each due date a WhatsApp template goes out with the amount and a payment link; again on the day; again after.

  4. 04

    Payment posts

    The customer pays PKR 85,000 by bank transfer. Finance posts it against installment 7; the receipt is sent automatically; the ledger updates.

  5. 05

    Overdue handling

    Installment 9 passes its 10-day grace. LPS of 0.1% per day applies and shows on the next reminder and the statement.

  6. 06

    Recovery list

    On the 1st, the file appears on the recovery list with the dealer’s name. Officer R. Sheikh logs a promise-to-pay for the 15th.

  7. 07

    Transfer

    Two years in, the owner sells. Dues are clear, the lock is acquired, the remaining 14 installments move to the new CNIC, the fee posts and the deed generates.

  8. 08

    Possession

    Balloons and possession charge cleared. The possession checklist opens and handover is documented.

§ 04 Interactive demo

QistFlow, screen by screen

Click the sidebar to move between the overview, lists, records, boards and the settings that drive the rules. Sample data on real layouts.

QistFlow Sep 2026 AB

Receivables & recovery

Green Valley · Phases 1–3 · 4,812 active files
Collections (MTD)
PKR 184.6M
92% of target
Overdue files
611
−4.2% vs Aug
Recovery rate (30d)
71.3%
+3.1 pts
LPS income (MTD)
PKR 4.1M
312 files
Collections vs target (PKR M, by week)
CollectedTarget
Overdue by age
  • 0–30 days26844%
  • 31–6017428%
  • 61–909616%
  • 90+7312%
Recovery list — Officer R. Sheikh · September
5 of 48
FileCustomerDealerDueOverdueOutcome
GV2-0417M. TariqAl-Noor Estate170,00038 dPromise · 15 Sep
GV1-1122S. AbbasDirect255,00064 dUnreachable
GV3-0088N. QureshiCity Marketing85,00012 dPaid
GV2-0930A. RehmanAl-Noor Estate340,00097 dDefaulter · blocked
GV1-0655F. IqbalDirect85,00021 dCallback
Interactive demo · sample data · click the sidebar to switch screens
Reports included

Scheduled to email or exported to Excel and PDF. Every report drills down to the record.

  • Receivables aging (0–30 / 31–60 / 61–90 / 90+)
  • Collections vs target, daily and monthly
  • Overdue and defaulters list
  • Recovery-officer performance and recovery %
  • LPS / penalty income
  • Projected cash flow from schedules
  • Dealer-wise recovery
  • Phase and category-wise outstanding
§ 05 Roles & permissions

Who uses it, and what each role sees

Access is scoped by role, team and field. A dealer never sees another dealer’s file; an agent never exports the database.

Finance / accounts

Ledger, receipts, LPS rules, refunds, bank posting

Recovery officer

Assigned list, tap-to-call, outcome logging, offline

Sales / booking

Plan selection at booking, schedule preview

Dealer

Recovery status of own files; commission tied to collection

Customer

Schedule, receipts, statement and pay link in the app

Management

Receivables aging, collections vs target, defaulters, officer performance

Select a role
What Finance / accounts can do
AllTeamOwnNone
Module ViewCreate / editApproveExportConfigureDelete
Payment-Plan Engine Own Own
Schedule Generation Own Own
Due/Paid Ledger Own Own
Receipts & Online Payments Own Own
LPS / Penalty Own Own
Balloon & Possession Own Own

Own = only records assigned to me · Team = my team’s records · All = the whole organisation. Field-level rules can further hide price, owner or CNIC per role.

§ 06 Automation & Flo

What happens without anyone clicking

Rules run the routine work. Flo, the AI assistant, handles the parts that need language or judgement, and every AI action is logged.

Automations

  • Schedule generation on booking
  • Reminders before, on and after due date
  • LPS after grace period
  • Defaulter flagging and blocking
  • Receipt generation and WhatsApp delivery
  • Monthly recovery-list generation
  • Commission clawback on cancellation
F

Flo in QistFlow

  • Default-risk prediction per file
  • Recovery prioritisation (who to call first)
  • Optimal reminder timing and channel
  • Duplicate and fraud anomaly detection
  • Cash-flow forecasting

Outbound WhatsApp uses approved templates. Low-confidence cases escalate to a person.

§ 07 Integrations & API

Connects to anything, not just the list

Every connector in the catalogue, the full REST API and a webhook for every state change. If it has an API, EstateFlow talks to it.

Every connector below is available to QistFlow. Those most used with it are highlighted; anything not listed connects through the REST API, webhooks or Zapier / Make / n8n.

Lead sources & portals
  • Zameen
  • Bayut
  • Graana
  • OLX Property
  • Meta Lead Ads (Facebook, Instagram)
  • Google Ads lead forms
  • TikTok lead forms
  • Website forms
  • Landing-page builders
  • Chat widget
  • QR / offline import (CSV, Excel)
Messaging & telephony
  • WhatsApp Business API (Meta Cloud API or any BSP)
  • SMS gateways (Telenor, Jazz, Zong, Ufone, Twilio)
  • Email (SMTP, Gmail, Outlook, SendGrid)
  • VoIP / cloud PBX (SIP, Asterisk, Twilio Voice)
  • Call tracking numbers
  • Push notifications (FCM, APNs)
Payments & banking
  • Payment gateways (PayFast, Safepay, JazzCash, Easypaisa, Stripe)
  • Bank transfer / IBFT references
  • Pay links
  • Bank statement import (CSV, MT940)
  • Bank feeds (Enterprise)
  • POS terminals
Maps & GIS
  • QGIS projects (.qgz)
  • PostGIS
  • GeoServer (WMS / WFS)
  • Shapefile, GeoJSON, KML, DXF / CAD import
  • Mapbox, Leaflet, OpenLayers clients
  • ArcGIS / Esri (Enterprise)
  • Satellite imagery providers
  • GPS from field devices
Accounting & finance
  • QuickBooks
  • Xero
  • Sage
  • Odoo
  • Tally
  • SAP / Oracle / Dynamics (Enterprise)
  • FBR e-invoicing
  • Excel / CSV export for any ledger
Identity, documents & e-sign
  • CNIC OCR
  • NADRA verification partners
  • DocuSign
  • Adobe Sign
  • PandaDoc
  • Google Drive
  • OneDrive / SharePoint
  • Dropbox
  • S3-compatible storage
HR & attendance
  • Biometric devices (ZKTeco, Hikvision)
  • Bank payroll files
  • Google Workspace / Microsoft 365 directories
  • SSO: SAML, OIDC, Azure AD (Enterprise)
Community & hardware
  • Boom barriers & RFID
  • ANPR cameras
  • Smart meters (electricity, water, generator)
  • IoT sensors (MQTT)
  • Sales-centre kiosks & touch tables
  • Digital signage
BI & automation
  • Power BI
  • Tableau
  • Looker Studio
  • Metabase
  • Zapier
  • Make
  • n8n
  • Google Sheets
  • Slack / Teams alerts
Getting it

QistFlow runs standalone or with the rest of the suite on the same database. Quotes are per organisation, based on users, plots and files.

  • Demo on your own data
  • Data migration from spreadsheets or your current system
  • Onboarding and WhatsApp template approval
Talk to sales WhatsApp sales
01 Can QistFlow handle plans that are not a simple monthly EMI?

Yes. A plan is composed from components: down payment, confirmation, allocation, periodic installments at any frequency, balloons on named months and a possession charge. Each project category can have its own plan.

02 How are penalties applied?

A rule per project sets the grace period and a flat or percentage surcharge per day or month. Once an installment passes grace, LPS posts automatically to the ledger and appears on reminders and statements.

03 What stops a file being transferred twice or sold to two people?

Every transfer and booking acquires an atomic lock on the unit. Duplicate CNIC and duplicate file checks run in real time, and a defaulter flag blocks transfer and possession until dues clear.

04 Do recovery officers need connectivity in the field?

No. The recovery app caches the assigned list, lets officers call, log outcomes and mark collections offline, and syncs when the phone reconnects.

Book a demo

See QistFlow on your own data.

A 45-minute demo on your own data. We load a sample of your inventory and files before the call, so you see your plots, your plans and your numbers, not a sample scheme.

What you get in the demo
  • One block of your scheme digitised on the live map
  • A booking → schedule → WhatsApp reminder, end to end
  • A file transfer with the lock and dues check
  • A rollout order and a written quote within two days
Request a callback
Reply within a working day
Full demo form

Opens WhatsApp with your details pre-filled to +44 7367 064067. We also log the request so sales can follow up.