ADR / 004

Separate commercial approval from financial validation

Two decisions with different owners, evidence and SLAs should not share one approval step—even when one form collects the data for both.

Reference pattern

Independently created. Contains no employer or client implementation detail, internal names or figures.

01Context

A commercial organization routes every new customer through a single ‘customer approval’. Sales managers approve terms they can judge—and tax data and credit exposure they cannot. Finance re-checks everything later, so the step neither protects Finance nor speeds up Sales.

02Decision drivers

  1. D01

    One accountable owner per decision

  2. D02

    Approvers see only evidence they can judge

  3. D03

    Rejections return to the stage that can fix them

  4. D04

    SLAs measurable per decision

03Options considered

Options considered: when each would be the right choice, what it costs, and the verdict under these premises
OptionRight whenCost / trade-offVerdict
One combined approvalSmall organizations where one role genuinely owns both decisionsApprovers sign for evidence outside their competenceRejected
Sequential, separate decisionsTerms must be settled before credit can be sizedLonger path unless each SLA has an ownerSelected
Parallel decisions, joint gateHigh volume where terms rarely change after validationRework when credit review changes the termsSituational

Every option is right under some premises. The verdict applies to the context above.

04Decision

Model commercial approval and financial validation as two decisions with separate owners, evidence, SLAs and return states. Commercial approval decides whether to commit on these terms; financial validation decides whether this legal entity can transact. A credit outcome that changes the terms returns to commercial approval—not to the start.

05Consequences

What this choice changes elsewhere in the system.

  1. Decision rights

    Sales managers stop approving tax and credit data they cannot assess.

  2. Exceptions

    Each rejection carries a reason code and returns to the stage that can fix it.

  3. Measurement

    Approval ageing and first-pass validation become separately measurable and separately owned.

  4. Business state

    CRM shows two distinct states instead of one ambiguous ‘pending approval’.

06Revisit when

The decision holds while its context holds. Challenge it when:

01

One role becomes accountable for both commercial and credit risk.

02

Credit exposure is pre-approved by segment, making validation deterministic.

07Where this decision is applied

The decision says why this path was chosen; each case shows how it takes part in a larger architecture.

  1. Process case / 01Designing the foundational lead-to-customer lifecycleAn operating foundation: what each state from lead to active customer means, who decides each transition and what happens on “no”—designed before any system is configured.Process ArchitectureSystems & CRM ArchitectureDigital Operating ModelArchitecture case · 20 min
  2. Operating Model & Process Design / 03Standardizing RFQ governance across commercial, technical, compliance and project decisionsTurning dispersed commercial, technical, compliance and project judgement on complex RFQs into one reproducible decision model: classification, required assessments, Go / No-Go, decision rights, clocks, escalation and a decision record.Process ArchitectureDigital Operating ModelRevenue OperationsArchitecture case · 11 min

Decisions this one depends on, or constrains.

  1. ADR / 001Make ERP customer creation asynchronousProtect the commercial workflow from ERP latency while making pending state and recovery explicit.Proposed patternIntegration · ERP · Resilience
  2. ADR / 015Name process, system, data and KPI ownership separately“Owner” is not one concept. Name the process owner, stage owners, decision owners, system owners, data owners and KPI owners separately—so the exception always has a name.Proposed patternOperating model · Ownership · Governance