|
|
Line 1: |
Line 1: |
| [[How to hide the Job Type while invoicing the client?]] | | [[How to hide the Job Type while invoicing the client?]] |
|
| |
|
| == Why does NEOSYS reverse PO/repost PI on the cost a/c even when the PO/PI amounts agree? ==
| | [[Why does NEOSYS reverse PO/repost PI on the cost a/c even when the PO/PI amounts agree?]] |
|
| |
| This is a common question but NEOSYS practice has prevailed for some very good reasons.
| |
|
| |
| #So that ALL purchase invoices show in the cost account. This makes life much easier for accountants to find information and auditors to verify the cost a/c.
| |
| #The reversal reflects the fact that there is no longer an ESTIMATED cost in the cost a/c and that it has been replace by a REAL cost.
| |
|
| |
| Dislike of the apparently unnecessary reversal and re-entry is generally based on:
| |
| #A lack of appreciation of the benefits mentioned above (usually overcome by explanation)
| |
| #A desire to be like manual accounting where one would save staff time by not doing the reversal (irrelevant if totally automated)
| |
| #A desire for the cost a/c to be shorter especially if most PI match PO (less important these days now paper records are less used)
| |
|
| |
| One can also apply the principle of not varying policy without good reason. In this case, making completely different accounting entries just because a PI varied by one current unit from its PO could be viewed as illogical.
| |
|
| |
|
| [[How to issue an estimate without creating a Job?]] | | [[How to issue an estimate without creating a Job?]] |
Revision as of 10:18, 18 October 2010