What is SavingStat

SavingStat is a record of what you spend and earn, built from bank statements and receipts you import. How data gets in, and what it does not do.

What SavingStat is

SavingStat is a record of what you spend and what you earn. It is built for money that more than one person is involved in, so you connect to the people you share costs with, and a budget you share then adds up everyone's spending in it alongside your own share, converted into the currency you picked.

The record is built by importing, not by typing. Most rows arrive from a bank statement file or a photo of a receipt, and they land on the wallet you scoped the import to with a category and a budget already filled in. Your job is to check them, not to enter them.

How your data gets in

There are three ways in. The first is the one you will use most.

  • A bank statement. Export a CSV or PDF from your bank, choose the wallet it belongs to, and upload it. Every row comes back as a draft with a category, a budget and an income source suggested, and anything that resembles a transaction you already have is flagged as a possible duplicate.
  • A receipt photo. A JPEG, PNG or WebP image goes through the same pipeline and produces drafts the same way.
  • The add-transaction form. Enter an expense, an income or a transfer yourself. Use this one for cash that no statement will ever show.

Anything that comes out of a file arrives as a draft. Drafts stay out of your transaction list and leave your wallet balances untouched until you publish them, so a messy import costs you nothing but the time to tidy it.

What SavingStat does not do

SavingStat writes down what already happened. It does not ask you to name a number in advance and then measure you against it.

A budget has a name, an owner, the members you invite, the categories its spending has turned out to use, and a total for the current month. It has no field for a number it is meant to stay under, so nothing in the app holds a transaction back, refuses it, or treats it as a problem because of what a budget already contains.

SavingStat also never asks for your online banking credentials. It never moves money. Statements come in as files you export yourself, which is why the import step is a file picker rather than a login, and nothing SavingStat reads joins your records until you have reviewed and published it.

Where to go next

Your first week lays out the order to do things in: the guided setup, one month of imported statements, then the people you share money with.

After that, the concept articles explain the pieces everything else is built from. Transactions sit at the center, with three types (expense, income and transfer) and a draft status for anything an import has proposed but you have not yet reviewed. Wallets hold every transaction. Categories and budgets are what spending is filed under. Income sources, events, currencies and imports round out the rest. Read transactions first, since every figure in the app is assembled from those, then wallets and budgets. The rest is easier once those three are clear.