Trust, access, and responsibility

Trust signals to look for

A trustworthy workflow should make sources, roles, and unresolved questions visible.

• Evidence stays attached to the monthly work it explains.
• Owners and accountants operate from role-appropriate surfaces.
• Open exceptions, decisions, edits, and handoff status remain inspectable.
• Legal and privacy details are linked to formal public documents rather than improvised in article copy.

How the trust model works

Trust comes from separation of preparation, facts, and professional review.

1. 01Keep sources attachedReview should trace work back to documents, bank rows, owner answers, or accountant edits.
2. 02Use role boundariesOwners provide business facts; accountants control professional treatment and approval.
3. 03Show exceptionsUnclear cases stay visible instead of being treated as done.
4. 04Preserve decision contextChanges and approvals should remain understandable later, especially before handoff.
5. 05Use legal pages for formal termsPrivacy, terms, cookies, and contractual obligations belong in the official legal documents.

What Hans prepares

Hans supports trust by organizing evidence and decisions.

• Attached source context and candidate facts.
• Task, matching, and review signals for uncertain work.
• Handoff context that keeps decisions visible for review.
• A public workflow model that avoids exposing internal instructions or customer data.

What people control

Access and review should map to real responsibilities.

• Owners control business facts and organization context.
• Accountants control professional review, edits, approval, and handoff decisions.
• Teams decide who should access a workspace, client, period, or review surface.
• Formal privacy and legal questions are governed by the published legal pages and agreements.

Public safety checks for articles

Use these checks before publishing or updating trust content.

• Do not reveal internal prompts, security procedures, private customer data, or implementation details.
• Do not imply automatic compliance, filing, fraud detection, tax advice, or accountant replacement.
• Use plain language about role boundaries, evidence, review, and responsibility.
• Link to formal legal pages when the question is legal or contractual rather than workflow-based.

Next guides

Trust topics connect to the workflow guides.

• Automation control explains how AI support stays bounded by human decisions.
• DATEV handoff explains why reviewed context matters before export preparation.
• Accountant review explains the professional control point.
• Glossary defines terms used across evidence, review, and handoff.