Question regarding documenting Reversing Transactions
David Carlson
david.carlson.417 at gmail.com
Wed Apr 26 09:17:55 EDT 2017
David T.,
I am glad that you are digging into this issue. If this results in a
change to, say, move the highlight to the new reversing transaction, then I
would ask the developer to also append a note to the source transaction
referring to the new transaction. Then an auditor could always find the
other half of the pair.
I have another use case for this tool. I sometimes use it to generate a
duplicate to then modify for use elsewhere, if I think it would be easier
than using the duplicate transaction tool for some reason. This, of
course, has nothing to do with good accounting practice.
David C
On Wed, Apr 26, 2017 at 6:32 AM, David T. via gnucash-user <
gnucash-user at gnucash.org> wrote:
> Dave C., the option already exists (under the Transactions menu), so the
> questions here are: should it be changed, and how should it be documented?
>
> My original question on this thread had to do with whether “old style”
> accounting included annotations with the reversing transaction, and I
> believe that the answer is probably “yes.” With the currently-implemented
> feature, I think it problematic that the reversing transaction is created
> without clear feedback, and without an option to add annotations to the new
> transaction. The user selects Add Reversing Transaction, and is immediately
> returned to the register with no further feedback. The feature as
> implemented requires the user to locate the newly-created reversing
> transaction and edit it to add annotations, and I believe it could be set
> up to allow a user to add an annotation before creating the new transaction.
>
> FWIW, I have already added a bug for documenting the feature (Bug 781714),
> and one for creating an entry in the glossary (Bug 781711).
>
> David T.
>
> > On Apr 26, 2017, at 6:52 AM, DaveC49 <davidcousens at bigpond.com> wrote:
> >
> > I wish to support Mike's position. There should be no need for a
> reversing
> > procedure to be implemented in any formal way. If you are making a
> reversing
> > transaction, then you need to notate it so that it is clear which
> > transaction it is reversing and why. The second point about other
> > adjustments is equally valid. You may have to make end of period
> adjustments
> > if you are using accrual accounting or to correct items (rounding errors)
> > etc. Reversals are rarely a routine transaction.
> >
> > It is possibly better to explain reversing/correcting a transaction and
> > adjustments with an example(s) in the Tutorial and Concepts guide rather
> > than having a specific feature for it.
> >
> >
> >
> > --
> > View this message in context: http://gnucash.1415818.n4.
> nabble.com/Question-regarding-documenting-Reversing-Transactions-
> tp4691271p4691292.html
> > Sent from the GnuCash - User mailing list archive at Nabble.com.
> > _______________________________________________
> > gnucash-user mailing list
> > gnucash-user at gnucash.org
> > https://lists.gnucash.org/mailman/listinfo/gnucash-user
> > -----
> > Please remember to CC this list on all your replies.
> > You can do this by using Reply-To-List or Reply-All.
>
> _______________________________________________
> gnucash-user mailing list
> gnucash-user at gnucash.org
> https://lists.gnucash.org/mailman/listinfo/gnucash-user
> -----
> Please remember to CC this list on all your replies.
> You can do this by using Reply-To-List or Reply-All.
>
More information about the gnucash-user
mailing list