Document Template
What It Is
A document template supplies the content and formatting used for an Accounting document or accounting-software download. It combines fixed wording with merge fields appropriate to a particular document kind. The customer can prepare invoice, receipt, statement and batch-download content without making every business unit maintain its own copy. Units select templates separately from editing their content.
Rhythm provides protected built-ins that staff can inspect and duplicate. A copied template becomes customer-maintained content with its own identity and active standing. Staff edit Liquid sources and preview them against sample data before saving. A template’s kind determines the variables and parts it may carry, so changing content does not turn an invoice template into a statement or software export.
What It Is Not
Accounting templates are distinct from console layouts and forms, which define record presentation and entry. Billing reminders and dunning content serve separate workflows, and a CRM communication template has a different purpose. A preview is a draft rendering against sample information; it neither saves the template nor proves that every producing workflow adopts the shared resolver.
How It Is Used
The controller opens the relevant kind tab and starts a customer template from a built-in copy or new content. They insert available merge fields, review the preview and correct any validation problems. Once the content is ready, they select it on a unit or as the workspace’s statement default. Readers can inspect the same editor without changing sources.
Staff should check usage before removing obsolete content. Configuration prevents removal or deactivation when a unit or default still depends on the template. Clearing those selections releases it for later cleanup. Explicit unusable choices produce a refusal rather than quietly substituting another document.
Its Facets
Kind. The permanent kind separates the document purposes and supplies their allowed fields. It also determines where staff can select the template.
Built-in content. Protected templates provide a reusable starting point. The invoice built-in’s limited content means customers should inspect its output rather than assume it already contains every desired detail.
E-mail parts. Subject, body and related addressing choices accompany documents where applicable. A statement requires e-mail content, while a batch download uses file output instead.
Statement recipients. Recipient mode distinguishes all customer contacts from contacts selected through named roles. It expresses delivery selection rather than a new template kind.
Merge vocabulary. Variables carry descriptions, types and examples, while formatting filters convert their values for readable output.
Preview. Draft rendering helps staff see problems and empty fields before a save. Document and export rendering use the escaping appropriate to their output.
Selections. Explicit choices, unit configuration and defaults supply the resolver’s alternatives. These links connect content to production and create the dependencies staff inspect before deletion.
How It Relates
Business units select their document templates, and workspace settings select the statement default. Producing workflows in Transactions, Billing and batch processing consume or are expected to consume those choices. This module owns the content and resolver; each producer remains responsible for using them correctly.
What It Could Become
The product should verify resolver adoption in every document-producing module before design promises consistent selection everywhere. It should confirm the inactive-template treatment and decide whether language-specific content is needed. Those decisions can extend the template concept while preserving the distinction between prepared content and an actual delivered document.