Fast Coding
Code and post bank feed rows across all firm-managed companies.
Fast Coding is the firm-level work queue for bank feed review. Instead of opening each company one at a time and hunting for uncoded feed rows, the firm can start from one list of companies with outstanding work.
This screen is meant for repeated bookkeeping work. The layout favors scanning, opening a company drawer, coding rows, posting what is ready, and moving to the next company. It is not a replacement for the company-specific Bank Feeds page. It is the faster route when the question is, "What feed work is waiting across the firm?"
Start From The Company Queue
Open Fast Coding from the Firm section of the left nav. The main queue shows companies with bank feed work. Companies with no remaining feed work disappear from the queue, which keeps the list focused on what still needs attention.
The most useful counts are coded ready-to-post rows and uncoded rows. Coded ready-to-post rows have accounting treatment and can be posted after review. Uncoded rows need review, category suggestions, matching, or manual coding before they can be posted. Pending-at-bank, posted, and excluded rows are not active Fast Coding posting work.
Coded rows can come from a user, a bank rule, or a suggestion. A row that is already coded is not automatically harmless; it is simply closer to posting. Review the account, amount, payee, and any warning evidence before posting a batch.
Open A Company Drawer
Select a company to open the transaction drawer. The drawer shows register scoped rows for that company, with controls for coding, warnings, and posting. This keeps the broad firm queue visible while still giving enough detail to finish one company at a time.
Use the drawer when you want to work through a batch without losing your place. If you need the full company Bank Feeds context, use the Bank feeds action from the drawer to jump directly to that company's Bank Feeds page.
Fast Coding and Bank Feeds share the same underlying feed rows. Use Fast Coding when the firm wants to move quickly across companies. Use the company Bank Feeds page when the user needs deeper account-card context, mapping details, feed health, setup diagnostics, or a narrower account view.
Use Suggestions Carefully
LedgerHQ can suggest categories for uncoded rows. Suggestions are meant to speed up review, not replace judgment. Review the payee, description, amount, and warning evidence before accepting a category, especially for large or unusual transactions.
If a row looks like an internal transfer, credit card payment, loan movement, or owner contribution, do not force it into an expense category just to clear the queue. It is better to leave a row unposted and ask Tally or support than to create a misleading entry.
When LedgerHQ recognizes both sides of an internal transfer or credit card payment, Fast Coding groups the pair into one visible work item. The queue shows one Ready item, one Needs code item, and one transfer amount rather than adding the two bank legs together. Use the pair posting action only when the source and destination accounts are correct. If one side is pending at the bank or missing, LedgerHQ holds the pair out of the active coding queue until the evidence is complete. The settled counterpart may still appear as informational banking context elsewhere, but it is not a transaction to code while the pair is waiting.
Rules and AI suggestions use different signals. A bank rule is a saved firm instruction for repeat patterns and can code or auto-post clean matching rows. An AI suggestion is researched help for rows that do not already have a rule. The AI auto-post switch applies to high-confidence AI researched rows; it does not turn bank rules on or off. See Bank rules and auto-posting before enabling automation for a company with unfamiliar activity.
Post Coded Rows
Once rows are coded and warnings are resolved, post them individually or use bulk Post coded where appropriate. Posting is the accounting step. It creates ledger activity that can affect reports and reconciliation.
Do not treat posting as a harmless queue cleanup action. A posted row has moved from review evidence into the books. If the coding decision is not clear, leave the row in the queue, add a note if available, or create a support ticket with the transaction details.
Review Automation Activity
Fast Coding also includes an Activity Log mode for reviewing recent Plaid-sourced rows that have already been posted across the firm and managed companies. This is useful after bank rules or Tally-assisted work because the queue may be empty while the user still wants to see what posted.
Rows with a matched bank rule can show Rule matched and the rule name. Treat that as evidence that a rule matched the row. It is not a complete audit of every actor involved, and it does not replace reviewing the journal entry when the posting looks wrong.
