Scenario:
Business requires a new charge/discount or tax category.
Action:
The user creates a TCD category by entering code, rounding logic, tax flag, and description.
Outcome:
The TCD category is created and available for configuration.
Scenario:
Each TCD must be uniquely identifiable.
Action:
The user assigns a unique and standardized code.
Outcome:
ERP ensures consistent TCD identification.
Scenario:
Charge or tax values require rounding rules.
Action:
The user selects the rounding method (e.g., nearest, up, down).
Outcome:
ERP applies rounding automatically during calculations.
Scenario:
Only specific TCDs should be treated as taxes.
Action:
The user marks the Is Tax flag accordingly.
Outcome:
ERP correctly handles tax and non‑tax TCDs in transactions.
Scenario:
Users need clarity on TCD usage.
Action:
The user enters a clear description.
Outcome:
Improved usability and reduced configuration errors.
Scenario:
TCD rules or descriptions change.
Action:
The user updates the TCD category details.
Outcome:
ERP reflects updated configuration for future transactions.
Scenario:
Charges, discounts, or taxes are applied during billing or procurement.
Action:
The user selects the relevant TCD category.
Outcome:
ERP calculates amounts consistently.
Scenario:
TCD values affect accounting entries.
Action:
ERP applies posting rules based on TCD configuration.
Outcome:
Accurate financial and tax postings.
Scenario:
Audit requires traceability of master changes.
Action:
ERP logs all create, update, and deactivate actions.
Outcome:
System remains audit‑ready and compliant.