Open table of contents
Key takeaways
- Define the expected source set before judging completeness.
- Reconcile each bank and payout; do not confuse a full folder with a complete month.
- Routine cases may be prepared while material exceptions remain clearly assigned.
- A review-ready package separates owner facts, software preparation, and accountant decisions.
- DeinHans close is a workflow gate, not filing, statutory close, or professional approval.
The owner’s question and the accountant’s question
The owner asks: “Have I supplied enough for the month to move forward?”
The accountant asks: “Can I review this month without first reconstructing what is present, what is missing, how the banks connect, and which decisions are still mine?”
A good handoff answers both. It shows completeness by source, prepared bookkeeping cases, bank evidence, and a short exception list. It does not bury uncertainty in notes across email, chat, and folders.
What should be present
| Area | Expected material | Ready result |
|---|---|---|
| Purchases and expenses | Original invoices, receipts, contracts, corrections, business explanations | Prepared cases linked to payment where available; evidence gaps visible |
| Sales and income | Sales invoices, cash or aggregated sales evidence, platform reports, corrections | Income source represented once and connected to settlement or open item |
| Banks and payment channels | Complete period for each account | Opening and closing balances agree; every material movement explained or open |
| Payouts | Original settlement files, fee/refund evidence, bank transfer | Components reconcile to net payout; carried balances not duplicated |
| Questions | Owner facts about purpose, identity, mixed items, deposits, unusual events | Answer retained with the affected case; unresolved professional decision routed |
| Proposals | Source facts and prepared booking effect | Balanced, inspectable working material; not yet professional approval |
| Exceptions | Missing source, ambiguous VAT, timing, counterparty, allocation, changed format | Owner, reviewer, next action, and close consequence are explicit |
Synthetic handoff: one month with one material exception
“Elbwerk Design GmbH” prepares May. The following case is invented.
The company supplies two complete bank statements, 31 supplier documents, 12 sales invoices, two platform reports, a rent contract, and owner answers for three mixed card payments. Routine invoices are connected to payment candidates, the payouts reconcile to their bank settlements, and the bank accounts prove opening-to-closing movement coverage.
One €2,400 foreign supplier payment remains material. The invoice names consulting services but contains contradictory supplier and VAT information. The bank row and invoice are present; the accountant decision is not.
The right result is not to hide the case so the dashboard looks complete. The review package should say:
| Field | Prepared handoff |
|---|---|
| Source | Original invoice and €2,400 bank movement |
| Business fact | Owner confirms the service and business purpose |
| Software preparation | Supplier facts extracted, payment candidate connected, inconsistency visible |
| Open decision | Supplier identity, VAT treatment, and final coding require accountant review |
| Month effect | Month may be handed over with an explicit professional blocker; it is not finally approved |
This is a useful exception: the accountant receives the evidence and the exact decision, not a vague message saying “foreign invoice unclear.”
How DeinHans prepares the package
1. Establish the month’s expected sources
Expected banks, sales channels, payout providers, contracts, and document groups create the completeness baseline. A missing expected payout report matters even if every uploaded document has been processed.
2. Prepare routine evidence
Documents retain supplier/customer, amount, dates, and source context. Owner questions ask for business facts. Recognised payouts are reconstructed. Bank movements receive evidence-based matching candidates.
3. Keep exceptions explicit
Missing receipts, new payout rows, ambiguous counterparties, combined payments, foreign invoices, or timing issues remain named cases. No silent guess is required to advance the rest of the month.
4. Assemble proposals and review context
Prepared booking proposals show the evidence and proposed effect for the accountant. They are working material. DeinHans does not turn them into professional approval merely because automated checks passed.
5. Apply the close gate
Before the workflow regards the month as prepared, required bank accounts and source groups must be addressed and material gaps acknowledged or resolved. This product state is not a tax filing, statutory close, signed declaration, or guarantee of downstream import.
Responsibility at handoff
| Role | Explicit verbs |
|---|---|
| Owner | Supplies original sources, explains business facts, confirms accounts and channels, answers bounded questions |
| DeinHans | Organises evidence, reconstructs supported payouts, prepares matches and proposals, displays exceptions and readiness |
| Bookkeeper | Checks completeness, follows up evidence, validates source connections, prepares the review package |
| Accountant | Reviews professional treatment, changes or approves proposals, decides material exceptions, signs or files where engaged and authorised |
No workflow can assign a professional duty merely by naming a role. The engagement and the facts determine who signs or files.
Review-ready checklist
- Every business bank and relevant payment channel covers the full period.
- Expected documents, contracts, sales sources, and payout reports are present or explicitly missing.
- Bank movements have specific results or visible exceptions.
- Payout components reconcile to the net settlements.
- Owner questions request facts and their answers remain with the case.
- Prepared proposals retain the supporting evidence and are distinguishable from approval.
- Every material exception has an owner, next action, and reviewer.
- The handoff states what remains unapproved, including tax, period, or counterparty decisions.
- No one describes the software close as filing or legal finality.
The strongest handoff is not the one with the fewest visible exceptions. It is the one in which the accountant can immediately see the complete month, the prepared work, and the small number of decisions that genuinely need professional attention.
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