Company scoped
A request belongs to the company and the work that needs an answer or document.
Company requests
Keep missing information attached to the bookkeeping work.
LedgerHQ requests help firms ask company owners for statements, explanations, documents, and other evidence without turning the bookkeeping queue into an untraceable email scavenger hunt.
Visible state
The firm can distinguish drafts, waiting items, delivered messages, replies, and work that still needs firm action.
Tally assisted
Tally can prepare and manage supported request work while external sends retain confirmation and recipient controls.
01
Turn a blocker into a specific request
“Need more information” is not actionable. A useful request states which company, account, transaction, statement period, or bookkeeping decision is blocked and what evidence would unblock it.
LedgerHQ keeps that request close to the company workflow instead of relying on an unstructured firm inbox as the system of record.
- Transaction questions
- Missing statements
- Supporting documents
- Company-owner explanations
02
Control externally visible delivery
Messages to company owners are externally visible and should use server-resolved allowed recipients rather than arbitrary addresses supplied to an agent. Tally can prepare a request, but supported sends use confirmation and company scope.
Replies can reopen or update the request state so the firm sees that the blocker has new evidence.
- Allowed company recipients
- Preview or confirmation before supported sends
- Delivery state
- Reply and reopen behavior
03
Bring the response back into firm work
A request is only useful if the reply returns to someone who can act. LedgerHQ separates items that need the company owner, items held inbound, and items that now need the firm.
Tally's firm supervision can surface supported human-input blockers without turning the firm home into a noisy notification dashboard.
- Waiting on company owner
- Inbound reply held for review
- Needs firm action
- Related bookkeeping follow-up
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.
- 1The firm or Tally identifies a company-specific missing fact or document.
- 2A request is drafted with the exact evidence needed.
- 3An authorized user confirms supported external delivery when required.
- 4The reply returns to the request thread and the firm resumes the blocked bookkeeping work.
Human control
Company-owner messages use company scope, allowed recipient resolution, external-send confirmation, delivery state, and supportable audit evidence.
Product boundary
Requests are not a general CRM, marketing email platform, unrestricted mailbox, or substitute for secure professional judgment about sensitive documents.
Questions
What firms usually ask.
Can Tally send a request to a company owner?
Tally can prepare and send supported company requests through guarded recipient and confirmation workflows. Raw arbitrary recipient fields are not the intended agent path.
What happens when the owner replies?
Supported replies return to the request thread and can reopen the item so the firm can review the new information and continue the work.
Are requests available on mobile?
The current accountant and company-owner mobile experiences include supported request workflows.