KENYA · GUIDE 0735 · EDITION 4.2
Property expense tracking setup in Kenya: Operations and Quality Checks
Deliver the agreed result consistently
Agree expense categories, properties covered and approval responsibilities, separating payment records from commitments, reimbursements and estimates that have not yet become an actual settled cost.
The operating sequence for this offer is:
- Agree expense categories and obtain the authorized receipts and payment records for a defined period, documenting missing opening information before starting.
- Enter only source-backed expenses and check for duplicates, keeping original references so the client can trace every recorded amount without relying on a summary.
- Reconcile available totals and deliver unresolved items separately, explaining the system's limits without providing an unqualified tax opinion or changing unsupported source facts.
Put acceptance into the job record
Totals reconcile to available sources and assumptions are visible; no tax opinion is implied.
Reconcile a sample month against receipts and payment evidence, checking whether a manager can trace each property total back to the supporting transaction and explanation.
Inspect at the point where a correction is still possible, then again at handover. Record rejected or incomplete output separately from accepted output. A completed task is not automatically an accepted task, and an invoice does not establish that the customer received the right result.
Measure real capacity
Time preparation, the main operation, transport, cleaning, approvals and correction as applicable. The slowest stage determines how much you can promise. Where two orders need the same person, space or equipment at the same time, resolve the conflict before confirming both deadlines. An additional enquiry should not erase a commitment already made.
| Operating checkpoint | Evidence for this business |
|---|---|
| Before starting | Agree expense categories, properties covered and approval responsibilities, separating payment records from commitments, reimbursements and estimates that have not yet become an actual settled cost. |
| During delivery | Enter only source-backed expenses and check for duplicates, keeping original references so the client can trace every recorded amount without relying on a summary. |
| At acceptance | Reconcile a sample month against receipts and payment evidence, checking whether a manager can trace each property total back to the supporting transaction and explanation. |
| At the pilot review | Log unmatched receipts, classification decisions, duplicate corrections and user retrieval questions, keeping the approved category definitions so future entries remain comparable across reporting periods and properties. |
Keep a correction and escalation rule
When inputs, access, specifications or customer instructions change, pause the affected work and confirm the effect on time and cost. Do not quietly lower the acceptance standard to avoid a delayed delivery. Keep rework caused by your error distinct from a customer-requested change of scope and agree the remedy clearly.
A useful-looking tracker misleads when transfers are counted as expenses, one invoice appears twice or repairs are assigned to the wrong property without supporting references.
Retain the minimum records needed to investigate a complaint without disclosing unrelated personal information. Use measured delivery and actual acceptance as the basis for expanding capacity, rather than the maximum theoretical output of a tool or production line.
Operating control points for this exact offer
| Sequence | Work method | Release checkpoint |
|---|---|---|
| 1 | Count the 60 documents and establish property, period, currencies and approved budget source. Give each receipt an ID; record missing invoice numbers, unreadable amounts and documents relating to another property. | The intake is complete and no receipt is silently discarded as irrelevant. |
| 2 | Enter supplier, document date, gross amount, stated tax where present, category, approval, payment evidence and source ID separately. A document being an invoice does not mean it was paid. | Payment and approval statuses can remain unknown without changing the original amount. |
| 3 | Ask the owner/accountant to resolve shared costs, deposits, refunds and ambiguous categories. Match payment evidence by reference and amount; retain possible duplicates for review instead of deleting them because totals look high. | Every non-routine accounting decision has an approval/reference rather than the data clerk’s guess. |
| 4 | Compare approved-period spending with the approved budget using consistent scope. Fictional example: KSh 27,000 actual minus KSh 25,000 budget equals KSh 2,000 over budget; this is a variance, not proof of misuse. | Totals reconcile to accepted source rows and unresolved items are shown separately. |
| 5 | Protect calculation cells from accidental edits while restricting actual file access separately. Test a correction and refund, then hand over the source register, monthly views and unresolved list for owner/accountant acceptance. | The report is labelled organized records, not audited accounts or tax-ready certification. |
Do not substitute a tick for an observation: record the count, measurement, approved sample or evidence reference used at each checkpoint. Mark unresolved work as held and identify who can approve the recheck.
Diagnose a failure before repeating it
| Observed symptom to investigate | Check the cause | Proposed response |
|---|---|---|
| Same repair invoice appears twice | Match supplier reference, amount and source copies. | Flag duplicate evidence and obtain approval before removing a posting. |
| Budget comparison is misleading | Check whether periods and included expense categories match. | Align scopes and disclose excluded/unresolved costs. |
| Paid status lacks evidence | Review bank/receipt reference provided by the authorized owner. | Leave payment unverified; do not infer it from an invoice stamp alone. |
These are diagnostic prompts, not proof of the cause in a real incident. Separate suspect output, record any correction and repeat the relevant acceptance check. Link rejected units, rework time, replacement materials, customer credits and collection delays to the actual job result.