You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@fineract.apache.org by "Foo Developer (Jira)" <ji...@apache.org> on 2026/08/19 06:51:00 UTC

[jira] [Updated] (FINERACT-2767) Tax Component – Fields should be locked once linked to transactions

     [ https://issues.apache.org/jira/browse/FINERACT-2767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Foo Developer updated FINERACT-2767:
------------------------------------
    External issue URL: https://github.com/apache/fineract/pull/6288

> Tax Component – Fields should be locked once linked to transactions
> -------------------------------------------------------------------
>
>                 Key: FINERACT-2767
>                 URL: https://issues.apache.org/jira/browse/FINERACT-2767
>             Project: Apache Fineract
>          Issue Type: Bug
>          Components: User Management
>            Reporter: Foo Developer
>            Assignee: Foo Developer
>            Priority: Major
>              Labels: beginner, beginner-friendly
>
> If the Tax Component has not been used, all fields (Name, Percentage, GL Accounts, Dates) should be editable 
> If the Tax Component is linked to products/charges but no transactions exist, only the Name is typically editable
> If the Tax Component has been used in transactions, also only the Name should remain editable 
> fields such as:
> Percentage
> Debit/Credit GL Accounts
> Start Date
> should be locked to preserve accounting and audit integrity.
> Any ability to modify percentage or GL accounts after transactions exist may cause inconsistencies in historical calculations and journal entries



--
This message was sent by Atlassian Jira
(v8.20.10#820010)