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 revisionPrevious revision
Next revisionBoth sides next revision
faq:counting_monies_at_eod [2007/02/19 17:12 (17 years ago)] clifffaq:counting_monies_at_eod [2007/02/19 17:26 (17 years ago)] cliff
Line 9: Line 9:
  
 ==== 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. 
 +==== What if we can't make things match for the deposit journal entry? ====
  
  
  
faq/counting_monies_at_eod.txt · Last modified: 2008/05/08 14:39 (16 years ago) by craig