Find savings hidden in supplier contracts and spend

What is the business problem, and what does it cost?

Supplier relationships are built over years by different managers, in different departments, often under different names. Contracts are signed, filed and forgotten. Renewal dates pass unnoticed, and the default outcome is that the agreement rolls over on its existing terms or at a new list price.

The hidden cost has three parts: money paid for things already owned, money paid at rates that no longer match the market, and management time spent discovering the problem too late. None of these shows up as a single line in a monthly report, which is why they persist.

• Two or more teams paying separately for the same tool or service
• Renewals that auto-extend with a notice window missed
• Price increases applied without reference to the signed agreement

What changes when Claude reviews contracts and spend together?

Claude reads the contract documents your team already stores in SharePoint and the spend records held in Excel exports and Oracle. It matches what the contract says against what is actually being invoiced, line by line, and records any gap.

The output is a working list rather than a report to file away. Each item shows the supplier, the contract clause, the amount paid, the difference, the next key date and a suggested next step. Finance leaders can sort by value or urgency and assign owners in minutes.

• A single register of supplier contracts, with key dates
• Flags for duplicates, unexpected increases and approaching renewals
• A ranked negotiation list with the evidence attached

How does Claude connect to your systems?

Claude for Microsoft 365 works within the Microsoft applications your organisation already uses. It can open documents in SharePoint and worksheets in Excel that your account is permitted to access. Spend data held in Oracle is brought in through an approved export or a secure connection set up during the engagement, so no one needs to copy figures by hand.

Claude Skills allow your finance team to package its own know-how, such as the approval thresholds, the clauses it always checks and the naming conventions for suppliers. Claude then applies those rules consistently every time, rather than relying on whoever happens to be reviewing that month. A closely related automation is Close the books faster with automated variance commentary. It is built on Claude for Microsoft 365, from Anthropic.

• SharePoint: contract documents, read within existing permissions
• Excel: spend extracts and supplier registers
• Oracle: spend data supplied through an approved export or secure link
• Claude Skills: your finance rules, applied the same way each time

What does a day look like before and after?

Before: a procurement analyst spends several days each quarter opening contract folders, copying renewal dates into a spreadsheet and comparing invoices by hand. By the time a price rise is spotted, the notice period has often passed.

After: the same analyst opens a prepared list on Monday morning. Renewals due within the next ninety days are at the top, each with the clause, the current price and the suggested position for negotiation. The analyst spends the morning on conversations with suppliers rather than on searching for information.

How are governance, security and permissions handled?

Claude only sees what each user is already allowed to see. If a contract folder is restricted to legal and finance, the review respects that restriction. Every finding is recorded so that the finance team can trace how a conclusion was reached.

Claude prepares and checks; named people approve. No supplier is contacted, no contract is terminated and no payment is changed without a person signing off. This keeps accountability where it belongs and supports the controls your auditors expect.

• Existing SharePoint and Oracle permissions are respected
• Every flag links back to its source document
• Named approvers decide every consequential action

How should success be measured?

Track three measures from the first review: the value of savings agreed with suppliers, the number of renewals negotiated before their notice dates, and the hours the finance team spends on contract discovery. Compare these against a baseline taken before the work starts.

Review the list each month with the CFO and the procurement lead. Retire findings that are resolved, and refine the rules that produced false alarms so the list becomes more useful over time.

• Value of savings agreed, compared with the baseline
• Share of renewals negotiated ahead of notice dates
• Hours spent on contract discovery and reconciliation

How should an organisation start?

Start with a free automation audit. The audit identifies which contracts and spend sources matter most, which systems hold them and what permissions apply. It also confirms where your data needs to be hosted, so that the approach fits your regulatory and internal policy requirements.

From there, a first pilot typically covers one category of spend, such as software or professional services. Once the list proves useful, the approach extends to the rest of the supplier base. For wider context on Claude across Microsoft 365, see how Claude and Microsoft 365 together lift productivity across the whole organisation.

• Book a free automation audit
• Pilot on one spend category for a short period
• Extend to the wider supplier base once the list is trusted