This is the single Updates tracker for Bills Must Be Paid. It separates official release information from community observations and keeps the full game distinct from the free demo. The base game is Steam AppID 4421010; the demo is AppID 4577620. When a detail can change after a build update, this page points you back to the current store page, game UI or dated developer post.
2026-07-29 - Base game release window
Type: Official release metadata
The official Steam listing identifies Bills Must Be Paid as a Rike Games title released on July 29, 2026. It describes an active incremental loop built around smashing piggy banks, paying bills, stamina, random loot, skill-tree upgrades and different hammers. The same page lists Windows and macOS requirements and Steam features. Release metadata and requirements should be rechecked on the live listing if a later update changes them.
Source: Official Steam listing
2026-06-15 - Launch feature announcement
Type: Official Steam Community post
The launch announcement describes bankruptcy, prestige points based on money paid toward bills, rings and bracelets with upgrades and unique perks, a new desk-gadget shop, more piggy types, more hammers, an ending and additional risk/reward mechanics. This is a first-party feature announcement; exact live values, unlock order and final balance still require an in-game check.
Source: Bills Must Be Paid Steam Community
2026-04-26 - Demo bug-fix context
Type: Demo update context
The Steam Community hub records a demo bug-fix post covering a skill-tree/bill UI issue, a crash on opening for some users, a bill timer display problem and hammer changes. This entry belongs to the demo context and must not be presented as a current base-game patch note without another source.
Source: Official Steam Community hub
Live-check queue
Recheck current bill deadlines, collector behavior, perk text, hammer stats, piggy drop behavior, rare-coin retention, prestige costs and platform requirements in the current base-game build. A dated community comment can explain an observation, but it is not a substitute for the current UI. Use the Links hub for verified destinations and the Guides hub for strategy pages that stay useful across patches.
How to read this tracker
Each entry has a date, source type and scope. “Official release metadata” describes what the store presents. “Official Steam Community post” records a developer-facing announcement or fix. “Demo update context” is narrower because the demo has its own AppID and may not represent the base game’s current build. A community observation can find a question, but it should not become a patch fact without a source.
Maintenance checklist
When a new patch arrives, update the live-check queue first. Confirm the base-game title and AppID, check the store description and news feed, then compare bill wording, stamina behavior, hammer stats, piggy types, rare-coin retention and prestige screens in-game. If one area changed, update the relevant guide and add a dated note here. Do not silently rewrite an old entry: historical context explains why an earlier screenshot no longer matches.
What this tracker does not claim
It does not claim that a launch announcement is a complete changelog. It does not merge the demo and base game. It does not turn a release date into a guarantee about a future patch, discount, mobile plan or browser build. Those boundaries keep the update page useful and auditable.
How updates should change the guides
If a patch changes a bill, add the date here and revise How to Pay Bills with the new decision rule. If a hammer or piggy behavior changes, update its child page and keep the old comparison in history. If a new prestige or shop system is confirmed, add it to Upgrades with the product scope. If only a bug is fixed, update Systems or the relevant troubleshooting note. This one-direction handoff prevents every article from becoming a duplicate changelog.
Evidence tiers
First-party store text and developer announcements are confirmed for the claims they actually make. A Steam Community bug report is official context but may describe only a past build or the demo. A player discussion is community-observed. The current UI is the final source for a value that affects today’s run. Labeling these tiers lets readers use useful observations without confusing them with patch guarantees.
Maintenance cadence
Review the tracker after a release announcement, after a visible store update, and whenever a guide receives a report that its UI no longer matches. Record the review date even when no changes are found. “No confirmed change” is a useful status when the search result is noisy or the source scope is unclear.
How to read this tracker
Use the dated entry to establish what a first-party source said and use the linked page to verify what the current build shows. A launch feature is not automatically a current number, and a demo bug report is not automatically a base-game rule. This separation is the main maintenance rule for every child guide.
When adding an entry, name the source type, date the observation, preserve the exact AppID and state what remains to be checked. Link the affected child page only after the change has a clear scope. If a community report and the live UI disagree, record the disagreement and let the current UI answer the mutable part. That makes the tracker a useful maintenance log instead of a pile of unqualified patch claims.