Part 022 — Margin Visibility, Commercial Guardrails, Exceptions, and Approval Policy

Positioning

Pricing menjawab:

Berapa harga komersial yang ditawarkan?

Profitability menjawab:

Apakah harga tersebut menghasilkan outcome ekonomi yang dapat diterima?

Approval menjawab:

Siapa yang berwenang menerima exception terhadap policy?

Ketiganya berhubungan, tetapi tidak boleh dicampur menjadi satu opaque calculation.

Core thesis: price calculation, cost/profitability analysis, dan commercial approval adalah responsibility yang berbeda. Approval engine tidak boleh menjadi pricing engine, dan pricing engine tidak boleh menyembunyikan authorization decisions.

1. Price versus Cost

Price

Amount charged or offered to customer.

Cost

Expected internal economic cost to deliver the product or service.

Price is customer-facing.

Cost is usually confidential.

2. Revenue

Revenue is recognized or expected economic inflow.

Quoted price is not automatically recognized revenue.

3. Profit

Simplified:

profit = revenue - cost

Real enterprise profitability may include:

• one-time costs;
• recurring costs;
• usage costs;
• support;
• implementation;
• risk;
• partner payment;
• and time value.

4. Margin

Common forms:

Gross Margin Amount

price - cost

Gross Margin Percentage

(price - cost) / price × 100%

Markup Percentage

(price - cost) / cost × 100%

Margin and markup are not interchangeable.

5. Contribution Margin

May subtract variable costs but not all allocated fixed costs.

Define local semantics.

6. Net Margin

May include broader costs, fees, or allocations.

Do not use unqualified margin.

7. Profitability Model

A profitability model should define:

• revenue basis;
• cost basis;
• time horizon;
• currency;
• allocation;
• risk;
• and version.

8. Profitability Horizon

Possible horizons:

• first month;
• first year;
• contract term;
• customer lifetime;
• or project delivery.

9. One-Time and Recurring Economics

A deal may have:

• high one-time cost;
• low installation charge;
• profitable recurring term.

Analyze across appropriate horizon.

10. Usage Economics

Usage price and variable cost may change margin by actual consumption.

Quoted profitability may require assumptions.

11. Cost Definition

A Cost Definition describes expected cost logic.

Possible types:

• fixed;
• per unit;
• recurring;
• usage;
• partner;
• implementation;
• risk reserve;
• and support.

12. Calculated Cost

Transaction-specific expected cost result.

13. Actual Cost

Observed cost after fulfillment/operation.

Expected and actual cost must be distinguished.

14. Standard Cost

A centrally maintained expected cost.

15. Contracted Supplier Cost

Cost from external partner agreement.

16. Estimated Cost

A preliminary estimate with confidence and validity.

17. Detailed Cost

A later design/fulfillment estimate with higher fidelity.

18. Cost Source

Possible authoritative sources:

• product finance;
• procurement;
• supplier contract;
• cost catalog;
• network planning;
• fulfillment estimate;
• and manual specialist input.

19. Cost Ownership

For each cost input, identify:

• semantic owner;
• write owner;
• validity;
• and correction process.

20. Cost Provenance

Store:

• source ID/version;
• calculation rule;
• time;
• scope;
• currency;
• and confidence.

21. Cost Confidentiality

Cost is usually sensitive.

Do not expose through:

• customer APIs;
• proposal documents;
• generic logs;
• broad events;
• or unauthorized support views.

22. Cost Currency

Cost may use different currency from price.

Profitability requires explicit conversion.

23. Cost Exchange Rate

Use defined rate source and effective date.

24. Cost Period

Recurring cost must have period.

25. Cost Quantity

Cost rate must have unit and quantity.

26. Cost Allocation

Shared costs may be allocated across:

• products;
• sites;
• customers;
• or contract periods.

27. Allocation Policy

Possible methods:

• equal;
• proportional revenue;
• proportional usage;
• capacity;
• direct assignment;
• and activity-based.

28. Cost Allocation Remainder

Use deterministic handling.

29. Cost Uncertainty

Estimated cost can include:

• range;
• confidence;
• risk reserve;
• and assumptions.

30. Confidence Level

Possible:

