---
id: SCR-ACC-TRX-020
title: Settlement record
route: '/console/{tenantId}/accounting/settlements/{settlementId}'
surface: console
product_area: accounting
module: transactions
revision: 1
status: draft
design_intent: proposed
implementation_evidence: observed
inference: []
source_sha:
  services-accounting: f47cb263875bbc0c5640fba7dae6785ec32695f8
  react-console: baf6dae382d6f41dce976c7f848667ccc37e076f
purpose: >-
  Trace settlement progress through its component applications, collection and
  recorded outcomes.
supports:
  - JNY-ACC-TRX-002
  - JNY-ACC-TRX-003
  - CAP-ACC-TRX-009
permission: >-
  accounting.settlements.read AND (accounting.payments.read OR
  accounting.credit-applications.read)
entry_from:
  - '/console/{tenantId}/accounting/payments/receive'
  - '/console/{tenantId}/accounting/payments/{paymentId}'
exits_to:
  - '/console/{tenantId}/accounting/payments/{paymentId}'
  - '/console/{tenantId}/accounting/creditApplications/{applicationId}'
  - '/console/{tenantId}/accounting/invoices/{invoiceId}'
displays:
  - field: >-
      Operation summary and state, step outcomes and refusals, related
      applications and receipt.
    source: getSettlement (DOM-ACC-TRX-003 settlements)
actions: []
states:
  - loading
  - error
  - read-only
validation:
  - BR-CAP-ACC-TRX-009-11
patterns:
  - Full PageLayout
  - Summary card
  - Operation-step list
component: >-
  components/accounting/settlements/settlement-detail-screen.tsx
  (SettlementDetailScreen)
evidence:
  - >-
    react-console at baf6dae3:
    components/accounting/settlements/settlement-detail-screen.tsx;
    lib/accounting/transactions/http/settlements.ts.
controls: [TC-IAM-001, TC-IAM-002, TC-IAM-004, TC-IAM-005, TC-AZ-001, TC-AZ-002, TC-AZ-003, TC-AZ-004, TC-AZ-006, TC-TEN-001, TC-TEN-002, TC-TEN-003, TC-DAT-001, TC-DAT-002, TC-DAT-003, TC-LOG-004, TC-LOG-005, TC-PI-001, TC-PI-003, TC-PRV-001, TC-PRV-002]
---
# Settlement record

## What the Screen Is For

Trace settlement progress through its component applications, collection and recorded outcomes.

## What It Shows and Lets People Do

This read-only record links the settlement’s resulting financial documents and explains each recorded step. It has no settlement mutation controls.

## States and Errors

Pending, failed and exception results identify incomplete work. There is no dedicated settlement list, and the API read requires the compound permissions recorded in frontmatter.

## Patterns It Must Respect

The frontmatter names the components and layout actually used. Confirmation behavior is action-specific, including inline review and direct submission where implemented. The contract records the current console behavior without declaring an approved visual baseline.