Skip to content

Insights

G-Cloud 15: A Public Sector Guide to Buying Expense Software Through G-Cloud

A practical guide to buying through G-Cloud 15: lots, call-offs, Procurement Act thresholds, and what gets published about your expense spend.

By Capture Expense

Four colleagues meeting around a table in a glass-walled office

In brief

  • Most UK public bodies buy expense software through G-Cloud. G-Cloud 15 (RM1557.15) has been live since September 2026, and expense software sits in Lot 2b, Software as a Service.
  • G-Cloud 15 runs under the Procurement Act 2023. G-Cloud 14 call-offs signed before it expired on 28 October 2026 stay under the Public Contracts Regulations 2015 for their whole life.
  • Below £12,000 (central government) or £30,000 (everyone else), no public notice is needed at all.
  • Local authorities publish every item of spend over £500, with a free-text description. Structure that field at implementation, because it’s very hard to fix later.

Most UK public bodies buy expense software through G-Cloud 15, the current version of the framework run by the Government Commercial Agency (GCA). You write your requirements, search the catalogue, shortlist, award a call-off without running a full tender, and keep the audit trail.

Below £12,000 for central government and £30,000 for everyone else, no public notice is needed at all.

Buying expense software for a council, NHS body, police or fire service, school, university or department means answering a question the private sector never faces: how are you allowed to buy it at all? That comes first below. Then which route fits your numbers, and then what happens to your expense data once it’s inside a public body, which is what makes government genuinely different from a 400-person engineering firm.

How buying through G-Cloud 15 works

G-Cloud is a Crown commercial agreement for cloud services. Crown Commercial Service (CCS) became the Government Commercial Agency on 1 April 2026, so guidance and templates that still say CCS are the same documents under a new name.

The live framework is G-Cloud 15, agreement number RM1557.15. It was awarded on 6 August 2026, opened to buyers in September 2026, and runs to 5 August 2030. G-Cloud 14 expired on 28 October 2026.

Three things changed with G-Cloud 15 that matter to a buyer:

  • It’s the first G-Cloud run fully under the Procurement Act 2023. That changes the notices you publish and the regime your contract sits under.
  • It’s an open framework. It reopens to new suppliers around 18 months after go-live, so the supplier list will grow during its term.
  • Call-offs can run longer. G-Cloud 14 capped a call-off at 48 months. G-Cloud 15 allows up to four years plus up to two years of extensions on the software and support lots, and up to eight years in total on the hosting lots.

If you’re planning a purchase for the rest of the 2026-27 financial year, you’re buying on G-Cloud 15. If you signed a G-Cloud 14 call-off before 28 October, it runs on under its original terms.

The lots, and which one expense software sits in

Lot What it covers Relevance to expense software
Lot 1a, Cloud hosting Hosting and infrastructure Not the licence
Lot 1b, Cloud hosting above OFFICIAL Hosting for data above the OFFICIAL classification Rarely relevant to expenses
Lot 2a, Infrastructure Software as a Service Infrastructure software delivered as a service Not usually where expense products sit
Lot 2b, Software as a Service Cloud software Expense software lives here
Lot 3, Cloud support Implementation, migration and training help The services around the licence, not the licence itself

By Advice Cloud’s count, G-Cloud 15 had 4,376 suppliers across 42,095 listings in early October 2026.

The split between the software lot and Lot 3 is often misunderstood. Your licence is Lot 2b. If you want a supplier to migrate data, configure your approval hierarchy or run training, that’s Lot 3, and it can sit on a separate call-off with a different term. Buying both on one software order is exactly what an internal auditor picks up in year two.

What a Digital Marketplace listing means, and what it doesn’t

A listing means the supplier was awarded a place on the framework, accepted its terms, and published a service against a set of mandatory fields. G-Cloud 15 scored suppliers on quality, price and social value at application, rather than only checking compliance. But a listing still isn’t a test of whether the software meets your requirements, and nobody checks the claims in a service description against your use case.

