---
id: TST-ACC-REC-086
title: Matching strength from processor evidence
kind: unit
product_area: accounting
module: reconciliation
revision: 1
status: draft
source_sha:
  services-accounting: f47cb263875bbc0c5640fba7dae6785ec32695f8
repository: services-accounting
files:
  - modules/reconciliation/tests/unit/rules/match-ranking.spec.js
implements:
  - ATS-ACC-REC-008-05
environment: local
implementation_state: implemented
latest_result: not-run
latest_run_at: null
latest_run_ref: null
conformance: not-verified
estimated_minutes: 1
isolation: Suite-owned workspace fixtures and deterministic records removed by suite cleanup.
evidence:
  - 'services-accounting:modules/reconciliation/tests/unit/rules/match-ranking.spec.js'
bindings:
  - scenario: ATS-ACC-REC-008-05
    assertions:
      - >-
        services-accounting:modules/reconciliation/tests/unit/rules/match-ranking.spec.js#ranks a candidate
        the processor reports paid in this payout
      - >-
        services-accounting:modules/reconciliation/tests/unit/rules/match-ranking.spec.js#ranks a candidate
        settled in a processor batch with an item claimed by payout reference
      - >-
        services-accounting:modules/reconciliation/tests/unit/rules/match-ranking.spec.js#ranks a candidate
        expected after the previous deposit and before this one
      - >-
        services-accounting:modules/reconciliation/tests/unit/rules/match-ranking.spec.js#ranks a candidate
        expected 4 business days before the deposit, with no previous payout
      - >-
        services-accounting:modules/reconciliation/tests/unit/rules/match-ranking.spec.js#ranks a candidate
        expected on the sixth business day before the deposit, with no previous payout
      - >-
        services-accounting:modules/reconciliation/tests/unit/rules/match-ranking.spec.js#ranks a candidate
        the same whatever amount it carries
---

# Matching strength from processor evidence

## Verification Boundary

This suite evaluates the production rules or declarations with controlled inputs. It does not perform a complete financial workflow.

## What This Suite Proves

The executable assertions identified in the binding records supply the registered scenario observations. When a scenario names several suites, this suite supplies its listed assertions and does not independently establish every clause.

## What It Does Not Prove

Database enforcement, API authorization, console behavior and deployed workflow completion require separate suites.

## Real Dependencies and Test Doubles

Production rules and declarations are real; fixtures supply literal amounts, dates and permission sets. No live database or deployed service participates.

## Must Not Be Doubled

The rule or declaration under examination remains production code; expected results remain independent literal observations.