How do we keep bills paid if the person who handles our money is unavailable?

Keep bills paid by preparing instructions that another person can use without the usual money handler's help. The backup needs a current bill list, enough money in the payment accounts, and access they are already authorized to use. Confirm which payments run automatically, assign the remaining actions, and test the arrangement before an illness or trip makes it necessary. Seeing an account balance or a bill does not give someone permission to make a payment.

Continuity requires instructions, money, and permission

A bill list answers what needs paying, but not whether the payment will happen. A complete backup plan also answers where the money comes from, what runs unattended, and what the backup can actually do. Missing any one of those pieces can leave a known bill unpaid.

Plan for the usual money handler to be unreachable, not available for a quick code or explanation. The backup should be able to find the next payment, check its status, and complete any permitted action without improvising. This is temporary coverage, not a redistribution of the household's normal money jobs.

Build a payment checklist the backup can follow

1. List the bills that could come due during the absence. Record the biller, amount or estimate, due date, payment account, and where to find the current bill. Include less frequent payments such as insurance renewals and annual memberships. Use recent statements and upcoming notices rather than relying only on last month's list.

2. Map the money that will fund those payments. Write down the usable starting balance and each expected deposit or scheduled transfer, including its source and date. Account for outstanding payments the balance does not already reflect, without subtracting anything twice. Reserve room for groceries and other essentials if they use the same account; a balance earmarked for bills is not entirely free to spend.

3. Verify every automatic payment. Check autopay at the biller or bank that actually schedules it, and record the amount setting, payment account, and next scheduled date. Distinguish a fixed-dollar instruction from one that follows the bill amount. Mark each item as automatic, manual, or not yet confirmed; an old payment in the history is not proof that the next one is scheduled.

4. Write the manual actions as instructions. Name the person covering each payment, the approved payment channel, and when they must act. Check the bank's processing instructions and the biller's deadline rather than assuming a payment sent on the due date will arrive in time. Include non-payment tasks that could interrupt service, such as responding to a renewal notice or correcting a rejected payment.

5. Record access without recording secrets. Note which institution-approved access the backup has, where the bill is delivered, and the biller's contact information from an official statement. Keep sensitive documents somewhere secure and accessible to the intended person. Do not put passwords, security answers, or one-time codes in the checklist.

6. Define when coverage starts and ends. Agree on the trigger, such as the start of a trip or a message that the usual handler cannot act. Record the last completed payment and any scheduled or pending items at handover. During coverage, the backup logs actions and confirmations so the returning person does not pay the same bill again.

A worked month keeps $3,200 of bills covered

Suppose you prepare for the usual money handler to be unavailable throughout October. The dedicated bills account starts with $2,000, and two scheduled transfers add $1,600 on October 3 and $1,600 on October 17. Everyday purchases use a different account.

The example assumes the starting balance reflects earlier activity, the transfers are usable on the stated dates, and no other withdrawals occur. Dates below are planned account debit dates, not promises about payment processing; the backup chooses submission dates using the bank and biller instructions.

The six automatic payments total $2,920. Water and the medical bill require $280 of manual payments. Automatic means no fresh payment instruction is needed for that cycle, not that the backup can ignore whether the payment succeeds.

The funding calculation is $2,000 + $1,600 + $1,600 − $3,200 = $2,000 at month end. But the lowest balance is only $400, immediately after rent leaves and before the first transfer arrives. The ending balance therefore hides the vulnerable point: an extra withdrawal or a delayed transfer could disrupt the plan even though the month looks comfortably funded overall.

The backup checks that both transfers arrive, watches for failed automatic payments, and handles the two manual bills. The credit card payment appears because this is a schedule of cash leaving the bills account, not a spending total in which purchases and their repayment should both be counted.

Test transaction authority before the absence

Visibility, login access, and permission to transact are different things. A person might be able to read a shared spending report but have no authority to move money from the underlying account. Ask each relevant institution what access the backup already has and what actions that access permits.

For a planned trip, have the backup sign in through their own approved access and complete a normal permitted task while the usual handler is available. Check access to the bill itself as well as the payment account. A working bank login is not enough if the only copy of a manual bill is in an inaccessible inbox.

For a possible absence involving incapacity, discuss a financial power of attorney with a qualified attorney. Its scope and use depend on the document and applicable law; ask the institution what it needs to recognize the authority before relying on it. Do not assume a household relationship or inclusion in a shared tracker settles that question.

Do not share passwords, forward authentication codes, or use the unavailable person's signed-in session as the backup plan. If approved access fails, contact the institution about the backup's own access and permitted options. The plan should work within account controls, not depend on bypassing them.

Monitor exceptions and leave a clean handback

During the absence, review the checklist before each cluster of payments and after expected withdrawals. Keep scheduled, pending, and completed payments distinct. A reminder says a bill needs attention; it does not prove a payment has been submitted or accepted.

If an automatic payment appears to fail, check both the bank and biller before sending another payment. Record any changed amount, delayed deposit, unresolved bill, or conversation with a biller. When the usual handler returns, hand over that short exception list alongside the payment confirmations.

Refresh the plan whenever a payment account, bill, access arrangement, or funding source changes. For a longer absence, extend the checklist to cover later renewals and funding dates rather than assuming the first month repeats unchanged. A bill calendar can provide the schedule, with the backup instructions kept beside it.

Common mistakes

• Treating automatic payments as guaranteed payments. Scheduling does not replace checking funding, the payment method, and completion.
• Checking only the month-end balance. A payment can come before the deposit intended to cover it; inspect the balance between payment dates.
• Leaving instructions in one person's inbox. The backup needs an authorized way to obtain the current bill, not just the name of the biller.
• Assuming shared visibility grants bank authority. Confirm transaction permissions separately with the institution before relying on them.
• Paying again because a bill still looks unpaid. Check scheduled and pending activity before sending another payment.
• Skipping the handback. An unrecorded action can become a duplicate payment when the usual handler resumes work.

Common questions

Is autopay enough if the usual money handler is unavailable? Not by itself. The payment account still needs funding, the payment method must remain usable, and someone needs to catch exceptions. Keep a separate list of bills requiring manual action, including new bills that have not been added to an automatic arrangement.

Can the backup pay a bill just because they can see it? No. A bill list or shared financial view is information, not transaction authority. Confirm what the backup is permitted to do through the relevant institution, using their own approved access, before relying on them to submit payments.

What if the expected income or transfer does not arrive? Recalculate the account balance against the next payments immediately. Identify the shortfall, check whether other usable money is available without endangering essentials, and contact affected billers about options before their deadlines. An access plan cannot compensate for missing funds.

How often should we test the backup plan? Choose a regular review, such as every three months, and repeat the test after a major account or payment change. Before a planned absence, confirm the next bills, account funding, and the backup's approved access again. The review interval is a household choice, not a banking requirement.

How Zypper handles this

On a couple plan, the household owner can invite a partner or family member through Settings › Members; the invited person gets a separate login to the household's shared financial accounts, transactions, and budgets, as described in Inviting your partner or family member. Zypper also detects recurring groups from transaction patterns and shows the next expected payment and amount, giving the backup visibility into predicted bills rather than confirmation that a bank payment is scheduled; see Recurring transactions and bill tracking. Shared visibility does not authorize bank payments, so arrange the backup's transaction authority separately with each institution. For a shared household view, get started with Zypper.