These are repeatable Level Operating Rule tests using invented records only. They identify a control boundary and a refusal condition. They do not establish vendor behavior or replace review of your actual configuration.
FST-005 · LOR-019 · LOR-021 · LOR-027
Exact composite identity
Test: Use native references, payer, date, and exact-cent amount before applying a remittance.
Expected: Only uniquely supported applications can be approved.
Refuse when: Conflicting native identifiers, Duplicate source use.
FST-006 · LOR-011 · LOR-019 · LOR-020
Fuzzy candidate requires review
Test: Use name similarity only to rank candidate records with supporting fields visible.
Expected: Similarity creates a review candidate, not an accounting identity.
Refuse when: No stable identity, Two plausible candidates.
FST-007 · LOR-021 · LOR-022 · LOR-026
One deposit, several invoices
Test: Foot every invoice component to one deposit with payer and remittance evidence.
Expected: A grouped application is accepted only when every component is supported.
Refuse when: Incomplete components, Non-footing amount.
FST-008 · LOR-020 · LOR-022 · LOR-028
Competing subsets
Test: Test whether more than one exact invoice subset could explain one payment.
Expected: No subset is selected automatically when alternatives remain.
Refuse when: Competing exact subsets, Capped candidate search.
FST-009 · LOR-022 · LOR-074
One-cent batch refusal
Test: Compare grouped components to cash at integer-cent precision.
Expected: A one-cent difference remains an exception until explained.
Refuse when: Non-zero difference, Unsupported fee or withholding.
FST-010 · LOR-003 · LOR-021 · LOR-075
Consume-once duplicate prevention
Test: Attempt to apply one source cash line to two active accounting relationships.
Expected: The second active application is refused.
Refuse when: Previously consumed source line.