How to use the Test Mode

Within Modern Treasury, you have the ability to test out any and all capabilities with the simple toggle of a button. Test mode can be toggled on with the dial on the left hand navigation bar underneath Settings (dial will set on the left for testing).

Some portions of test mode are environment-independent, meaning they have no Live/Test distinction and changes to these shared resources are visible across both environments. This is done in part to speed planning and allow a cleaner experience when building your application. Currently the following resources are shared: Organizations, Users, and Groups.

In order to fully test out the ins and outs of testing, you will want to make use of the different test accounts and types we have available. All payment types are available for testing except for checks and lockbox testing.*

Internal Accounts

Your organization will work with two fake banks:

  • Gringotts Wizarding Bank (GWB)
  • The Iron Bank of Braavos (IBB)

You will have access to accounts with both of these banks. These accounts are known as internal accounts.

The most important distinction to note between these two accounts is that one actively will simulate what you would see in a live account (Gringotts). The other account is stagnant so you can cancel out specific actions within the platform (Iron Bank of Braavos).

Creating Counterparties

Counterparties are the entities outside of your organization that you want to send or receive money from. In order to test, you will want to set up counterparties with a real routing number (you can use your current bank routing number for testing) and a dummy account number. Upon setting up a counterparty, you will be able to test payment orders.

Simulating Payment Orders

Payment orders are the instructions to move money to or from your bank account as an ACH, wire or check.

Payment orders which use Gringotts as the originating account will be “sent” to the bank every minute and transactions will post immediately after.

The Iron Bank does not process any payment orders, meaning once a payment order has been created with the Iron Bank as the originating account, it will not change statuses - you should use these payment orders to test cancellations.

Simulating Expected Payments

An Expected Payment is information about a payment you expect to occur in your bank account that is not initiated by Modern Treasury. Our system will connect expected payments to transactions in order to keep your account reconciled.

Within testing, Expected Payments at Gringotts will always have a transaction created for them. Our system knows to use the data in the expected payment to create a transaction that looks as close as possible to the expected payment. The transaction will be created in about 10 seconds and automatically reconciled to the transaction.

Expected Payments at The Iron Bank will remain in an unreconciled state and no corresponding transaction will be created. You will have the ability to archive expected payments so that you can see how to delete if the expected payment is no longer needed or was reconciled differently.

Simulating Balances

When you are live and in production, your bank will provide balances for your bank accounts throughout the day (based on their update schedules). These balances will typically be paired with information about transactions that have occurred in your bank account. Note that this will only happen in the Gringotts bank accounts.

As you submit payment orders or expected payments, the dashboard will show how the balance is affected when a new transaction is created. The dashboard will also show you the the prior day balances alongside current balances.

*If you have any questions about testing or need your testing enabled for checks/lockbox activity, reach out to your account manager for more help.

Did this answer your question?