Thought Leaders

One Customer, One View: Convergence from the Client to the Board

Share

A plant hire business needed four finance products to take on a major contract. Chris Coleman, then working in commercial finance at a bank, joined colleagues from across the business to put together a single proposal. The team won the deal. Once the paperwork was signed, the customer was handed four logins.

“The team had created this dream, but actually what the customer got was completely siloed,” recalls Coleman, now Sales Director at CODIX. “Four different logins for four different systems; four different views for four different products”.

The experience illustrates a problem for lenders looking to grow across asset, receivables and commercial finance. Specialist teams can work together to win business, but the systems they use can leave the customer managing each facility separately.

Speaking to Finance Connect ahead of its UK Autumn Conference, Chris Coleman explains how a shared platform could bring the relationship together while giving each team the tools and authority it needs to make its own lending decisions.

One relationship across several products

Coleman points to the experience many customers already have in their personal banking. A mortgage, current account, credit card and loan can appear in the same app. A business finance director, by contrast, may need to sign into several systems, download separate reports and reconcile the figures before presenting them to the board.

CODIX’s iMX platform uses a common data model across products. For the customer, Coleman says, that means “one login, single view, single reporting cadence”. For the lender, it means teams can see what facilities a customer already uses and consider what else might fit as the business develops.

Take a wholesaler that uses invoice finance and starts selling overseas. It may need trade finance. A shared view gives the relationship team a place to start that conversation and lets the relevant specialists assess the opportunity against what the lender already knows about the customer.

This shared view can also help strengthen the lender-client relationship. When a client’s products sit on separate systems, moving one to another lender may feel like a relatively small decision. When they sit together in one view, moving one out feels like breaking up an established relationship.

A shared platform with room for specialist judgement

Factoring, asset-based lending and supply chain finance each have their own working practices, credit requirements and approval routes. Coleman argues that a common platform has to accommodate those differences rather than force every team into one way of working.

“They’re specialists for a reason,” says Coleman. “Each team needs to be able to configure the platform to suit the way it wants to work.”

The process map runs the process

Most lenders already document how each business should work, in process maps kept in shared folders and rarely opened again. iMX takes those maps, however different they are across factoring, asset-based lending, asset finance or supply chain finance, and builds them into the system.

“iMX lets you build the process map in the system, and the map then runs the process,” says Coleman. Each business line works to its own rules, approvals and workflows, and all of them are governed within the same architecture.

Take a £500,000 payment request. Rather than an approval chased by email, the request is routed by the lender’s own rules to someone with the right authority, with a record of who approved it and when. If approval limits change, management updates the workflow once. Each business line keeps the rules it needs, and the lender applies its controls consistently across all of them.

What boards and funders can see

“If you’ve got one view, from the board all the way down, you can see where your exposure is,” says Coleman.

If a lender wants to grow its wholesale book, for example, it can see how much it already lends to a particular customer and how that exposure is spread across facilities. It can then decide whether there is scope to lend more and ask the relevant team to assess which product would suit. If the board wants to reduce exposure to a sector, it can see where that exposure sits across the business.

The same visibility is essential when managing overall client exposure. If a lender caps its total exposure to a client, it needs to see every facility that client holds. With separate systems, nobody sees the total. With one view, the next facility can be stopped before it takes the lender over the limit.

Getting to that point can be laborious when teams work from separate systems. “I’ve spoken to many lenders in the UK whose senior people are just cleaning data every month,” says Coleman. He says a common data model allows lenders to schedule reports from the underlying records, so operational teams, boards and funding partners can each receive the information they need.

For non-bank lenders, traceable reporting can also help funders see how their capital is performing. Coleman says lenders can give a funding partner permission to view agreed indicators, such as arrears and impairments, or send a scheduled report if the partner prefers.

“The big thing for me is that the capital partner should be given what they want, not what the lender is able to give to them,” he says.

Connecting partners, not platforms

Coleman is clear about what should be joined up. On a unified platform, a lender no longer needs to wire its own systems together. What still needs connecting is the lender’s wider ecosystem of third-party providers, such as credit insurers, credit bureaus, KYC and onboarding tools, payment and banking systems, and the lender’s own client portals.

“Flat files are fine, APIs are preferred, and we have 1,350 API endpoints,” says Coleman. That lets a lender keep the specialist partners it already relies on and connect them to one record, rather than building and maintaining links between its own separate platforms.

Moving to a shared platform can happen in stages. Chris Coleman gives examples of lenders that start by moving their factoring business first, then add payables finance and asset-based lending. Each team can get its operations running before the next product is brought onto the platform. “We create a delivery path that will work for them,” he explains.

The platform is already used across different markets and product lines: a French bank runs its factoring on iMX, a Spanish bank runs confirming on iMX, and a US bank runs its ABL on iMX.

AI in the day-to-day work of lending

Because every product sits on one data model, AI works from one record too.

Coleman sees the immediate opportunity for AI in routine operational work. “It’s where can we take out the repeatable load that’s quite low risk,” he says.

In collections, CODIX uses historical data to examine which approaches work, including when to call, when to chase and when to escalate. It is also getting good results in testing with AI that improves the matching of incoming payments to invoices, including where a customer makes a part payment or provides an incomplete reference. A virtual assistant can help staff find a document or take them directly to a task in iMX.

CODIX is also developing a Model Context Protocol (MCP) server, which Coleman says will let a lender’s chosen AI tool interact with iMX within defined permissions and provide a record of what it accessed. The CODIX MCP server is nearing completion and will be released shortly.

For lenders considering where to start, Coleman brings the question back to what their existing systems allow them to see: “What are you not doing for your clients today, because your system won’t let you?”

To discuss how CODIX’s iMX software could support your business, meet the CODIX team at the Finance Connect UK Autumn Conference on 24 November at Kings Place, London. To arrange a meeting in advance, email CODIX Sales Director Chris Coleman at ccoleman@codix.co.uk.

Codix is a Silver Sponsor of the Finance Connect UK Autumn Conference 2026.