Transfers

A transfer in SavingStat moves money between two of your wallets. What the record keeps, why no category applies, and why the statistics never see it.

What a transfer is

A transfer in SavingStat is money leaving one wallet you own and arriving in another. A card paid off from a current account, cash drawn out, a savings pot topped up: all three qualify. Nothing was earned and nothing was bought.

That one fact decides everything else about the record.

Two wallets, two amounts

A transfer names the sending wallet and the receiving wallet, and keeps a figure for each: what went out, and what actually landed.

The received amount is always asked for and always yours to type. SavingStat applies no rate of its own here, which is the opposite of how an expense or an income behaves. On those the conversion is offered and you may accept it. Here there is nothing to accept, because what your bank credited is a fact you have and the app does not.

The two figures usually agree. Where a fee was taken they do not, and the record keeps both rather than picking one.

No category, no budget

A transfer takes no category and no budget. There is nothing to label it as, so the record has nowhere to put one and the form does not ask.

Categories and budgets belong to expense lines, which a transfer lacks.

Why the statistics cannot see a transfer

A transfer creates neither an expense nor an income record, and the Stats pages are built from those two, so it cannot reach them. Your balances move. Your spending does not.

Filing one as an expense instead counts money you still have as money you spent. Do it at both ends and the same move is counted twice, once as spending and once as income, and every category, budget and monthly figure downstream inherits the double count.

The guide to recording a transfer walks through the form.