Review what posted and who posted it

Read The Activity List

Check what became ledger activity, when, and from which source — especially after an automated run.

Open Fast Coding and select Activity. Each entry shows the company, transaction, account, amount, and when it posted.

Use the company and date filters to narrow to the run you are reviewing. Do not assume everything on one date came from one action — a rule match, an individual post, an automated run, and a batch can all land the same day.

What The Source Labels Mean

A coded or posted row carries the mechanism that produced it:

• Rule coded — an active bank rule applied the account.
• Suggested — category research proposed it.
• Tally — Tally coded it from researched evidence.

The label tells you the mechanism, not that the result is correct. Review the payee, description, amount, and account yourself — particularly after a new rule's first runs.

Trace One Posting To The Ledger

1. Find the transaction in the list.
2. Open the company's Bank Feeds, select Posted, and open the row.
3. Or open the account register and find the entry on its date.

The register is the reliable proof that the posting affected the books. The feed row alone only shows the bank evidence.

After An Automated Run

Tally reports its own work in Done, Staged, and Needs you groups. Activity is where you confirm what those lines actually did. See How Tally codes your bank feed.

If Something Is Wrong

Use Undo a posted bank transaction, then fix the cause. A posting that came from a rule repeats until the rule changes — see Stop an overbroad bank rule.

If activity appeared that nobody on your team performed and no source label explains, report an unexpected change to the books before making corrections.