What the listing does give you is a structured, comparable disclosure. Every service page carries the same headings, from features, pricing and service documents to security testing, staff security, standards and certifications, and social value. Suppliers must publish a price and a unit, which makes G-Cloud the one place in the UK expense software market where you can read real prices in pounds without booking a demo.

Two fields deserve more attention than they usually get:

  • Staff security: whether the supplier’s people are vetted, to what level, and against what standard. If your expense data will hold the travel patterns of people whose location is sensitive, this field isn’t a formality.
  • Resellers: whether you’re contracting with the software vendor or an intermediary. A reseller listing means your counterparty isn’t the company writing the code, which changes what happens when something breaks.

One more thing a listing doesn’t mean is that it still exists. Listings expire with the framework. A supplier whose website says “G-Cloud approved” without naming an iteration is telling you nothing useful. Ask for the service ID and check it on the Digital Marketplace before you build a route around it.

Search, shortlist, and the audit trail you have to keep

The process runs in this order:

  1. Write your requirements down first.
  2. Filter the catalogue against them.
  3. Shortlist.
  4. Assess the shortlist against the requirements you wrote before you started looking.
  5. Award.
  6. Record every step.

The order is the whole point. The single most common finding in a public sector procurement audit is a requirements document written after the supplier demonstration, because it reads like the supplier’s feature list.

G-Cloud 15 offers two call-off procedures on every lot: award with competition, where you set the assessment criteria and invite tenders from a shortlist, and award without competition, where the framework supplies the selection rule (GCA’s guidance says lowest price). Either way, the platform keeps clarification questions and published requirements. You have to keep:

  • Screenshots of the filters you applied, so the shortlist can be reproduced.
  • Your assessment scores and the reasoning behind them.
  • The reason each supplier was excluded at shortlisting, individually.
  • Notes of every call, meeting and demonstration, including who attended.
  • All written correspondence with every supplier, not just the winner.
  • A record of who had access to supplier responses, and when.

Keep it for at least three years, in an accessible format, somewhere other people in your team can reach. On award, publish the contract details and complete any return the framework’s buyer guidance asks for.

There’s a neat irony here. The audit trail you must keep to buy expense software is the same class of evidence the software then produces for every claim. If you can’t show a defensible trail for a £96,000 purchase, you’re unlikely to show one for 40,000 claims.

Call-off contracts, and what you can’t change

The framework sets the core terms, and they form part of every call-off. This mostly works in your favour: you can’t negotiate a bespoke liability cap or an exotic exit clause, but neither can the supplier hide an auto-renewal or an uncapped uplift in their own paper. What you can vary sits in the order form: the services, the quantity, the price against the published rate, the term, and the optional clauses the framework allows.

On Lot 2b, a call-off can run for up to four years, plus up to two years of extensions. Confirm the term against the call-off terms before you write the business case.

The practical consequence is that a supplier who mentions “our standard terms” during a G-Cloud call-off is either confused or seeing whether you’ll accept different terms. There are no supplier standard terms on a G-Cloud order.

Where G-Cloud is the wrong route

G-Cloud isn’t a universal answer. It’s wrong when:

  • The contract needs to run beyond the lot’s maximum call-off term.
  • What you’re buying isn’t a cloud service: an on-premises licence, a managed bureau, or a consultancy engagement without software.
  • You need to negotiate a term the framework fixes.
  • The requirement is bundled into something larger that another agreement covers better.

Below your own notification thresholds, running any framework process at all is disproportionate. You’re allowed to get quotes, document the choice under your standing orders, and buy.

The thresholds that decide this were updated on 1 January 2026. All of them include value added tax (VAT):

Contract (goods and services, inclusive of VAT) Threshold from 1 January 2026
Central government authority £135,018
Sub-central authority (most councils, NHS bodies, police, fire, schools and universities) £207,720
Notifiable below-threshold contract, central government £12,000 or more
Notifiable below-threshold contract, everyone else £30,000 or more

A notifiable below-threshold contract triggers a below-threshold tender notice and a contract details notice. Below those figures there’s no public notice requirement at all (Procurement Policy Note 023).

