---
id: ADR-ACC-REC-014
title: No Reconciliation Operation Is Published to Submissions
product_area: accounting
module: reconciliation
revision: 2
status: proposed
design_intent: proposed
source_sha:
  services-accounting: f47cb263875bbc0c5640fba7dae6785ec32695f8
  react-console: baf6dae382d6f41dce976c7f848667ccc37e076f
decision: >-
  Record every operation’s current lack of a Submissions binding and retain its
  rationale.
constrains:
  - SVC-ACC-REC-reconciliation
  - RESP-ACC
origin: R2-ARCH-002 (publish or say why not); FND-ACC-REC-032
alternatives:
  - option: Publish payout entry as a Submissions operation.
    why_not: >-
      The observed entry path is staff finance work; later processor integration
      has no built binding.
  - option: Omit publication information entirely.
    why_not: >-
      Reviewers could not assess the requested architectural publication
      boundary.
consequences:
  - Each contract operation states its unpublished status.
  - >-
    Future import architecture and any intake binding need their own decision;
    neither is implemented now.
supersedes: []
evidence:
  - >-
    services-accounting at f47cb263: modules/reconciliation/aws/api/*.routes.ts
    (no binding declarations).
---
# No Reconciliation Operation Is Published to Submissions

## Context

Publication status must be visible even where staff work and internal reads have no intake binding.

## Decision

Record every operation’s current lack of a Submissions binding and retain its rationale.

## Alternatives Considered

Publish payout entry as a Submissions operation. The observed entry path is staff finance work; later processor integration has no built binding.

Omit publication information entirely. Reviewers could not assess the requested architectural publication boundary.

## Consequences

Each contract operation states its unpublished status. Future import architecture and any intake binding need their own decision; neither is implemented now.