Common issues
- Tally is not suggesting anything yet. Expected until a pattern has been observed at least 3 times with confidence at or above 0.5. Until both hold, nothing is shown.
- The suggestion is wrong. Reject it. Tally takes the rejection into account. If the same kind of suggestion keeps being wrong, retire the pattern from the Memory tab.
- The suggestion is right but the value needs a small change. Use Edit instead of Apply. Tally records both the original suggestion and your edit, so future suggestions move toward your edited form.
- I don't want any suggestions on a particular kind of document. Reject suggestions on that kind of document; once enough rejections accumulate, the pattern stops surfacing.
How resolutions become patterns
Tally records two things on every review: the kind of issue that was flagged (for example "missing category", "possible duplicate", or "new vendor needs mapping") and the resolution the reviewer chose.
A pattern is only suggested once both of these hold:
- it has been observed at least 3 times, and
- its confidence is at least 0.5.
Below either threshold the pattern stays a candidate and is not shown. Meeting them makes the pattern eligible to be suggested on a matching document — it does not change what happens to any particular document, which is still evaluated on its own.
Confidence is not simply an accept-versus-reject rate. It combines three things:
- how the pattern has been acted on — applying counts fully, editing counts as half, rejecting counts against it;
- how recently it was last seen — a pattern that has not appeared for a long time decays;
- how often it has been observed, up to a ceiling.
Acceptance carries the largest single share, and recency and frequency carry the rest. A pattern can therefore drop below the bar simply by going stale, without anyone rejecting it.
You don't author these patterns; they are recorded from real decisions. If your firm has consistently mapped a subscription to "Software & Tools", that is what the recorded pattern holds. Changing to "Marketing" records new observations, and the recorded pattern reflects what has actually accumulated.
Privacy and safety
- Patterns are learned from your own workspace's review history, not from anyone else's books.
- A bookkeeping firm's patterns roll up across the firm's clients in aggregate views only, never as raw cross-client data.
- Suggestions are read-only until you accept them. Tally never silently changes a document in your books on the strength of a learned pattern.
- The audit trail (who applied what suggestion, who edited it, who rejected it, when) is preserved for every action.
What's next
- Learn how Tally thinks — the broader Memory layer that resolution patterns live inside.
- How Tally learns — the difference between imported context and live review authority.
- Documents — review and approve — the review surface where resolution suggestions appear.
What Tally suggests — and what she will not
Tally only suggests resolutions that the reviewer can already perform manually inside Tally — categorising a transaction, mapping a new vendor, marking a duplicate, fixing a missing field. The Apply button is a shortcut for an action you would have done by hand; nothing more, nothing less.
Tally will not auto-push to QuickBooks, will not auto-file taxes, and will not auto-send anything to a vendor or a client. Those remain explicit human-initiated actions in the existing flows where they have always lived.
What you'll do
- Review documents the way you already do.
- Know the exact conditions a pattern must meet before it is suggested at all.
- Accept, adjust, or reject each suggestion — your call, every time.
- Browse the patterns Tally has learned in the Memory tab when you want to see what she's picked up.
When patterns get retired
Patterns are not permanent. Each rejection lowers a pattern's confidence and counts toward retirement.
A pattern is deprecated — no longer suggested — once both hold: its rejection ratio reaches 0.4, and it has accumulated at least 5 actions. An action is an Apply, an Edit or a Reject. Merely being shown is not an action, so a pattern nobody has acted on cannot be retired by this rule, and a single rejection never retires a pattern.
A firm administrator can also retire a pattern manually from the Memory tab if a clear bad fit shows up. The retirement is logged.
Where you see them
- On a similar future document. The document detail view shows a small Tally's insights section. When a learned pattern matches, Tally shows the suggestion with three options:
- Apply — accept the suggestion as-is.
- Edit — accept the suggestion but change one or more fields before it lands.
- Reject — dismiss this suggestion. The rejection is recorded and lowers the pattern's confidence.
- In the Memory tab → Past resolutions. A directory view of patterns Tally has learned for this workspace. Each row shows the kind of issue, the resolution, how often it has been seen, and when it was last applied.
- In your review history. Every Apply, Edit, or Reject is recorded so the audit trail of "why this document was resolved the way it was" stays intact.