MIGRATED TOhttp://wavelet.asia/customer-portal/2011/05/19/credit-terms-control-configuration-rules/
This function allows you to define a more flexible credit terms scheme that can be applied to specific customers only or all of them, as you wish. The default credit terms function (found in the customer edit and create page) is generally sufficient for most businesses. This function, however, is available for businesses which require more flexible credit terms schemes for their customers. For example, users may define "grace periods" for their customers, each period having their own system feedback and effect based on which terms the customer currently falls under. Currently there are only two effects, 'normal' and 'block_invoice'. More will be added as required or requested, depending on system restrictions. In this example, you may create a set of rules where the user may have outstanding invoices for as long as 30 days, and after that no new invoices can be created. If required, users can also set the time limits to "end of the month" rather than strict day counts. Users may even set "exception" date ranges. What this means is, if an invoice is created within the "exception" date range, it is assumed to be created on a different date (predefined by the business) for the purpose of credit terms calculation only. For example, if the current date is 30 March and an outstanding invoice was created on 26 February (which falls within the exception date range), you can still create invoices for that customer, because the 26 February invoice is considered to be created on 1 March instead. The idea is to create a credit terms control scheme, followed by rules that define the scheme. Each credit terms control scheme will usually have at least one rule, although it is more common to see at least 2 or more rules attached to a scheme. You can therefore create a scheme that gives a customer 30 days normal terms, perhaps another 30 days as grace period, and finally blocking invoice creation for that customer after the grace period has expired. This example will create a single scheme with 3 rules. The Screen  Description of the screen above follows: 1. Code: Enter a code for your credit terms scheme. Should not be more than 100 characters. 2. Name: Enter a name for your credit terms scheme. Should not be more than 1000 characters. 3. Description: Add a short description to your credit terms scheme. Should not be more than 5000 characters. 4. Date Start Set: This set of fields will help define the starting point of the date range to determine if the current date falls within the exception date range. This is calculated by taking the current date, and replacing the date's individual elements with the values specified in the corresponding fields. For example: The diagram above shows 0 for Year, 0 for Month and 25 for Day. Let's say the current date is 13 April 2009. Placing a 0 in any of these fields means to leave the current date values alone, it will not set the respective date values with any new value. To create the starting point of the the exception date range, we set Year 0 to 2009 = 2009, Month 0 to April(04) = April, and Day 25 to 13 = 25. Therefore, the starting point of the exception date range is 25 April 2009. You should not set more than 31 for Day field and 12 for Month field. Setting the value to 40 tells the system to use the last day of that particular month (30 for April, 31 for May, 28 or 29 for Feburary depending on leap year conditions). 5. Date Start Add: This set of fields will help define the starting point of the exception date range. This is calculated by adding the specified values to the previously-modified date. For example, using the previously-modified date of 25 April 2009, we add Year 0 to 2009, Month 0 to April(04) = April, and Day 0 to 25 = 25. This brings the final starting point of the exception date range to 25 April 2009. If the Day field had a value of 2, it would have modified the date to 27 April 2009. If the values specified in the Day and Month field would bring the value to more than the upper limit of the Month/Day field (based on month's maximum days), it will adjust the Year and Month portions accordingly. Setting the value to 40 tells the system to use the last day of that particular month (30 for April, 31 for May, 28 or 29 for Feburary depending on leap year conditions). 6. Date End Set: This set of fields help define the ending point of the exception date range. It works the same way as Date Start Set. Setting the Day field to 40 will set the day portion of the date to the last day of the month in question. 7. Date End Add: This set of fields also help define then ending point of the exception date range, in the same way as Date Start Add. Using the previous example, we calculate the ending point of the exception date range to be 30 April 2009. 8. Date Exception Set: This set of fields help define the date to which the current date will "change" to for the purposes of determining credit terms only. It works the same way as Date Start Set. Using the previous example, this will change the current date from 13 April 2009 to 1 April 2009. 9. Date Exception Add: This set of fields help define the date to which the current date will "change" to for the purposes of determining credit terms only. It works the same way as Date Start Add. Using the previous example, this will change the previously-modified date from 1 April 2009 to 1 May 2009. How this works is, outstanding invoices for a customer will have each of their dates measured against the exception date range. If any of them fall within the date range, those invoices will have their transaction dates "assumed" to be the calculated exception date specified by the credit terms scheme. In this way, an invoice with a transaction date of 26 April 2009, which falls within the exception date range, will be treated as if it were created on 1 May 2009. This is a kind gesture to the customer, giving them a few more days to settle the invoice, since invoices created within that range are assumed to be created in the following month instead. This is all done before the individual outstanding invoices are subjected to the individual rules of each credit control scheme, to determine what actions are to be taken based on which rule's "requirements" they meet. 10. Status: Determines whether a credit control scheme is active or not. This means the credit control scheme can be turned on and off. 11. Save/Cancel: Save a new scheme, save changes to an existing scheme or cancel any changes. 12. Edit/Remove: Edit or delete an existing scheme. As a side note, calculations for setting and adding modifications to the dates will always follow this rule: apply the set portions first before applying the add portions. Then apply year first, then month, then day. Learn how to define new rules for a scheme here. |
MIGRATED-PAGES >