module:accounting:acctjoonhold:list
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision | |||
|
module:accounting:acctjoonhold:list [2019/12/04 18:21] target |
module:accounting:acctjoonhold:list [2019/12/04 18:47] (current) target |
||
|---|---|---|---|
| Line 34: | Line 34: | ||
| Use of system Hold Order arises when an account receivable reached the past due limit of 60 and 90 days, for hold chain and hold client respectively. This means that any further delivery or actions that will incur additional cost should be notified and prevented by following Hold-Request-Activation process. | Use of system Hold Order arises when an account receivable reached the past due limit of 60 and 90 days, for hold chain and hold client respectively. This means that any further delivery or actions that will incur additional cost should be notified and prevented by following Hold-Request-Activation process. | ||
| Note: system automatically holds delivery of unmatched down payment requirement | Note: system automatically holds delivery of unmatched down payment requirement | ||
| - | ** | + | |
| - | Process:** | + | **Process: |
| 1. Accounting reviews list of Account Receivable | 1. Accounting reviews list of Account Receivable | ||
| + | |||
| 2. Accounting puts erring client/ | 2. Accounting puts erring client/ | ||
| + | |||
| 3. Accounting emails list of client/ | 3. Accounting emails list of client/ | ||
| + | |||
| Note: Accounting may opt for automatic hold function to client with >60 days past due account | Note: Accounting may opt for automatic hold function to client with >60 days past due account | ||
| **Policies: | **Policies: | ||
| + | |||
| • see F&A MEMO 18-001 along with other guidelines. | • see F&A MEMO 18-001 along with other guidelines. | ||
| - | ** | ||
| - | **B. Hold-Request-Activation Process**** | + | **B. Hold-Request-Activation Process** |
| System notifies user that he/she cannot proceed due to hold control. User requests for activation by obtaining written approval from management and have it as an instruction to allow order to proceed given the circumstances | System notifies user that he/she cannot proceed due to hold control. User requests for activation by obtaining written approval from management and have it as an instruction to allow order to proceed given the circumstances | ||
| - | ** | + | |
| - | Process:** | + | **Process: |
| * 1. PM/User sends request for activation of order; | * 1. PM/User sends request for activation of order; | ||
| * • Orders for activation can be viewed in ON HOLD JO module | * • Orders for activation can be viewed in ON HOLD JO module | ||
| Line 58: | Line 62: | ||
| **Policies: | **Policies: | ||
| + | |||
| • Do not bypass system activation process | • Do not bypass system activation process | ||
| • see F&A MEMO 18-001 along with other guidelines. | • see F&A MEMO 18-001 along with other guidelines. | ||
module/accounting/acctjoonhold/list.txt · Last modified: 2019/12/04 18:47 by target
Page Tools
