---
id: SCR-ACC-BAT-003
title: Batch detail
route: '/console/{tenantId}/accounting/batches/{batchId}'
surface: console
product_area: accounting
module: batches
revision: 1
status: draft
design_intent: proposed
implementation_evidence: observed
inference: []
source_sha:
  react-console: baf6dae382d6f41dce976c7f848667ccc37e076f
  services-accounting: f47cb263875bbc0c5640fba7dae6785ec32695f8
purpose: >-
  Review collection contents and accounting readiness, follow execution and
  inspect the resulting ledger through permitted actions.
supports:
  - JNY-ACC-BAT-001
  - JNY-ACC-BAT-002
  - JNY-ACC-BAT-004
  - JNY-ACC-BAT-005
  - CAP-ACC-BAT-002
  - CAP-ACC-BAT-004
  - CAP-ACC-BAT-007
  - CAP-ACC-BAT-012
  - CAP-ACC-BAT-013
  - CAP-ACC-BAT-016
  - CAP-ACC-BAT-018
permission: >-
  accounting.batches.read for the screen; each action shows or disables by its
  own key (batch update, posting, unposting); the entries and preview need
  accounting.subledger-entries.read and accounting.batch-postings.preview
entry_from:
  - '/console/{tenantId}/accounting/batches'
  - '/console/{tenantId}/accounting/batches/new (after creation)'
  - A document's batch link
  - An attention item for a batch awaiting posting
exits_to:
  - '/console/{tenantId}/accounting/batches/{batchId}/edit'
  - '/console/{tenantId}/accounting/batches'
  - A document's own screen from the Transactions tab
displays:
  - field: >-
      Collection header with readable identity, financial placement, lifecycle
      badge and derived delivery display
    source: getBatch (DOM-ACC-BAT-001)
  - field: >-
      Generation readiness and validation problems, including missing product
      accounting setup
    source: previewBatchPostings
  - field: >-
      Durable-job panel with checking and writing phases and interpreted
      progress
    source: >-
      Platform's jobs interface over the posting job (DOM-ACC-BAT-003 job steps
      and events)
  - field: Current collection totals alongside persisted generation statistics
    source: 'getBatch (posting statistics, live totals)'
  - field: >-
      Document rows and payment/refund views from the batch-filtered transaction
      query
    source: Platform query over the accounting transactions dataset filtered by batch
  - field: >-
      Ledger entries and account summary built from the capped entry read, with
      an optional historical-reversal view
    source: >-
      listSubledgerEntries by batch, up to twenty-five pages of two hundred
      (DOM-ACC-BAT-004)
  - field: Delivery and export tabs backed by empty placeholder responses
    source: 'none: answered empty by the console until delivery is built'
  - field: Status History presentation without an implemented history read
    source: 'none: no service source (FND-ACC-BAT-045)'
  - field: Activity presentation and stored collection details
    source: The shared activity feed and getBatch
actions:
  - label: 'Close, Reopen, Unarchive'
    operation_id: performBatchAction (listed by listBatchActions)
    permission: accounting.batches.update
    confirm: false
  - label: Archive
    operation_id: performBatchAction (archive)
    permission: accounting.batches.update
    confirm: true
  - label: Post
    operation_id: performBatchAction (post)
    permission: accounting.batch-postings.post
    confirm: true
  - label: Unpost
    operation_id: performBatchAction (unpost)
    permission: accounting.batch-postings.unpost
    confirm: true
  - label: Edit Details
    operation_id: updateBatch (through SCR-ACC-BAT-004)
    permission: accounting.batches.update
    confirm: false
  - label: Validate
    operation_id: previewBatchPostings
    permission: accounting.batch-postings.preview
    confirm: false
  - label: Move to Another Batch (on a document row)
    operation_id: the document's batch reassignment (owned by MOD-ACC-TRX)
    permission: accounting.batches.update
    confirm: true
  - label: Add Transactions
    operation_id: 'none: not connected to a service operation (FND-ACC-BAT-010)'
    permission: accounting.batches.update
    confirm: false
states:
  - loading
  - error
  - read-only
  - inactive
validation:
  - BR-CAP-ACC-BAT-004-06
  - BR-CAP-ACC-BAT-004-07
  - BR-CAP-ACC-BAT-004-08
  - BR-CAP-ACC-BAT-004-09
  - BR-CAP-ACC-BAT-004-10
  - BR-CAP-ACC-BAT-012-03
  - BR-CAP-ACC-BAT-016-07
  - BR-CAP-ACC-BAT-018-04
  - BR-CAP-ACC-BAT-018-08
patterns:
  - Standard-width shared batch layout
  - >-
    Service-derived action menu with disabled explanations and confirmation
    dialogs
  - 'Tabbed collection, accounting and detail presentation'
  - Durable execution panel with job polling
  - Shared TransactionStatusBadge
component: components/accounting/batches/batch-detail-screen.tsx (BatchDetailScreen)
evidence:
  - >-
    react-console at baf6dae3:
    components/accounting/batches/batch-detail-screen.tsx,
    batch-detail-tabs.tsx, batch-accounting-tabs.tsx, batch-entries-tab.tsx,
    batch-posting-panel.tsx, batch-posting-readiness.tsx,
    batch-validation-card.tsx, batch-posting-breakdown.tsx;
    lib/accounting/transactions/http/http-service.ts, batch-delivery.ts,
    batch-posting.ts, batch-transactions.ts
  - >-
    services-accounting at f47cb263:
    modules/batches/aws/api/batch-records.routes.ts, batch-postings.routes.ts,
    subledger-entries.routes.ts
controls: [TC-IAM-001, TC-IAM-002, TC-IAM-004, TC-IAM-005, TC-IAM-006, TC-AZ-001, TC-AZ-002, TC-AZ-003, TC-AZ-004, TC-AZ-005, TC-AZ-006, TC-TEN-001, TC-TEN-002, TC-TEN-003, TC-DAT-002, TC-DAT-005, TC-LOG-001, TC-LOG-002, TC-LOG-003, TC-LOG-004, TC-LOG-005, TC-PI-001, TC-PI-005]
---

# Batch detail

## What the Screen Is For

This page brings collection review, accounting execution and result inspection together. Finance staff follow posting here, and administrators can begin ordinary recovery when its admission checks permit it.

## What It Shows and Lets People Do

The page combines a service-derived action menu with validation, job progress, current figures and recorded results. Tabs expose documents, payments, refunds, ledger entries, account totals, activity and details. Post and Unpost request durable jobs; Edit Details opens the sheet. Reassignment uses the document operation.

## States and Errors

Missing or failed reads provide an error and return path. The service supplies available actions and disabled reasons, while entry and preview requests have their own permissions. Document and ledger reads are capped, so displayed detail and summaries can be incomplete without an explicit partial-result indication.

## Patterns It Must Respect

The page uses the standard layout, shared lifecycle badge, action confirmations, tabs and job panel. Status history, Add Transactions and delivery experiences retain implementation gaps; presenting those controls is not evidence their advertised workflow works.