• indicative;
• estimated;
• validated;
• contracted;
• actual.

31. Cost Validity

Cost can become stale when:

• supplier rate changes;
• design changes;
• site changes;
• capacity changes;
• or time passes.

32. Re-Costing Trigger

Examples:

• product configuration;
• quantity;
• site;
• delivery method;
• vendor;
• term;
• and exchange rate changes.

33. Cost Snapshot

Profitability analysis should preserve the cost inputs used.

34. Margin Snapshot

A margin result should reference:

• price snapshot;
• cost snapshot;
• conversion;
• allocation;
• formula;
• and policy version.

35. Profitability Snapshot

May include:

revenue schedule
cost schedule
gross margin
margin percentage
cash-flow estimate
payback period
risk-adjusted result

36. Profitability Is Not Customer Price

A price can remain unchanged while profitability changes because cost changed.

37. Price Change Is Not Always Needed

If margin worsens but remains above guardrail, customer price may remain valid.

38. Cost Change after Approval

This can:

• invalidate approval;
• trigger reanalysis;
• or remain accepted under approval conditions.

Policy must be explicit.

39. Cost Change after Acceptance

The accepted customer price should not automatically change.

The provider may:

• absorb cost change;
• seek amendment;
• change realization;
• or trigger internal exception.

40. Commercial Guardrail

A guardrail defines acceptable economic boundaries.

Examples:

• minimum margin percentage;
• minimum margin amount;
• maximum discount;
• maximum payback period;
• minimum contract value;
• and risk limit.

41. Target versus Floor

Target

Preferred result.

Floor

Minimum acceptable result without exceptional authority.

42. Warning Threshold

Below target but above floor may produce warning.

43. Blocking Threshold

Below hard floor may block unless overrideable by policy.

44. Absolute versus Relative Threshold

Examples:

• margin amount >= 1000;
• margin percentage >= 20%.

Both may be needed.

45. Product-Specific Guardrail

Different products may have different economics.

46. Market-Specific Guardrail

Market cost and strategy may differ.

47. Channel-Specific Guardrail

Partner channels may use different margin model.

48. Customer-Specific Guardrail

Strategic customer policy may permit lower margin.

Use explicit policy, not hard-coded customer ID.

49. Term-Specific Guardrail

Longer contracts may accept lower monthly margin due to lifetime value.

50. Portfolio Guardrail

A low-margin component may be acceptable within profitable bundle or account.

51. Item-Level Margin

Useful to identify loss-leading items.

52. Bundle-Level Margin

Captures packaged economics.

53. Quote-Level Margin

Evaluates overall deal.

54. Account-Level Profitability

Can include existing portfolio and future value.

This may belong outside quote domain.

55. Guardrail Scope

Every rule must identify:

• item;
• bundle;
• quote;
• account;
• contract;
• or market scope.

56. Guardrail Result

Possible results:

• PASS;
• WARNING;
• APPROVAL_REQUIRED;
• BLOCKED;
• INDETERMINATE.

57. Indeterminate Profitability

Use when:

• cost missing;
• exchange rate unavailable;
• or confidence too low.

Do not assume zero cost.

58. Missing Cost Policy

Possible:

• block quote;
• use standard cost with warning;
• manual estimate;
• or approval required.

59. Zero Cost

Zero is a valid cost only when intentional.

Do not use zero for missing.

60. Negative Cost

May represent rebate or subsidy.

Require explicit semantics.

61. Approval

Approval is an authorized commercial decision on an exception or commitment.

62. Approval Request

Contains:

• subject;
• policy violation;
• evidence;
• requested exception;
• scope;
• quote revision;
• and required authority.

63. Approval Decision

An immutable fact:

• approved;
• rejected;
• conditionally approved;
• expired;
• or withdrawn.

64. Approval Is Not Workflow Status Only

Approval needs:

• authority;
• reason;
• evidence;
• conditions;
• and audit.

65. Commercial Exception

Examples:

• margin below floor;
• discount above threshold;
• non-standard term;
• price override;
• waived fee;
• delayed payment;
• and unsupported liability condition.

66. Exception Type

Use stable taxonomy.

Examples:

