---
id: TST-COM-ORD-127
title: InvoiceTaxOf
kind: unit
product_area: commerce
module: orders
revision: 1
status: draft
source_sha:
  services-commerce: c8b66a98e2490617aec38ba5c8165dd9bd0a8f9b
repository: services-commerce
files:
  - modules/orders/tests/unit/billing/invoice-tax.spec.js
implements: []
environment: mock
implementation_state: implemented
latest_result: not-run
latest_run_at: null
latest_run_ref: null
conformance: not-verified
estimated_minutes: 1
isolation: 'The suite owns its in-memory inputs, scripted responses and rendered component state.'
evidence:
  - provenance: test
    source: 'services-commerce:modules/orders/tests/unit/billing/invoice-tax.spec.js'
    test_cases:
      - services/billing/invoice-tax.ts
      - 'answers the header’s tax and each line’s on the order line named, or linked by its invoice line'
      - answers nothing for an invoice with no tax_total (an Accounting before M5)
      - refuses an amount in another currency
      - agrees when the invoice’s tax is the order’s
      - 'says an order ships by its snapshot’s shippable lines, else by a shipping charge, else not'
      - >-
        holds an invoice of the whole order to its net total and re-prices the order to a differing tax
        (D-P3-41)
      - does not re-price an invoice of the whole order whose tax is the quote
      - names both totals and both taxes when the net totals differ
      - compares the whole totals when Commerce bills the tax as a line
      - holds the deposit invoice to the deposit net of its tax
      - never re-prices the order to the deposit’s tax
      - says what the deposit owes when the net totals differ
      - compares the deposit’s whole total when Commerce bills the tax as a line
scenario_coverage: []
---

# InvoiceTaxOf

## Verification Boundary

The unit suite checks the named contract or helper with controlled inputs.

## What This Suite Proves

The registered cases check invoiceTaxOf with their fixture records and assertions. Scenario bindings name only the examples those cases exercise.

## What It Does Not Prove

A registered file supplies no run result or verified conformance by itself. Local fixtures do not establish deployed cross-service behavior or complete browser journeys.

## Real Dependencies and Test Doubles

Inputs and external responses are controlled in process; this suite establishes no deployed service behavior.

## Must Not Be Doubled

The named contract validation or component behavior under assertion must use its actual implementation.