---
id: ADR-ACC-CLS-014
title: Deployment Currently Shares Accounting Functions
product_area: accounting
module: close
revision: 1
status: proposed
design_intent: open
source_sha:
  services-accounting: f47cb263875bbc0c5640fba7dae6785ec32695f8
  react-console: baf6dae382d6f41dce976c7f848667ccc37e076f
decision: >-
  Reads and recovery are hosted by Reconciliation, close and reopen submissions
  by Books configuration, and tasks by batch posting until deployment ownership
  is decided.
constrains:
  - SVC-ACC-CLS-fiscal-close
  - RESP-ACC
origin: >-
  services-accounting:docs/architecture/accounting-2.0/02-decisions.md (open
  item: where fiscal close gets its own stacks and function, a stage 2
  decision); FND-ACC-CLS-008
alternatives:
  - option: Create dedicated close stacks and a function immediately.
    why_not: >-
      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.
supersedes: []
evidence:
  - >-
    services-accounting at f47cb263: modules/fiscal-close/README.md;
    aws/api/fiscal-close.routes.ts, fiscal-period-close.routes.ts (headers);
    aws/logic/fiscal-close.step-functions.ts;
    docs/architecture/accounting-2.0/03-module-structure.md.
---

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