Transaction tags
A tag is a free-form label on a transaction: “for friends”, “lent”, “holiday”, “gifts”. One transaction can carry as many tags as you like. They make it easy to filter the journal and to look at separate statistics. And one tag is special — “Not counted”: it keeps the transaction in the list and in the account balance, but takes it out of statistics, budgets and reports.
How a tag differs from a category and a project
Svodly has three separate dimensions, and they do not replace one another:
- A category answers “on what” — “Groceries”, “Transport”. A transaction has exactly one, and all analytics and budgets rest on it.
- A project answers “what for” — “Kitchen renovation”, “Trip to Sochi”. Also one per transaction.
- A tag is just a label, and there can be several. It does not take the category away from a transaction and does not get in the project’s way: “Groceries” plus the tags “for friends” and “country house” live together in one record.
A practical rule: if you need a slice that cuts across categories (the same label shows up under “Food”, “Transport” and “Entertainment”), that is a tag.
Putting a tag on a transaction
Tags live in the transaction form next to the attachments — a row of coloured chips above the “Documents” section, the same on the computer, on the web and on the phone.
- Open a transaction (or create a new one).
- Press the Add tag chip.
- Tick the tags you need — there can be several. The list is split into “My tags” and “System”.
- Nothing fits? Start typing a name — + Create “…” appears under the results. The tag is created with that name, and you pick its colour right away.
- Save the transaction. To take a tag off, press the cross on its chip.
The “Tags” reference
The full list of the book’s tags is the “Tags” section. On the computer and on the web it sits in the collapsible “References” group at the very bottom of the sidebar, next to “Categories”, “Counterparties” and “Projects”. On the phone it is in the sections menu: a “References” row under “Budgets”, and “Tags” inside it.
The list shows how many transactions carry each tag and what income and expense they add up to over the selected period. Tap a row to open the card: name, colour from the palette and an optional description — what the tag is for (handy when several people keep the book).
On the computer and on the web every reference row has an Open transactions button — the journal opens already filtered by that tag and the period of the screen. Clicking the row itself still opens it for editing.
System tags
Every book has tags the app creates itself. They are marked with a crossed-out icon and carry a description right in the reference: they cannot be renamed or deleted. In filters and statistics they work just like ordinary tags.
“Not counted” — you set this one
This is the only system tag you switch on and off by hand. It is for the cases where the money really did leave the account, but the spending was not yours:
- you paid the shared bill at a café and your friends will pay their part back;
- you bought something for your parents with their money;
- you ran an amount through your card in transit.
What the tag does:
- The transaction stays in the journal and in the account balance — the money really did leave, and the balance shows it.
- It disappears from statistics: the “Income / Expense” figures, structure charts, graphs, “Purchases”, “Large expenses”, budgets and management reports (P&L, cash flow statement, counterparty turnover) no longer see it.
The tag does not touch taxes. The KUDiR ledger, the self-employment register and the liability forecast count the transaction as usual. The tax base is calculated from actual receipts — an interface label must not understate it.
In analytics, the “Not counted” row of the “By tag” card shows how much money you have taken out of the statistics over the period — so that it does not turn into a silent hole in the reports.
Automatic ones — the app sets these
Svodly puts these tags on and takes them off itself, based on where the transaction came from. You cannot add or remove them by hand — they tell you the transaction’s origin:
- “FTS receipt” — the transaction came from a scanned receipt.
- “Recurring” — generated by a recurring transaction.
- “With attachments” — the transaction has documents attached.
- “Dictated” — recorded by voice.
- “Imported” — arrived from a statement import.
Your existing history is labelled with these tags when the app updates — there is nothing to search for or set by hand. It gives you handy filters: “show me everything I dictated” or “all transactions with attachments this quarter”.
Filtering by tag
“Transactions” has a “Tags” chip with multiple selection. The logic is OR: a transaction makes the cut if it carries at least one of the selected tags. The filter stacks with the others — period, account, category.
On the computer and on the web you can add a “Tags” column to the table — it is hidden by default and switched on in the column settings (the gear in the table header).
The “By tag” statistics
“Analytics” has a “By tag” card — the turnover of each tag over the selected period. In a personal book it lives on the “Structure” tab, in a business book — in business analytics, and on the phone — on the analytics screen.
It is a list, not a donut chart, and that is deliberate: a transaction with two tags would land in both segments, the shares would stop adding up to 100 % — tags do not make “parts of a whole”.
Deleting a tag
You can delete your own tag at any time — there is nothing to move anywhere. The app shows how many transactions the tag will come off, and the transactions themselves stay where they are: only the label disappears. System tags cannot be deleted.
Where to next
- Transactions — filters, columns and the transaction form.
- Categories and counterparties — the main analytics dimension.
- Analytics — where to find the “By tag” card.
- Budgets — why a labelled transaction does not eat into the limit.