Accounts Preferences - Revision history

Simon Clive at 23:57, 21 July 2011

2011-07-21T23:57:47Z

Simon Clive at 23:52, 21 July 2011

2011-07-21T23:52:34Z

Simon Clive at 23:50, 21 July 2011

2011-07-21T23:50:24Z

Simon Clive at 06:44, 21 July 2011

2011-07-21T06:44:24Z

Dene at 07:21, 16 May 2011

2011-05-16T07:21:23Z

Dene at 07:15, 16 May 2011

2011-05-16T07:15:33Z

Dene at 07:14, 16 May 2011

2011-05-16T07:14:57Z

Dene at 07:10, 16 May 2011

2011-05-16T07:10:47Z

Dene at 06:44, 16 May 2011

2011-05-16T06:44:57Z

Dene at 06:44, 16 May 2011

2011-05-16T06:44:00Z

@@ Line 27: / Line 27: @@
 The fiscal year setting also creates your '''Year End''' postings automatically, so be aware of the effect that changing this field will have.
-By '''Year End''' postings we are taking about how ERP will take your profit and loss earnings or losses and put them automatically onto your balance sheet as '''Retained Earnings.'''
+By '''Year End''' postings we are talking about how ERP will take your profit and loss earnings or losses and put them automatically onto your balance sheet as '''Retained Earnings.'''
 There is nothing you need to do for this to happen as it is fully automated.

@@ Line 19: / Line 19: @@
 This date setting is a way of '''Summarising''' all transactions in your chart of accounts down to a single line posting. This setting will take '''1000''' postings and make '''1''' posting. Fantastic for speeding the system up in all aspects from lists to reports. At any stage this date can be adjusted backwards to any point and the transactions will be expanded out again.<br>
-ERP does this by creating a '''Separate Table''', that is not a part of the normall reporting hierarchy and it stores all the individual posting for the 1000 transactions. It replaces them in the normal reporting hierarchy with 1 summarised entry.
+ERP does this by creating a '''Separate Table''', that is not a part of the normall reporting hierarchy and it stores all the individual postings for the 1000 transactions. It replaces them in the normal reporting hierarchy with 1 summarised entry.
 Please Note that if you do adjust the '''Summarised Transactions Before''' date backwards and the actual date right now is more than '''3 Months''' after the '''Fiscal Year End''' date preference, as set in ERP, then this adjustment will automatically be returned to the month of the current fiscal year, after 24 hours. This is done to return speed back to the software.<br>

@@ Line 27: / Line 27: @@
 The fiscal year setting also creates your '''Year End''' postings automatically, so be aware of the effect that changing this field will have.
 By '''Year End''' postings we are taking about how ERP will take your profit and loss earnings or losses and put them automatically onto your balance sheet as '''Retained Earnings.'''
 There is nothing you need to do for this to happen as it is fully automated.
@@ Line 37: / Line 37: @@
 '''(2) Global'''
-This date is designed to lock the entire system down so that no matter what your access levels are, no transactions prior to this date, can be altered. Recommended in your have done your tax office reporting.
+This date is designed to lock the entire system down so that no matter what your access levels are, no transactions prior to this date, can be altered. Recommended if you have done your tax office reporting.
 '''(3) Accounts Receivable'''<br>
@@ Line 45: / Line 45: @@
 '''(4) Accounts Payable'''
 Similar to the Global date but designed just for the Accounts Payable report.
 '''N.B''' All other users must be logged out of ERP&nbsp;before selecting '''Refresh'''<br><br>

@@ Line 17: / Line 17: @@
 '''(1) Summarised Transactions Before'''
-This date setting is a way of summarising all transactions in your chart of accounts down to a single line posting. This setting will take 1000 postings and make 1 posting. Fantastic for speeding the system up in all aspects from lists to reports. At any stage this date can be adjusted backwards to any point and the transactions will be expanded out again.<br>
+This date setting is a way of '''Summarising''' all transactions in your chart of accounts down to a single line posting. This setting will take '''1000''' postings and make '''1''' posting. Fantastic for speeding the system up in all aspects from lists to reports. At any stage this date can be adjusted backwards to any point and the transactions will be expanded out again.<br>
-ERP does this by creating a separate table, that is not a part of the normally reporting hierarchy and it stores all the individual posting for the 1000 transactions. It replaces them in the normal reporting hierarchy with 1 summarised entry.
+ERP does this by creating a '''Separate Table''', that is not a part of the normall reporting hierarchy and it stores all the individual posting for the 1000 transactions. It replaces them in the normal reporting hierarchy with 1 summarised entry.
-Please Note that if you do adjust the "Summarised Transactions Before" date backwards and the actual date right now is more than 3 months after the Fiscal Year end date preference, as set in ERP, then this adjustment will automatically be return to the month of the current fiscal year, after 24 hours. This is done to return speed back to the software.<br>
+Please Note that if you do adjust the '''Summarised Transactions Before''' date backwards and the actual date right now is more than '''3 Months''' after the '''Fiscal Year End''' date preference, as set in ERP, then this adjustment will automatically be returned to the month of the current fiscal year, after 24 hours. This is done to return speed back to the software.<br>
-<u>Fiscal Year End</u>
+'''<u>Fiscal Year End</u>'''
-The fiscal year setting also creates your "Year End" postings automatically, so be aware of the effect that changing this field will have.
+The fiscal year setting also creates your '''Year End''' postings automatically, so be aware of the effect that changing this field will have.
-By Year End postings we are taking about how ERP will take your profit and loss earnings or losses and put them automatically onto your balance sheet as "Retained Earnings".
+By '''Year End''' postings we are taking about how ERP will take your profit and loss earnings or losses and put them automatically onto your balance sheet as '''Retained Earnings.'''
 There is nothing you need to do for this to happen as it is fully automated.
