Before you install, buy or troubleshoot Bills Must Be Paid, check the destination and product scope. The full game is AppID 4421010. The demo is AppID 4577620. Both are connected to Rike Games, but they can have different menus, limits, balance and bug history.
The three checks
Check one: title and AppID. The canonical base-game destination is [Bills Must Be Paid on Steam](https://store.steampowered.com/app/4421010/Bills_Must_Be_Paid/ “Bills Must Be Paid base game” rel=“nofollow ugc”). Check two: publisher. The official page identifies Rike Games as developer and publisher. Check three: announcement source. Use the [Steam Community hub](https://steamcommunity.com/app/4421010 “Official Steam Community hub” rel=“nofollow ugc”) for dated posts, and [Rike Games](https://rikegames.com/bills-must-be-paid “Rike Games official site” rel=“nofollow ugc”) for developer-authored product information.
Demo comparisons
If an article or video discusses the demo, label it clearly and keep it in the demo section of your notes. A demo bug report can be useful evidence of a past issue, but it does not prove that the base game currently behaves the same way. Check the release date, post date and product name before repeating it.
Security reminders
There are no official code or generator claims in the evidence used for this guide. Do not download an executable, browser extension or “verification” tool offered by an unofficial page. Steam login and payment actions belong on Steam. Report suspicious links rather than testing them with an account.
Source status
The URLs above are first-party destinations checked for this guide. Store text, community posts, release dates and game mechanics can change, so read the live page when a decision depends on current information.
Link verification record
For each destination, record the final URL, page title, AppID if shown, developer or publisher, date checked and why the link is useful. A base-game purchase link should not be used as proof of a demo-only bug. A developer page should not be presented as a Steam patch note. A community hub should not be presented as an official system-requirement page. Matching source to claim is as important as checking that the URL opens.
If a search result looks convincing
Open the result and inspect the destination before following its instructions. Confirm that the domain is Steam, Rike Games or another source you intentionally trust. Do not install a file offered by a “code,” “generator” or “verification” page. The game has no verified code system in this audit, so a reward claim is a security warning rather than an invitation to test it.
Update hygiene
When a first-party destination changes, update the link label and source date. Keep the old date in the update tracker if it explains a previous guide. This gives readers a clear path from a current page to a dated historical claim.
The same record should be carried into localized pages so a translated link never silently changes product scope.
If the page is unavailable in a region, keep the canonical URL and explain the destination rather than substituting an unverified mirror.
Canonical destination policy
Use the canonical Steam URL with the base AppID in metadata and visible link text where space allows. Keep the developer page separate from the Steam page, even when it links back to the same game. Do not attach an unofficial price, release date or download claim to a first-party link. If a page redirects, verify the final domain and record the redirect date.
This keeps a safe link useful even when store presentation changes.
It also gives search visitors enough context to avoid the sibling demo.
Keep that context in every locale.
Link-check checklist
Before publishing a link, open it, confirm the domain and AppID, read the surrounding label, and check that the destination matches the claim. Keep the base game and AppID 4577620 demo separate. If a destination changes, update the link and date rather than leaving a stale redirect as evidence. This check protects every locale from a copied sibling-product URL. It also keeps search visitors from confusing a demo fix with a full-game rule.