Transaction Hub: Manage Payments

These steps assume you have already set up the following:
Banks
Bank accounts
Payment destinations (in each bank account’s Payment > Destinations tab)
Approver types
Approval agendas
Approval rules
Payment templates
Applicable types of payments:
Single-entry payment
Multiple-entry payments
Internal transfer

Please follow the above links to complete any setup steps that you may have missed before continuing.

Introduction to transaction status workflow

The Transaction Status Workflow screen shows the payments you have access to. With the proper level of access, you can edit, approve, and perform other actions on payments here.

The template actions performed in this screen are the same as the actions you can perform in the Transaction List screen. The difference is this screen has more robust search options and it divides payments by status rather than presenting them in a single list.

mceclip4 (5).png

mceclip5 (4).png

Open the Transaction Status Workflow

Go to Payments > Transaction > Transaction Status Workflow.
The Transaction Status Workflow screen opens.
- When initially visiting this screen, it typically opens to the Search screen. After running a search and then returning, it typically opens to the Results screen.
- You can move between the Search and Results screens using the buttons at the top right of the screen.

Search for payments by status

Open the Search screen for the transaction status workflow.
Select the search parameters:
- Date Type: Set the date type to search for templates:
  - Trn. Date: Date of the payment (initiation date, not necessarily value date).
  - Value Date: Date the payment was debited or credited to the bank account.
  - Process Date: Date the payment was created in Ripple Treasury.
- Range: Set the range of dates to search. Enter the dates or use the calendar icon to select the dates.
- Rows Per Page: Use the drop-down list to select the number of rows to display per page in the search results.
- Transaction Type: Select the payment type to search by:
  - All: Include all payments regardless of whether credit and debit are locked.
  - Repetitive: Payments where both credit and debit sides are locked.
  - Free Form: Payments where neither credit nor debit sides are locked.
  - Semi-Repetitive: Payments where either credit or debit is locked, but not both.
- Filter By: Select the additional filter type for the payment search from the drop-down list, if desired. If you add an additional filter, the adjoining value drop-down field allows you to select the value to add as the filter.
- Netting: Mark to include only payments that aren’t netted into wires, only payments that are netted, or all payments.
- Enable Filters: Mark to enable filtering by instrument group or instrument type.
- Inst. Group: (Only applicable when Enable Filters is marked) Mark to select the instrument group as an added filter.
- Inst. Type: (Only applicable when Enable Filters is marked) Mark to select the instrument type as an added filter.
- Show Process Flow: Mark to add a Process Flow section with a flow chart for a visual representation of where in the process payments are.
- Show Only Items User Can Approve: Mark to only include payments that you can approve. You can’t approve payments that you’ve either created or edited. Permissions may limit you from approving other payments.
Select Search.
The Results screen opens.

View payment search results

Open the Results screen for the transaction status workflow.
Select List for any status to view the payments at that status.
Perform the desired actions on the payment.

Perform actions on payments

You can perform actions on templates depending on their current status. The Action column buttons indicate what you can do on each template.

Approval Needed actions

Action buttons:

	(View): Open the `View Transaction` screen to view details. The fields and sections are listed and defined in Single payment transactions: Create and edit.
	(Edit): Open the `Edit Transaction` screen to edit the payment. The fields and sections are listed and defined in Single payment transactions: Create and edit.
	(Delete): Voids the payment. The `Void Payments` screen opens; enter a reason for voiding the payment then select `Proceed`.
	(Approve): Approves the payment to advance the payment to status Ready to Extract. Payments must be approved by a different user than the one who created the template.

Ready to Extract actions

Using the X button here doesn’t send your payments to the bank. It only marks them as extracted. This is used when you send payments to the bank outside of the Ripple Treasury Platform and need to mark them as extracted.

Action buttons:

	(View): Open the `View Transaction` screen to view details. The fields and sections are listed and defined in Single payment transactions: Create and edit.
	(Edit): Open the `Edit Transaction` screen to edit the payment. The fields and sections are listed and defined in Single payment transactions: Create and edit.
	(Delete): Voids the payment. The `Void Payments` screen opens; enter a reason for voiding the payment then select `Proceed`.
	(Extract): Marks the payment as Extracted without sending it to the bank. The `Extract Payments` screen opens; enter a reason for extracting the payment then select `Proceed`. Don’t use the Extract button unless you are sending the payment to the bank outside of the Ripple Treasury Platform. Payments are extracted (sent to the bank) in `Connectivity` > `Jobs` > `Run On Demand`.
	(Fail): Fails the payment. Failed payments can’t be used but are still visible in reports.. The `Fail Payments` screen opens; enter a reason for failing the payment then select `Proceed`.

