Appearance
Deposit Account Opening To Close
This guide explains how to test a full deposit flow: configure the product, open an account, fund it, apply restrictions, process transactions, run scheduled activity, and close or reactivate the account where policy allows.
Use this example for savings, current, fixed deposit, community fund, or other deposit products where account status, mandates, interest, fees, and accounting must stay aligned.
Workspace Reference
| Workspace | How Users Reach It | What Users Usually Do There |
|---|---|---|
| Parties | Parties -> Individual Clients, Groups, or Organizations | Create or confirm the account holder and signatories. |
| Deposit Products | Deposits -> Setup -> Products | Configure account rules, currency, limits, interest, fees, flags, GL mappings, and availability. |
| Deposit Accounts | Deposits -> Operations -> Accounts | Create, validate, activate, transact, review detail, freeze, close, or reactivate accounts. |
| Mandates | Deposits -> Operations -> Mandates | Define who can operate the account and what approvals are required. |
| Holds And Blocks | Deposits -> Operations -> Account Holds / Blocked Funds | Restrict balances or account activity for liens, disputes, controls, or pending items. |
| EOD Processing | Deposits -> Operations -> EOD Processing | Run interest, fees, dormancy, maturity, and scheduled product behavior. |
| Accounting And Reporting | Accounting and Reporting workspaces | Review balances, statements, GL posting, and customer/account reports. |
Scenario
Mirembe Traders opens a business savings account.
The operations and finance teams must:
- confirm the organization party record
- confirm the deposit product is ready
- open and validate the account
- activate the account
- fund the account
- apply a temporary hold
- process a withdrawal or transfer after release
- run EOD activity where product rules apply
- review account statement and accounting
- close or reactivate the account only when policy allows it
End-To-End Flow
| Step | Workspace | Business Meaning |
|---|---|---|
| 1 | Parties | Account holder and signatory records are confirmed. |
| 2 | Deposit Product Setup | Product behavior and accounting are ready before account opening. |
| 3 | Deposit Accounts | Account is created and validated against product rules. |
| 4 | Activation | Account becomes available for transactions. |
| 5 | Funding | Opening deposit or first deposit creates balance. |
| 6 | Mandates | Account operating authority is confirmed. |
| 7 | Holds Or Blocks | Available balance is restricted where policy requires it. |
| 8 | Transactions | Deposits, withdrawals, transfers, or instructions are processed. |
| 9 | EOD | Interest, fees, dormancy, maturity, or scheduled activity is reviewed. |
| 10 | Closure Or Reactivation | Account lifecycle actions are tested with policy controls. |
| 11 | Reporting And Accounting | Statements, balances, and GL outcomes are reviewed. |
1. Confirm Account Holder
Open Parties.
Confirm:
- account holder is active and approved
- organization or individual details are complete
- signatories or representatives are captured where required
- contact and identification details are current
- duplicate party records do not exist
Important party checks:
| Field Or Detail | Why It Matters |
|---|---|
| Party name | Appears on account, statement, mandate, and reporting views. |
| Party type and role | Controls eligibility and downstream account context. |
| Contact details | Used for communication, alerts, statements, and follow-up. |
| Signatory details | Supports mandate and authorization controls. |
| Approval and active status | Inactive or unapproved parties may be blocked from account opening. |
2. Confirm Deposit Product
Open Deposits -> Setup -> Products.
Before account opening, confirm:
- product is active
- holder type is allowed
- currency is correct
- minimum opening balance is understood
- transaction limits are configured
- fees, interest, dormancy, and maturity rules are understood
- mandates, holds, blocked funds, fixed deposits, or savings plan behavior is clear
- GL mappings are ready
Important product settings:
| Setting | User Impact |
|---|---|
| Product Type | Determines account behavior, such as savings, current, fixed deposit, or special-purpose account. |
| Currency | Controls account currency and allowed transactions. |
| Minimum Opening Balance | Blocks account opening or activation when opening balance is too low. |
| Interest Settings | Controls whether and how interest is calculated. |
| Fees And Pricing | Controls service charges, maintenance fees, withdrawal fees, or penalties. |
| Product Flags | Enable or restrict features such as withdrawals, holds, dormancy, fixed deposit behavior, or account linking. |
| GL Mappings | Required for posting deposits, withdrawals, fees, interest, and closing entries. |
3. Create Deposit Account
Open Deposits -> Operations -> Accounts.
Use Create Deposit Account.
Important account-opening fields:
| Field | Meaning For The Test Flow |
|---|---|
| Deposit Product | Product whose rules the account follows. |
| Holder Type | Individual, group, organization, joint, or another enabled holder structure. |
| Account Holder | Mirembe Traders or the relevant party. |
| Business Unit | Branch or operating unit responsible for the account. |
| Opening Balance | Initial funding amount where captured during opening. |
| Currency | Account currency, usually inherited or constrained by product. |
| Mandate or Signatory Setup | Who can operate or approve account instructions. |
| Notes | Opening reason, source of funds, or exception explanation. |
Use Validate Opening where available. Validation should catch product restrictions, eligibility gaps, missing holder details, branch restrictions, and opening-balance problems before activation.
4. Activate The Account
Activate only when:
- opening details are correct
- product rules pass validation
- required approvals are complete
- mandates or signatories are ready where required
- initial funding policy is satisfied
Expected test result:
- account status changes to active or the tenant's equivalent usable status
- permitted transaction actions become available
- statement and balance review show the correct opening state
5. Fund The Account
Use the transaction or deposit action available from Deposits -> Operations -> Accounts or the teller/payment workflow available to your role.
Important funding fields:
| Field | Meaning |
|---|---|
| Deposit Account | Account receiving funds. |
| Amount | Funding amount. |
| Transaction Date | Date used for transaction and accounting review. |
| Channel | Cash, bank, wallet, transfer, cheque, mobile money, or another configured channel. |
| Reference | Receipt, teller, bank, cheque, mobile-money, or internal reference. |
| Narration | Explanation that appears in review and statement context. |
After funding, confirm available balance, ledger balance, statement history, and posting status.
6. Configure Mandates
Open Deposits -> Operations -> Mandates.
Use mandates when the account requires controlled operating authority.
Check:
- signatories are correct
- approval limits are correct
- mandate status is active
- execution history is visible where instructions run
- mandate changes are approved before live use
Mandates should prevent unauthorized withdrawals or account instructions.
7. Apply And Release Holds Or Blocked Funds
Open Deposits -> Operations -> Account Holds or Deposits -> Operations -> Blocked Funds.
Use restrictions for liens, disputes, pending instructions, legal controls, security, or internal review.
Important restriction fields:
| Field | Meaning |
|---|---|
| Deposit Account | Account being restricted. |
| Amount or Scope | Balance amount or activity area affected. |
| Reason | Why the hold or block exists. |
| Effective Date | When the restriction starts. |
| Expiry or Release Date | When the restriction should end where known. |
| Notes | Supporting explanation, document reference, or approval reason. |
Expected test result:
- available balance changes when funds are blocked
- ledger balance remains explainable
- withdrawal is blocked or reduced while the restriction is active
- release restores availability according to policy
8. Process Withdrawal Or Transfer
After restrictions are clear, process a withdrawal or transfer where product rules allow it.
Before submitting:
- account is active
- available balance is sufficient
- mandate requirements are satisfied
- product limits allow the amount
- channel and reference are correct
- fees or charges are understood
Expected test result:
- balance decreases correctly
- statement shows the transaction
- fees or charges appear where configured
- accounting posts to expected cash, bank, wallet, clearing, or deposit liability accounts
9. Run Or Review EOD Processing
Open Deposits -> Operations -> EOD Processing.
EOD may process:
- interest
- maintenance fees
- dormancy checks
- maturity behavior
- sweeps or mandates
- fixed-deposit accruals
- scheduled account changes
After EOD, review exceptions before relying on balances for the next business day.
10. Close Or Reactivate
Use close only when:
- balance policy is satisfied
- holds and blocked funds are resolved
- pending mandates or instructions are complete
- fees, interest, and accounting are up to date
- approvals are complete
If policy allows reactivation, test reactivation with the same care: confirm why the account was closed or restricted and whether product rules still allow activity.
11. Review Statements, Reports, And Accounting
Review:
| Area | Question It Answers |
|---|---|
| Account detail | Is status, holder, product, balance, and restriction state correct? |
| Statement | Does the customer-facing transaction history explain the balance? |
| Holds and blocked funds | Is available balance lower for a valid reason? |
| EOD output | Did scheduled interest, fees, dormancy, or maturity activity run? |
| GL Journals | Did deposits, withdrawals, fees, and interest post correctly? |
| Reports | Do product, branch, and account totals agree with account detail? |
Pass Criteria For The Test Flow
The flow is complete when:
- account holder is approved and correctly selected
- product validation controls opening behavior
- account activates only after required checks
- funding updates balance and statement history
- holds or blocks restrict available balance correctly
- withdrawals or transfers respect account status, mandates, limits, and available balance
- EOD activity is visible and exceptions are reviewed
- closure or reactivation follows policy
- reports and accounting agree with operational account history
Common Problems
| Problem | What To Check |
|---|---|
| Account cannot open | Product status, holder type, business unit, KYC, opening balance, and approval requirements. |
| Funding does not post | Channel setup, account status, currency, business date, and GL mapping. |
| Withdrawal is blocked | Available balance, holds, blocked funds, mandate, account status, and product limits. |
| Interest or fee missing | Product flags, pricing, EOD run status, account status, and accounting setup. |
| Closure fails | Pending balance, holds, blocked funds, pending transactions, mandates, fees, or approval status. |