• LOW_MARGIN;
• HIGH_DISCOUNT;
• COST_UNCERTAIN;
• NON_STANDARD_TERM;
• PRICE_BELOW_FLOOR;
• MANUAL_NET_PRICE;
• SPECIAL_CREDIT_TERM.

67. Exception Severity

Possible:

• minor;
• material;
• major;
• and executive.

68. Authority Level

Approval authority may depend on:

• exception type;
• threshold;
• amount;
• margin;
• product;
• market;
• and customer.

69. Approval Matrix

Example:

This is illustrative only.

70. Multi-Dimensional Matrix

Real policies may consider:

• margin percentage;
• total contract value;
• term;
• risk;
• and strategic account.

71. Decision Table

A decision table is often clearer than nested conditionals.

72. Authority Policy Version

Approval route should reference policy version.

73. Approver Identity

Record:

• user/party;
• role;
• authority scope;
• and delegation.

74. Separation of Duties

Requester should not approve own exception unless explicit emergency policy allows.

75. Delegated Authority

Delegation needs:

• delegator;
• delegate;
• scope;
• start/end;
• limit;
• and audit.

76. Temporary Delegation

Use for leave or operational coverage.

Avoid permanent elevated role.

77. Approval Group

A group may represent authority pool.

Need assignment and quorum rules.

78. Sequential Approval

Approval stages happen in order.

Example:

• manager;
• finance;
• legal.

79. Parallel Approval

Independent authorities decide concurrently.

80. Any-One Approval

Any qualified approver can decide.

81. All-Required Approval

Every required domain must approve.

82. Quorum Approval

A minimum number or combination is required.

83. Conditional Approval

Example:

Approved if contract term remains at least 36 months and implementation fee is not waived.

84. Approval Condition Model

Conditions should be machine-readable where possible.

85. Approval Condition Validation

Before transition, verify all conditions still hold.

86. Approval Scope

Can apply to:

• one adjustment;
• one item;
• one quote revision;
• one customer/account;
• or one defined condition set.

87. Revision-Bound Approval

A decision should usually reference exact quote revision and price snapshot.

88. Component-Bound Approval

A discount exception may target one component only.

89. Reusable Approval

Some authority may approve a reusable exception for a time period.

This is a policy/entitlement, not a quote decision.

90. Approval Validity

Approval can expire by:

• time;
• quote revision;
• input change;
• authority expiry;
• or cost validity.

91. Reapproval Trigger

Possible triggers:

• price changed;
• discount changed;
• quantity changed;
• term changed;
• product changed;
• cost changed;
• margin changed;
• or condition no longer holds.

92. Materiality Tolerance

Minor rounding change may not require reapproval.

Define tolerance explicitly.

93. Reapproval Decision

Do not infer from generic updated_at.

Use semantic diff.

94. Approval Withdrawal

Requester or policy may withdraw request before decision.

95. Approval Cancellation

If quote revision is superseded, old request becomes obsolete.

96. Approval Expiry

Expired approval is distinct from rejection.

97. Approval Escalation

Escalate when:

• SLA exceeded;
• authority unavailable;
• or severity increases.

98. Escalation Is Not Approval

Escalation routes responsibility.

It does not imply acceptance.

99. Approval SLA

Track:

• time to assignment;
• time to decision;
• and queue age.

100. Approval Priority

May depend on:

• customer deadline;
• deal value;
• and exception severity.

Avoid allowing commercial urgency to bypass controls silently.

101. Approval Evidence

Possible evidence:

• price snapshot;
• cost snapshot;
• margin calculation;
• discount breakdown;
• contract terms;
• risk analysis;
• and reason.

102. Evidence Immutability

Approver must decide on stable evidence.

If evidence changes, decision may be invalidated.

103. Evidence Checksum

Can bind approval to exact snapshot.

104. Approval Explanation

Approver should understand:

What exception?
How far from policy?
What is the economic impact?
What assumptions exist?
What alternatives are available?

105. Approval Alternatives

System may suggest:

• increase term;
• reduce discount;
• add setup fee;
• remove costly option;
• or choose alternate realization.

106. Approval Recommendation

An automated recommendation can support but not impersonate authority unless policy explicitly delegates decision to automation.

