---
id: TST-ACC-BAT-072
title: Batch integration revenue recognition
kind: integration
product_area: accounting
module: batches
revision: 1
status: draft
product_intent: proposed
implementation_evidence: observed
source_sha:
  services-accounting: f47cb263875bbc0c5640fba7dae6785ec32695f8
repository: services-accounting
files:
  - >-
    modules/batches/tests/integration/services/close/revenue-recognition.integration.spec.js
implements:
  - ATS-ACC-BAT-020-04
  - ATS-ACC-BAT-020-05
environment: local
implementation_state: implemented
latest_result: not-run
latest_run_at: null
latest_run_ref: null
conformance: not-verified
estimated_minutes: 5
isolation: >-
  The suite owns its test workspace or fixed integration fixtures in the
  prepared local database.
assertion_sources:
  - scenario: ATS-ACC-BAT-020-04
    provenance: test
    source: >-
      services-accounting:modules/batches/tests/integration/services/close/revenue-recognition.integration.spec.js#posts
      the entries in July's deferred revenue batch, named and dated as 1.0 did,
      with one entry per schedule entry
  - scenario: ATS-ACC-BAT-020-04
    provenance: test
    source: >-
      services-accounting:modules/batches/tests/integration/services/close/revenue-recognition.integration.spec.js#sweeps
      in B's back-dated July entries with A's and B's August entries
  - scenario: ATS-ACC-BAT-020-04
    provenance: test
    source: >-
      services-accounting:modules/batches/tests/integration/services/close/revenue-recognition.integration.spec.js#closes
      both schedules, their last entries recognized
  - scenario: ATS-ACC-BAT-020-04
    provenance: test
    source: >-
      services-accounting:modules/batches/tests/integration/services/close/revenue-recognition.integration.spec.js#refuses
      recognition outside a transaction (`transaction-required`)
  - scenario: ATS-ACC-BAT-020-05
    provenance: test
    source: >-
      services-accounting:modules/batches/tests/integration/services/close/revenue-recognition.integration.spec.js#un-recognizes
      A's and B's September entries and opens both schedules again
  - scenario: ATS-ACC-BAT-020-05
    provenance: test
    source: >-
      services-accounting:modules/batches/tests/integration/services/close/revenue-recognition.integration.spec.js#leaves
      the July and August entries recognized
evidence:
  - provenance: observed
    source: >-
      services-accounting:modules/batches/tests/integration/services/close/revenue-recognition.integration.spec.js
    note: >-
      The executable file is inspected at the pinned revision; duration is an
      unmeasured planning estimate.
  - provenance: documented
    source: >-
      services-accounting:modules/batches/tests/integration/services/close/revenue-recognition.integration.spec.js#suite
      header
    note: >-
      Real: the integration database, the configuration, products and
      transaction services, the posting job (inline runner), the ported
  - provenance: documented
    source: >-
      services-accounting:modules/batches/tests/integration/services/close/revenue-recognition.integration.spec.js#suite
      header
    note: >-
      (`support/close-world.js`, `setPeriodStatus`). Doubled: B's two back-dated
      entries (above).
unbound_scope: null
candidate_implements:
  - scenario: FAS-ACC-BAT-05-03
    gap: FND-ACC-BAT-076
    provenance: test
    source: >-
      services-accounting:modules/batches/tests/integration/services/close/revenue-recognition.integration.spec.js#September
      reopen and re-close
---

# Batch integration revenue recognition

## Verification Boundary

This suite exercises the imported batch services or storage against the prepared local database. It does not imply that a deployed workflow is contacted.

## What This Suite Proves

Successive fiscal periods release due amounts, reopening restores selected releases and re-close writes a fresh system generation. The assertion anchors identify the supported portions of the bound scenarios.

## What It Does Not Prove

Local assertions do not establish deployment configuration, remote delivery guarantees, or unasserted lifecycle and concurrency paths.

## Real Dependencies and Test Doubles

PostgreSQL and the exercised persistence or accounting functions are real. Controlled clocks, imported test fixtures and any suite-specific doubles delimit the asserted behavior.

## Must Not Be Doubled

The database constraints, transaction boundaries and exercised accounting functions must remain real when qualifying the asserted persistence or generation behavior.