How Large PMCs Enforce Dual-Control on Every Material Financial Decision
Who this is for
The problem
Property management at scale involves hundreds of financial transactions per month: invoices, supplier payments, journal entries, credit notes. Without a structured approval system, the organisation relies on people being diligent and processes being followed voluntarily. But under workload pressure, shortcuts happen. A bill gets paid without a second signature. A GL journal is posted to fix a mistake without going through a proper process.
The consequences can be severe: a KRA audit finds transactions with no approval documentation, an owner notices an unauthorised expense on their building's P&L, or an internal audit reveals that a payment was made twice because two people approved the same WhatsApp message. External auditors classify this as a material control weakness — it affects the company's reputation and the owner relationships at the core of the business.
What you can achieve
- Every material payment has a documented, timestamped approval chain — external audit-ready by default
- Junior staff cannot post GL journals unilaterally — finance controls are structurally enforced, not voluntary
- Approval via the platform replaces WhatsApp messages — no ambiguity about what was authorised
- Directors spend 30 minutes a day on structured approvals instead of ad-hoc interruptions throughout the day
- Internal audit findings on control weaknesses eliminated — Kokodi's approval trail is the control evidence
- Building owners can be shown documented approval evidence for any expense on their property
The Kokodi workflow
- 1Step 1
Define approval tiers by amount
SetupConfigure amount thresholds: bills under KES 10,000 need one approver; KES 10,000–100,000 need two; above that require director sign-off.
- 2Step 2
Assign approvers by role
SetupMap each approval tier to named users by role. Finance Manager approves tier 1 and 2; Director approves tier 3. Approval permissions are enforced at the system level.
- 3Step 3
Supplier bill submitted by staff
ActionAn accounts assistant creates the bill in Kokodi. It enters a Pending Approval state — it cannot be paid until the approval chain is satisfied.
- 4Step 4
Approver receives notification and reviews
AutomatedThe approver is notified by email. They review the bill details, attached invoice document, and expense account. They approve or reject with a mandatory comment.
- 5Step 5
GL journal approval follows the same workflow
ApprovalManual GL journals — adjustments, corrections, opening balances — are also subject to approval. A junior accountant cannot post a journal unilaterally.
- 6Step 6
Approved transaction locked and immutable
AutomatedOnce approved, the GL posting is locked. Changes require a formal reversal journal, which itself requires approval. Every step is timestamped and attributed.
- 7Step 7
Approval audit report for external review
ReportGenerate a full approval history report for any period: every bill, every journal, who approved it, who rejected it, and when. Handed directly to auditors.
Kokodi features used
Ready to set this up for your portfolio?
Talk to the Kokodi team and get a personalised walkthrough of this exact workflow for your buildings.
Get started