Almost every expense software purchase in UK local government lands in the same place: comfortably under the main threshold, comfortably over £30,000 across a three year term.

Public sector procurement route selector

Put in what you're buying and for how long. See which route fits, which rules govern it, and what you have to publish.

Include any extensions you expect to use

Your numbers

What you'll need to publish or keep

    Based on the Procurement Act 2023 thresholds from 1 January 2026 (£135,018 central government, £207,720 sub-central, inclusive of VAT), the notifiable below-threshold limits of £12,000 (central government) and £30,000 (everyone else), and G-Cloud 15 call-off terms of up to four years plus two years of extensions on Lot 2b. A guide, not legal advice: check your own standing orders and the framework's buyer guidance. Calculated in your browser; nothing you enter is stored or sent.

    What the Procurement Act 2023 changed, and what still runs on the old rules

    The Procurement Act 2023 came into force on 24 February 2025 and replaced the Public Contracts Regulations 2015 (PCR) for new procurements. Guidance that describes the open procedure, the restricted procedure and OJEU-style notices without mentioning the central digital platform predates the current law.

    The transitional trap that catches G-Cloud buyers

    The Act didn’t retrospectively convert existing frameworks. Contracts awarded through a framework set up under the previous legislation continue to be managed under that legislation. A call-off awarded under a PCR framework still needs the relevant PCR notices until it ends, even after the framework itself has expired.

    G-Cloud 14 was established on 29 October 2024, before the Act commenced. So any G-Cloud 14 call-off signed before the framework expired is governed by the PCR, not the Procurement Act, for its whole life. A four year call-off signed in September 2026 is a 2015-regime contract you’ll be administering into 2030.

    G-Cloud 15 is a Procurement Act framework. So for the next few years, a public body can easily run two expense-adjacent contracts under two different procurement regimes at the same time.

    That isn’t a reason to panic. It’s a reason to write the governing regime on the contract file at signature, rather than working it out three years later when somebody asks.

    The central digital platform

    The central digital platform went live on 24 February 2025. It’s an enhanced Find a Tender service plus a Supplier Information Service, and it’s free.

    Suppliers register once and submit core information: legal name and address, Companies House number, VAT number, connected persons, recent accounts, and any mandatory or discretionary exclusions under the Act. They then generate a share code and give it to buyers instead of retyping the same details into every selection questionnaire. G-Cloud 15 suppliers had to register before applying.

    Two things follow for you as a buyer:

    • You can check a supplier’s registered information before you talk to them, including whether they’ve declared an exclusion.
    • Since 1 April 2026, the winning supplier on a below-threshold contract has to register on the platform to get a unique identifier, so check it early rather than at the end.

    The notices that arrived in 2026

    The Act runs transparency across the whole contract life, not just the award. Three notices started in 2026 and change what your finance system has to produce:

    Notice Live from What you publish
    Payments compliance notice 1 January 2026 (1 April 2026 in Wales) Every six months: average days to pay, and the share of invoices paid within 30 days, 31 to 60 days, and beyond 60 days
    Contract payment information 1 April 2026, for contracts procured on or after that date Every payment over £30,000 including VAT, published quarterly within 30 days of quarter end
    Contract performance notice 1 January 2026 For contracts over £5 million: performance against at least three key performance indicators (KPIs), annually, and within 30 days of a breach or poor performance

    Section 68 of the Act implies 30 day payment terms into public contracts, which is what the payments compliance notice reports against.

    For a call-off under a framework, the notice load is lighter than for an open procurement. You don’t publish a tender notice, and a transparency notice under section 44 is only needed before a direct award under sections 41 or 43, not for a framework call-off. You do publish a contract details notice within 30 days of signing. That’s the whole efficiency argument for G-Cloud.

    How public spending rules affect your expense data

    Public bodies publish far more about their spending than a private business ever has to, so expense data needs a little more thought at set-up.

    Central government departments publish spending over £25,000 each month. Local authorities publish expenditure over £500, and every government procurement card transaction, whatever the amount. Those records usually show the merchant, the amount, a spend category, and often a short description of what it was for.

    Staff expense claims reimbursed through payroll don’t normally appear in that published data, but card spend does, and almost anything else can be requested under Freedom of Information (FOI). Three practical points follow:

    • Structure the description field: set categories and a required, validated purpose field, so a published line reads “travel to regional meeting” rather than whatever someone typed in a hurry. It’s simple to set up at implementation, and much harder to change once years of history exist.
    • Think about who holds a card: every procurement card transaction is published, so a £4.20 coffee on a card is public in a way the same coffee claimed back through payroll isn’t. That’s worth weighing when you decide how widely to issue cards.
    • Assume FOI can reach it: approval trails and, in some cases, receipt-level detail can be requested. Design the fields on the basis that they may be disclosed.

    Before you talk to a supplier

    Write the requirements down first, and date the document. It’s the cheapest possible protection against the most common audit finding, and it takes an afternoon.

    Then check which framework your purchase sits on. G-Cloud 14 expired on 28 October 2026, so a new purchase goes through G-Cloud 15 under the Procurement Act. Any G-Cloud 14 call-off already signed runs its full term under the terms in force at signature, so record the regime on the contract file.

    And before you sign, look at the description field. Anything that reaches published spend data, card transactions especially, stays public indefinitely. Structured categories and a validated purpose field cost nothing to configure at implementation and are close to impossible to impose afterwards. Of everything here, that’s the decision most likely to matter to somebody five years from now.

    On that last point, Capture Expense for government has staff choose the project code and cost centre at submission, then reports on both with every approval, receipt and export timestamped, which turns a published spend line into something explicable. Approval workflows are multi-stage and conditional, so they can follow a scheme of delegation rather than a reporting line. Book a demo to see it set up for a public sector body, or find us on G-Cloud 15.

    Frequently asked questions

    Q. What is G-Cloud 15?

    A. G-Cloud 15 (RM1557.15) is the current Crown commercial agreement for buying cloud services in the UK public sector, run by the Government Commercial Agency. It was awarded on 6 August 2026, opened to buyers in September 2026, and runs to 5 August 2030 under the Procurement Act 2023. Expense software sits in Lot 2b, Software as a Service.

    Q. How do public bodies buy expense software?

    A. Most buy through G-Cloud 15, in Lot 2b Software as a Service. You write requirements first, filter the catalogue, shortlist against those written requirements, award through either call-off procedure, and keep the audit trail for at least three years.

    Q. Do we have to run a tender?

    A. Not a full one. Framework call-offs don’t need a tender notice or a mandatory standstill period. You do publish a contract details notice within 30 days. Below £12,000 for central government or £30,000 for everyone else, no public notice is needed at all.

    Q. How long can a G-Cloud contract run?

    A. On Lot 2b, where expense software sits, up to four years plus up to two years of extensions, so six years in total. That’s longer than G-Cloud 14’s 48 month cap, and the hosting lots allow up to eight years.

    Q. Which procurement regime governs our contract?

    A. It depends on when the framework was established, not when you sign. G-Cloud 14 was established in October 2024, so its call-offs run under the Public Contracts Regulations 2015 for their whole life. G-Cloud 15 call-offs run under the Procurement Act 2023.

    Q. Does a G-Cloud listing mean the software has been assessed?

    A. Not for your requirements. G-Cloud 15 scored suppliers on quality, price and social value at application, but nobody tests a service description’s claims against your use case, and there’s no certification that the software does what you need.

    Q. What gets published about our expense spend?

    A. Central government publishes items over £25,000 monthly. Local authorities publish items over £500 and every procurement card transaction with no lower threshold, including a free-text description of the purpose.

    Want this handled automatically?

    Capture Expense reads receipts, applies your policy and posts to your finance system. Live in four to six weeks.

    Book a demo

    See how simple expenses can be

    Book a 30 minute demo with one of our team, or start a free trial and explore a ready-made workspace with your own data.

    Rated 4.9 out of 5 on Capterra No credit card for the trial Reply within one working day

    Free trial Book a demo