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

Case File: Remittance Payout, Platform Credit and Provider Settlement Were Being Mixed Together

A remittance “received/out” entry could move the wrong side because payout, immediate platform credit and later provider settlement were not clearly separated.

Field-derived caseTiming + direction riskRIA / MoneyGram / Western Union
Evidence basisOur earlier remittance control workbook explicitly separated remittance send and payout directions. Later TrustPoint revisions added provider receivables because some payouts occur before provider settlement. V20.1 retained the receivable logic but lost the explicit send/payout types, creating ambiguity again.

Four events that must not be collapsed

EventPhysical cashRemittance/platform valueProvider receivable
Remittance send — customer gives cashInOut under the configured prepaid/settlement modelNo automatic change
Payout with immediate platform creditOutInNo automatic change
Payout before provider settlesOutNo premature increaseIncreases
Provider later settlesNo second cash movementIn to actual settlement accountDecreases

The “received out” trap

Words such as “received,” “payout,” “credit,” and “settlement” describe different sides depending on whose perspective is used. A control system therefore cannot safely infer direction from one vague word. The transaction type must say what happened to the business assets.

Which payout type should be used?

If the provider/platform value is credited at the same time the business pays the customer, use an immediate-platform-credit payout path. If the business pays the customer first and the provider will settle later, use Provider Settlement Receivable. When the provider later settles, clear the receivable into the actual settlement account without moving physical cash again.

Control lesson

  • Name remittance send and payout types explicitly.
  • Do not treat delayed settlement as if platform value already exists.
  • Provider Settlement Received increases the actual settlement account and reduces Provider Receivable.
  • Never post a second physical-cash outflow when settlement arrives.
  • Require provider/reference evidence for remittance and settlement entries.

Provider contracts and actual settlement models differ. The public case states the control distinction; each business must configure the real provider behavior and verify it against statements.

Questions this case answers

Frequently asked questions

Is remittance payout always a provider receivable?

No. If the platform credits value immediately, the payout can move cash out and platform value in. If settlement is delayed, a provider receivable is the safer bridge.

What happens when a delayed provider settlement arrives?

Increase the actual settlement/platform account and decrease provider receivable. Do not move physical cash again.

Why was “remittance received” ambiguous?

Because “received” may refer to the customer, agent, provider or platform. Explicit asset-direction transaction names are safer than vague labels.