← All vendorsPaid by the cityJOHN BEAN TECHNOLOGIES CORPORATION
The city's published checkbook records $28,530,340 paid to JOHN BEAN TECHNOLOGIES CORPORATION across 621 payment lines, from FY2018 to FY2022.
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$6,862,529
FY2019$8,030,499
FY2020$7,834,572
FY2021$4,489,220
FY2022$1,313,520
FY2023—
FY2024—
FY2025—
FY2026—
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 — $25,055,693
PO Contract Release — $3,426,813
PO One-time — $50,000
Vendor Invoice — -$2,166
These are the purchasing routes the city recorded. None of this vendor's payments were flagged sole-source or emergency.
Contracts billed under
4600012673 — $16,882,564
4600014008 — $11,599,942
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.