---
id: ADR-ACC-TRX-014
title: Unpublished Transaction Intake Contracts
product_area: accounting
module: transactions
revision: 1
status: proposed
design_intent: proposed
source_sha:
  services-accounting: f47cb263875bbc0c5640fba7dae6785ec32695f8
  react-console: baf6dae382d6f41dce976c7f848667ccc37e076f
decision: >-
  No versioned Submissions contract is declared for the observed transaction
  operations, and the service contract records their current unpublished status
  without deciding future intake policy.
constrains:
  - SVC-ACC-TRX-transactions
  - RESP-ACC
origin: >-
  R2-ARCH-002 (publication status stated per operation), applied by this design
  draft
alternatives:
  - option: Publish financial collection directly as form intake.
    why_not: >-
      There is no recorded intake contract for the intent-based collection and
      recovery lifecycle.
  - option: Publish billing creation directly as form intake.
    why_not: >-
      The observed callers are staff and Commerce, without an established
      Submissions billing contract.
consequences:
  - >-
    Future intake billing or collection needs an explicit supported integration
    and publication decision.
  - >-
    The service inventory records an unpublished reason for every current
    operation.
supersedes: []
evidence:
  - >-
    services-accounting at f47cb263:
    docs/architecture/accounting-2.0/02-decisions.md, 05-lifecycles.md,
    06-integrity-model.md.
---
# Unpublished Transaction Intake Contracts

## Context

Publication must be stated per operation. Absence of a published intake declaration supports the current status but does not authorize a permanent prohibition.

## Decision

The structured decision records the governing boundary and its observed limits. Its origin distinguishes Andrew’s rulings from reversible implementation choices and proposed publication policy.

## Alternatives Considered

The listed alternatives explain the competing responsibility or recovery approaches and why the recorded direction differs. They are explanatory comparisons, without evidence of a separate approval discussion for each alternative.

## Consequences

The consequence rows identify implementation obligations, current departures and gaps requiring further verification. Artifact status remains proposed until Andrew approves it.