Deployment Currently Shares Accounting Functions

Context

The source module owns close behavior while deployment currently shares other Accounting functions.

Decision

Keep the module’s records and contracts together in the design while describing the shared function arrangement. A dedicated deployment remains the restructure’s recorded open decision.

Alternatives Considered

Create dedicated close stacks and a function immediately. The restructure reserves that change for its deployment plan and connection-register work.

Consequences

Reconciliation, configuration and batch-posting deployments can each change the close behavior they host. Close submission shares the configuration period-route prefix. The source module and record groups still define the logical boundary.