Supplier trust is now an ownership question. It used to be obvious. Procurement vetted the supplier, finance paid them, and the handoff worked because the cadence was slow enough that the seam did not show. In 2026 the seam is the risk. Bank-detail changes happen mid-cycle. Behavioural drift moves week to week. Exception handling spans both teams. Neither side fully owns the result, and the gap is where AP fraud and supplier churn now live.
The handoff that used to work
The traditional split was clean. Procurement ran selection, due diligence and contract negotiation. Finance ran payment, accruals and supplier statements. The boundary was the signed contract. Once the supplier was approved and the master record was created, finance took ownership of the operational relationship.
That worked when supplier data was static. Bank details did not change between contract and invoice. Beneficial ownership did not shift mid-year. Behavioural drift was so slow it could be picked up at the annual review.
None of that is true now. Supplier data changes constantly. Behaviour changes faster. The seam between the two teams sees more activity than either team's core workload. We have argued elsewhere that supplier onboarding is broken; the ownership question is the natural next step in that conversation.
The four tasks that fall between the cracks
Bank-detail changes. A supplier requests an account change. Procurement does not see the request because the relationship is now financial. Finance receives it but does not have the underwriting view to assess whether it makes sense. The change is processed, often without sufficient review.
Payment timeliness against terms. Procurement negotiated the terms. Finance is held to them. Where the business fails to deliver, procurement is not informed, so the supplier relationship deteriorates without procurement's awareness. Closing this gap is part of why procure-to-pay visibility matters as a discipline rather than a tool category.
Exception handling. An invoice that triggers an exception sits in finance. Procurement is rarely looped in unless the exception escalates. The supplier sees a delay and reads it as a finance failure, even when the root cause is procurement-related.
Behavioural reporting. Neither team owns the behavioural view of supplier performance, so it does not exist as a regular artefact in the business. The board therefore does not see it.
Three operating models for 2026
Procurement-led. Procurement extends its ownership through the payment lifecycle. Finance executes payment but does not own supplier trust. Works in businesses with sophisticated procurement functions and a clear category-management model. Less effective where procurement is decentralised or transactional.
Finance-led. Finance absorbs supplier trust into the AP function and treats procurement as an upstream feed. Works where procurement is light or where AP has already invested in identity and exception controls. Less effective where supplier strategy is a competitive differentiator that needs procurement leadership.
Networked. Both teams operate against a shared supplier trust layer. Procurement owns selection and strategy. Finance owns execution. The trust layer, which holds identity, behaviour and exception data, is shared infrastructure rather than owned by either side. Works where the business has, or is willing to adopt, network-level supplier data.
What a shared trust layer looks like in practice
A shared trust layer is not a shared spreadsheet. The defining feature is that supplier identity, bank details, beneficial ownership, payment history and behavioural baseline all live in one place and are kept current by the supplier, not by either team. Buyers consume the verified record. Changes trigger workflow on both sides.
The supplier portal model does not produce this. Each buyer's portal creates a separate record. The trust layer requires the supplier to hold the canonical version, with verified attributes that travel. We have made the case for this shift in the supplier portal is dead.
A simple RACI
For mid-market businesses without the appetite for a full operating model shift, a clean RACI usually closes 70 per cent of the gap.
Supplier selection: procurement R, finance C. Onboarding identity verification: procurement R, finance A. Bank-detail changes: finance R, procurement C, with risk informed where the supplier is in the top fifty. Exception handling: finance R, procurement C. Behavioural reporting: shared, with the artefact owned by whoever runs the quarterly business review.
The RACI is not the answer in isolation. It is a way to stop bleeding while the deeper operating model question is worked out.
.jpg)
