SAP Vertex × Pricing
SAP Vertex and SAP Pricing: Condition Technique Meets Tax Determination
- SAP Pricing
- Condition technique
- Vertex
- Tax base
- Freight
SAP pricing — condition technique, access sequences, condition types, pricing procedure, account keys — decides list, discount, surcharge, freight, and net. Vertex decides tax. If the net Vertex sees is not the net legal wanted, every invoice is a dispute. MWST in the procedure is not Vertex. Leaving both in the procedure is how juniors double-tax. SR Soft LLC is a major player on this seam because we staff pricing consultants and Vertex specialists as a pair.
Statistical conditions that must or must not enter the Vertex base, header versus item freight, configurable products and variant pricing, rebates and condition contracts that reopen tax, manual overrides that tax will not forgive — these are the hard objects. We force a pricing-base workshop before Vertex configuration. Fortune 500 OTC programs that skip it buy a second project.
The workshop we refuse to skip
Tax, SD, and legal in one room. Every condition type: in base, out of base, statistical, or forbidden. Freight rules by incoterm. Variant configuration: which characteristic changes taxability. We leave with a signed matrix. Configuration starts after that, not before.
- 01
Inventory the procedure
Every type, every account key, every statistical flag.
- 02
Legal on the base
What the statute taxes. Not what the last project did.
- 03
Freight and kits
Header, item, BOM, configurable.
- 04
Manuals and rebates
What is allowed to change after Vertex has spoken.
- 05
Return path
Credit memo clones original base and jurisdiction.
Defects by root cause
Condition technique as tax law in disguise
Access sequences, exclusion indicators, condition class, calculation type, account keys, subtotals — every one of those can change the Vertex base. A statistical freight condition that still adds into the subtotal Vertex reads will tax freight you swore was exempt. Header freight distributed to items after determination will drift. Variant configuration that changes taxability mid-configuration will not be caught by a PR00 test. We inventory the procedure line by line with tax counsel in the room. Configuration starts after the matrix is signed.
MWST remaining in a Vertex procedure is how juniors double-tax. Manual overrides after Vertex has spoken are a policy, not a convenience. Rebates and condition contracts that reopen the invoice must reopen tax. We write those rules as test cases. S/4 condition contract settlement does not retire this workshop. It makes it more visible.
