How to Record E-Wallet Loads (Stored Value Liabilities)
Accounting for the receipt of funds from a user to 'top up' a digital wallet, creating a fiduciary liability.
| Account Name | Type | Debit ($) | Credit ($) |
|---|---|---|---|
| Cash - Safeguarding Account | Asset (+) | 500.00 | - |
| User Stored Value Liability (E-Wallet Balance) | Liability (+) | - | 500.00 |
💡 Accountant's Note
When a user tops up their wallet (via bank transfer or card), the FinTech does not earn revenue. The cash is an asset, and the balance in the app is a liability representing the user’s claim on those funds. Under Electronic Money (E-money) regulations, these funds must usually be moved immediately to a safeguarded bank account to protect the consumer.
Practitioner & Systems Framework
💻 ERP Architecture
The 'User Ledger' in the FinTech's app acts as the sub-ledger. The G/L must be reconciled daily to ensure the sum of all individual user balances matches the total 'Stored Value Liability' account.
⚠️ Audit Flags
Reconciliation Gaps. If the sub-ledger and G/L are out of sync, it suggests technical 'double-spending' bugs or unrecorded deposits, which are high-risk for regulatory audits.
📄 Required Documentation
Daily user balance report, safeguarding bank statement, and deposit logs.
Automate this entry with the JEH Accounting Suite
Stop doing manual entry. Our VBA-powered ERP automatically generates your ledgers, Trial Balance, and Financial Statements.
No Subscriptions. Own your data.
Expert Analysis by Qusai Ahmad
General Accountant Supervisor & IFRS Specialist
Specialized in SAP GUI automation and Middle Eastern tax compliance. Building digital tools for the next generation of finance leaders.
Related Journal Entries
Discussion & Community Questions
Loading comments...