State-aware queues
Pending, uncoded, coded, warning, ready, excluded, and posted states communicate what can actually move.
Bank feed automation
Move bank activity through a bookkeeping workflow—not just an inbox.
LedgerHQ uses Plaid-connected bank and card activity, explicit queue states, rules, posting controls, and Tally assistance to help firms process daily activity without losing the path to the ledger.
Account-level context
Bank account cards, transaction activity, coding, posting, and register paths remain connected.
Firm supervision
Bookkeepers and Tally can work from company queues while the firm retains broader visibility.
01
Connected activity is intake, not accounting
A bank feed provides transaction evidence, but the feed row is not automatically a complete ledger decision. Pending state, duplicate risk, transfer relationships, business purpose, and the correct account still matter.
LedgerHQ keeps the feed state visible and uses the supported posting workflow to produce accounting records.
- Plaid-connected account activity
- Pending state retained
- Bank and card accounts
- Import and sync health handled as plumbing
02
Route rows by the work they need
The most useful automation separates clean repeat activity from rows that need research or human judgment. Rules, category suggestions, match workflows, exclusions, and posting controls each have a different purpose.
A firm should be able to count what is truly ready without inflating the queue with pending or already posted activity.
- Rule matches
- Uncoded research
- Coded-ready review
- Warnings and exclusions
03
Keep the bank feed connected to posting and reconciliation
Once supported activity is posted, the register and journal evidence become the accounting source. Reconciliation then compares posted account activity with statement evidence.
That sequence prevents the bank feed from becoming a parallel ledger that looks clean while the actual books remain incomplete.
- Posted ledger records
- Account registers
- Bank reconciliation
- Financial reports
How the workflow moves
A visible sequence, not a black box.
The exact action depends on permissions, company context, and the evidence available. The workflow stays inspectable from intake through review.
- 1Plaid brings supported bank and card activity into the account feed.
- 2LedgerHQ separates pending rows and classifies the remaining work state.
- 3Rules, Tally, and bookkeepers code, match, exclude, or review supported rows.
- 4Posting writes the accounting result; reconciliation checks it against statements.
Human control
Only coded, eligible activity should move through posting, and warnings, period locks, company scope, role permissions, and reconciliation state remain enforceable.
Product boundary
Plaid is the supported bank activity source. LedgerHQ does not promise every institution, instant settlement, perfect merchant detail, or a generic provider-import marketplace.
Questions
What firms usually ask.
Which bank-feed provider does LedgerHQ use?
LedgerHQ uses Plaid for supported bank and card activity.
Are pending rows included as ready bookkeeping work?
Pending activity remains distinct and should not be described as ready-to-post or reconciliation-ready work.
Can rules post activity?
Supported trusted rule workflows can prepare or move clean matching activity according to configuration and safeguards. Warnings and ineligible rows stay out of the clean path.