Accounting Workspace
What It Is
The Accounting workspace is the customer’s shared accounting context across all its business units. It includes the configuration that should have one meaning throughout the customer’s work, the access conventions protecting that information and Accounting’s participation in operational lifecycle work. A staff member normally sees particular units, accounts and financial documents, but the workspace explains the common choices those records rely on.
Named payment terms and methods are shared definitions rather than separate copies per unit. One settings record selects policies applied by transaction and posting workflows. Schedules support recurring work, and lifecycle participants answer for Accounting data when Platform provisions, exports or deletes the workspace. This broad concept keeps those facets understandable together without turning each setting or operational table into another product noun.
What It Is Not
A workspace is not a set of books: a business unit supplies that narrower context. Nor does Accounting own Platform’s workspace record, licensing or lifecycle orchestration. Accounting owns its contribution and data within that boundary. Tax configuration still hosted here is also transitional; its decided determination owner is Commerce, while Accounting retains financial mapping and recorded tax.
How It Is Used
Administrators maintain shared terms, methods and policy. Staff use those choices during invoice and payment work without needing authority to change configuration. Authorized users preview recurrence while configuring a scheduled subject and inspect its later outcomes. Platform jobs handle initial provisioning and customer data operations, with availability checks limiting ordinary work during lifecycle transitions.
A successful experience preserves the customer’s boundaries and explains failure. A stale save asks for reconciliation instead of overwriting a colleague. A schedule that repeatedly fails pauses for attention. A blocked export explains its reason, while deletion continues from completed batches after an interruption.
Its Facets
Payment vocabulary. Terms describe named durations; methods describe receipt behaviour, offering channels and reference prompts. Initial system methods provide the starting vocabulary.
Transitional tax setup. Classes, zones and rates remain editable here at the pinned implementation. Their future ownership and migration require a settled transition rather than two permanent sources of tax treatment.
Access and saved records. Resource permissions, versions, locks and workspace boundaries control configuration changes. Published permission names alone do not establish supported actions.
Shared policies. Statement selection, overpayment handling, refund approval and deferral choices apply across units. Related reconciliation and close switches remain the responsibility of their consuming modules.
Recurring timing. Schedules describe when owning records run and preserve occurrence history. Preview and run-history access serve different stages of that work.
Lifecycle participation. Provisioning establishes initial methods; availability follows Platform state. Export streams declared customer datasets with exclusions and secret checks. Erasure removes owned data in dependency order without touching another workspace.
How It Relates
Business units hold individual books within this shared context. Templates supply the workspace statement default, while the chart supplies payable destinations. Transactions, posting, reconciliation and close consume shared policy. Scheduled subjects belong to their owning modules, and Platform coordinates the workspace lifecycle rather than delegating ownership of its own record to Accounting.
What It Could Become
The product should settle the tax transition and the scheduler’s relationship to Billing before design fixes their long-term ownership. It should make unsupported published permissions distinguishable from usable actions. Future exposure of related settings needs clear ownership so a shared storage location does not imply one editor can change every policy.