Extracted actions

Action buttons:

	(View): Open the `View Transaction` screen to view details. The fields and sections are listed and defined in Single payment transactions: Create and edit.
	(Confirm): Confirms the payment. The `Confirm Payments` screen opens; enter a reason for confirming the payment then select `Proceed`.
	(Complete): Completes the payment. The `Complete Payments` screen opens. Enter a reason for completing the payment, the transaction confirmation number (may be required by the template), and the system reference number (external system acknowledgement of payment if applicable). Then select `Proceed`.
	(Re-extract): Returns the payment to status Ready to Extract. The `Re-Extract Payments` screen opens; enter a reason for re-extracting the payment then select `Proceed`.
	(Fail): Fails the payment. Failed payments can’t be used but are still visible in reports.. The `Fail Payments` screen opens; enter a reason for failing the payment then select `Proceed`.

Confirmed actions

Action buttons:

	(View): Open the `View Transaction` screen to view details. The fields and sections are listed and defined in Single payment transactions: Create and edit.
	(Delete): Voids the payment. The `Void Payments` screen opens; enter a reason for voiding the payment then select `Proceed`.
	(Confirm): Confirms the payment. The `Confirm Payments` screen opens; enter a reason for confirming the payment then select `Proceed`.
	(Complete): Completes the payment. The `Complete Payments` screen opens. Enter a reason for completing the payment, the transaction confirmation number (may be required by the template), and the system reference number (external system acknowledgement of payment if applicable). Then select `Proceed`.
	(Re-extract): Returns the payment to status Ready to Extract. The `Re-Extract Payments` screen opens; enter a reason for re-extracting the payment then select `Proceed`.
	(Fail): Fails the payment. Failed payments can’t be used but are still visible in reports. The `Fail Payments` screen opens; enter a reason for failing the payment then select `Proceed`.

Completed actions

Action buttons:

	(View): Open the `View Transaction` screen to view details. The fields and sections are listed and defined in Single payment transactions: Create and edit.
	(Complete): Completes the payment. The `Complete Payments` screen opens. Enter a reason for completing the payment, the transaction confirmation number (may be required by the template), and the system reference number (external system acknowledgement of payment if applicable). Then select `Proceed`.
	(Re-extract): Returns the payment to status Ready to Extract. The `Re-Extract Payments` screen opens; enter a reason for re-extracting the payment then select `Proceed`.
	(Fail): Fails the payment. Failed payments can’t be used but are still visible in reports. The `Fail Payments` screen opens; enter a reason for failing the payment then select `Proceed`.
	(Delete): Voids the payment. The `Void Payments` screen opens; enter a reason for voiding the payment then select `Proceed`.

Failed actions

Action buttons:

	(View): Open the `View Transaction` screen to view details. The fields and sections are listed and defined in Single payment transactions: Create and edit.
	(Edit): Open the `Edit Transaction` screen to edit the payment. The fields and sections are listed and defined in Single payment transactions: Create and edit.
	(Fail): Fails the payment. Failed payments can’t be used but are still visible in reports. The `Fail Payments` screen opens; enter a reason for failing the payment then select `Proceed`.
	(Unfail): Returns the payment to status Approval Needed. The `Unfail Payments` screen opens; enter a reason for unfailing the payment then select `Proceed`.
	(Delete): Voids the payment. The `Void Payments` screen opens; enter a reason for voiding the payment then select `Proceed`.

Void actions

Action buttons:

	(View): Open the `View Transaction` screen to view details. The fields and sections are listed and defined in Single payment transactions: Create and edit.
	(Edit): Open the `Edit Transaction` screen to edit the payment. The fields and sections are listed and defined in Single payment transactions: Create and edit.
	(Un-void): Returns the payment to status Approval Needed. The `Unvoid Payments` screen opens; enter a reason for unvoiding the payment then select `Proceed`.