Open banking has been available to regulated businesses for long enough that the question is no longer whether to use it. Most businesses in lending, financial services, and adjacent regulated industries have integrated open banking data into their processes in some form.
The more useful question now is where in the process that data actually lives — and whether the way it is connected is creating value or creating work.
The integration that is not really an integration
Many businesses have open banking connected in the technical sense. A provider is integrated. Data can be requested. Responses come back.
But the data does not live inside the case. It arrives in a separate system, or as a PDF, or in a format that someone has to interpret and summarise before it can inform a decision. The team member handling the case has to retrieve it, cross-reference it with the rest of the case, and make a judgement call about what it means for the outcome.
That is open banking as an additional data source. It is better than not having the data. But it is not open banking as part of the operational process, and the difference matters.
What it means for the customer
When open banking sits outside the case process, customers feel it.
They are asked to provide consent and share their data at a point in the process that may not make sense to them. They may be asked again later because the first request was not connected to the right stage of the case. The time between providing data and getting a decision is extended because someone has to retrieve and review it manually. And if something in their financial data prompts a question, they may be contacted through a different channel entirely — because the process for handling that exception is disconnected from the original case.
None of this is the customer’s problem to solve. It is an operational process problem. And customers in competitive markets notice when the process feels fragmented.
What it means for the team
For the operations team, disconnected open banking data creates a specific type of overhead: the overhead of interpretation and coordination.
The data exists. But working out what it means for this specific case, at this specific stage, in the context of the other information already collected, requires a member of staff to do cognitive work that a well-designed process could structure for them. Not replace — the human judgement is still valuable. But structure: presenting the right data at the right moment, flagging what needs attention, connecting the affordability picture to the decision that needs to be made.
When that structure is absent, experienced staff manage by developing their own mental frameworks. Newer staff ask colleagues. Both approaches work, but neither scales cleanly and neither produces a consistent audit trail.
What it means for compliance
The compliance case for embedding open banking in the case process is straightforward.
Regulated firms using open banking data in credit or affordability decisions need to be able to show what data was used, when it was collected, what it showed, and how it informed the decision. If the data lives in a separate system from the case, that demonstration requires assembling evidence from multiple places. If the data lives inside the case, it is part of the record automatically.
The firms that are most confident in regulatory reviews are not necessarily the ones that use the most sophisticated open banking analysis. They are the ones where the connection between data, decision, and case record is clean and complete.
The operational change worth making
The shift that creates the most value is not switching open banking providers or upgrading the quality of the data. It is connecting the data to the case at the point in the process where it is actually needed.
That means the consent request going out at the right stage, not as a separate pre-process step. The data arriving inside the case, connected to the affordability assessment rather than sitting alongside it. The case moving forward based on what the data shows, with any exceptions routed through a governed process rather than landing in someone’s inbox.
When open banking works that way, it stops being an additional source of operational coordination and starts being a genuine part of how cases get resolved efficiently and on record.
