Testing
Overview
The Testing phase validates that DDM Program configuration, data exchanges, reporting outputs, and funding instructions are functioning as expected before production deployment.
Successful completion of Testing provides confidence that the DDM Program is configured correctly and ready to proceed to funding and production use.
Testing Approach
Testing consists of two workstreams:
- Account Verification
- User Acceptance Testing (UAT)
All Clients are required to complete Account Verification.
Automated Send-Only and Reciprocal implementations are also required to participate in User Acceptance Testing (UAT).
These activities may occur in parallel. To help avoid delays, Clients are encouraged to complete account verification activities as early as possible while UAT activities are underway.
Important:
- Account Verification is required for all Clients.
- User Acceptance Testing (UAT) is required only for Clients utilizing automated SFTP file transmissions.
Objectives
- Verify account and wire instruction accuracy
- Validate data exchange processes and file formatting
- Confirm report outputs and operational workflows
- Identify and resolve defects, exceptions, or configuration issues
- Ensure readiness for production deployment
Key Activities
Account Verification
A member of the R&T Proof and Control team will contact the designated representative identified on the Client Setup Form to verbally verify the wire instructions provided.
Once wire instructions have been verified, R&T will initiate a one-dollar test wire to the designated account. Upon receipt, the financial institution must return the one dollar to the designated R&T settlement account.
Client Action: Verify wire instructions, confirm receipt of the one-dollar test wire, and return the funds to the designated settlement account.
Important: The one-dollar test wire should not be rejected. Rejection of the wire will delay testing activities and will not satisfy the account verification requirement.
User Acceptance Testing (UAT) (Automated Send-Only & Reciprocal)
User Acceptance Testing validates that data exchanges, reporting outputs, and operational workflows function as expected within the pre-production environment before funding and production deployment.
Automated implementations participate in a User Acceptance Testing (UAT) period of approximately five (5) business days within a pre-production test environment.
During UAT, clients and R&T work together to validate that the implemented solution functions as expected.
UAT Validations
The following validations are performed during UAT:
- File formatting and data accuracy
- Reporting output validation
- Error handling and exception management
- Mock period-end processing validation
- Production readiness verification
Client Action: Review test results, validate expected processing outcomes, and work with R&T to resolve identified issues or exceptions.
→ See: Operational & Systematic Flow – End-to-end processing and system interactions
→ See: Data Exchange & File Options – File formats, transmission methods, and integration requirements
Sample Test Scenarios (Reciprocal)
Test scenarios are modified as needed to align with the specific requirements of each implementation.
| Test Scenario | Input | Expected Result |
|---|---|---|
| Initial Funding & Net Deposit Settlement | This test must consist of purchases to all test accounts. | The Sending Institution's net settlement is a buy into DDM Program or DDM. As a Receiving Institution, and depending on the reciprocity target, the Program Account will also receive a deposit. The deposits belong to customers of other Participating Institutions in the DDM Program network. |
| Net Withdrawal Settlement | This test should consist of a mix of purchases and redemptions, resulting in a net sell. | The Sending Institution's net settlement is a sell from the DDM Program's network of Receiving Institutions. As a Receiving Institution, the Receiving Institution processes the withdrawal from the Program Account. |
| Mid-Month Full Withdrawal | This test may consist of a mix of purchases and redemptions but must include at least one mid-month full withdrawal (principal only). | The Sending Institution's net settlement is a buy into DDM. As a Receiving Institution, and depending on the reciprocity target, the Program Account will also receive a deposit. Interest may or may not be posted to the account. Month-end interest, fees, reconciliation activities, and reporting are reflected in DDM reporting. Whether interest is posted depends on the Sending Institution's decision to pre-fund interest when an account closes mid-month. → See: Pre-Funded Interest – Learn how interest is handled when accounts are closed before month-end and how this impacts reporting and settlement activity. If pre-funding is enabled, interest will appear on reports and be included as part of the daily settlement. |
| Month-End Processing |
| The only change to the Sending Institution's account balances is the posting of accrued interest. The Month-End Position Report provides the data needed to calculate and post interest to the SCG II Account for reciprocal deposits. → See: Month-End Position Report – Understand how month-end interest, fees, reconciliation, and reporting are reflected in DDM reporting. → See: Customer Interest Accruals – Understand how interest is accrued and posted during period-end processing → See: Rate Mechanics – Learn how customer rates impact interest calculations and reporting. |
| Full Withdrawal of All Accounts | This test should include the full withdrawal and closing of all accounts. | Sending Institution's net settlement is a withdrawal from the DDM Program's network of Participating Institutions. As a Receiving Institution, the Sending Institution will also see a withdrawal from the SCG II Account. Interest will or will not be posted to the account that was fully withdrawn. This depends on the Sending Institution's decision to pre-fund interest if an account closes mid-month. If pre-funding, interest will appear on reports and will be included as part of the daily settlement. |
Roles & Responsibilities
Client
- Participate in testing activities and validations
- Review testing outputs and reports
- Complete account verification requirements
- Validate expected processing results
- Sign off on testing completion
R&T Implementation Manager
- Coordinate and support testing activities
- Review testing results and exceptions
- Conduct wire instruction verification
- Initiate and validate the one-dollar test wire
- Approve production readiness
Exit Criteria
The Testing phase is complete when:
- Wire instructions have been successfully verified
- The one-dollar test wire has been successfully completed in both directions
- All UAT test scenarios have been completed and validated (if applicable)
- Any identified defects or exceptions have been resolved or formally accepted
- Required client and R&T testing sign-offs have been completed
- The solution has been approved for production deployment
Successful completion of Testing confirms readiness to proceed to funding and production deployment.
What’s Next
- Awaiting Funding: Complete final readiness activities and prepare for production funding and go-live.
Updated 2 days ago