Understand what is waiting in Fast Coding

Read The Company Queue

Open Fast Coding from the Firm section of the left navigation.

Use the counts this way:

• Ready is the number of eligible unposted rows available for work.
• Coded rows already have an accounting account and can be reviewed for posting.
• Needs code rows do not yet have an account or another complete treatment.

The queue excludes pending holds, posted or reconciled rows, excluded activity, and checks held for evidence. A company disappears from Ready after its active work is cleared.

A coded row may have been handled by a person, a bank rule, or a suggestion. “Coded” means the row is prepared for review; it does not mean you should post it without checking the description, amount, account, and any warning.

Open One Company

Click the company name, Code, or Review. The drawer shows its counts and individual bank rows without losing your place in the firm queue.

Use the four drawer filters to narrow the work:

• Ready shows the active rows.
• Needs code shows rows that still need an account.
• Coded shows rows prepared for posting.
• Warnings shows rows that need extra review.

Choose Bank feeds when you need the company’s full account-card and feed context. Use Code one bank transaction to assign an account without posting. Before posting a row or batch, compare your posting options.

When every eligible coded row for one company has been reviewed, follow Use Post coded in Fast Coding before starting the company-wide action.

Use Guided Fast Coding In Tally

Open full-page Tally and select Fast Coding in its top toolbar beside Files. The coding pane presents up to five transactions from one company at a time. Check the company name before making decisions.

1. In Review, check each transaction's description, bank account, date, amount, and suggested account.
2. Choose an account, or select Ask Client for an eligible transaction that needs an owner answer.
3. Open Vendor history or View vendor history to see up to four recent posted transactions for each vendor in that company. Imported history and split-account details appear when available.
4. Return to Review, check every decision, then select Submit N decisions.

Submitting posts the coded transactions. Ask Client decisions post to the appropriate holding account and can send the designated owner a request; without a recipient, the request remains queued. This action changes the books and can contact the owner.

Review the result and any failures inside the coding pane before continuing. Switching tabs, chatting, or closing and reopening the pane preserves the current draft choices. Reopening restores the current batch. A retry preserves successful work rather than posting those transactions twice.

If a transaction looks like a transfer, credit-card payment, loan movement, or owner contribution, do not force it into an expense category just to clear the queue. Leave it unposted and create a support ticket with the company, account, date, amount, and description when the treatment is unclear.