Understand your posting options

Choose the smallest posting scope that matches the work you have reviewed. Coding prepares a bank row; posting creates ledger activity.

Manual Posting Controls

• Post affects one coded row. Use it when you want the narrowest possible action and then verify the result in Posted or the account register.
• Post selected affects only the checked rows in the company’s Bank Feeds. The result reports how many requested rows succeeded.
• Post all coded works from the selected Bank Feeds account. It posts the eligible coded rows for that bank or card register. If visible coded rows may duplicate imported register activity, LedgerHQ asks before continuing.
• Post coded in Fast Coding affects every eligible coded row for the opened company—not only the current filter or rows you personally coded. Its confirmation gives the exact count. Completing this action also creates bank rules for matching coded activity.

Rules And Automatic Posting

A saved bank rule applies its defined treatment to future matching rows. A rule configured to post automatically can post a clean match when its account still matches and no warning blocks the action.

The firm’s AI auto-post setting is separate. When it is on, high-confidence researched suggestions may post automatically; lower-confidence suggestions remain available for review.

Review automated results in Posted, the account register, or Fast Coding’s posted activity. Rule and AI automation do not change the recovery path: use Undo on an incorrect feed-owned posting. Do not create a separate offsetting entry. See Undo a posted bank transaction.

For a single row, continue with Post one coded transaction. For the company-wide action, use Post coded in Fast Coding and read the exact-count confirmation before continuing.