Urgent.News

What's breaking now, across thousands of outlets.

Tech

Separating Available, Held, Actual, and Displayed Balances

Why one balance field cannot represent every financial truth in a virtual-account product. “What is the balance?” sounds like a simple question until the system includes pending deposits, withdrawals awaiting completion, provider-reported funds, fees, manual reconciliation, and temporary account restrictions. These values describe different truths. Compressing them into one number makes failures…

In a virtual-account product, distinguishing between available, held, actual, and displayed balances is crucial for accurate financial representation. The ledger balance is the result of locally applied credits and debits, while the held amount represents funds reserved for operations that have not completed. The available balance is what can be spent now, and the actual balance is the latest balance reported by the external account provider.

These four concepts provide a clearer picture of the true financial state. It is essential to treat provider-reported balances as reconciliation evidence, as they may not arrive simultaneously with individual transaction events. By recording reference, direction, amount, balance before and after, transaction type, and metadata with a timestamp, the platform can provide a comprehensive explanation of the customer balance's path.

Additionally, transaction fees should be recorded as separate financial events within the ledger, ensuring transparency and proper accounting.

Brief written by urgent.news from Dev.to's own syndicated text. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in Tech

Combining Automated Payment Rails with Human Fallback

Designing one transaction lifecycle that can move safely between API-based payouts and operational fulfillment. Payment coverage is rarely uniform. One destination may support an immediate API payout.

  • Automated and manual fulfillment treated as distinct strategies within unified customer lifecycle
  • Routing layer determines fulfillment method based on destination and payment method
  • Manual fallback should only occur when appropriate, not for every provider error

More from Saturday 10 October →