The controller at fictional Civic Workshop needs a traceable Operations repair and Project prototype cost. Done means required coding, two correctly dimensioned postings, and an exported Project analysis.
Civic Workshop's controller found that every expense has a dimension, yet the project report still looks wrong. Presence alone can't prove correct coding. The approved request separates an Operations repair from a Project prototype cost.
Set the master defaults and required account rule, then post the two source documents with their own dimensions. Preserve both entries when you run the analysis. The final question asks whether a master-card change can rewrite an earlier posted transaction. In a workplace tenant, use the supported correction controls and audit process. This local case demonstrates the distinction through the original entries and a checked decision.