Bank Third-Party Renewal Register

This concept illustrates a third-party register for the vendor management, procurement and risk teams of a bank. It extends Subscriber Bot's relationship records so that every supplier contract, license and software service the bank depends on carries the facts a renewal decision needs: how critical the supplier is, whether it handles customer data, when notice must be given, when due diligence was last done and which documents sit behind it.

In banking and financial services, the view of third parties is often split between a contract repository, a procurement tracker and corporate card statements. A critical supplier can auto-renew before anyone notices that its due diligence is more than two years old, and a tool bought on a corporate card may be handling customer data without ever being assessed. The concept puts registered suppliers and unregistered recurring charges in one list, so the gaps are visible before a notice window closes.

The Third-party register page sits under Relationships with an Add supplier action. Tiles count critical suppliers, notice windows in the next 30 days, overdue due diligence and unregistered card charges, the last two highlighted as warnings. A supplier search and filters for criticality, customer data and notice window narrow a table whose columns are supplier, service, criticality, customer data, notice-by date, last due diligence and review status. Sample suppliers range from card dispute handling and core banking hosting to statement printing, identity document checks and office productivity licenses, tagged critical, high or standard. A survey tool found on a corporate card appears as unregistered and unassessed, with customer data marked as likely. The selected supplier opens in a side panel with its contract document, a 12-month auto-renewal term, the owning team, risk and security sign-offs shown as pending, and a Send notice action.

FluidGrids appears in the review column. The design envisions that as a notice window approaches, a FluidGrids workflow opens a renewal review and routes critical suppliers to the risk and security owners, with the review status, such as open for a critical supplier or triage for the unregistered tool, written back to the register row. The sign-off items in the side panel show where those owners' decisions are designed to land.

Within Subscriber Bot, the register builds on the product's relationship records and the contract documents attached to them, applying them to an institution's supplier base rather than one person's subscriptions.