User Tools

Site Tools


faq:counting_monies_at_eod

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Last revision Both sides next revision
faq:counting_monies_at_eod [2007/02/19 17:26]
cliff
faq:counting_monies_at_eod [2007/02/19 17:39]
cliff
Line 10: Line 10:
 ==== Why the minute by minute nature of the POS Transaction report is important ==== ==== Why the minute by minute nature of the POS Transaction report is important ====
 The 2 biggest advantages to a minute by minute recording of what was happening in the System are: 1) It is important to be able to chronologically follow the sequence of events in many situations where you are trying to put together what was going on; 2) If you were to make a transaction and it was somehow dated for jan 01/2006 instead of jan 01/2007 it would be very difficult to find if they were not all recorded as being created today. One of the drawbacks of the POS Transaction report are that it is one of the last things to be recorded so if any glitches or problems happen, they can prevent the entry from being created in the POS Transaction report which will throw out the POS Transaction report, but does not effect the rest of your system. So if it doesn'​t effect the rest of the system, what do we do if it is out. First: make very sure the original transaction (Ex: the invoice) is correct. Second: Take the printed copy of the POS Transaction reports and adjust for the errors you see. Please note that it is possible to remove the bad entries, but is against our reccomendation so we do not show users how to do this unless the situation is extreme. ​ The 2 biggest advantages to a minute by minute recording of what was happening in the System are: 1) It is important to be able to chronologically follow the sequence of events in many situations where you are trying to put together what was going on; 2) If you were to make a transaction and it was somehow dated for jan 01/2006 instead of jan 01/2007 it would be very difficult to find if they were not all recorded as being created today. One of the drawbacks of the POS Transaction report are that it is one of the last things to be recorded so if any glitches or problems happen, they can prevent the entry from being created in the POS Transaction report which will throw out the POS Transaction report, but does not effect the rest of your system. So if it doesn'​t effect the rest of the system, what do we do if it is out. First: make very sure the original transaction (Ex: the invoice) is correct. Second: Take the printed copy of the POS Transaction reports and adjust for the errors you see. Please note that it is possible to remove the bad entries, but is against our reccomendation so we do not show users how to do this unless the situation is extreme. ​
 +
 ==== What if we can't make things match for the deposit journal entry? ==== ==== What if we can't make things match for the deposit journal entry? ====
 +So the totals don't match up. First we close the POS Transaction report anyway. Then we post the deposit journal entry using the actual Cash, VISA, and other monies that we have recorded. After this there should be a small difference in the Cash Clearing account. This account is normally the 1020 account (Windward System Five default setting). That difference can be moved to the 1021 account called: Cash Clearing Holding. This holding account for cash clearing will hold the outages you accumulate, and at a glance will tell you if you are far enough out to warrant further investigation. According to the accountant pennies of outage might be enough for investigation,​ but you can avoid this till closer to month end. Please make sure it is done before month end though. When you do start to track down the problem, I would start with System Five's Integrity Checks. These entegrity checks will display problems that the system detects for you. After all of these are cleaned up your original outage should be fixed. The trouble is now if you look back at the Cash clearing account on the day of the original problem it will show the outage, but in the negative of the original. What has happened is that the problem was fixed with the adjustment you made to 1021 and then again when you fixed the problem. The double entry of the fixed can easily be fixed by reversing the adjustment to the 1021 on the as at the day the adjustment occured. ​
  
 +=== Benifits ===
 +The benifit of this situation is that your cash clearing will always come to $0 at the end of every day, making it drastically easier to find problems. When we look at our cash clearing at the end of the day after our deposit has been entered the balance will not be $0. Then if we look at the previous day and find it isn't $0 we know the problem was in the past, because it came to $0 the day before. If we keep going back we find the last day that the cash clearing did come to $0 and between that day and the next is when the error occured and you should often be able to just find ad fix it on the spot saving time and energy tracking the problem down other ways.
  
  
faq/counting_monies_at_eod.txt ยท Last modified: 2008/05/08 14:39 by craig