Allow currency field to be changed if source record unposted
Accounting Seed has made it so that you are unable to change the currency field on a source record (Billings, Payables, Journal Entries, etc) once it has been set. Having discussed this with your Support Team, this was put in place to b/c subordinate child lines (i.e. Billings Lines, Payable Lines, Journal Entry Lines, etc.) did not have their currency fields updated to match the currency on the header.
This was the wrong approach by AcctSeed and demonstrates a fundamental lack of understanding of how users work and that users are not perfect 100% of the time. A user can choose to set the currency when creating the source record header, however, many users may forget and the currency will default accordingly. A user may not realize his/her mistake until they've gotten far into the process and created many child lines. As a result of AcctSeed's approach, they've introduced a new friction point for users where they now have to completely redo their work instead of just being able to update the header currency field. A common complaint is that AS introduces too many clicks and too many friction points in a user's workflow. This creates another one.
I agree that currencies on child lines should agree to parent headers. I also agree that the currency fields should not be allowed to be changed if a record is unposted. However, the correct approach here by AcctSeed should have been to allow users to change the currency field on a source record's header (which is what matters and where the currency conversion rate is defined) as long as the record is unposted. Furthermore, to address that lines stay consistent with header, two triggers should be instituted:
- Header - If currency field on header is updated, then all subordinate child lines' currencies are updated to match header currency.
- Lines - If currency field is attempted to be changed on line, override it so that it always equals header currency (I believe this is already in place)
-
Official comment
Hello Bao,
Thank you for submitting this request. I will have the Product Development team look into removing this restriction.
Comment actions
Please sign in to leave a comment.
Comments
1 comment