← All vendorsPaid by the cityOVERDRIVE INC
The city's published checkbook records $14,206,198 paid to OVERDRIVE INC across 272 payment lines, from FY2018 to FY2026.
Name as the city files it — often the legal name, not the trading name. The city's budget year runs July 1 to June 30, so FY2026 means July 2025 through June 2026.
By fiscal year
FY2018$141,135
FY2019$665,106
FY2020$570,852
FY2021$847,723
FY2022$1,312,900
FY2023$1,275,000
FY2024$3,050,000
FY2025$3,516,967
FY2026$2,826,515
A dash means no payment to this vendor appears in that year's file. The city publishes this a few times a year, so it runs behind — the newest payments can take a few months to appear, and a fiscal year that has just ended usually isn't published at all yet. Treat the most recent year as incomplete.
How these purchases were made
Service Rel. Order — $10,626,049
Vendor Invoice — $2,683,607
PO Emergency — $802,723
PO One-time — $68,820
PO Contract Release — $25,000
These are the purchasing routes the city recorded: 6% was bought under emergency procurement rules. The city publishes the route, not the reason for it.
Contract billed under
A contract number is the city's master agreement; individual purchases are released against it and don't each go back to council for a vote.
Where this comes from
Every figure on this page is summed from , FY2018–FY2026. PlainDocket stores the totals; the individual payments stay on the city's portal, where you can filter them yourself.
- These are payments, not a budget. The same ledger carries debt payments, bank and pension transfers and accounting reversals alongside what the city bought, so adding it all up doesn't describe city spending — which is why you won't find a citywide total here. What a named vendor or department was paid is solid.
- This covers what the city paid — not what a council vote approved. A contract approved years ago can still be generating payments, and money approved recently may not have been paid yet.