Transaction matching is a premium feature that connects the dots between what you planned and what actually happened. When your bank sends Pluto a new transaction, Pluto compares it against your scheduled expenses and automatically proposes the most likely match. Instead of categorizing every transaction from scratch, you simply review and confirm.

The Matching Process

When a transaction posts to your connected bank account, Pluto's matching engine compares it to your upcoming and recent scheduled events. It evaluates several signals to determine the best match: the transaction amount, the date relative to the scheduled date, the merchant name, which account it came from, and historical matching patterns from your past approvals.

Confidence Score Guide
ConfidenceMeaningTypical Action
95%+Very high — almost certainly correctReview and accept quickly
70–94%Good — probably the right matchGlance at details before accepting
Below 70%Uncertain — review carefullyVerify amount and merchant before accepting

Reviewing and Accepting Matches

  1. Open the Activity tab

    Unmatched transactions waiting for review appear at the top with a highlighted indicator.

  2. Select a pending match

    This shows the proposed match: the actual bank transaction on one side, and the schedule it's being linked to on the other.

  3. Review the details

    Check that the amount, date, and merchant look correct for the proposed schedule.

  4. Accept or reject the match

    Select Accept to confirm the link. Select Reject if the match is wrong — you'll then be able to manually link to a different schedule or mark the transaction as unplanned.

Unplanned Transactions

Not every transaction will match a schedule — impulse purchases, one-off expenses, and new charges won't have a scheduled counterpart. These are flagged as "Unplanned" in your transaction list. Unplanned transactions still reduce your Safe to Spend, so your budget stays accurate even for things you didn't plan ahead.

If an unplanned charge is really a new bill or paycheck, plan for the next one from the transaction itself: Create Expense or Create Income sets up a new account, and Create Schedule adds a schedule to one you already have. Either way, the transaction you started from is linked to the new schedule. See Creating Expenses, Income and Schedules from a Transaction.

Match Quality: why a match was made

Open any matched transaction and expand the Match Quality card to see how the match was scored. It says whether the match was made automatically or confirmed by you, gives an overall score, and breaks it down by signal:

Match Quality signals
SignalWhat it compares
AmountThe planned and posted amounts, from "Exact match" to "Larger difference than usual".
DateHow many days the charge posted before or after the planned date.
MerchantThe merchant on the planned transaction against the description from your bank.
Historical patternHow consistently this merchant and schedule have matched before.

Below the signals, Planned and Actual tiles show both amounts and dates side by side, along with the amount variance.

Charges whose amount changes

Some charges are approved for one amount and post for another. A restaurant adds the tip after approval, and a gas station may approve $1 before you pump. Pluto knows about both: it matches a tipped charge to your planned transaction and keeps the tip set aside, and it treats gas, hotel and rental holds as placeholders rather than flagging them as unmatched. See Tips on Restaurant Charges and Gas, Hotel and Rental Holds.

When a Match Is Consistently Wrong

If Pluto keeps proposing the wrong match for a particular transaction type, the best fix is to improve the underlying schedule. Make sure the schedule has the correct amount, date, and merchant name. The matching engine learns from your acceptance and rejection history, so it becomes more accurate over time as you use Pluto.

Matching pairs one bank transaction with one planned transaction of about the same amount. When a bank transaction is only part of what you planned, split it out instead with Take from a planned transaction in Find Match. See Splitting a Planned Transaction.

Sources and further reading