Common issues
- Tally is not suggesting anything yet. That's expected early on. Tally needs to see a small number of consistent resolutions before a pattern is confident enough to surface. As your review history accumulates, suggestions appear naturally.
- 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 pays attention to 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. After enough similar resolutions accumulate for a pattern — typically a small handful — Tally is confident enough to surface it as a suggestion on the next similar document.
You don't author these patterns. They are learned from your real decisions. If your firm consistently maps a particular subscription to "Software & Tools," that becomes the suggestion. If you change your mind later and start mapping it to "Marketing," the suggestion drifts the same way.
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 context and authority, and why suggestions get sharper over time.
- 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.
- Notice that, after a few reviews of the same kind, Tally starts suggesting how to resolve similar future documents.
- 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. If you repeatedly reject a suggestion, Tally lowers its confidence. If a pattern keeps being rejected after enough samples, it stops being suggested at all. If the underlying business changes — a vendor moves to a new accounting category, an integration is deprecated, a process changes — your reviews naturally retrain Tally without any extra step.
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. Tally records that you declined; future suggestions will weight your rejection appropriately.
- 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.