107. Automated Approval

Suitable for low-risk deterministic policies.

Need:

• policy owner;
• audit;
• version;
• and override.

108. Human Approval

Needed for:

• judgment;
• strategic exception;
• high risk;
• and incomplete evidence.

109. Human-in-the-Loop

Automation routes and summarizes; human decides.

110. Approval and Pricing Boundary

Pricing produces:

• price;
• adjustment;
• and maybe policy signals.

Approval decides whether exception is authorized.

111. Approval and Margin Boundary

Profitability calculates economic result.

Approval evaluates policy and authority.

112. Approval and Quote Boundary

Quote owns lifecycle and references decisions.

Approval may be separate bounded context.

113. Approval and Agreement Boundary

Some non-standard terms may require legal approval independent of commercial margin approval.

114. Approval and Order Boundary

Order conversion should verify required approvals are valid for accepted revision.

115. Approval and Billing Boundary

Billing should not independently reinterpret commercial approval.

It consumes accepted monetary instruction.

116. Margin Visibility

Different roles need different views.

117. Sales View

May show:

• margin band;
• warning;
• and approval requirement

without detailed cost.

118. Manager View

May show:

• margin percentage;
• cost category;
• and exception reason.

119. Finance View

May show detailed profitability and cost assumptions.

120. Customer View

Should not expose internal margin or cost.

121. Support View

May need:

• approval status;
• reason category;
• and decision timeline

without confidential cost.

122. Field-Level Authorization

Protect:

• cost;
• margin;
• internal floor;
• target;
• and approval commentary.

123. Data Minimization

Events and logs should contain only necessary profitability data.

124. Encryption

Sensitive commercial data may require:

• encryption at rest;
• encryption in transit;
• and restricted backups.

125. Audit Access

Viewing confidential cost may itself need audit.

126. Tenant Isolation

Cost/margin data must be isolated across tenants and customer environments.

127. On-Prem Considerations

Customer-operated deployment may have different:

• cost sources;
• authority directory;
• and data-residency policy.

Keep extension boundaries explicit.

128. Profitability State

Possible states:

• NOT_CALCULATED;
• INDICATIVE;
• COMPLETE;
• STALE;
• BELOW_TARGET;
• BELOW_FLOOR;
• APPROVED_EXCEPTION;
• SUPERSEDED.

129. Cost Staleness

Profitability can become stale independently of price.

130. Margin Staleness

Triggered by:

• price change;
• cost change;
• currency change;
• quantity;
• or term.

131. Reanalysis

Explicit operation recalculates profitability using selected price snapshot and current/target cost context.

132. Price Lock with Cost Change

Price remains locked, but profitability can deteriorate.

This should produce internal risk or reapproval, not customer price mutation.

133. Approval Snapshot

Store:

• quote revision;
• price snapshot;
• cost snapshot;
• margin result;
• policy version;
• and decision.

134. Approval Event

Representative events:

• CommercialApprovalRequested;
• ApprovalAssigned;
• CommercialExceptionApproved;
• CommercialExceptionRejected;
• ApprovalExpired;
• ReapprovalRequired.

Names require internal verification.

135. Event Payload Security

Do not broadcast detailed cost/margin broadly.

Use:

• IDs;
• decision;
• scope;
• and restricted lookup.

136. Approval API

Possible commands:

• RequestApproval;
• ApproveException;
• RejectException;
• WithdrawApproval;
• DelegateAuthority;
• EscalateApproval.

137. Decision Command

Should include:

• request ID;
• expected version;
• decision;
• reason;
• conditions;
• authority;
• and idempotency key.

138. Approval Idempotency

Repeated decision command must not create conflicting decisions.

139. Approval Concurrency

Two approvers may act concurrently.

Use request version and terminal-decision policy.

140. Conflicting Decision

If one approves and another rejects, policy must define:

• first terminal wins;
• all-required semantics;
• quorum;
• or escalation.

141. Approval Workflow State

Possible:

• DRAFT;
• REQUESTED;
• ASSIGNED;
• IN_REVIEW;
• NEEDS_INFORMATION;
• APPROVED;
• REJECTED;
• EXPIRED;
• WITHDRAWN;
• SUPERSEDED.

