Book a live walkthrough
Before a tax, legal or statutory changeC16 first.
Use Case · SAP tax, GST and e-invoicing changes

The tax rule changed. Do you know every place your SAP still applies the old one?

Your SAP runs on rules. Every rule needs an expert to find it, keep it right and change it safely. A new tax rate, a GST change or an e-invoicing mandate touches rules set up years ago. With C16 first, your people get the rule, the gap and the design in hours, and your experts approve every step.

SAP Partner Listed on SAP Store PEOL is ISO 27001 certified SOC 2 Type II compliant

Why every rule change waits for an expert

The value of SAP isn't its code. It's the rules your company has built into it over years: tax, approvals, payments, pricing, close. Some live in configuration, many live in custom code nobody documented. Every change needs an expert to find the rule, see the gap, design the change, build it, test it and write it down. That expert time is the bottleneck, and a tax deadline does not wait for it.

Where tax rules hide in SAP

A tax change is rarely one setting. The old rule usually sits in several places at once.

Tax codes and tax setup

The tax procedure, tax codes and how tax is determined in purchasing and sales. A new rate or a new tax type starts here.

Custom code

Enhancements and billing logic written years ago, sometimes with a rate or a rule hard-coded inside. Nobody remembers it until an invoice comes out wrong.

Invoice forms

The legal invoice forms and documents that print tax fields. When a statutory field changes, every form that has to carry it must change too.

E-invoicing settings

The settings behind your e-invoicing process. A new mandate or a new format means checking what is set up today against what is now required.

Six steps, your experts approve each one

The same order for every rule change, tax first.

  1. Find the rule. C16 maps how tax is set up today: tax codes, how tax is determined, the custom code and the forms that use it.
  2. See the gap. C16 compares that setup with the new requirement and lists what is missing or wrong: codes, determination, form fields, rates hard-coded in code. Your advisers confirm what the rule should be.
  3. Design the change. C16 drafts the configuration and code changes, with the reason for each, for your experts to review.
  4. Build in development. On request, the change is built in development and approved by your experts. It then moves forward through your own change process.
  5. Test. C16 writes test cases for each tax scenario, so your team can check the change before it goes anywhere near a live invoice.
  6. Document. C16 records the rule and the change, so the next change starts from what is known, not from memory.

Ten rule areas, one way of working

Tax is the most urgent. The same six steps apply wherever your SAP holds a rule.

01

Tax and e-invoicing

Tax rules change every year. Find every place your SAP applies the old one, before the deadline.

02

New company, plant or sales org

A new plant inherits years of rules. Know which ones you are copying.

03

Who can approve what

Approval limits are rules in your SAP. Know them before the next reorg changes them.

04

Payment and bank rules

A new bank or file format touches rules set up years ago. Find them first.

05

Pricing and rebates

Every new discount sits on top of old ones. See the whole stack before you add another.

06

Invoice tolerances

Invoice tolerances decide what gets paid without a question. Know what yours allow.

07

Credit rules

Credit rules decide which orders stop. Check them when the policy changes.

08

Legal output and forms

When a statutory field changes, find every form that has to carry it.

09

Rules hidden in code

Many of your rules live in custom code nobody documented. Find them before you change anything.

10

Access rules

Access rules decide who can do what. Find the conflicts before the audit does.

Never writes to production. Never changes business data. Code only when you ask, in development, approved by your experts.

Your advisers decide the rule. Your tax, legal and audit advisers decide what the rule should be. C16 finds where and how your SAP applies it, so your experts can change it safely and spend their time on the decisions only they can make.

Frequently asked questions

How does C16 help with a tax, GST or e-invoicing change in SAP?+
C16 finds every place your SAP applies the current tax rule: tax codes and tax setup, custom code, invoice forms and e-invoicing settings. It compares that with the new requirement, lists the gap and drafts the change with the reason for each item. Your experts approve every step.
Does C16 decide what the new tax rule should be?+
No. Your tax, legal and audit advisers decide what the rule should be. C16 finds where and how your SAP applies it, so your experts can change it safely.
Does C16 change our SAP system?+
C16 never writes to production and never changes your business data. When you ask for a change to be built, it is built in your development system, your experts approve it, and it moves forward through your own change process.
Which rule changes besides tax can C16 help with?+
Ten rule areas: tax and e-invoicing; new company, plant or sales org; who can approve what; payment and bank rules; pricing and rebates; invoice tolerances; credit rules; legal output and forms; rules hidden in code; and access rules.
Does it work on SAP ECC and S/4HANA?+
Yes. C16 works with SAP ECC 6.0 (EHP7 and above) and all S/4HANA releases, using standard interfaces and the permissions you grant.
Before a tax, legal or statutory changeC16 first.

See it on a real SAP system

20 minutes. Bring your next tax or rule change. A live walkthrough, no slides.

Book a walkthrough View on SAP Store

Related: SAP AMS · S/4HANA migration · SAP as-is documentation · Security and governance · All solutions