Open table of contents
Key takeaways
- Ask for one decisive fact at a time.
- Include the evidence and explain why the answer matters.
- Route factual questions to the business and judgment questions to the accountant.
- Record answer, source, respondent and resulting action together.
Anatomy of a useful question
| Element | Example |
|---|---|
| Case | Bank payment €480, 14 June, ABC GmbH |
| Available evidence | Card receipt only; no invoice |
| Observed issue | Receipt lacks service description and customer name |
| Precise question | What was purchased, for which business purpose, and can you request the invoice? |
| Due date/impact | Needed before June handoff |
Avoid embedding the proposed answer in the question. “Please confirm this is software and reverse charge” encourages agreement rather than factual correction.
Question types and owners
- Business fact: purpose, participants, delivery, refund reason—business owner or employee.
- Document request: invoice, contract, statement—person with source access.
- Reconciliation: allocation, payout component, duplicate—bookkeeping team, sometimes business input.
- Professional judgment: VAT, period, account, correction—qualified accountant or tax adviser.
- System issue: import, access, rendering—support or system owner.
Route by resolution authority. A queue is not efficient if everyone can see a question but nobody owns it.
Structured resolution workflow
- Assemble the smallest complete case packet.
- State what is known and what conflicts.
- Ask one or two answerable questions.
- Assign person and due date.
- Keep follow-up in the same case.
- Record the answer and attached evidence.
- Apply the resulting decision and close with a reason.
Example: payout difference
A €9,940 payout is €300 below the settlement bridge. Instead of “Why doesn’t this match?”, ask: “The report shows a €300 reserve withheld on payout P-118. Is there a reserve statement or contract notice for this amount?” The owner supplies the statement. The bookkeeping team carries the reserve balance, and the accountant reviews its presentation. Each person answers at their level.
Three questions, three different routes
| Situation | Question | Recipient | What can continue |
|---|---|---|---|
| One invoice lacks purpose | “What was the €480 service used for, and can you attach the invoice?” | Owner or purchaser | Other complete invoices continue; this proposal waits |
| One payout has a shared reserve row | “Does the €300 row carry an existing reserve, create a new hold, or release one? Please attach the provider notice.” | Owner with platform access | Known sales, fees and refunds can be reconstructed; every affected component retains the shared question |
| Cross-border facts are complete but treatment is unresolved | “Please review the supplier country, service and invoice wording for VAT treatment.” | Accountant/tax adviser | Factual preparation remains visible; no owner is asked to choose a tax code |
The payout case is important because one provider fact can affect several reconstructed components while the bank match remains a separate check. DeinHans can keep one shared question attached to the payout container, preserve which child records depend on it and continue only the work supported by independent evidence. It should not duplicate the same question across five rows or close all five because one amount happens to match.
What DeinHans can support
DeinHans can keep the question attached to its transaction, document and task, with ownership and status visible to both business and accountant. AI may help draft a concise question from available evidence, but the workflow should not invent the missing fact or close the case without a real answer.
On mobile, the owner should see the source, amount, plain-language question and requested evidence without accounting jargon. The professional reviewer should see the same answer in context, including what it changed and which work still needs approval.
Boundary: Answers from business users establish facts but do not automatically determine tax or accounting treatment. Material judgments still require the appropriate reviewer.
Improve the question system
Review recurring question categories monthly. A repeated missing invoice may need a collection change; repeated unclear purposes may need a card-use policy; recurring payout questions may need a better source export. Improve the upstream process, but keep legitimate one-off exceptions visible rather than forcing every case into a template.
Quality standard for answers
An answer is complete when it identifies the respondent, states the fact in unambiguous language, includes or points to supporting evidence and resolves the requested input. “Business expense” is not enough if the question asked who attended and why. A screenshot without its source or date may also be insufficient.
If the answer changes a material proposal, show the old and new result to the appropriate reviewer. Do not let a factual response silently authorize accounting treatment. Close the question only after the downstream task has consumed the answer or explicitly recorded that no change is needed.
Protect confidentiality
Ask only for facts necessary to resolve the bookkeeping case. Avoid copying full customer correspondence, health data or unrelated contract sections into a broad queue. Use access roles and secure source links for sensitive evidence. The question can describe what a restricted reviewer needs without exposing the document to every participant.
Measure reopened questions and incomplete first responses. Improving the question wording and evidence packet is usually more valuable than sending more reminders.
Sources
Sources were checked on 21 July 2026. This article provides orientation and is not tax, legal, or accounting advice.
Related resources
See how DeinHans supports this workflow
Explore the product flow without confusing automation with professional approval.
View product