Slide 1

Slide notes: In this tutorial we are going to look at how to perform a Forced Reversal. We start by looking at a Transaction that we have drilled, in this case on a Stock Code Enquiry, and the purpose for starting here is that we wish to show an easy method for storing the Transaction Key that we wish to reverse. Note the system Key of the Transaction that we are looking at. This Key can be found on a Drill and also on an Audit Trail Report.

 

 

 

Slide 2

Slide notes: On the Drill Screen, we actually have a Key Stacking function, where the system will record this Key for us, for later retrieval.

 

 

 

Slide 3

Slide notes: Note the message that the Key has been stacked.

 

 

 

Slide 4

Slide notes: We will now back out of this Transaction Drill and move to Forced Reversals.

 

 

 

Slide 5

Slide notes:

 

 

 

Slide 6

Slide notes:

 

 

 

Slide 7

Slide notes:

 

 

 

Slide 8

Slide notes:

 

 

 

Slide 9

Slide notes:

 

 

 

Slide 10

Slide notes:

 

 

 

Slide 11

Slide notes:

 

 

 

Slide 12

Slide notes:

 

 

 

Slide 13

Slide notes: Forced Reversals are performed from the Problem Management menu in Accounting Controls.

 

 

 

Slide 14

Slide notes:

 

 

 

Slide 15

Slide notes:

 

 

 

Slide 16

Slide notes:

 

 

 

Slide 17

Slide notes:

 

 

 

Slide 18

Slide notes: The system informs that Forced Reversals should not be used in the place of normal Reversals. It is only reserved for fixing a system problem, and as such should only be used by a Support Person who understands what is being done, and also the implications.

 

 

 

Slide 19

Slide notes: When we are on the Transaction Forced Reversal screen, then we are expected to input or provide the Transaction Key to reverse. This Key could have been noted before and captured now, or we can retrieve it from the lookup function if we have previously stacked it.

 

 

 

Slide 20

Slide notes:

 

 

 

Slide 21

Slide notes: The Help explains that we can just use the lookup function.

 

 

 

Slide 22

Slide notes:

 

 

 

Slide 23

Slide notes:

 

 

 

Slide 24

Slide notes:

 

 

 

Slide 25

Slide notes: The system retrieves the Key from the stack and inputs it to retrieve the Transaction details.

 

 

 

Slide 26

Slide notes: A Forced Reversal does not reverse a Transaction Family with multiple legs as does a standard Reversal. This is a 'system fix' utility and it only reverses the specific Transaction leg indicated by this Transaction Key. We note here that the Amount of 703.92 is the Transaction leg that we are going to reverse in this case.

 

 

 

Slide 27

Slide notes: We can also see that by looking at the Financials, where we see the same amount for the current Transaction leg.

 

 

 

Slide 28

Slide notes: Then we choose 'Reverse Now'.

 

 

 

Slide 29

Slide notes:

 

 

 

Slide 30

Slide notes: Again, the point is made that this is not a standard reversal.

 

 

 

Slide 31

Slide notes: Next, we choose the Period in which the reversal should be processed.

 

 

 

Slide 32

Slide notes:

 

 

 

Slide 33

Slide notes:

 

 

 

Slide 34

Slide notes: The Reversal has now been processed and we can continue with another, or quit the process.

 

 

 

Slide 35

Slide notes:

 

 

 

Slide 36

Slide notes:

 

 

 

Slide 37

Slide notes:

 

 

 

Slide 38

Slide notes:

 

 

 

Slide 39

Slide notes: The system keeps a special log of Forced Reversals, and we can get a Report of Forced Reversals that have been performed in the system.

 

 

 

Slide 40

Slide notes:

 

 

 

Slide 41

Slide notes: We can select the Date Range.

 

 

 

Slide 42

Slide notes:

 

 

 

Slide 43

Slide notes: And in this Report we can see the Forced Reversal that we have performed a moment ago.