Resolve a bank-feed warning
Read what each warning is telling you and correct the cause before posting.
Find The Flagged Rows
A warning means LedgerHQ found evidence that posting this row may be wrong. Resolve the cause rather than confirming past it.
In Fast Coding, open the company and select the Warnings filter. In Bank Feeds the badge appears on the row itself.
Warnings also keep a row out of batch actions — Post all coded posts only coded, warning-free rows. Flagged rows stay behind until someone decides.
Warnings You Can Confirm Past
Some warnings ask for a decision. Posting shows:
This transaction has warnings. Post anyway?
Or, when the row resembles activity already in the register:
This transaction may already be in the register. It resembles imported entry #1042. Post anyway?
Before confirming, open the register and look at the entry it named. If it is genuinely the same transaction, do not post — the activity is already in the books, usually from an import. Exclude the feed row instead. See Exclude a bank transaction.
If it is a different transaction that happens to share a date and amount, confirming is correct.
Flags That Redirect You
Others are not questions — the row needs a different workflow:
- transfer match → Code an internal transfer
- possible card payment → Code a credit-card payment
- pending at bank → Understand pending bank transactions
- a held check → Resolve a held check
Do not force these into an expense account to clear the queue.
Before A Batch
Resolve flagged rows individually first, then run the batch on what remains. See Understand your posting options.
If The Warning Is Unclear
Leave the row unposted and create a support ticket with the company, account, date, amount, description, and the warning text.
An unposted row costs nothing. A wrong posting has to be undone and verified — and because posting also creates a bank rule, a wrong one can repeat itself.