Trigger
Before invoicing, settlement or change confirmation, contract, technical agreement, order, change record, acceptance evidence and invoice fields must agree.
SCENARIO-DETAIL / LOCALIZED DECISION BRIEF
Contract, Change, Order, Acceptance and Invoice Consistency
Business trigger: Before invoicing, settlement or change confirmation, contract, technical agreement, order, change record, acceptance evidence and invoice fields must agree.
REFERENCE_ARCHITECTURE · READBACK_VERIFY
DECISION RECORD / C.23
What this route helps you decide
Source-traceable reference · pp.50–51
Goal
Locate clause and field differences before a finance action, and make clear who confirms them and which version governs execution.
Risk / exception
Freeze invoicing or settlement when a supplemental agreement is unsigned, formal acceptance is missing or contract versions conflict. The Agent must not decide legal effect.
Close condition
Contract fields are locatable; cross-document differences are resolved; legal, business and finance approve the applicable version; finance receipts agree with the project balance.
Next safe action
Choose one project awaiting invoice and list the critical consistency fields across contract, change, acceptance and invoice.
KNOWLEDGE → COMPARISON → DIRECTION → OPTIMIZATION
Evidence stays attached to the decision.
The full-detail canonical evidence record remains available in Chinese. IDs, Truth classes, boundaries, and source references stay unchanged across languages.
Knowledge
Source-traceable reference
Comparison
Compare the same operating fields before choosing a direction.
Direction
Confirm the owner, authority, human gate, and readback rule.
Optimization
Define a baseline, target, owner, and observation window before claiming impact.