Meet the Authors

Key Takeaways What you need to know
  1. SAP pricing control often breaks below the executive layer, where condition records, CPQ workflows, sales exceptions, and order-to-cash processes shape realized margin.

  2. Zilliant research shows that inconsistent discounting, inconsistent governance, siloed decisions, and unauthorized overrides remain major causes of margin erosion.

  3. SAP customers can strengthen pricing governance by connecting executive accountability with workflow-level visibility across quoting, exceptions, discounts, orders, and invoices.

The execution gap in SAP pricing environments is visible in pricing decisions that degrade across condition records, CPQ workflows, sales exceptions, and order-to-cash execution.

Many companies have responded by pushing pricing accountability higher in the organization, assigning responsibility to the CFO, CRO, or CEO. Control, however, still breaks lower in the workflow. That is the challenge Zilliant’s Pricing Without Control research puts back on the table.

During the ‘Margin at Risk: 300 Executives Expose the Pricing Control Gap You’re Not Seeing’ webinar on May 27 at noon EDT, Zilliant Chief Technology Officer Russ Halvorson and Vice President of Marketing Adrian Chang will present the survey’s findings, and show how systems, governance, and execution problems influence the value of price changes.

Explore related questions

Pricing Accountability Breaks Below the Executive Layer

In most SAP environments, pricing governance is spread across the business. Master data teams maintain condition records. Pricing architects configure procedures. Sales operations manages exceptions and customer-specific agreements. Commercial teams negotiate the rates. Finance approves the strategy.

When pricing breaks, accountability moves upward. That mismatch explains why the problem persists. A CFO can tighten approval chains, ask for more reporting, or add governance checkpoints. Those steps may improve visibility, but they do not always reach the transactional layer where prices actually change.

A common pattern might start with a distributor approving a 4% list increase. The approved change then begins to erode across the workflow: a manual override at the quote stage, an exception for a strategic account, a condition record that is not updated in time, and a sales-edge discount that removes another point before the transaction reaches the order.

That is where margin leakage becomes hard to see. It accumulates across small decisions made in different systems, by different teams, under different commercial pressures. The CFO may still own the outcome, but the causes sit deeper in the workflow.

Like the example, Zilliant’s survey found that the causes of margin erosion — inconsistent discounting (34%), inconsistent governance (29%), siloed decision-making (27%), and unauthorized overrides (22%) — are execution failures.

More than 30% of executives responsible for pricing decisions reported feeling exhausted. That is what happens when a systems problem is treated as a leadership problem.

Pricing Control Needs to Reach the Workflow

The constructive takeaway is that pricing control has to extend across the full workflow where prices are created, adjusted, approved, and applied.

That matters because SAP customers are not starting from a blank slate. Many already run pricing through condition records, pricing procedures, customer-specific agreements, CPQ workflows, and downstream order-to-cash processes. Those capabilities remain essential, but the control challenge grows as price changes become more frequent and commercial exceptions become harder to govern.

A pricing decision only creates value if it survives that path. SAP teams need to know how a price change moves from strategy into a quote, how exceptions are approved, how customer-specific agreements are maintained, how discounting is monitored, and how the final price appears in the order or invoice. Control cannot stop at the policy level if the price changes again before it reaches the customer.

Zilliant’s webinar brings together product and market perspectives on pricing control. Halvorson oversees Pricing and CPQ as CTO, giving him visibility into the architecture behind pricing execution and the handoffs between pricing logic, quoting, and downstream workflows. Chang, as VP of Marketing, can connect those questions to the business pressures driving frequent price changes. Together, they can help SAP teams evaluate how pricing decisions hold, erode, or change as they move through enterprise systems.

SAP customers do not need to treat pricing control as a choice between software replacement or additional governance reviews. A connected model keeps SAP central to transaction execution while dedicated pricing capabilities help manage strategy, governance, optimization, and exception control across the commercial workflow.

The next step is making sure pricing control reaches the systems and teams that determine whether those decisions become realized margin.

What This Means for SAPinsiders

  • Pricing control needs workflow evidence. SAP teams need more than approval records to know whether pricing decisions are holding. They need visibility into how prices change across quotes, exceptions, condition records, discounts, orders, and invoices.
  • Executive ownership raises operational pressure. Moving accountability to the CFO, CRO, or CEO makes pricing a financial performance issue. It also increases the need for clearer handoffs between finance strategy, sales execution, pricing teams, and system maintenance.
  • Dedicated pricing tools can complement SAP. SAP-native pricing remains central to transaction execution. However, SAP customers may need connected pricing capabilities that strengthen governance, optimization, and exception control while SAP remains central to transaction execution

Events

04Jun
Mastering SAP Connect – Gold Coast 2026Gold Coast, QLD, Australia
View All