This article is general information, not legal advice. It summarizes the statute and publicly available Comptroller guidance as of July 29, 2026. Procurement decisions on any specific purchase should be reviewed with your district's or municipality's counsel before you act.

The short version

General Municipal Law §103(1) requires advertised competitive bidding for contracts for public work involving an expenditure of more than $35,000 and purchase contracts involving an expenditure of more than $20,000.

Almost nobody gets in trouble on the thresholds themselves. Districts get in trouble on the measuring. The statute does not ask whether this order exceeds $20,000. It asks whether the reasonably expected aggregate of all purchases of the same commodities, services or technology, across a twelve-month period, across every vendor you buy them from, exceeds it. A district can place eight orders of $3,000 each, never see a number over five figures on a single purchase order, and be squarely over the threshold the whole time.

That is the aggregation rule, and it is the most common way a routine purchasing operation drifts out of compliance without anyone deciding to.

The two thresholds, and one word that matters

Public work: more than $35,000. Purchase contracts, including contracts for service work: more than $20,000.

Note the "more than." The threshold is exceeded at $20,000.01, not at $20,000. A contract at exactly the threshold amount is below it. This sounds pedantic until someone writes a specification or a policy that says "contracts of $20,000 or more," which quietly moves the line and creates a self-imposed requirement stricter than the statute — which you must then follow, because your own policy binds you.

Which threshold applies is a classification question, and it is less obvious than it looks. "Public work" is not defined by whether the job involves labor. Following a series of amendments a decade and a half ago, the Comptroller's guidance takes the position that services — other than those necessary for the completion of a public works contract subject to the prevailing wage requirements of Labor Law article 8 — are now generally categorized as purchase contracts, not contracts for public work. OSC's stated view is that absent statutory or judicial clarification, the safest approach is to apply the $20,000 threshold to such services.

So a maintenance agreement, a service contract, or a repair engagement is presumptively measured against the lower number. If your instinct on a $28,000 service contract is "under $35,000, no bid required," that instinct is running the wrong test.

Separately: for building construction, Wicks Law (GML §101) layers its own separate-specification thresholds on top of all of this. That is its own article. The point here is only that §103's $35,000 figure is not the last word on construction procurement.

The aggregation rule, in the statute's own words

Here is the operative language, because paraphrase is where this rule gets softened into something it is not:

"In determining whether a purchase is an expenditure within the discretionary threshold amounts established by this subdivision, the officer, board or agency … shall consider the reasonably expected aggregate amount of all purchases of the same commodities, services or technology to be made within the twelve-month period commencing on the date of purchase."

Four things in that sentence do real work.

"Shall consider." This is not optional planning advice. The estimate is a statutory duty that attaches at the moment of purchase.

"Reasonably expected." The test is forward-looking and predictive. You are not totaling what you have already spent; you are estimating what the district will spend on this category over the coming year. A purchasing agent who genuinely could not have anticipated a mid-year spike is in a different position than one who knew the pattern and ignored it — which is why the documentation, discussed below, matters.

"All purchases … within the twelve-month period commencing on the date of purchase." The window is rolling and forward from each purchase — not the fiscal year, not the calendar year. A purchase in March is measured against expected purchases through the following February. Budget-cycle thinking is the wrong frame, and it is the frame everyone naturally uses.

Across all vendors. The Comptroller is explicit that the aggregate is counted whether the purchases are from a single vendor or multiple vendors. Splitting the year's copy paper between two suppliers does not divide the number. OSC's own illustration makes the point: Vendor A projected at $14,500 and Vendor B at $10,000, no single order anywhere near the threshold, and the answer is that competitive bidding or a competitive offering is required, because the aggregate is $24,500.

What counts as "the same"

The statute says "same commodities, services or technology" and defines none of those words. The Comptroller's guidance fills the gap with a functional test: commodities, services or technology that are "similar or essentially interchangeable" should be considered the same for this purpose.

That is a substitutability standard, not a SKU match. Two brands of copy paper are the same commodity. Letter and legal stock are almost certainly the same commodity. Copy paper and toner are not — they are not interchangeable — even though both come from the office-supply budget line and possibly the same vendor. The budget code is not the unit of analysis; the market is.

"Technology" has a statutory anchor the other two lack: State Finance Law §160(10) defines it as a good or a service or a combination that results in a technical method of achieving a practical purpose or in improvements in productivity. That is broad enough to sweep hardware, software, and IT services into one category faster than most districts expect, and it deserves particular care because technology spending is exactly where purchases accrete in small increments across a year.

There is judgment at the margins of "similar or essentially interchangeable," and reasonable people can classify differently. What you cannot do is classify with the answer in mind — drawing category lines narrow precisely so each category ducks under $20,000. Which brings us to the prohibition.

Artificial division

The statute is blunt: purchases "shall not be artificially divided for the purpose of satisfying the discretionary buying thresholds." The Comptroller reads the same principle into contracts for public work — you cannot phase a $60,000 job into two $30,000 jobs to stay under $35,000 either.

Two honest observations about how this plays out in practice.

