---
id: TST-COM-FUL-056
title: Order billed on terms
kind: unit
product_area: commerce
module: fulfillment
revision: 1
status: draft
source_sha:
  services-commerce: c8b66a98e2490617aec38ba5c8165dd9bd0a8f9b
  react-console: baf6dae382d6f41dce976c7f848667ccc37e076f
repository: services-commerce
files:
  - modules/fulfillment/tests/unit/register/order-billed-on-terms.spec.js
implements:
  - ATS-COM-FUL-002-05
environment: mock
implementation_state: implemented
latest_result: not-run
latest_run_at: null
latest_run_ref: null
conformance: not-verified
estimated_minutes: 1
isolation: 'In-memory inputs, recorded calls and test-owned doubles; no shared customer records.'
evidence:
  - repository: services-commerce
    path: modules/fulfillment/tests/unit/register/order-billed-on-terms.spec.js
    test_titles:
      - is a console order whose profile requires terms
      - is a console order with a succeeded terms tender
      - is not an order whose terms tender is only submitted or declined
      - is not an order paid by card or left pay-now
      - 'is not a portal order, even on terms'
    scenario_anchors:
      - >-
        services-commerce:modules/fulfillment/tests/unit/register/order-billed-on-terms.spec.js#is a
        console order whose profile requires terms
      - >-
        services-commerce:modules/fulfillment/tests/unit/register/order-billed-on-terms.spec.js#is a
        console order with a succeeded terms tender
      - >-
        services-commerce:modules/fulfillment/tests/unit/register/order-billed-on-terms.spec.js#is
        not an order whose terms tender is only submitted or declined
      - >-
        services-commerce:modules/fulfillment/tests/unit/register/order-billed-on-terms.spec.js#is
        not a portal order, even on terms
---

# Order billed on terms

## Verification Boundary

This suite checks order billed on terms with controlled inputs and recorded dependencies. Its entry points remain within the process.

## What This Suite Proves

The bound scenarios identify the assertions this suite contributes. Source anchors retain the exact test cases; where a capability scenario has several contributing suites, a single binding does not imply that every branch runs here.

## What It Does Not Prove

Controlled inputs do not establish database enforcement, deployed integration or browser behavior. A recorded call is evidence about the adapter contract rather than a remote operation.

## Real Dependencies and Test Doubles

The imported logic is real; test inputs and dependency responses are controlled.

## Must Not Be Doubled

Keep the imported production logic and its request construction real. Record dependency calls and refusals rather than replacing the behavior being asserted.