Lessons in Partner Banking — Part 5: Governance

Governance is one of those topics that gets a lot of lip service in partner banking and not nearly enough action. I have seen FIs launch partner banking programs with virtually no formal governance structure in place — no documented approval process, no change management framework, no consistent reporting. The result is almost always the same: gaps that regulators find before the FI does. Getting governance right does not have to be complicated, but it does require intentional design from the start.

Onboarding/Offboarding Structure

How an FI structures the onboarding and offboarding process says a lot about how seriously it takes governance. A well-designed structure ensures that every prospective partner goes through a consistent set of reviews, that approvals are formally documented at each stage, and that there is a clear record of the decisions made — and the reasoning behind them. This matters not just for internal accountability, but for regulators, who will expect the FI to demonstrate that every partner in the program was vetted appropriately before going live.

The same discipline applies to offboarding. FIs often spend a great deal of time designing onboarding and very little time thinking about how a relationship ends — whether that is a voluntary exit, a compliance issue, or a partner going out of business. Offboarding should be as structured as onboarding, with defined triggers, escalation paths, and documented approvals. It should also include a plan for protecting customers throughout the process.

Change Management

This is the area where I see the most gaps. Partners change — their products evolve, their technology changes, their customer base shifts — and without a formal process for managing those changes, the FI can find itself exposed to risks it never signed up for. A change management framework requires partners to notify the FI of any material change in advance. Not after the fact. Before it goes live.

What counts as material? That needs to be defined and documented — but it typically includes new product features, fee structure changes, core technology migrations, new third-party vendors, or significant shifts in the partner’s customer base or business model. The management committee should be involved in reviewing and approving changes that cross the materiality threshold. Smaller changes can be handled operationally, but they still need to be documented and tracked.

One more thing worth requiring: a post-implementation review for significant changes. This is a simple ask — the partner confirms that the change went as expected and that no new risks or issues emerged. It creates an audit trail and reinforces that the FI is actively managing the relationship, not just passively watching it.

Board and Management Committee Reporting

Reporting is where governance becomes visible. If the board and management committees lack clear, consistent, and meaningful information about the partner banking program, they cannot provide effective oversight. And if they cannot provide meaningful oversight, that is a problem — both from a regulatory standpoint and from a risk management standpoint.

Tailor the reporting to the audience. Management committees need detail — partner-level metrics, compliance findings, open issues, pipeline, and any change management items under review. The board needs a high-level summary: where the program stands, what risks are elevated, what actions are being taken. A good rule of thumb is monthly reporting to management committees and quarterly reporting to the board, though the cadence should be adjusted based on the program's size and complexity.

The most common mistake I see is FIs that over-report without context — dashboards full of data with no narrative, no trend analysis, no clear indication of what requires attention. Good reporting tells a story. It should be obvious from a single read what is going well, what is not, and what decisions need to be made. If a board member has to dig to figure out what they are looking at, the reporting needs work.

So What?

Governance does not have to be a burden. When well designed, it actually makes the program easier to run. Here is a practical guide for FIs building or improving governance for partner banking:

Document the Onboarding Structure: Define the full approval workflow from initial prospect review through go-live. Identify which stakeholders must approve at each stage, what documentation is required, and how decisions will be recorded. Make sure the offboarding process gets the same level of detail, including triggers for suspension or termination and a plan for customer protection.

Define What Constitutes a Material Change: Work with risk, compliance, and legal to create a documented definition of materiality for partner changes. This should include product changes, technology changes, vendor changes, and shifts in the partner’s business model or customer base. Having this defined upfront removes ambiguity when a change comes in and ensures the right level of review is applied consistently.

Build the Change Management Process: Require partners to submit change notifications to the FI before implementing material changes. Define how those notifications will be reviewed, who is responsible for the review, and what the approval and sign-off process looks like. For significant changes, require a post-implementation review that confirms the change was performed as expected and that no new risks were introduced.

Design the Reporting Framework: Determine what needs to be reported, to whom, and how often. Management committee reporting should be monthly and detailed. Board reporting should be quarterly and focused on material risks, trends, and items requiring board-level decisions. Build a reporting package that tells a story, not just presents data, and make sure it includes trend analysis and clear indicators of what requires attention.

Document Everything: Governance only works if it creates a paper trail. Every approval, every change review, and every board report should be documented and stored so they can be retrieved during an audit or exam. If the FI cannot demonstrate that the governance process was followed, for regulatory purposes, it effectively was not. Documentation is the evidence that the program is being managed responsibly.

Review and Iterate: Governance structures should not be set and forgotten. Schedule periodic reviews of the onboarding process, change management framework, and reporting package to ensure they remain aligned with the program's size and complexity. As the partner portfolio grows, what worked for two partners may not work for ten.

The FIs that treat governance as an asset rather than an obligation are the ones that build programs that last. Done right, governance is not what slows partner banking down — it is what makes it possible to scale with confidence.

Stay tuned for the next installment of Lessons in Partner Banking, where we dive into how to work with regulators…