|
Layout 1 Recurring Purchase Page
.png)
1.Supplier: This is the supplier’s name when the supplier list has been created.
2.Status is the purchase status, which is selected from the dropdown list when you create a quote, order or bill recurring;
3.Frequency: is to define how frequently this transaction will be repeated.
if a user has created a transaction to recur every 3 days , in here it will show 3 day(s)
if a user has created a transaction to recur every 2 weeks , Monday, it will show 2 week(s) on Monday
4.Last run: This is the date of the last automated transaction.
5.Next run: This is the date when the next transaction will be generated as scheduled. It should be no later than the designed End Date and the last day of EOFY, and on or after today’s date. Same principles applies to editing recurring purchase.
6.Total: This is the total amount for this transaction.
Function
1.Add Recurring: It will open layout 2 to add a new recurring template.
2.Delete: This button will be activated if the user selects a recurring transaction from the table.
3.Exit: Click this button to jump to the homepage.
4.Search: User may select specific supplier to display its recurring transactions.
Layout 2 Recurring Template
.png)
1.Quote: This is a dropdown list with three options of Quote, Order and Bill.
2.Next recurring Create Date: is to define when the next purchase transaction will be created. It should be after today’s date.
3.No End date: is a dropdown list with two options “No end date” and “End by”.
1.1 If a user chooses “No end date”, the recurring transaction will keep on repeating forever.
1.2 If the user choose” End by”, then a date selection field will show at its right-hand side, which means the recurring transaction will stop after on this date recurring transaction will be generated as the last run.
Recurs Every field only allows a user to input a number greater than 0 and less than 10,950 (this is maximum 30 years times 365 days), any other strings or signs etc. is not acceptable.
4.Days dropdown list have three options Day(s),Week(s),Month(s)
1.1 If a user inputs 5 at Recurs Every field, and then chooses day(s), this recurring will automatically be generated every 5 days
1.2 If a user inputs 2 at Recurs Every field and then chooses week(s), another field with Monday to Sunday 7 options will show up in dropdown list. Then if user chooses Monday, then this transaction will be generated automatically every fortnight Monday.
1.3If a user chooses Month(s), the above weekly dropdown list (Monday to Sunday) will be replaced with a Month dropdown list, which will show the date of each month (e.g. 1st, 2nd, 3rd, 4th, 5th, 6th, 7th, 8th, 9th, 10th, 11th, 12th, 13th, 14th, 15th, 16th, 17th, 18th, 19th, 20th, 21st ,22nd, 23rd, 24th, 25th, 26th, 27th, 28th, Last Day).
The reason why there is no 29th, 30th and 31st not every month have these three dates. Therefore, Q6 uses Last Day to represent these three dates.
5.The rest of table below would be same as Purchase Bill’s page, except the following field.
6.Date：This field is not editable since every transaction date would be different from the recurring creation date.
7.Due Date：This field only allows a user to input number greater than 0 and less than 10,950 (this is maximum 30 years times 365 days).
|