Daily cash + float control for mobile money, POS, remittance and agent-banking businesses
Methodology

Methodology, Source Policy & What We Keep Private

Enough transparency to verify the control principle. Not enough public detail to copy the product’s implementation.

Public control method

Freeze the period

Confirm the last transaction for the shift has been entered before calculating expected balances.

Calculate expected balances

Use opening positions plus valid recorded movements. Keep provider/platform balances and physical cash distinguishable.

Count actual balances independently

Count physical cash and enter actual provider or platform closing balances without changing the expected side to make it match.

Investigate the variance

Review settlements, internal transfers, receivables, reversals, fees, FX and missing evidence. Record the cause without treating “explained” as “resolved.”

Public case files remove staff/customer identities and sensitive details. When a worked example uses a number, the amount is simplified to explain the control principle rather than presented as a specific customer loss. We do not publish proprietary app formulas, thresholds, permission logic, risk scoring, backend architecture or roadmap.

The authority library is informed by continuing field use, reconciliation testing and technical QA. Repeated control problems include provider settlement timing, platform credit classification, customer and provider receivables, internal versus external money movement, fee/commission classification, reversals, staff transfers, dual-currency FX direction, missing references and expected-versus-actual platform mismatches. Public lessons are updated when testing exposes a safer or clearer control method.

Field-derived evidence and case-study policy

Why we do not publish the full control logic

The public site explains the accounting and control principle and buyer-facing workflow. Detailed formulas, implementation logic, app rules, thresholds and product roadmap are proprietary and are intentionally not published.

Authoritative sources

Verification policy

Provider features, pricing, regulations and directives can change. Date-sensitive claims are reviewed against current official sources. Product pages avoid claiming that the system prevents theft or replaces licensed audit or accounting functions.