Booking proposals explained

What a proposal should include

A proposal is useful only when the reviewer can understand why it exists.

• The original evidence and extracted facts behind the draft.
• Owner-provided business context where the evidence alone is not enough.
• Payment or matching context when money movement explains the record.
• Visible flags for VAT, splits, account treatment, evidence gaps, or low confidence.

Proposal review flow

The proposal helps the accountant move faster without losing control.

1. 01Read the sourceCheck the invoice, receipt, statement, or report before trusting any prepared structure.
2. 02Inspect the draftReview the suggested structure, supporting context, and reasons for any caution flags.
3. 03Compare with policyApply the firm’s professional standards for VAT, accounts, splits, reimbursements, and edge cases.
4. 04Edit, reject, or askCorrect the proposal, reject it, or request more owner context when the record is not reviewable.
5. 05Approve only when readyApproval should be explicit and tied to the reviewer’s decision, not to the existence of a draft.

What Hans prepares

Hans packages proposal context for inspection.

• Draft structure based on available evidence and context.
• Source attachments and extracted facts that explain the proposal.
• Confidence signals, missing-context flags, and owner answers.
• A review state that can be accepted, changed, rejected, or sent back.

What the accountant decides

The accountant owns the professional conclusion.

• Whether the proposal is acceptable, needs edits, should be rejected, or requires more information.
• How VAT, SKR03/account treatment, split lines, reimbursements, and private-use cases are handled.
• Whether the item can move into period readiness or must remain a blocker.
• How the decision is documented for downstream review or handoff.

Proposal boundaries

These boundaries keep proposal language accurate.

• A proposal is prepared context, not final accounting treatment.
• High confidence is not the same as accountant approval.
• Missing source evidence or owner facts should remain visible until resolved.
• Public examples should not be reused as tax, legal, or firm policy advice.

Next guides

Continue with the guides that explain review and handoff.

• Accountant review explains the broader queue and approval workflow.
• Glossary explains VAT, SKR03, matching, period, and handoff terms.
• DATEV handoff explains how reviewed context can support export preparation.
• Trust and access explains why decisions and evidence must stay traceable.