Skip to content
Software Behavior

Case · Invoice review

Same queue. Different system posture.

A short, illustrative product experiment. It demonstrates a design argument; it is not client work, a production system, or measured performance evidence.

Change the invoice condition

  1. INV-20431Northwind Supplies€ 1,240.00Matched
  2. INV-20422Contoso Logistics€ 18,900.00Needs review
  3. INV-20418Fabrikam Ltd€ 4,312.50Blocked

Observed condition

The supplier, legal entity, purchase order, totals, and receipt agree. The user is allowed to review this entity.

Prepared for review

Prepare the coding as a draft, link every value to its source, and leave approval and posting to the authorized reviewer.

Evidence

Supplier
Completed
Northwind Supplies
PO match
Completed
3 of 3 lines
Bank account
Completed
Unchanged since last invoice

Fig. · bank detail change

Plausibility is not provenance. Confidence is not authorization.

Revised design · The behavior spec separates five decisions

Exact rules

Totals, currency, duplicate detection, legal-entity permission, and workflow state stay deterministic and independently testable.

Interpretation

Coding and likely policy exceptions remain proposals tied to source evidence.

Authorization

The system may prepare a review. It may not approve, post, schedule payment, or alter supplier details.

Visibility

Facts, inferences, rule matches, missing evidence, and policy conflicts have distinct labels.

Recovery

Preserve the original, allow field-level correction, and distinguish cancellation from compensation after an external action.