Random loot is the reason Bills Must Be Paid can feel different from run to run. The official store page says piggies spawn random loot and that rare coins can be collected. That confirms the system’s shape, not a table of guaranteed values. If a guide gives a drop percentage or says one piggy is always best, check the AppID, build and evidence before trusting it.
Separate income from collection
For a bill decision, regular money that reaches the current payment screen is the immediate objective. A rare coin can be valuable for collection or a later system, but it may not solve the bill in front of you. Mark which reward you saw, where it went, and whether the current UI treats it as spendable cash, a collectible or a separate resource.
Test variance without wasting runs
Use a low-pressure window to observe a piggy type. Keep the hammer and route stable, record several results and write down the date. Do not reset your conclusion after one lucky stack. When a bill is close, choose reliable targets even if an unusual drop might be more exciting. Risk is easier to justify when the collector pressure is low and stamina remains healthy.
Rare coins and route planning
If the game exposes a collection screen, read its wording and retention rule. A rare coin may persist across runs, or it may be a run resource; never assume. After a bankruptcy or update, confirm whether the collection is still present. This is where Prestige, Rings and Bracelets and Updates help keep long-term systems separate from ordinary loot.
Useful record format
Record product (base game or demo), date, visible build, piggy name, hammer, stamina state, bill state, observed reward and any screen text. This turns an anecdote into a reproducible observation without pretending it is official balance data.
Sources
Random loot and rare coins are named on the [official Steam page](https://store.steampowered.com/app/4421010/Bills_Must_Be_Paid/ “Bills Must Be Paid on Steam” rel=“nofollow ugc”) and the [developer page](https://rikegames.com/bills-must-be-paid “Rike Games product page” rel=“nofollow ugc”). Exact odds and collection behavior are live-check.
A route for uncertain rewards
Use a two-pass approach. In the first pass, keep the bill safe and learn the ordinary reward screen. In the second, test one unusual piggy or rare-coin possibility while stamina and collector pressure are visible. If the test fails, you still know whether target movement, hammer mismatch, low stamina or random loot caused it. If you test only during a desperate bill, you cannot tell whether the reward or timing caused the loss.
Evidence levels
An official page can confirm that random loot or rare coins exist. A repeated live observation can suggest behavior. A community report can identify a lead. None alone proves a drop percentage, guaranteed source, persistence rule or best route. Use confidence labels and keep product scope beside every note, especially when demo and full game show different menus.
Collection questions to ask
Does the coin appear in ordinary inventory, a collection panel or the post-run screen? Does bankruptcy keep it? Is the reward spent on a bill or only on a later system? The current UI answers those questions; a guide should not fill the gap with assumptions.
Until those questions are answered in the base game, describe rare coins as a collection objective and keep their economy unknown.
That wording still gives a player a next step: collect one safely, inspect the screen, and record what persists before spending a run on farming.
Keep farming decisions reversible
Start a rare-coin test when no bill is close and stamina is healthy. If the first result costs too much time or produces an unclear screen, stop and preserve the note instead of sacrificing the run. Repeat only after the same product and build are confirmed. Never turn one lucky result into a guaranteed route. A collection observation still needs its product scope and date, plus the visible result screen and retention state for the current version.