Case File: Float Changed During the Day, but the Transaction Type Could Not Explain Why
Float was added or removed during operations, but the transaction list no longer had a proper float type, so the movement risked being recorded under “Other.”
There are two fundamentally different ways float can increase
| Float event | Platform/float bucket | Physical cash | Total business assets |
|---|---|---|---|
| External / owner float top-up | Increases | No automatic customer-cash movement | Increases because new value entered business control |
| Cash-to-platform float transfer | Increases | Decreases by same principal | Unchanged; one asset became another |
| Owner float withdrawal | Decreases | No automatic customer-cash movement | Decreases |
| Platform-to-cash rebalance | Decreases | Increases by same principal | Unchanged |
Why the distinction matters
If a LRD 20,000 shortage exists and the owner injects LRD 20,000 of new float, the business may look balanced after the injection. But the original shortage did not disappear; it was financed. This is Float Injection Masking.
Do not let a top-up rewrite history
The system should preserve opening value, transaction movements and the timing of the injection. A top-up should be visible as an owner/manager value event, not blended into customer cash-in or a generic “Other” transaction.
Control lesson
- Use a dedicated external-float type for new value entering the business.
- Use a dedicated transfer type when physical cash is converted to platform float or vice versa.
- Require the source/destination in the note.
- Keep pre-injection variances visible.
- Never treat float injection as sales or fee income.
The public site teaches the distinction between external capital/value and internal transfer. App-specific automation remains private.