142. Needs Information

Approver requests additional evidence.

Quote may remain pending.

143. Request Revision

If evidence changes, create new request version rather than mutate decided evidence.

144. Approval History

Record:

• assignments;
• comments;
• decisions;
• escalations;
• and delegations.

145. Comments

Comments can contain sensitive data.

Apply retention and access controls.

146. Approval Document

For major deals, generate an approval package.

It should reference exact snapshots.

147. Approval Search

Users may search by:

• queue;
• age;
• authority;
• market;
• deal;
• and exception type.

148. Approval Dashboard

Useful metrics:

• pending count;
• age;
• threshold;
• rejection rate;
• reapproval rate;
• and bottleneck.

149. Profitability Metrics

• target attainment;
• floor breach;
• margin distribution;
• cost uncertainty;
• and actual-versus-expected margin.

150. Commercial Governance Metrics

• exception rate;
• approval latency;
• override frequency;
• and delegated-authority usage.

151. Gaming Risk

Metrics can incentivize:

• hiding cost;
• splitting discounts;
• manipulating quantity;
• or delaying updates.

Use controls and audits.

152. Threshold Evasion

Example:

• split one 20% discount into two 10% adjustments.

Guardrails should evaluate cumulative effect.

153. Quote Splitting

Splitting deal into multiple quotes can evade approval threshold.

Policy may need account/opportunity-level aggregation.

154. Cost Manipulation

Manual cost override should require authority and audit.

155. Margin Model Drift

Different services or spreadsheets may calculate margin differently.

Establish authoritative formula and version.

156. Spreadsheet Shadow Process

If approval relies on spreadsheet outside system:

• evidence can diverge;
• audit weakens;
• and automation cannot validate.

Integrate or explicitly govern the handoff.

157. Profitability Replay

Given price and cost snapshots, reproduce margin result.

158. Actual-versus-Expected Profitability

After fulfillment, compare:

• quoted expected cost;
• actual cost;
• expected revenue;
• and actual revenue.

159. Feedback Loop

Use outcome to improve:

• cost model;
• guardrails;
• and pricing assumptions.

Do not retroactively alter historical approval.

160. Margin Reconciliation

Compare:

quoted profitability
-> approved exception
-> ordered economics
-> actual fulfillment cost
-> billed revenue

161. Approval Reconciliation

Verify:

• required approvals existed;
• conditions held;
• and accepted revision matched evidence.

162. Missing Approval

If order created without required approval:

• stop or contain downstream progression;
• create incident;
• identify scope;
• and audit.

163. Expired Approval

Order conversion should reject or require reapproval according to policy.

164. Condition Violation

If condition no longer holds:

• mark approval invalid;
• block transition;
• and explain.

165. Approval Incident

Examples:

• requester self-approves;
• cost hidden as zero;
• old approval reused after repricing;
• delegation exceeds limit;
• and confidential margin leaks to customer.

166. Incident Containment

Possible actions:

• disable affected authority;
• block quote acceptance/order conversion;
• invalidate approvals;
• identify affected deals;
• and preserve evidence.

167. Commercial Policy Rollout

Use:

• versioned policy;
• simulation;
• shadow evaluation;
• canary market;
• and rollback.

168. Policy Simulation

Evaluate historical/current quotes under candidate guardrail policy.

169. Policy Drift Analysis

Compare:

• current decisions;
• candidate thresholds;
• and expected approval volume.

170. Approval Capacity Planning

A stricter policy can overwhelm approval queues.

Evaluate operational impact.

171. Approval SLI

Examples:

• 90% low-risk approvals decided within business SLA;
• zero unauthorized approvals;
• zero order conversions with missing mandatory approval.

Targets must be internal.

172. Stuck Approval

Detect when:

• queue age exceeds SLA;
• no active approver;
• authority expired;
• or evidence missing.

173. Escalation Automation

Escalate without changing decision semantics.

174. Reminder Noise

Avoid excessive notifications.

Use role/priority-aware reminders.

175. Margin Smells

• margin and markup confused;
• one cost field;
• zero means missing;
• and no cost version.

176. Approval Smells

