Scenario:
Customer or Supplier requires specific tax configuration.
Action:
The user creates a TCD Group with required tax details.
Outcome:
TCD Group is available for transactional use.
Scenario:
Each tax group must be uniquely identifiable.
Action:
The user assigns a unique code.
Outcome:
ERP ensures structured tax group identification.
Scenario:
Correct tax structure must be applied.
Action:
The user selects the applicable tax group.
Outcome:
ERP applies accurate tax calculations.
Scenario:
Users need clarity on tax setup purpose.
Action:
The user enters a meaningful description.
Outcome:
Improved usability and reduced errors.
Scenario:
Tax applicability varies by state/location.
Action:
The user selects the applicable location.
Outcome:
ERP enforces location‑based tax rules.
Scenario:
Different parties have different tax applicability.
Action:
The user maps the TCD group to a party.
Outcome:
ERP applies party‑specific tax rules.
Scenario:
Tax applicability depends on customer category.
Action:
The user selects the relevant category.
Outcome:
ERP validates taxes accordingly.
Scenario:
GST calculation requires HSN/SAC.
Action:
The user enters the HSN number.
Outcome:
ERP calculates GST accurately.
Scenario:
GST type determines tax treatment.
Action:
The user selects GST tax group type.
Outcome:
ERP applies correct GST logic.
Scenario:
Tax amounts must post to correct ledgers.
Action:
The user maps the basic account.
Outcome:
ERP ensures correct accounting postings.
Scenario:
Tax rules or party details change.
Action:
The user updates the TCD Group.
Outcome:
Changes apply to future transactions only.
Scenario:
Taxes must auto‑apply during billing.
Action:
ERP fetches TCD Group during transaction entry.
Outcome:
Accurate tax calculation and posting.
Scenario:
Audit requires traceability of tax changes.
Action:
ERP logs all TCD Group changes.
Outcome:
System remains audit‑ready and compliant.