Paying a bill in Bills Must Be Paid is a timing decision. The Steam description confirms that bills appear during a run, ignoring them lets the collector take a cut, and paying them can unlock a perk. It does not publish one universal timer, price or best threshold. Those values can differ between a demo build, the full game and a patch, so use this guide as a decision framework and use the current screen for the final number.
The payment routine
First, read the bill rather than clicking through it. Identify the amount, the time or state shown by the current build, and the perk offered after payment. Second, compare that requirement with your cash, stamina and the field. Third, ask whether one short smash window can safely cover the gap. If the answer is no, pay or accept the loss instead of turning a manageable bill into collector pressure. Fourth, select the perk that fixes the bottleneck you actually felt in the run.
When a short delay is reasonable
A delay can make sense when a nearby target is easy to hit, your stamina is healthy and the next payment is clearly reachable. It is risky when the target is moving, loot is inconsistent, the hand is nearly tired or the field requires a long detour. The more uncertain the income, the less value there is in waiting for a perfect payout. A smaller guaranteed payment can protect more future progress than a lucky target that costs the run.
How to choose the perk
Read perks as modifiers to the next decision. A stamina-related option is useful when the run ends before the bill cycle is complete. A grip, wrist or hammer option may help when swings fail to clear targets. Luck can be attractive when random loot is the limiting factor, but it is not a promise of a particular drop. If the perk wording is ambiguous, capture the exact text in your notes and test it once before calling it best.
Collector and bankruptcy warning
The collector’s cut changes the value of every later coin. If you keep delaying, compare the projected loss with the cost of payment, not only the cost of the next upgrade. If the current build has a bankruptcy outcome, read Bankruptcy and the Collector before spending a long run’s earnings. Do not copy numeric advice from a discussion unless it names the same AppID, build context and date.
Sources and live checks
The payment and collector rules are confirmed on the [Steam store page](https://store.steampowered.com/app/4421010/Bills_Must_Be_Paid/ “Official Steam store page” rel=“nofollow ugc”). The launch feature list is also discussed in the [official Steam Community hub](https://steamcommunity.com/app/4421010 “Official Steam Community hub” rel=“nofollow ugc”). Current amounts, deadlines, perk names, payment animation and balance are live-check information.
Three common mistakes
The first mistake is saving every coin for a future upgrade while the current bill is already reducing later income. The second is paying immediately without reading the perk or noticing that a safe target could fund the payment. The third is trusting an old threshold without checking whether it describes the demo. Each mistake comes from treating a bill as a static price rather than a state that changes the value of time, stamina and loot.
A note-taking template
Write the date and product at the top. Then record the bill text, amount, displayed deadline, current cash, stamina state, collector status, available perk and the target you considered. After the decision, note the result: payment completed, collector changed, run ended or perk improved the next loop. This makes a future update easy because you can compare like with like.
When to stop testing
Stop when the bill outcome is no longer isolated. If a new patch appears, the target table changes, the hammer is replaced or the hand is nearly tired, mark the result incomplete. A clean unknown is more useful than a confident threshold that only worked in one demo build.
A safe comparison rule
When two payment choices seem close, prefer the one whose outcome you can observe and explain. A short, repeatable payment test is more useful than a long chase built on an assumed payout. Record the result with the same AppID and build before turning it into advice.