A renewal control system for finance and procurement

Consider a 15-person finance and procurement team at a professional services firm with 180 employees.

The firm uses dozens of SaaS tools, data providers, contractor platforms, subscriptions, and specialist vendors. Renewals arrive through email, vendor portals, calendar reminders, contract folders, card statements, and the memories of budget owners. Finance wants earlier visibility. Procurement wants cleaner evidence. Department leads want less admin. Leadership wants costs controlled without slowing the business down.

The risk is not only overspend. It is unmanaged commitment. A tool may be expensive but essential. Another may be cheap but risky. A vendor may be unused by one team and critical to another. A renewal may look routine until legal, security, or client delivery context is considered.

This is a good place for Proximity to act as renewal control infrastructure.

The goal is not to automate spend decisions. The goal is to prepare better renewal reviews so finance, procurement, budget owners, and leadership can make decisions with clearer context.

The Workflow

The workflow is monthly vendor renewal review.

The team wants to see:

• Which renewals are due in the next 30, 60, and 90 days.
• Which contract, invoice, or vendor notice confirms the renewal.
• Who owns the vendor internally.
• Which team uses it and for what purpose.
• What the current spend and prior trend look like.
• Whether there are security, legal, client, or delivery dependencies.
• Which approvals are needed before renewal, cancellation, or renegotiation.

Most finance systems can show spend. That is not enough. Renewal judgment depends on spend plus context.

Proximity would connect the renewal workflow around approved records, not replace the finance stack. It would create a shared operating view for the review rhythm.

What Proximity Models

For this deployment, Proximity would model the renewal as the core work object.

Approved sources might include:

• Contracts and order forms.
• Invoices and card transactions.
• Procurement records.
• Vendor owner lists.
• Usage exports where available.
• Budget records.
• Security or legal review notes.
• Email notices and calendar dates.
• Prior approval decisions.

The system would structure those sources into review context:

• Vendor, product, owner, department, and business purpose.
• Renewal date, notice period, auto-renewal terms, and cancellation window.
• Current spend, prior spend, and budget link.
• Usage evidence, where available.
• Required reviewers: finance, procurement, legal, security, budget owner, or leadership.
• Known risks, missing documents, and unresolved questions.

COSO frames internal control as a system for supporting operations, reporting, and compliance. The GAO Green Book similarly treats internal control as a process that helps management achieve objectives. For AI in finance operations, the lesson is practical: the control environment must be visible before software can safely accelerate work.

Proximity supports that environment by making the renewal state legible.

What The System Prepares

Before the monthly review, Proximity could prepare a renewal packet for each vendor.

The packet might include:

• Contract summary with source link.
• Renewal timeline and notice window.
• Spend trend and budget owner.
• Usage or adoption evidence.
• Open questions.
• Required approval path.
• Prior decisions and rationale.
• Draft questions for the vendor or internal owner.

The system could also maintain a review queue:

• Ready for budget owner review.
• Missing contract.
• Missing usage evidence.
• Legal review needed.
• Security review needed.
• Leadership approval needed.
• Cancellation window approaching.

That queue does not decide the outcome. It helps the team see what needs professional attention.

IBM describes workflow automation as using software to execute defined process steps. In this Proximity design, the important workflow is not "renew automatically." It is "prepare the renewal so people can decide responsibly."

What Remains Human

Spend judgment remains human.

Proximity must not approve a renewal, cancel a vendor, negotiate terms, change bank details, approve payment, alter the ledger, or decide that a vendor is worth keeping. Those are professional and organisational decisions.

Humans remain responsible for:

• Budget judgment.
• Commercial judgment.
• Risk acceptance.
• Vendor negotiation.
• Approval decisions.
• Final finance records.
• External communication.
• Any action that commits money.

The system can prepare evidence and route the review. It cannot own the decision.

This boundary should be visible in the product. Renewal packets should say "prepared for review." Approval controls should belong to named humans. Audit history should show who reviewed, approved, changed, or rejected an action. NIST SP 800-53's access control and audit families are useful background because finance workflows need clear permission and accountability trails.

Pilot Shape

A strong pilot would focus on software renewals above a chosen threshold, for example vendors over 10,000 per year or renewals requiring more than one reviewer.

The first phase would map the renewal sources and approval rules. The second phase would build review packets for a small vendor cohort. The third phase would test the monthly renewal meeting with Proximity as the operating surface.

Success should be measured by preparation quality, not by automation volume.

Useful signals include:

• More renewals identified before the notice window.
• Fewer missing contracts or owners.
• Faster assembly of review evidence.
• Clearer approval routes.
• Better visibility into unused, duplicated, or risky vendors.
• Finance and budget owners reporting fewer last-minute decisions.