• approval is boolean;
• no policy version;
• no evidence snapshot;
• not tied to quote revision;
• and comments are the only reason.

177. Authority Smells

• global admin approves everything;
• delegation never expires;
• user role equals authority without scope;
• and no separation of duties.

178. Visibility Smells

• cost returned in generic quote API;
• logs contain margin;
• customer proposal exposes internal floor;
• and support access is unrestricted.

179. Anti-Patterns

Pricing Engine Approves Its Own Exception

Decision and authorization conflated.

Margin as UI Calculation

Server-side authority missing.

Approval Reused across Repricing

Evidence no longer matches.

Cost as Zero when Unknown

Profitability overstated.

Thresholds in Code and Spreadsheet

Policy drift.

Approval Comment as Policy

No machine-readable decision.

180. Cost Snapshot Template

## Cost Snapshot Identity

## Quote / Revision

## Cost Components

For each:
- Cost type
- Amount/currency
- Quantity/unit
- Period
- Source/version
- Confidence
- Validity

## Allocation

## Exchange Rates

## Assumptions

## Checksum

## Audit

181. Profitability Result Template

## Result Identity

## Price Snapshot

## Cost Snapshot

## Formula / Policy Version

## Time Horizon

## Revenue

## Cost

## Margin Amount

## Margin Percentage

## Markup

## Guardrail Results

## Confidence / Assumptions

## Validity

182. Commercial Guardrail Template

Guardrail ID/version:
Scope:
Metric:
Target:
Warning threshold:
Floor:
Currency/time horizon:
Overrideable:
Required authority:
Effective period:
Owner:

183. Approval Request Template

## Request Identity and Version

## Quote / Revision

## Exception Type

## Requested Change

## Price Snapshot

## Cost Snapshot

## Profitability Result

## Policy / Threshold

## Required Authority

## Requester and Reason

## Evidence

## SLA / Priority

## Status

184. Approval Decision Template

Request:
Decision:
Approver:
Authority role/scope:
Delegation:
Reason code:
Explanation:
Conditions:
Decided at:
Valid until:
Evidence checksum:
Policy version:

185. Reapproval Matrix Template

186. Profitability Invariants

Representative invariants:

• margin formula is versioned;
• price and cost currencies are reconciled;
• missing cost is not zero;
• approval references exact quote revision and snapshots;
• requester authority is checked;
• conditional approval is revalidated;
• and customer-facing contracts never expose confidential margin.

187. Worked Example: Margin versus Markup

Price:

Cost:

Margin:

(100 - 80) / 100 = 20%

Markup:

(100 - 80) / 80 = 25%

Using the wrong denominator changes approval outcome.

188. Worked Example: One-Time Loss, Recurring Profit

Installation cost:

Installation charge:

Recurring margin:

• 100/month.

24-month profitability may be positive despite initial loss.

Guardrail must use correct horizon.

189. Worked Example: Missing Cost

Partner cost service unavailable.

Correct result:

• profitability INDETERMINATE;
• quote may require manual estimate or block.

Incorrect:

• cost = 0.

190. Worked Example: Margin Floor

Target:

• 30%.

Floor:

• 20%.

Calculated margin:

• 24%.

Result:

• below target;
• manager approval required;
• not automatically blocked.

191. Worked Example: Negative Margin

Price:

Expected cost:

Result:

• -10% margin.

Policy may block or require executive authority.

192. Worked Example: Cost Change after Approval

Approved margin:

• 22%.

Supplier cost increases.

New margin:

• 17%.

System:

• marks profitability stale;
• evaluates reapproval policy;
• does not mutate customer price automatically.

193. Worked Example: Conditional Approval

Approved if:

• term = 36 months;
• setup fee retained.

Sales changes term to 24 months.

Approval becomes invalid.

194. Worked Example: Delegation

Commercial Director delegates approval up to a defined threshold for one week.

Decision checks:

• time;
• market;
• exception type;
• and value limit.

195. Worked Example: Quote Split

Two quotes each below approval threshold belong to one opportunity.

Portfolio/opportunity-level guardrail detects aggregate exception.

196. Worked Example: Approval Race

Two approvers act on same request.

