Post every coded row for one bank account
Understand the exact scope of Post all coded, and why it usually posts without asking.
Know The Scope
Post all coded posts every eligible coded row on the bank or card account you are viewing.
Open the company, select Bank Feeds, and select the account. Post all coded sits in the toolbar beside Suggest categories.
Two things surprise people:
- It covers the whole register, not your current view. Filtering or searching narrows what you can see; it does not narrow what posts. Every coded, warning-free row on that account is included.
- It covers one account, not one company. A company with a checking account and two cards needs this run three times. For the company-wide action, use Post coded in Fast Coding.
Post all coded normally posts without telling you how many rows it will affect. It asks first only when visible coded rows may already be in the register. Read the Ready list before you click — this is the widest action in Bank Feeds with the least confirmation.
Review Before You Run It
- Select Ready and read every coded row's account and amount.
- Resolve flagged rows first — see Resolve a bank-feed warning. Rows with warnings are not eligible and stay behind.
- Leave transfers and card payments alone; they have their own workflow. See Code an internal transfer.
Post And Verify
Click Post all coded. If LedgerHQ asks whether visible coded rows may already be in the register, stop and check the register before continuing.
The result reports Posted n of m, with a skipped count when some rows were ineligible. If nothing qualified you get Nothing to post — no coded, warning-free transactions.
Open Posted and confirm the account, amounts, and row count match what you reviewed.
Each posted row also saves a bank rule — see How your bank rules get made and maintained.
Correct A Mistake
Use Undo a posted bank transaction for one row, or Reverse an accidental posting batch for a wider set. Never add an offsetting entry to cancel a feed-owned posting.