---
id: CON-ACC-BKS-005
name: Payment and Tax Setup
feature: FEAT-ACC-BKS-04
product_area: accounting
module: books
revision: 1
status: superseded
product_intent: confirmed
implementation_evidence: inconsistent
source_sha:
  services-accounting: f47cb263875bbc0c5640fba7dae6785ec32695f8
  react-console: baf6dae382d6f41dce976c7f848667ccc37e076f
definition: >-
  This superseded grouping preserves the draft identity for payment and tax
  configuration now explained as workspace facets.
owned_by: MOD-ACC-BKS
synonyms:
  - terms
  - payment methods
  - tax configuration
not_to_be_confused_with:
  - Customer-specific financial terms in Transactions.
  - Member payment credentials.
  - Commerce-owned tax determination.
facets:
  - name: Named due-date choices
    meaning: Payment terms define named invoice durations.
    used_for: Choosing invoice credit periods.
  - name: Receipt behaviour
    meaning: >-
      Named methods use card, bank-debit or offline behaviour with offering
      settings.
    used_for: Recording and offering receipts.
  - name: Initial vocabulary
    meaning: Provisioning supplies protected payment methods for a new workspace.
    used_for: Beginning payment entry.
  - name: Product tax classifications
    meaning: Classes label the tax treatment used for products.
    used_for: Looking up applicable percentages.
  - name: Geographic tax configuration
    meaning: Zone criteria and rate definitions describe where and how tax applies.
    used_for: Determining recorded invoice tax.
  - name: Liability destinations
    meaning: Each rate can select a payable account for a business unit.
    used_for: Posting the collected liability.
relationships:
  - to: CON-ACC-BKS-002
    statement: Payable mapping chooses a GL destination in the mapped unit.
    provenance: test
    source: >-
      services-accounting:modules/books/tests/integration/services/persistence/tax-zones.integration.spec.js#refuses
      a rate naming a tax class the tenant has not, and one naming a GL account
      of another unit, by position
  - to: CON-ACC-BKS-006
    statement: Accounting provisioning establishes initial payment methods.
    provenance: test
    source: >-
      services-accounting:modules/maintenance/tests/integration/services/participants/configuration-participant.integration.spec.js#answers
      provision done, having written the tenant’s five system payment methods
      (WP-01)
lifecycle:
  - state: active
    meaning: The configured choice remains available for new work.
    how_it_changes: >-
      An administrator may deactivate eligible choices, excluding protected
      system methods.
  - state: inactive
    meaning: The choice remains on existing work but is no longer offered.
    how_it_changes: An administrator restores availability.
acted_on_by:
  - CAP-ACC-BKS-011
  - CAP-ACC-BKS-012
  - CAP-ACC-BKS-013
  - CAP-ACC-BKS-019
visible_to:
  - ACT-ACC-001
  - ACT-ACC-002
  - ACT-ACC-003
  - ACT-ACC-005
evidence:
  - >-
    Verified source file:
    services-accounting:modules/books/db/payment-methods.table.ts
  - >-
    Verified source file:
    services-accounting:modules/books/db/payment-terms.table.ts
  - >-
    Verified source file:
    services-accounting:modules/books/db/tax-classes.table.ts
  - >-
    Verified source file:
    services-accounting:modules/books/db/tax-zone-rates.table.ts
  - >-
    Verified source file:
    services-accounting:modules/books/db/tax-zones.table.ts
  - >-
    Verified source file:
    services-accounting:modules/books/tests/integration/services/persistence/tax-zones.integration.spec.js
  - >-
    Verified source file:
    services-accounting:modules/maintenance/tests/integration/services/participants/configuration-participant.integration.spec.js
supersedes: []
---

# 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.