Optimistic version and workflow semantics determine whether:

• first terminal decision wins;
• or both are required.

197. Worked Example: Accepted Quote, Cost Spike

Customer accepted price.

Actual realization cost rises.

Internal response may include:

• alternate fulfillment;
• exception;
• or margin impact.

The accepted price is not silently repriced.

198. Senior Engineer Operating Model

Define profitability vocabulary

Margin, markup, contribution, and horizon.

Identify cost authority

Do not assume pricing service owns cost.

Preserve cost and margin provenance

Version, confidence, and validity.

Separate calculation from decision

Profitability computes; approval authorizes.

Model guardrails explicitly

Target, warning, floor, and scope.

Bind approval to evidence

Exact revision, price, cost, and policy.

Enforce separation of duties

Including delegated authority.

Protect sensitive data

Field-level access and secure events.

Design reapproval triggers

Semantic diff, not timestamp.

Operate approval flow

SLIs, stuck queues, incidents, and reconciliation.

199. Internal Verification Checklist

Cost and profitability

• Which system owns cost inputs?
• Are expected, standard, contracted, and actual costs distinguished?
• What formulas and time horizons are used?
• Are cost confidence and validity modeled?

Guardrails

• What targets, warnings, and floors exist?
• Are they item-, quote-, account-, product-, market-, or channel-scoped?
• Are cumulative discounts and quote splitting considered?
• Which rules are hard versus overrideable?

Approval authority

• What approval matrix exists?
• How are roles, limits, and scope represented?
• Is delegated authority supported and expiring?
• Is separation of duties enforced?

Evidence and lifecycle

• Does approval bind to quote revision, price snapshot, cost snapshot, and policy version?
• What changes trigger reapproval?
• Are conditional approvals machine-checkable?
• What happens when cost changes after approval or acceptance?

Visibility and security

• Which roles can see cost, margin, floor, and comments?
• Are APIs/events/logs field-restricted?
• Is access to sensitive data audited?
• Are on-prem/customer-specific policies isolated?

Operations

• Are approval queues and SLAs observable?
• Can profitability be replayed?
• Are actual-versus-expected outcomes reconciled?
• Can missing/expired approvals block order conversion?

200. Practical Exercises

Exercise 1 — Formula audit

Find every definition of margin and markup and reconcile them.

Exercise 2 — Cost-source map

Map source, version, confidence, and validity for each cost component.

Exercise 3 — Guardrail matrix

Define target, warning, floor, authority, and scope.

Exercise 4 — Reapproval analysis

Map price, cost, quantity, term, and configuration changes.

Exercise 5 — Security design

Create role-based views for sales, approver, finance, support, and customer.

Exercise 6 — Outcome feedback

Design expected-versus-actual profitability reconciliation.

201. Part Completion Checklist

You are done if you can:

• distinguish price, cost, revenue, profit, margin, and markup;
• define profitability horizon;
• model cost provenance, confidence, and validity;
• calculate item/bundle/quote profitability;
• define target, warning, and floor guardrails;
• design exception taxonomy and approval matrix;
• enforce delegated authority and separation of duties;
• bind approval to immutable evidence;
• define reapproval triggers;
• protect sensitive cost and margin data;
• and create an internal commercial-approval verification backlog.

202. Key Takeaways

1. Price, cost, profitability, and approval are separate responsibilities.
2. Margin and markup use different denominators.
3. Profitability needs a time horizon.
4. Missing cost is not zero.
5. Cost and margin results need provenance and validity.
6. Guardrails require scope, target, warning, and floor.
7. Approval is an immutable authorized decision.
8. Approval must bind to exact evidence and revision.
9. Cost change can invalidate approval without changing accepted customer price.
10. Internal CSG cost, margin, and authority policies must be verified.

203. References

Conceptual baseline:

• General enterprise profitability, gross-margin, contribution-margin, and commercial-governance practices.
• CPQ discount, price-floor, exception, delegation, and approval-policy patterns.
• Domain-Driven Design separation of calculation, policy, authorization, and workflow.
• Security, field-level authorization, audit, and immutable evidence practices.

These references do not define internal CSG cost sources, margin formulas, approval thresholds, or authority structures.