In Review

Planned

In Progress

Completed

Main Roadmap

Payments and recipients can be approved directly in online banking without navigating to PayRecs

High Priority

OB Approval Widget

Linear

Add a visual within the payment wizard or the UI that shows the amount remaining in a companies daily limit and or the companies remaining Count limit for that day. Also we could include visuals for back office within the company profile showing the same.This can reduce end user errors when limits are hit and also allow for back office to troubleshoot end user reach out.

User limit remaining balance and User remaining count visuals

michael

When more information is requested from a downstream bank, flag the recipient so that future payments will warn the user that extra information is required .Today, if an invoice is attached, that flag automatically sends the attachment to the bank, but doesn’t account for additional questions.

Request for information flag

Steve Habegger

For partner users, the company search on the home page is very slow in production and the screen goes blank between each letter

Low Priority

Partner User - Company Search - Slow Performance and Blanking Screen

<ol><li>for mca originated payments -&gt; use billing account<ol><li>if billing account is undefined, use existing MCAxxxx designation</li></ol></li><li>for dda originated payments -&gt; use dda</li></ol>

XAA Report billing account for MCA

Sam Mancini

Allow a user profile to save their preference by adding a "make this my default" checkbox in the time duration form.When loading the payments hub, check the user preference for time duration and load it.if they uncheck the "make this my default" - make the preference nullif the user resets, or chooses a different value, uncheck the "make this my default" and if they check it, update that preference.

Partner user Payments hub time duration - user preferences

Only a single FI email can be configured to receive return notifications. Add the ability to support more than one.

support multiple return emails

this asks if you want to continue but only provides "Accept" as an option.
Change language:
Top: "We detected a possible duplicate:"
Bottom: <remove>"Are you sure…"</remove>
Button: "Continue"

dupe payment warning

<h2>Problem/Feature</h2>We are seeing user login errors at Q2 on FT during a mass submission of scheduled payments.<h2>Scope</h2> Reattempt the scheduled payment for specific known errors.

Scheduled Payment Retry

<h2></h2>Receiving amount is not accurate for some scheduled payments.

Scheduled payments received amount

<ol>
<li>Add table: <code>ComplianceEvent</code> (use enums where appropriate)</li>
<li><code>complianceEventId</code> - GUID</li>
<li><code>complianceResultId</code> - GUID</li>
<li><code>complianceSystem</code> - enum: 'VERAFIN', 'LEXISNEXIS'</li>
<li><code>resultType</code> - enum: 'FRAUD', 'SANCTIONS'</li>
<li><code>event</code> - enum: 'INIT', 'HOLD', 'RELEASE', 'MANUALLYRELEASED', 'CANCELLED', 'REVERSED', 'MATCH', 'NOMATCH'</li>
<li><code>dateCreated</code> - datetime</li>
<li>Capture every event related to a <code>complianceResult</code> (including initiation - INIT) in the <code>complianceEvent</code> table</li>
<li>For Partner and Ops view only, of the payment detail, add a tab for compliance.
</li>
<li>Add new tab: Compliance 
<ol>
<li>Table of ComplianceEvent rows<ol>
<li>scanType - "Type"</li>
<li>complianceSystem - "Vendor"</li>
<li>event - "Event"</li>
<li>dateCreated - "Date"</li></ol></li>
<li>Design<ol>
<li>
<a href="https://share.zight.com/NQuXQJKB">payment details - compliance Lucidchart 2025-10-13 at 2.57.22 PM</a></li>
<li>Should match styling or the "status" tab: <a href="https://share.zight.com/Qwurp990">https://share.zight.com/Qwurp990</a></li></ol></li></ol></li>
</ol>

Add Compliance Status tab to Payment Detail

<h1>Scope</h1>For IBANs that appear to be antiquated or have a possible mismatch, show a warning message. Example:<blockquote>Please recheck the account number with the user and make the payment with caution as this could point to a typographic error or an old out-of date bank code. This checks either an embedded number or numbers or is a routine that allows us to calculate if the bank code is valid. In certain countries this means that the payment should not be made (UK being an example of this). (03an)" </blockquote>

catch isWarning on iban validation

Add Today filter for Payments Hub

Recipient detail needs to show 
<ol>
<li>Classification: (Individual or Business)</li>
<li>Type: SWIFT or EFT
in the detail for end user, FI backoffice and PayRecs operator</li>
</ol>