Documents (evidence)
Documents (evidence)
A document is the evidence file that supports a transaction, such as a PDF invoice, receipt, contract, or statement. Bookkeeping needs documents to be linkable and auditable by period, counterparty, and transaction so that every posting can be justified later.
Ownership
Owner: bus attachments. This module is responsible for implementing write operations for this object and is the only module that should directly change the canonical datasets for it.
Secondary read-only use cases are provided by these modules when they consume this object for validation, matching, posting, or reporting:
bus invoices links evidence to invoices for audit trails. bus bank links evidence to statement items when needed, and bus journal is reviewable through links from postings back to evidence.
Actions
Register an evidence document adds evidence files and metadata for deterministic retrieval. Link evidence to a record attaches evidence to invoices or bank transactions for one-step audit navigation. Review evidence completeness marks evidence status so items are not booked without acceptable attachments.
Properties
Core document fields are document_id, doc_date, content_type, path, and document_role. Workflow and linkage fields are evidence_status and linked_entity_reference.
Relations
A document belongs to the workspace’s accounting entity. Scope is derived from the workspace root directory rather than from a per-row key.
A document can be linked to one or more bookkeeping records using linked_entity_reference. In practice the primary targets are sales invoices, purchase invoices, and bank transactions, so that reviewers can navigate from postings and open items back to evidence.