FrontAccounting forum — 'Reverse transaction' option in Journal Entry is planned for removal

Re: 'Reverse transaction' option in Journal Entry is planned for removal

null@example.com (apmuthu) — Tue, 24 Feb 2015 18:47:05 +0000

Yes, #_debtors_master table's pymt_discount field is only displayed in the Customer Payment Form in FA currently.

Re: 'Reverse transaction' option in Journal Entry is planned for removal

null@example.com (breetlee6666) — Tue, 24 Feb 2015 12:46:10 +0000

Therefore we want to move prompt payment discount input from customer/supplier payment screen to order entry page, to be used during invoicing. This way we can also make proper use with Prompt Payment Discount Percent customer parameter, which currently is not used in invoice calculations, but only informative.
Any comments are welcome.
____________________
http://www.test-king.com/cert-CWNA.htm
http://www.test-king.com/cert-RHCSA.htm
http://www.cnsu.edu/
http://www.keiseruniversity.edu/

Re: 'Reverse transaction' option in Journal Entry is planned for removal

null@example.com (itronics) — Thu, 11 Mar 2010 12:34:35 +0000

After the discussion we have decided to leave Reversing Journal Entry here without changes.
Janusz

Re: 'Reverse transaction' option in Journal Entry is planned for removal

null@example.com (mithun) — Thu, 11 Mar 2010 11:42:35 +0000

This i.e Reversing Journal Entries is a very useful option present in all large ERP packages. The purpose is to book monthly closing Provisions, Accruals and Prepayments. This is an important scalability feature and should be part of any accounting package.

Re: 'Reverse transaction' option in Journal Entry is planned for removal

null@example.com (infotechaccountant) — Tue, 12 May 2009 17:16:13 +0000

reversing the transaction practically doesn't have this much importance in my opinion , as we are using this feature when we are rectifying the errors either it will be in the previous period or in the current period , in some cases the developers of financial solutions compare between the side effects of some programming scripts which will cause some strange behaviour in the database and the importance of one specific feature , for example compare between having this feature of reversing with some strange behaviour of database or voiding this feature with healthy database
for me as a financial controller has some background of database programming i can say the important thing in this case is to have a healthy database and healthy queries that can work fast and the feature of reversing can be done manually .

Re: 'Reverse transaction' option in Journal Entry is planned for removal

null@example.com (joe) — Sat, 09 May 2009 21:15:51 +0000

Thanks fblauer.
I forgot this practice. We will let it be as it is.

/Joe

Re: 'Reverse transaction' option in Journal Entry is planned for removal

null@example.com (fblauer) — Sat, 09 May 2009 19:06:53 +0000

This is for reversing of accrual transactions, and would be useful from an accounting point of view. I don't see why it would be removed. The purpose is to record the transaction in the current period, instead of the next one. The reversal is to counter the transaction when it gets recorded in the next period. It is a very common accounting practice.

'Reverse transaction' option in Journal Entry is planned for removal

null@example.com (itronics) — Mon, 04 May 2009 09:35:43 +0000

Currently our development team is about to improve GL journal maintenance area. We have found that 'Reverse transaction' option in Journal Entry is somewhat strange and inconsistent with data flow rules used in other parts of FrontAccounting source.

When reverse transaction option is selected there are in fact two journal entries added during processing, first one with the data entered by user, the other with changed posting side (sign), and dated on first day of next month.

We are about to remove the option in FA v.2.2, but if this functionality is crucial for some current FA users, we are open for discussion.

Janusz