Joint account mandate testing verifies that banking software applies the configured authority rules for a jointly held account. It checks which account holders can perform actions, whether one or several approvals are required, and how the rules affect transactions and access. Tests also confirm that unauthorised actions are rejected and that the result is recorded consistently across relevant channels and services.
What joint account mandate testing covers
A mandate defines authority for an account, such as who may view information, make a payment, amend account details or approve a transaction. The rules vary by product and customer agreement. A system may require approval from every holder, allow either holder to act alone, or apply different rules according to transaction type or value.
Testing should verify the configured rules for each in-scope action. It should also check mandate status and effective dates, where these are part of the system, and confirm that a change or revocation takes effect as specified. Account ownership, user authentication and mandate authority are related but distinct: a user may sign in successfully and still lack authority for a particular action.
Test design and preconditions
Start with the applicable business rules and a controlled test account. Set up test users for each holder, the mandate configuration, suitable balances and transaction data, and any required approval channels. Confirm that the test environment contains the intended configuration. Environment drift or stale test data can make a correct rule appear to fail, or conceal a defect.
Use a decision table to cover authorised and unauthorised combinations. For example, where the configured rule requires both holders to approve every outgoing transfer:
| Action | Holder A approval | Holder B approval | Expected result |
|---|---|---|---|
| Submit transfer | Yes | No | Remains unauthorised; no payment is released |
| Submit transfer | Yes | Yes | Authorised for processing |
| View account details | Yes | Not required by the rule | Access follows the configured viewing permission |
The example describes a test policy, not a universal banking rule. Include cases for each relevant account action and transaction route. Where limits, currencies, payment types or effective dates change the rule, test those boundaries and combinations as well.
How to verify the result
Check the outcome at the point where the bank enforces authority, such as the payment service or core banking system, as well as in the customer-facing channel. A disabled button is insufficient evidence on its own: a request made through another supported channel or directly to an application programming interface (API) must receive the same applicable decision.
For rejected actions, verify that the transaction is not released or posted, that the response explains the rejection appropriately, and that the audit record identifies the relevant action and approval state. For accepted actions, check that the required approvals are present before processing continues. Where multiple systems hold mandate data, verify that updates propagate as expected and that channels do not apply conflicting versions.
Common failure modes include checking only the user interface, applying an outdated mandate after a change, accepting duplicate or incomplete approvals, and allowing one channel to bypass a rule enforced elsewhere. Tests should also examine retries and concurrent approval attempts where these could change the final authorisation state.
Scope and boundaries
Joint account mandate testing is a form of authorisation and access control testing within banking software testing. It establishes whether the application implements the supplied rules; it does not determine whether the mandate is legally valid or whether the rules meet a bank's policy. Those decisions require appropriate business, legal and compliance ownership. Keep expected results traceable to approved requirements and record the configuration used for each test.
Frequently asked questions
Is joint account mandate testing the same as maker-checker testing?
No. Joint account mandate testing checks authority assigned to account holders or their authorised representatives. Maker-checker testing checks a workflow in which one staff member initiates an action and another reviews or approves it. A banking process may use both controls, so each should have clear expected results.
How should a mandate change be tested while a payment is awaiting approval?
Use the bank's approved rule for in-flight payments to define the expected result. Test whether the pending payment keeps the mandate version in force when it was created or is re-evaluated against the updated mandate, then verify the final approval decision and audit history.
Does passing these tests prove that a mandate is legally valid?
No. Passing tests shows that the software applies the configured rules in the tested conditions. Legal validity and policy suitability require review by the bank's authorised business, legal or compliance functions.