First, artificial division is rarely a scheme. It is usually an accident of decentralization: five buildings ordering the same commodity independently, nobody totaling across the district, every individual decision defensible in isolation. The statute does not care that it was innocent. The aggregate is the aggregate.

Second, this is a standard audit finding — the kind that appears in Comptroller audits of school districts with enough regularity that the fact pattern is practically a template: recurring purchases of the same commodity, spread across vendors or across the year, aggregate over threshold, no bid, no exception documented. If you want to know what the finding looks like, read a few OSC district procurement audits; the language barely changes.

The renewal trap

Buried in the same subdivision is a rule that gets far less attention than it deserves, so here it is in full:

"A change to or a renewal of a discretionary purchase shall not be permitted if the change or renewal would bring the reasonably expected aggregate amount of all purchases of the same commodities, services or technology from the same provider within the twelve-month period commencing on the date of the first purchase to an amount greater than the discretionary buying threshold amount."

Translate: you made a lawful below-threshold purchase — say $14,000 of a service under your §104-b quote procedures. Mid-year, you want to extend or expand it. If the change would push the twelve-month aggregate from that provider past $20,000, the statute prohibits the change. Not "requires you to bid the increment" — prohibits the renewal as a discretionary purchase at all. The clock on this one runs from the date of the first purchase, and unlike the general aggregation rule, this one is provider-specific.

This is the provision that catches the well-run office. The original purchase was clean. The vendor performed. Extending feels like the responsible move. And it is the moment the statute requires you to stop and run the competition you skipped — lawfully — the first time.

Below the threshold is not a free zone

A number under $20,000 does not mean "buy however you like." GML §104-b requires every political subdivision to adopt written policies and procedures governing procurements that are not subject to bidding — verbal or written quotes at set dollar bands, documentation of the selection, justification when the low quote is not taken. Whatever your policy says, it binds you; an auditor will test your below-threshold purchases against your own document, not against the statute's silence.

The honest way to think about the architecture: §103 governs above the line, §104-b governs below it, and the aggregation rule decides which side of the line you are on. There is no unregulated territory. I have written separately about what belongs in a §104-b policy and how the annual review works — that piece is the companion to this one.

What this rule is not

The aggregation rule decides whether competition is required. It does not decide the form. Above the threshold, a purchase contract may be awarded to the lowest responsible bidder or — if your board has authorized it by resolution adopted at a public meeting — on the basis of best value. And a required competition can still be satisfied through a lawful exception: OGS state contracts under GML §104, county contract purchasing under §103(3), piggybacking under §103(16) for what remains of it after Lynch and the NYSED guidance, emergencies under §103(4), true sole sources, professional services under the case-law exception, and surplus purchases from other governments under §103(6).

Every one of those is its own analysis with its own documentation. The mistake to avoid is running them in the wrong order: the exceptions answer "how do we satisfy the requirement," and the aggregation rule answers the prior question, "does the requirement apply." A district that reaches for an OGS contract on a $12,000 purchase has skipped a step that costs nothing; a district that treats a $12,000 purchase as exempt without ever estimating the annual aggregate has skipped the step that produces findings.

What the file should show

The Comptroller's guidance says planning documents should state how the amount was determined and whether the procurement will be a purchase contract or a contract for public work. In practice, the defensible file for a discretionary purchase has three sentences in it:

1. The category, and why its edges sit where they do — what you treated as "the same," in interchangeability terms.
2. The twelve-month estimate and its basis — last year's actuals, enrollment or building changes, known projects.
3. The classification — purchase contract or public work — and therefore which threshold governed.

Written at the time of purchase, that record converts a judgment call into a documented, reasonable estimate. Written after the auditor's document request, it converts nothing.

If you are not in New York

The dollar figures and section numbers above are New York's, but nearly every state's local procurement statute pairs a bidding threshold with an anti-fragmentation rule, and the failure mode is identical everywhere: decentralized small purchases of the same thing, aggregating past a line nobody was watching.

Three questions locate your state's version. First, what is the aggregation window — a fixed fiscal year, or a rolling period the way New York measures forward from the date of purchase? Second, what is the unit of sameness — some states aggregate by vendor, New York aggregates by commodity across all vendors, and the difference is enormous. Third, is there a renewal or change-order provision that separately polices growth of a contract that started below the threshold? Your answer to the second question matters most, because vendor-based aggregation is easy to comply with by accident and commodity-based aggregation is easy to violate by accident.

Disclaimer. This article is provided for general informational purposes only and does not constitute legal advice, nor does it create any advisory or professional relationship between the author, BidLogiQ, LLC, and any reader. It reflects the statute and publicly available guidance as of July 29, 2026; statutes, regulations, agency guidance, and case law change, and this article may not reflect subsequent developments. Application of these authorities depends on the specific facts of a given procurement. Readers should consult their own counsel and, where applicable, the Office of the State Comptroller before making procurement decisions. The author and BidLogiQ, LLC disclaim any liability for actions taken or not taken in reliance on this article. The views expressed are the author's own and are not those of any employer or client.