@@ Line 45: / Line 45: @@
 '''(4) Accounts Payable'''
-Similar to the Global date but designed just for the Accounts Payable report.<br><br>
+Similar to the Global date but designed just for the Accounts Payable report.

@@ Line 21: / Line 21: @@
 ERP does this by creating a separate table, that is not a part of the normally reporting hierarchy and it stores all the individual posting for the 1000 transactions. It replaces them in the normal reporting hierarchy with 1 summarised entry.
-Please Note that if you do adjust the "Summarised Transactions Before" date backwards, ERP will automatically return it to the month of the current fiscal year as defined in your preferences, after 24 hours. This is done to return speed back to the software.<br>
+Please Note that if you do adjust the "Summarised Transactions Before" date backwards and the actual date right now is more than 3 months after the Fiscal Year end date preference, as set in ERP, then this adjustment will automatically be return to the month of the current fiscal year, after 24 hours. This is done to return speed back to the software.<br>
 <u>Fiscal Year End</u>
-The fiscal year setting also creates your year end postings automatically, so be aware what changing this field will effect. By Year End it will take your profit and loss earnings or losses and put them automatically onto your balance sheet as "Retained Earnings". There is nothing you need to do for this to happen as it is fully automated.
+The fiscal year setting also creates your "Year End" postings automatically, so be aware of the effect that changing this field will have.
 <br>

@@ Line 1: / Line 1: @@
-<menu align="center" name="myMenu">
+<menu name="myMenu" align="center">
 More Detail=
 [[Audit Trail List]]
@@ Line 17: / Line 17: @@
 '''(1) Summarised Transactions Before'''
-This date setting is a way of summarising all transactions in your chart of accounts down to a single line posting. This setting will take 1000 postings and make 1 postings. Fantastic for speeding the system up in all aspects from lists to reports. At any stage this date can be adjusted backwards to any point and the transactions will be expanded out again.<br>
+This date setting is a way of summarising all transactions in your chart of accounts down to a single line posting. This setting will take 1000 postings and make 1 posting. Fantastic for speeding the system up in all aspects from lists to reports. At any stage this date can be adjusted backwards to any point and the transactions will be expanded out again.<br>
 ERP does this by creating a separate table, that is not a part of the normally reporting hierarchy and it stores all the individual posting for the 1000 transactions. It replaces them in the normal reporting hierarchy with 1 summarised entry.

@@ Line 14: / Line 14: @@
 == Overview  ==
-This date setting is a way of summarising all transactions in your chart of accounts down to a single line posting. This setting will take 1000 postings and make 1 postings. Fantasic for speeding the system up in all aspects from lists to reports. At any stage this date can be adjusted backwards to any point and the transactions will be expanded out again.<br>
+'''(1) Summarised Transactions Before'''
-ERP does this by greating a separate table, that is not a part of the normally reporting hieracy and it stores all the indivual posting for the 1000 transactions. It replaces them in the normal reporting hieracy with 1 summarized entry.
+This date setting is a way of summarising all transactions in your chart of accounts down to a single line posting. This setting will take 1000 postings and make 1 postings. Fantastic for speeding the system up in all aspects from lists to reports. At any stage this date can be adjusted backwards to any point and the transactions will be expanded out again.<br>
-Please Note that if you do adjust the date backwards, ERP will automatically return it to the month of the current fiscal year after 24 hours. This is done to return speed back to the software.<br>
+ERP does this by creating a separate table, that is not a part of the normally reporting hierarchy and it stores all the individual posting for the 1000 transactions. It replaces them in the normal reporting hierarchy with 1 summarised entry.
 '''Closing Dates '''<br>
 '''(2) Global'''
@@ Line 30: / Line 31: @@
 This date is designed to lock the entire system down so that no matter what your access levels are, no transactions prior to this date, can be altered. Recommended in your have done your tax office reporting.
-'''(3) Accounts Recievable'''<br>
+'''(3) Accounts Receivable'''<br>
-Similair to the Global date but designed just for the Accounts Recievable report.<br>
+Similar to the Global date but designed just for the Accounts Receivable report.<br>
 '''(4) Accounts Payable'''
-Similair to the Global date but designed just for the Accounts Payable report.<br><br>
+Similar to the Global date but designed just for the Accounts Payable report.<br><br>