Payment and Tax Setup
What It Is
This retired grouping brings together the payment and transitional tax configuration shared across a customer’s Accounting workspace. It is retained to preserve the draft’s permanent identity, but the active planning explanation places these subjects among the Accounting Workspace’s facets. The grouping does not represent an additional financial entity that staff create or a separate owner of the same configuration.
The original practical questions remain useful: how long customers have to pay, which receipt methods finance offers and where collected tax is recorded. Payment terms supply named durations. Payment methods supply recognizable names backed by fixed processing behaviour. Transitional tax classes and zones describe treatment still hosted in Accounting while the decided ownership moves to Commerce. Their payable choices connect the resulting liability to each unit’s chart.
What It Is Not
The retired grouping is not a second home for payment or tax rules. It does not own customer-specific terms in Transactions, member payment credentials or Commerce’s intended tax determination. Its continued presence preserves references and history rather than approval for a separate concept in design. New explanations of the shared configuration belong with the workspace, and financial destinations belong with the chart.
How It Is Used
A reader uses this record to understand why the draft grouped these facets together and where they now belong. Administrators still maintain the corresponding configuration through its capabilities and console areas. They define named terms, adapt offered payment methods and review transitional tax configuration. Staff encountering those choices on invoices or payment work consume workspace definitions rather than create a new setup aggregate.
Removing a referenced term or class can fail because financial records still need it. Editing a zone changes future configuration without rewriting issued tax. These consequences are described and sourced in the relevant capabilities so the retired record does not become another independent contract.
Its Facets
Named terms. A term describes an invoice credit period. The workspace supplies the vocabulary, while transaction work interprets the selected term for a particular customer or invoice.
Receipt methods. A method combines customer wording with card, bank-debit or offline behaviour. Offering channels and reference prompts are settings on that method.
Initial methods. Provisioning establishes a protected starting set. Migration can retain additional historical vocabulary without making those additions protected system methods.
Tax classifications. Classes describe product treatment used by rate configuration. Their present location is transitional rather than proof that Accounting remains the intended tax owner.
Zones and rates. Geographic matching and percentages determine applicable tax treatment. These settings sit beside financial mapping today but have a different intended responsibility.
Payable mapping. The collected liability needs a destination in the unit’s chart. Accounting retains that financial concern through the tax ownership change.
How It Relates
Accounting Workspace absorbs the shared definitions and provisioning explanation. Chart of Accounts explains payable destinations. Business units supply the accounting context for recorded money, and Transactions owns invoice and payment use of these choices. Commerce owns the decided future tax service.
What It Could Become
This record should remain retired rather than grow into a new design object. The product should resolve the tax transition in the active workspace and chart explanations. Future stored payment credentials or collection capabilities need their own owning-module decisions rather than revival of a convenient but overly broad setup grouping.