Most issues in Pluto fall into a small number of categories. This article walks through the most common problems and their solutions. If something here doesn't resolve your issue, open a support ticket: on the web, select your avatar, then Help & Support; in the mobile app, choose Help & Support in your profile menu, then Support Tickets.
Safe to Spend is only as accurate as the data feeding it. The most common causes of a surprising number are:
If bills aren't scheduled, they're not subtracted from Safe to Spend. Go to the Accounts tab, open each account, and confirm all regular expenses have active schedules in the Schedules section. The ghost expense candidates flagged by Pluto Pulse are a helpful starting point for finding gaps.
Pluto flags accounts with a stale balance warning when the balance is more than a day old. For bank-connected accounts, open the Accounts page and select the Bank connections card, select the bank, then select Sync Now to force a refresh. If the connection is down or you're on a manual account, you can update the balance directly from the account: open the account, tap the settings menu, and enter the current balance from your bank.
The through date for each account is determined by its Income Sources setting — the income schedule Pluto uses to define your pay period. If the through date looks wrong, open the account, tap the settings menu (the three-dot icon), and check the Income Sources selector under Safe to Spend Calculations. Selecting a different income source will change which pay period Pluto is looking ahead to. A longer through date includes more upcoming bills, which can make Safe to Spend look lower.
If a bank transaction posted but wasn't matched to a planned transaction, the planned expense still shows as upcoming — potentially double-counting it. Review your Needs Attention section in the Activity tab and confirm any pending matches.
If your bank updated your balance before sending the deposit, Pluto marks the planned paycheck Already in your balance in the Safe to Spend breakdown and stops adding it, so it isn't counted twice. If it shows as added while your balance already includes it, the next sync after your bank moves the balance should catch it. If a paycheck is marked but hasn't really arrived, select Not yet beside it. See Safe to Spend: A Complete Breakdown.
Most banks take 1–3 business days to post a transaction after authorization. Pending transactions are not final and may not appear in Pluto yet.
Open the Accounts page and select the Bank connections card, then select Sync Now for the bank. Some banks throttle refresh requests, so if no new data returns, wait until the next overnight run.
Open the Accounts page and select the Bank connections card. Connections that need attention are listed at the top under Needs Your Attention, each with what's wrong and what to do about it. A re-authentication prompt usually means your bank updated their security requirements.
Bank connections break for a few common reasons: your bank password changed, your bank started requiring a new form of multi-factor authentication, or there was a bank-side system update or outage.
Log into your bank's own website to confirm your credentials work. This rules out a forgotten password change.
Open the Accounts page and select the Bank connections card. From there you can re-authenticate your bank connection through the secure connection flow.
If the connection error appeared suddenly with no credential change, it may be a temporary bank outage. Wait 24 hours and try again before contacting support.
To inspect a schedule, go to the Accounts tab, open the account it belongs to, scroll to the Schedules section, and tap the schedule card to open its action sheet. From there, tap Edit Schedule to review its settings.
In the schedule's action sheet, a Pause Schedule option indicates it is currently active. If the schedule has already been paused, you'll see a Resume option instead. Tap Resume to reactivate it.
Open the schedule via Edit Schedule and check the Advanced options for an end date. If an end date was set and has passed, the schedule has stopped generating transactions. Remove or extend the end date if it should continue.
If the start date is in the future, the schedule hasn't begun yet — this is expected.
The schedule card in the account's Schedules section shows the next occurrence date. If it's further out than expected, open the schedule via Edit Schedule and review the recurrence pattern.
Duplicates most commonly occur when the same bank transaction file is imported twice, or when two import date ranges overlap. Pluto's duplicate detection handles most of these cases automatically, but if duplicates do get through, find the duplicate pair in your transaction list and delete one of them. If you imported a large batch with many duplicates, contact support for help with bulk removal.