Skip to main content
CountyERP+254 728 729474
Practical Guide

County Revenue Report Pack and Metric Dictionary

Use six report definitions and synthetic CSV examples to evaluate collections, unmatched payments, arrears, cashier close, waivers and approval queues.

Updated 15 October 2026 · 6 min read

Illustration of report sheets and a magnifying glass for reviewing exceptions

These original planning resources use synthetic examples. They contain no customer results or personal records. Confirm product behavior and acceptance criteria in your proposed deployment.

Choose reports around decisions

A report should help someone take a defined action. Before choosing dashboard charts, agree the report owner, reporting period, filters, source records and treatment of adjustments. A large report count does not establish usefulness or accuracy.

This pack contains six synthetic report examples for evaluation. They are not customer records, production exports or proof that a specific product edition generates these formats. Each sample is independent unless explicitly linked; do not add totals across different report types.

Define the measures before comparing them

Billed means charges raised within the agreed scope. Received means payment records captured under the chosen confirmation rule. Allocated means payments linked to obligations. Settled means funds confirmed through the applicable bank or provider evidence. Outstanding means the amount still due after accepted allocations and adjustments.

Specify whether a report uses event date, posting date or settlement date. Record the timezone and cutoff. Mixing these definitions can create an apparent discrepancy even when the underlying records are complete.

Define the measures before comparing them
ReportDecision and definitionSource check
Daily collectionsReview received amounts by channel for a stated periodUnique receipt references and confirmation state
Unmatched receiptsAssign payments not yet allocated to a billUnallocated amount, age and reviewer
ArrearsPrioritize unpaid obligations at a cutoffDue date, remaining amount and aging convention
Cashier closeInvestigate expected versus counted cashReceipt/adjustment totals and signed count
WaiversReview authorized reductions separately from collectionsOriginal bill, reason and approval record
Approval queueIdentify delayed work by stageStage entry time, owner and current status

Read the synthetic examples correctly

The daily sample records KES 3,000 by mobile money and KES 700 by bank, totaling KES 3,700. The unmatched-payment sample contains the KES 700 bank payment; it is part of the daily total, not additional revenue. The arrears sample shows KES 2,000 remaining on DEMO-B001 after its KES 3,000 allocation against a KES 5,000 bill.

The independent cashier example compares KES 4,500 expected cash with KES 4,400 counted, a variance of minus KES 100 using counted minus expected. The waiver example reduces a separate KES 1,000 obligation by KES 200, leaving KES 800 before payments. A waiver is not cash collected.

The approval example has a synthetic item open for 30 hours against an illustrative 24-hour stage target: 6 hours overdue. Neither the target nor the duration describes a real county’s service level.

Validate a report before relying on it

Select a small known dataset and calculate expected results independently. Change the date range and filters, then trace each aggregate to its source records. Include a reversed entry, a partial payment and an unresolved item in the test.

Retain the definitions and filters with the exported report. Assign an owner to approve changes in logic so comparisons across periods remain meaningful. A change in revenue does not by itself establish software impact: tariffs, coverage, seasonality and payment timing may also change.

Worksheets and next steps

Open the CSV files in a spreadsheet application and adapt the blank fields to your evaluation. Preserve the synthetic labels when sharing example rows. No registration is required.

Prepared as CountyERP editorial guidance. The examples explain review methods and do not certify compliance, prove a live integration or replace an agreed implementation specification.

Use the evaluation workbook to record observations, evidence and unresolved questions.

See How CountyERP Addresses These Challenges

Talk to a CountyERP specialist about your organization’s workflows, reporting requirements and rollout priorities.