Ask about something specific
The request is tied to the transaction, account, statement period, or decision holding up the books.
Client requests
Every firm has a client who owes you a statement and a bookkeeper who has asked three times. LedgerHQ turns that into a tracked request attached to the exact transaction it is blocking — and when the client replies, the work picks up where it stopped.
Watch the follow-up happen
The request, the reply, and the blocked bookkeeping resuming from it.
2 min 12 secSee every walkthrough
The request is tied to the transaction, account, statement period, or decision holding up the books.
See at a glance whether a request is waiting on the client, on Tally, or on your firm.
Tally can raise requests, read replies, follow up, and resume the bookkeeping work the answer unblocked.
Instead of a vague “we need more information” email, the request names the transaction, statement period, document, or accounting choice that is holding up the books.
Clients answer specific questions. They ignore general ones, which is why the third follow-up email exists.
Replies return to the request thread rather than disappearing into one bookkeeper's personal email, where nobody else can find them.
LedgerHQ updates the request state so the right person — or Tally — knows there is new information to use.
LedgerHQ tracks what is waiting on the client, what needs Tally, and what needs your firm.
Tally can follow up on supported requests and hand over only the items that genuinely need a person.
Questions
Yes. Tally can create and send supported requests to approved company owners, read the replies, follow up, and then resume the bookkeeping work the missing information was blocking.
The reply returns to the request thread, updates the work state, and can wake Tally to continue the blocked task.
Approved company recipients only. Delivery and reply history stay attached to the request.
Yes. Both the accountant and company-owner mobile experiences include supported request workflows.
Keep exploring