---
id: ADR-ACC-BAT-013
title: Run generation in the accounting task function
product_area: accounting
module: batches
revision: 1
status: proposed
design_intent: proposed
source_sha:
  services-accounting: f47cb263875bbc0c5640fba7dae6785ec32695f8
  react-console: baf6dae382d6f41dce976c7f848667ccc37e076f
decision: >-
  The deployed API submits jobs and invokes synchronous preview; accounting
  generation resides in the task function used by execution workflows.
constrains:
  - SVC-ACC-BAT-batches
  - WF-ACC-BAT-005
  - WF-ACC-BAT-006
  - WF-ACC-BAT-007
origin: >-
  T5b of the batch posting port (the deployed shape), recorded at
  services-accounting:docs/migrations/batch-posting/README.md and
  modules/batches/aws/batches.module.ts (header)
alternatives:
  - option: Bundle and execute posting in the HTTP function.
    why_not: >-
      That would include carried generation logic in the submission bundle and
      extend request-held accounting work.
consequences:
  - >-
    Preview invokes the task synchronously with identifiers rather than creating
    a job.
  - >-
    The task deployment also hosts fiscal-close workflows owned by the close
    module.
  - >-
    Missing start configuration can leave a prepared job Pending rather than
    executed.
supersedes: []
evidence:
  - >-
    services-accounting at f47cb263: modules/batches/aws/batches.module.ts;
    services/preview/batch-posting-preview.ts;
    aws/logic/batch-posting-tasks.lambda.ts
---

# Run generation in the accounting task function

## Context

The posting port isolates carried generation rules and long accounting transactions from the HTTP submission bundle.

## Decision

This record describes the proposed boundary in its decision field. Its observed implementation does not constitute Andrew’s approval.

## Alternatives Considered

The alternatives above identify the competing implementation choices and their consequences. They preserve the distinction between a recorded product ruling and a proposed engineering boundary.

## Consequences

The consequence rows describe obligations and known implementation limits at this boundary. Related artifact references retain the affected design homes.