LedgerHQBanks, Coding And Posting
32 articles
Connect a bank or credit cardStart Plaid Link, select accounts, map every return, and verify the first healthy feed activity.Connect bank feedsReview Plaid-connected bank and card activity before it posts to the ledger.Understand pending bank transactionsWhy some bank rows can be seen but not coded, matched, reconciled, or posted.Find missing bank transactionsWork through connection health, mapping, buckets, and cutoff before concluding that activity is lost.Reconnect a bank that needs attentionRestore a Plaid connection yourself when the automatic outreach has not worked, then confirm activity resumed.Disconnect or pause a bank feedUnderstand the exact scope of pausing versus disconnecting, and what happens to posted and unposted rows.Import bank activity from a CSVUse CSV import as the fallback for institutions Plaid does not cover, and set a starting point so the register is right from day one.Bank connection textsText company owners secure no-login links for new bank connections and reconnects.How Tally codes your bank feedWhat Tally researches, codes, posts, and stages on its own each day, and which rows it deliberately leaves for you.How Tally settles transfers and card paymentsTally confirms matched pairs, rejects false matches, and chases card payments with no visible funding side.How Tally investigates unknown moneyUnidentified deposits and opaque withdrawals get researched, booked when provable, and turned into one clear question when they are not.How Tally watches your bank connectionsTally detects broken and silently stale feeds, chases the reconnect with the company owner, and escalates when the connection cannot be saved.How your bank rules get made and maintainedPosting a transaction creates a rule. Tally then adds the ones you missed and retires the ones that go bad.Bank rules and auto-postingUnderstand rule coding, rule auto-posting, and firm-confidence AI posting in bank feeds.Understand what is waiting in Fast CodingRead the Fast Coding queue and open one company’s bank-feed work.Code one bank transactionAssign an accounting account to one bank row without posting it.Code an internal transferRecord money moving between two company accounts once, without creating income or expense.Code a credit-card paymentRecord a payment from checking to a card once, without double-counting the original expenses.Resolve a bank-feed warningRead what each warning is telling you and correct the cause before posting.Exclude a bank transactionRemove a row from the coding queue without posting it, and restore it if you were wrong.Resolve a held checkWhy a check is quarantined out of ordinary coding, what evidence releases it, and what only a person can decide.Create a narrow bank ruleWrite a rule by hand when you want a treatment applied before the transaction ever posts.Understand what a bank rule will postKnow which past and future rows a rule can reach, and when it posts without you.Stop an overbroad bank ruleDisable a rule that is catching the wrong transactions, then narrow it and clean up what it already did.Understand your posting optionsChoose between posting one row, selected rows, coded rows, rules, and automatic posting.Post one coded transactionPost one reviewed bank row and verify the resulting ledger activity.Post selected transactionsPost only the bank rows you checked, and confirm exactly which rows the action covered.Post every coded row for one bank accountUnderstand the exact scope of Post all coded, and why it usually posts without asking.Use Post coded in Fast CodingReview and post every eligible coded row for one company from Fast Coding.Review what posted and who posted itTrace posted bank activity to the person, rule, suggestion, or Tally run that created it.Undo a posted bank transactionRemove an incorrect bank-feed posting from balances and return the transaction to review.Reverse an accidental posting batchDefine an accidental bank-feed posting set and use the supported recovery path. All collections