Accounting

Purpose and Outcomes

Accounting gives a customer a connected account of what it bills, what it receives and how those movements reach its books. Finance colleagues use it to establish the accounting context, work with financial documents, review posted results and understand whether a period is ready to close. The area brings those responsibilities together while retaining a clear home for each kind of record.

The customer can keep separate books for its business units while sharing workspace definitions and a common product catalogue. Those foundations connect operational money records to accounting treatment and reporting. Finance staff, reviewers and controllers approach the area through different responsibilities; service callers and scheduled workers also contribute to the same financial record.

The intended outcome is a financial account that staff can follow from everyday activity through posting, processor settlement and month-end review. Configuration, financial documents, ledger results and closing evidence remain distinguishable so readers can find the layer that answers their question. Accounting also contributes its owned records to the workspace’s managed data lifecycle. The landed planning and design identify implementation limits and unresolved choices, so this overview describes the area’s division without treating every intended outcome as verified or approved.

Scope and Boundaries

Accounting owns the books configuration, shared product record and financial treatment, money documents, posting records, settlement investigation and period closing state. It supplies its financial datasets and lifecycle contributions to shared execution facilities.

Platform owns identity and authorization, workspace lifecycle orchestration, durable execution facilities, communications, query execution and integration transport. CRM owns the people and organizations referenced in financial work. Commerce owns orders and price evaluation; Billing owns recurring billing and collection orchestration as a separate application. Domain applications own the business records that extend a shared product. These boundaries determine where readers follow a handoff when an accounting outcome depends on another area.

Tax configuration and determination retain an observed Accounting footprint during the intended transfer to Commerce. The current service location does not settle future product ownership. Likewise, retained installment interfaces in the financial service do not move Billing’s product responsibility into Accounting.

How the Area Is Divided

Books, Business Units and Chart of Accounts establishes the accounting context shared by financial work. Open it for configuration ownership, the calendar, accounting definitions, document content, shared scheduling or Accounting’s workspace lifecycle contribution.

Products holds the common saleable record and its financial setup while domain applications retain their extensions. Open it to understand the shared catalogue boundary, configured selling information or the handoff from a product’s setup to pricing and posting.

Transactions holds the financial documents and customer money position. Open it when the question concerns a source money record, its financial history, a customer’s standing or the service boundary used by Commerce and processors.

Batch Management connects collections of financial documents to ledger results and deferred revenue records. Open it for the boundary between operational documents and posting, including scheduled intake, retained posting work and the accounting functions used during closing.

Reconciliation connects expected processor settlement to recorded deposits and their explanations. Open it for settlement investigation, independent review, accounting requests and the reconciliation assessment supplied to month-end close.

Month-End Close owns period standing and the evidence around its controlled changes. Open it for the boundary between the calendar maintained by Books and the closing review, execution and retained evidence that depend on posting and reconciliation.

Area-Level Invariants

Every financial record has one owning module. Modules share configuration and consume financial results through their declared boundaries, with assigned fields remaining under the designated writer’s responsibility. Workspace authority and ownership constrain customer work, while business-unit selection establishes its accounting context. The area keeps configuration, source money records, posted results, reconciliation and period standing distinct. Shared execution facilities support that work without taking ownership of its financial meaning.

These are proposed area obligations derived from the landed module boundaries. Detailed guarantees and their observed limits remain in their owning artifacts.

Open Ownership Questions

The tax transfer still needs a cutover that identifies the authoritative editable configuration and the caller of tax determination. The Products ownership question retains the migration decision.

Legacy installment interfaces remain served alongside financial transaction interfaces even though Billing owns the intended orchestration. The retained footprint and the target boundary need an explicit transfer and retirement plan.