Know where a workflow should stop

Define the narrow task and its permitted output. Preparing a review queue is different from changing an invoice or contacting a supplier.

Identify stop conditions before using real records: ambiguous matches, missing documents, conflicting quantities or an unknown approval owner.

Route fixed-price, warranty, disputed and unusual transactions to the appropriate person. Do not apply a general billing rule to every job.

Test with clearly fictional records and known outcomes. Confirm that missing or contradictory information produces a visible exception.

Keep human approval at the action boundary. Record decisions and changes, and establish who can pause the workflow if behavior is unexpected.