Use “What went under a tag” in Recued. Everything spent under one tag, including every tag beneath it, at any depth.
What went under a tag
Use “What went under a tag” in Recued. Everything spent under one tag, including every tag beneath it, at any depth.
Complete workflow
Use Ledger book in Recued for accounting, double entry, budget, and records. It includes 44 built-in actions and 15 ready-to-run workflows. Actions that change data use Recued's approval controls.
You are viewing one recipe in this workflow. Installing it opens the complete pack so its other recipes and background automations arrive together.
Use “Records runtime” in Recued. It helps you complete this workflow using the connections and settings you choose.
Use “The accounts” in Recued. Every account with its id — what you post to, and what anything else in this workflow needs before it can name one.
Use “The tags” in Recued. Every tag with its id and how deep it sits — the trees you can spend against, and the ids the rest of the pack takes.
Use “What it all comes to” in Recued. Each currency's balance read exactly, then converted at rates you give and added up.
Use “Every budget at once” in Recued. All your budgets for a period, each counting everything under its tag — in four queries, however many budgets you have.
Show all 16 recipes
Use “How a budget is doing” in Recued. What a budget has left, counting everything under its tag at any depth.
Use “The lines under a tag” in Recued. Every transaction line under a tag and everything beneath it — the lines themselves, not a total. With a CSV to copy.
Use “Open an account” in Recued. Adds an account to your chart. Its currency is fixed here and every line posted to it inherits it.
Use “Post an entry” in Recued. One entry, any number of legs, written in a single all-or-nothing transaction. It will not post unless the legs sum to zero.
Use “Add a tag” in Recued. Adds a tag anywhere in your tree, at any depth. The tag and its place in the tree are written together or not at all.
Use “Tag a month of lines” in Recued. One tree at a time: every line in a period on one page, with a picker in the tag cell.
Use “Tag a transaction line” in Recued. Sets which tags a line belongs to, one per tree. Each tag and every tag above it counts the full amount.
Use “Set a budget” in Recued. A cap on a tag for one period. It counts everything under that tag, at any depth.
Use “Move a tag” in Recued. Puts a tag inside a different one. Everything recorded under it follows automatically — no transaction is rewritten.
Use “Delete a tag” in Recued. Removes a tag and everything beneath it. Refuses while anything is still tagged with it.
Any level, same answer
Ask about a leaf and you get the leaf. Ask about the tag three levels above it and you get everything underneath, at any depth. There is no separate "rolled up" mode, because there is no separate stored total — the tree is read at the moment you ask.
⛔ A parent equals the sum of its children. Always, by construction: the tag you ask about is one of its own descendants, and so is everything beneath it. Nothing is stored twice and nothing has to be recomputed when you reorganise.
⛔ Every line counts in FULL at every level above it. A line tagged to a person is fully that person's, fully their department's, fully their division's — the same money seen from further out. Nothing is apportioned, so the number here needs no reconciliation.
⚠ Lines and transactions should always match. They can only differ if one line carries two tags from this tree, which tag-leg refuses — so a mismatch means a row got in some other way, and the check is on the card.
One currency at a time
⛔ A currency is required and every figure is scoped to it. Adding pounds to dollars gives a number with no unit that looks exactly like money — and a tag tree is precisely where a mixed book gets summed without anyone noticing, because the tags say nothing about which account the spending sat in.
The one limit
⛔ It reads at most 100 tags beneath the one you name, and refuses rather than truncating. A short answer that looks complete is worse than no answer — you would budget against it. If you hit this, ask about something narrower; for the whole book, read the accounts, which needs no tag at all.
⚠ The money is summed inside Records as whole units, never as decimals. Adding fixed-point strings in a recipe would drift, and a total that is out by a fraction of a penny in the wrong direction is exactly the kind of wrong nobody notices.
How it works
Inspect the data fetches, transforms, gates, and output this recipe runs.
Settings
Configurable at install. Defaults shown — change them anytime in Recued.
period
setting
=
tag id
setting
=
[object Object]
currency
setting
=
GBP
account id
setting
=