.title "Payroll" .id 907020050326101956 .tags "manual" .body { dummy } /271820160224160425 { .title "Suspicious Pay Period" .id 271820160224160425 .tags {dialog confirm} .body { [p { Warning: The check date of this payrun is prior to the pay period begin date. }] [p { Under normal circumstances this is a very unusual thing to do and continuing can throw payroll calculations out. }] [p { When a new payrun item is added the pay period number is incremented by one and the pay period start and end dates are calculated automatically. (Note the pay frequency may cause the pay year to increment by one and reset the pay period number to one. For example, after 12 months in a payroll with a monthly pay frequency, a newly added payrun will automatically have the pay year advanced by one and the pay period number reset to one.) }] [p { A common cause of a problem is the need to issue an additional check in a previously processed pay period. Users add a payrun, and edit the check date but forget to edit the pay period year and/or pay period number. }] [ul { [li {[link .chm $::qw_manual_file .id 150220040805155130 {[bold "Creating a Payrun"]}]}] }] } } /271820141222154301 { .title "Payrun Check Date prohits processing or unprocessing" .id 271820141222154301 .tags {error} .body { [ ::set ::Html ""; ] [p { The check date of this payrun ([qw_s_args .check_date]) is outside the date range of this payroll version ([qw_s_args .tables_start_date] to [qw_s_args .tables_end_date]). }] [p { For example, if you were allowed to unprocess an old payroll, there would be no way to ever reprocess it. }] } } /271820120204160434 { .title "Select Report Style" .id 271820120204160434 .tags {dialog confirm} .body { [p { Select report style }] [ul { [li {[link .chm $::qw_manual_file .id 907020054031205040 {[bold "Custom Payroll Reports"]}]}] }] [p { }] } } /271820120203120505 { .title "No earnings in the period specified." .id 271820120203120505 .tags {error} .body { [p { }] [p { }] [p { }] [p { }] } } /271820120203120506 { .title "No employees selected for print. Review Direct Deposit Status and/or Email Status for mismatch." .id 271820120203120506 .context {payroll_report is being used to print paychecks and remittance advisory} .tags {error} .body { [p { None of the employees selected matched the [qw_menu_command Print "Payroll Report"] prompt setting for [bold "Direct Deposit Status"]. }] [p { Check each employee's [bold "Direct Deposit Status"], found in the employee detail window pane, using the [qw_menu_command Information "Payroll Information"] window tab. }] [p { Or, you may have a mismatch between the [bold {Email Status}] setting and the [bold {Email}] address of the employee(s). }] [ul { [li { [p { When [bold {Email Status}] is set to [bold {active}] only employees with an email address are selected. }] }] [li { [p { When [bold {Email Status}] is set to [bold {inactive}] only employees with an empty email address are selected. }] }] [li { [p { When [bold {Email Status}] is set to empty all employees are selected (respecting of course any other option values). }] }] }] } } /271820070925145613 { .title "Attempted to commit a payroll transaction that does not reference an employee." .id 271820070925145613 .tags {error} .body { [p { This error occurs when you are attempting to record an incomplete payroll transaction header. Complete the transaction before continuing. }] [p { [bold NOTE:] You may have to restore (all) windows to see the offending transaction row. Either restore the appropriate window or press [qw_key F8] to restore all windows. Then examine the transactions to locate the incomplete row (a cell on this row will be highlighted). }] [p { The incomplete transaction is [qw_s_args .transaction_path]. }] [p { One possible reason for this is subtle. For example, if you set a default journal on an account ledger (with [qw_menu_command Edit "Default Value" Set] or [qw_key F12]) to a payroll journal, the next insert or append will create a row for a payroll transaction. Problem is, this is completely out of context. A payroll transaction can only be created in a payroll journal, or within the appropriate payroll folders. }] [p { Another possible reason could be an attempt to block paste transactions that are referencing deleted employees or deleted payrolls, or posting to deleted accounts. If this is the case, execute a block copy command, select the offending buffer entry and delete it. (Adding new payrolls, employees or accounts with the old names will NOT work - in the paste buffer, references to objects are stored as database addresses, and since database addresses are machine generated, unique and never reused, the addresses of the original objects can never be recreated.) Delete the old buffer entry and create a new one if necessary. }] } } /271820070817141911 { .title "Unallocated wage expense account has not been set." .id 271820070817141911 .tags {error} .body { [p { Select the "Settings" tab of the payrun window and then select an account to post unallocated wages to. }] [p { This account is required in the case there are no timecards to provide an allocation "pie chart". Wages entered directly to the paylist (or calculated automatically) are allocated according to the pie chart obtained from timecard wage allocations. When there are no timecards, wages entered directly or calculated will be posted to the specified unallocated wages account. }] [/* {FIXED with throw at process preview [p { [bold "Payroll users who never do timecards must also set this account."] (You may change your mind and start allocating wages at a later date.) You can select any existing miscellaneous account (of type general or expense) or add one for this purpose. }] */ }] [p { Remember that payrun settings are copied from the prior payrun for starting point default values, so normally this account can be set once. }] [ul { [li {[link .chm $::qw_manual_file .id 907020050419171200 {Payrun Settings Window}]}] }] } } /271820070721124700 { .title "Creating Employee Accounts for Timecard Payroll" .id 271820070721124700 .tags {error} .body { [p { Setup the employee for timecards. }] [p { Or change the pick root for employee selection. }] [ul { [li {[link .chm $::qw_manual_file .id 444420070626161329 {Creating Employee Accounts for Timecard Payroll}]}] [li {[link .chm $::qw_manual_file .id 857720050603114831 {Referenced Fields}]}] }] } } /907020050325100600 { .title "Confirm Payrun Unprocess" .id 907020050325100600 .tags "dialog" .body { [p { Your are being asked to confirm the "unprocessing" of a Payrun. }] [p { Unprocessing a payrun does the following: }] [ul { [li [p { Deletes all of the pay checks that were created by the Payrun. }]] [li [p { Resets the status of the Payrun to "unprocessed". }]] }] [p { Unprocessing the Payrun can only succeed if all the pay checks can be deleted from the books. If any pay checks cannot be deleted, then none will be deleted, and there will be no net effect on the Payrun. }] } } /907020050325105300 { .title "Attempted to set an employee's account name before setting the employee's Id." .id 907020050325105300 .tags {error} .body { [p { You tried to set the name of an employee payroll account before the employee has been given an employee id. }] [p { Each employee payroll account name must have the form [qw_field_value PREFIX-SUFFIX] where the prefix is the employee's employee id. }] [p { Therefore, the employee must have an employee id before you can add payroll accounts to the employee or set their account names. }] } } /907020050325110821 { .title "The employee's I.D. must be filled in before accounts can be created." .id 907020050325110821 .tags {error} .body { [p { You tried to create employee payroll accounts before the employee has been given an employee id. }] [p { Each employee payroll account name must have the form [qw_field_value PREFIX-SUFFIX] where the prefix is the employee's employee id. }] [p { Therefore, the employee must have an employee id before you can add payroll accounts to the employee or set their account names. }] } } /907020050325132040 { .title "Encountered an invalid type paycode" .id 907020050325132040 .tags {error} .body { [/* { _s_args .bad_value .good_list */ }] "[::sargs::get $_s_args .bad_value]" is not a valid type paycode. } } /907020050325162421 { .title "Encountered an invalid XXX paycode XXX." .id 907020050325162421 .tags {error} .body { [/* { _s_args .paycode .old_value .new_value */ }] The value "[::sargs::get $_s_args .new_value]" is not a valid setting. } } /907020050328134240 { .title "Payroll is already installed." .id 907020050328134240 .tags {error} .body { [p { Payroll object and window class have already been installed in the database [[qw_s_args .database] cpp_database_path]. }] } } /907020050328134250 { .title "Attempted to change the Payrun of a payroll transaction." .id 907020050328134250 .tags {error} .body { [p { Payroll transactions (pay checks) "belong" to the Payrun they were created by. You cannot change the Payrun of a paycheck to a different (or no) Payrun. }] } } /907020050328134300 { .title "Attempted to change the Employee of a payroll transaction." .id 907020050328134300 .tags {error} .body { [p { The pay check is for employee [[[[[[[::sargs::get $_s_args .object] odb_master] ".employee"] odb_get] odb_master] ".employee_id"] odb_get] and cannot be changed to a different employee. }] } } /907020050328134310 { .title "Attempted to change the employee of a payroll account." .id 907020050328134310 .tags {error} .body { [p { The employee a Payroll account "belongs" to cannot be changed. }] [p { If the account does not contain any postings, then the account can be deleted. }] } } /907020050328134330 { .title "You can't create an account desktop in a table." .id 907020050328134330 .tags {error} .body { [p { You have clicked on the menu branch "Employee" which would cause an employee dektop to be created. Desktops cannot be added to tables though. }] } } /907020050328134340 { .title "Attempted to change the status of a payrun that is currently being processed." .id 907020050328134340 .tags {error} .body { [p { The status of the Payrun is "processing" which means that you, or another user is currently processing the Payrun. }] [p { There are two ways that the status can be changed from processing: }] [ol { [li { [p { Click the "Abort" button on the Payrun preview window. }] [p { This will abort the processing and return the Payrun status to "unprocessed". }] }] [li { [p { Click the "Post Pay Checks" button on the Payrun preview window. }] [p { This will post the paychecks and set the status of the Payrun to "processed". }] }] }] } } /907020050328134350 { .title "You can not change the payroll this payrun is a member of." .id 907020050328134350 .tags {error} .body { [p { The Payrun contains the a Paylist and paychecks that were created for the current payroll. The payroll cannot be changed. }] } } /907020050328134410 { .title "Attempted to edit employee information on a Paylist." .id 907020050328134410 .tags {error} .body { [p { Employee information such the Id or name cannot be edited on a Paylist. }] } } /907020050328134420 { .title "You can't create a payroll desktop in a table." .id 907020050328134420 .tags {error} .body { [p { You have clicked on the menu branch "Payroll" which would cause an payroll dektop to be created. Desktops cannot be added to tables though. }] } } /907020050328134430 { .title "You can't create an account desktop in a table." .id 907020050328134430 .tags {error} .body { [p { You have clicked on the menu branch "Account" which would cause an account dektop to be created. Desktops cannot be added to tables though. }] } } /907020050328134500 { .title "Invalid setting \"%_value\", setting must be \"summary\", \"detail\", or \"detail with employee subtotals\"." .id 907020050328134500 .tags {error} .body { [p { There are three detail level settings: }] [ol { [li { [p { [bold summary] - One line is printed for each employee in the report. The line contains the total of the amounts for the period the report covers. }] }] [li { [p { [bold detail] - One or more lines are printed for each employee in the report. A line will be printed for each transaction that affects the employee's accounts. }] }] [li { [p { [bold {detail with employee subtotals}] - Detail lines are printed, plus a subtotal line for each employee. }] }] }] [p { Use the [qw_key F3] to choose a detail level. }] } } /907020050328134510 { .title "Invalid setting \"%_value\", setting must be \"no\" or \"yes\". (Include employees with no earnings)" .id 907020050328134510 .tags {error} .body { [p { The choice must be set to "yes" or "no". }] [p { To include employees in the report, even if they have no earnings in the report period, set this choice to "yes". }] [p { To include only those employees that have earnings in the report period, set this choice to "no". }] } } /907020050328134520 { .title "Template file %_value does not exist." .id 907020050328134520 .tags {error} .body { [p { No file with the name entered exists. }] [p { Reenter the filename, or use the [qw_key F3] to choose a choose a file. }] } } /907020050328134530 { .title "Template file must have .xls or .xlt or .xlsx or .xltx extension." .id 907020050328134530 .tags {error} .body { [p { The template filename must have the extension .xls or .xlt or .xlsx or .xltx. }] [p { Reenter the filename, or use the [qw_key F3] to choose a choose a file. }] } } /907020050328134540 { .title "Invalid choice \"%_value\", choice must be \"display\", \"file\" or \"printer\"." .id 907020050328134540 .tags {error} .body { [p { There are three choices for the destination: }] [ol { [li { [p { [bold display] - The report is generated in Excel, and then Excel is opened so you can viewq the resuklt on-screen. }] }] [li { [p { [bold file] - The report is generated in Excel, and then the Excel workbook is saved to the disk under the name specified. }] }] [li { [p { [bold print] - The report is generated in Excel, and then sent to the printer specified. (If no printer is specified, then the report is sent to the system default printer.) }] }] }] } } /907020050328134600 { .title "The printer name cannot be typed in. Press F3 to pick a printer." .id 907020050328134600 .tags {error} .body { [p { You cannot type in the name of the printer - you must choose it from a printer selection dialog window. }] [p { Press [qw_key F3] to choose a choose printer. }] } } /907020050328134620 { .title "You cannot edit the number." .id 907020050328134620 .tags {error} .body { [p { The numbers in this column are a fixed list that cannot be edited. }] } } /907020050328134750 { .title "Attempted to edit the transaction description." .id 907020050328134750 .tags {error} .body { [p { In the current version you cannot edit the description. }] } } /907020050328134800 { .title "You can't edit this amount. (Withheld/Accrued In Period)" .id 907020050328134800 .tags {error} .body { [p { The amount displayed is the total withheld/accrued for the remittance period. Because it is a total based on transactions in the books, you cannot edit the amount. }] } } /907020050328134810 { .title "You can't edit this amount. (Perpetual Balance)" .id 907020050328134810 .tags {error} .body { [p { The amount displayed is the total perpetual withheld/accrued amount minus the total perpetual remitted amount. Because it is the total based on transactions in the books, you cannot edit the amount. }] } } /907020050328134820 { .title "Attempted to edit the pay amount total. It is calculated automatically." .id 907020050328134820 .tags {error} .body { [p { The amount is the total of amounts above and cannot be edited. To change this amount, change one of the individual remittance amounts above it. }] } } /907020050328134830 { .title "Attempted to edit the final balance total. It is calculated automatically." .id 907020050328134830 .tags {error} .body { [p { This is a calculated amount based on the total perpetual balance outstanding minus the currrent remittance total. Because it is a calculated amount, you cannot edit it. }] } } /907020050328134850 { .title "Encountered an invalid type paycode" .id 907020050328134850 .tags {error} .body { [/* { _s_args .bad_value .good_list */ }] [p { "[::sargs::get $_s_args .bad_value]" is not a valid type paycode. }] [p { Press [qw_key F3] to choose a valid type. }] } } /907020050328134910 { .title "Encountered invalid employee account name." .id 907020050328134910 .tags {error} .body { [p { The name [qw_field_value [qw_s_args .after]] is not a valid name for an employee payroll account. }] [p { Each employee has a collection of accounts used to track payroll that employee. These employee payroll accounts must have account names in the form [qw_field_value PREFIX-SUFFIX], where the prefix is the employee's employee id, followed by a hyphen, followed by the suffix. For example, if the employee id is [qw_field_value ABC], then each of the accounts must have a name in the form [qw_field_name ABC-XXX] where XXX must be non-empty but can have any length. }] [p { In addition, an employee payroll account name can contain only letters and digits. Spaces or special characters are not allowed, with the exception of the hyphen separator. }] [p { In this case the employee id is [qw_quoted [qw_field_value [qw_s_args .employee_id]]] so each account name must of the form [qw_field_value [qw_s_args .employee_id]-XXX]. }] } } /907020050328134950 { .title "Encountered pay period number $Period but was expecting a number between 1 and $Periods." .id 907020050328134950 .tags {error} .body { [/* { _s_args .pay_frequency .year .maximum */ }] [p { There are [::sargs::get $_s_args .maximum] pay periods in the year [::sargs::get $_s_args .year]. }] [p { Please enter a pay period number between 1 and [::sargs::get $_s_args .maximum]. }] } } /907020050328135130 { .title "Encountered an unexpected error attempting to increment a value" .id 907020050328135130 .tags {error} .body { [/* { _s_args .value */ }] [p { NewViews was attempting to add a number to, or subtract a number from the value "[::sargs::get $_s_args .value]". }] [p { The operation failed unexpectedly. }] } } /907020050328135135 { .title "Payroll contains no active employees." .id 907020050328135135 .tags {error} .body { [p { The payroll either has no employees, or all employees are set to "inactive". Since there are no active employees, a Payrun will not be created. }] } } /907020060118174354 { .title "Paylist create error X employees with no Id, Y employees with no accounts" .id 907020060118174354 .tags {error} .body { [/* { #20051223_build_change_1 */ }] [/* {_s_args passed from payroll in throw: .no_id_errors # of employees with no ID set .no_account_errors # of employees with no accounts .no_account_ids List of employee IDs that have no accounts .no_earnings_errors # of employees who have accounts, but no earnings amounts .no_earnings_ids List of employee IDs who have accounts, but no earnings amounts .payroll_country "CANADA" or "USA" */ }] [p { Creation of the Payrun has failed because of missing or incomplete setup information for one or more employees. }] [p { The errors are explained below. }] [ ::set ::Html ""; ::set ::Text ""; ::if {[qw_s_args .no_id_errors]} { ::if {[qw_s_args .no_id_errors]==1} { ::append ::Text [h3 "[qw_s_args .no_id_errors] employee has no I.D."] } else { ::append ::Text [h3 "[qw_s_args .no_id_errors] employees have no I.D."] } ::append ::Html [::subst $::Text]; ::append ::Html [p {All employees on a payroll must have their I.D. set before a Payrun can be created.}]; ::set ::Text ""; ::append ::Text {Employees with no ID will also not have any earnings or deduction accounts set up, so in addition }; ::append ::Text {to setting the employee ID, you will also need to create accounts for the employee, and set their}; ::append ::Text {earnings amount(s).} ::append ::Html [p $::Text]; ::set ::Text ""; ::append ::Text {This error can also be caused by accidentally adding an employee to the employee list. }; ::append ::Text {If this is the case, then you can simply delete the blank employee line from the employee list.}; ::append ::Html [p $::Text]; ::switch -- [qw_s_args .payroll_country] { "CANADA" {::set ::ManualPage "150220041018164350";} "USA" {::set ::ManualPage "907020050419095720";} } ::append ::Html [ul {[li {[link .chm $::qw_manual_file .id $::ManualPage {More on Setting Up Employees}]}]}]; } ::set ::Text ""; ::if {[qw_s_args .no_account_errors]} { ::if {[qw_s_args .no_account_errors]==1} { ::append ::Text [h3 "Employee [qw_s_args .no_account_ids] has no accounts set up."] } else { ::append ::Text [h3 "Employees [::linsert [qw_s_args .no_account_ids] end-1 and] have no accounts set up."] } ::append ::Html [::subst $::Text]; ::set ::Text ""; ::append ::Text {Before an employee can be paid, they must have earnings and deduction accounts set up.}; ::append ::Html [p $::Text]; ::switch -- [qw_s_args .payroll_country] { "CANADA" {::set ::ManualPage "150220041020190828";} "USA" {::set ::ManualPage "857720041229115343";} } ::append ::Html [ul {[li {[link .chm $::qw_manual_file .id $::ManualPage {More on Setting Up Employee Accounts}]}]}]; } ::set ::Text ""; ::if {[qw_s_args .no_earnings_errors]} { ::if {[qw_s_args .no_earnings_errors]==1} { ::append ::Text [h3 "Employee [qw_s_args .no_earnings_ids] has no earnings set up."] } else { ::append ::Text [h3 "Employees [::linsert [qw_s_args .no_earnings_ids] end-1 and] have no earnings set up."] } ::append ::Html [::subst $::Text]; ::set ::Text ""; ::append ::Text {Each employee on the payroll must have at least one earnings account with either a flat rate of pay set, }; ::append ::Text {or a rate set together with the Quantity/Time set to input. The employees listed above have no amounts set, therefore they cannot be paid.}; ::append ::Html [p $::Text]; ::set ::Text ""; ::append ::Text {You must either set an earnings amount for each employe, or, if the employee should not be paid, then set the employee's }; ::append ::Text {status to inactive.}; ::append ::Html [p $::Text]; ::switch -- [qw_s_args .payroll_country] { "CANADA" {::set ::ManualPage "150220041020191430";} "USA" {::set ::ManualPage "857720041229115516";} } ::append ::Html [ul {[li {[link .chm $::qw_manual_file .id $::ManualPage {More on Setting Earnings Amounts}]}]}]; } ::append ::Html ""; ] } } /907020050328135150 { .title "Attempted to manually add a pay check transaction." .id 907020050328135150 .tags {error} .body { [p { Paychecks are created by NewViews Payroll, and cannot be created "by hand". }] } } /907020050328135200 { .title "Attempted to delete the anchor date." .id 907020050328135200 .tags {error} .body { [p { Once an anchor date has been set, you cannot delete it. You can change it if you choose, however. }] } } /907020050328135210 { .title "Anchor date must be a month end." .id 907020050328135210 .tags {error} .body { [/* { _s_args .pay_frequency */ }] [p { For a pay frequency [::sargs::get $_s_args .pay_frequency], the pay period end anchor date must be a month-end. }] } } /907020050328135220 { .title "Attempted to change the pay frequency of a payroll that has payruns." .id 907020050328135220 .tags {error} .body { [p { Once Payruns have been created in a a payroll, you cannot change the pay frequency. }] } } /907020050328135230 { .title "Expected pay frequency of 1, 4, 12, 13, 24, 26, or 52." .id 907020050328135230 .tags {error} .body { [/* { _s_args .after */ }] [p { [::sargs::get $_s_args .after] is not one of the pay frequencies supported by NewViews payroll. }] } } /907020050328135250 { .title "Attempted to create an employee on a payroll that has sub-payroll(s)." .id 907020050328135250 .tags {error} .body { [p { The payroll you are attempting to create an employee on has sub-payrolls below it. Please move to one of the sub-payrolls and add the employee there. }] } } /907020050328135300 { .title "Attempted to delete a payroll that has employees." .id 907020050328135300 .tags {error} .body { [p { You cannot delete a payroll if it contains employees. }] [p { If necessary, you can move the employees from this payroll to another one, then the payroll can be deleted. }] } } /907020050328135310 { .title "Attempted to create a payrun on a payroll that has sub payrolls." .id 907020050328135310 .tags {error} .body { [p { The payroll you are attempting to create an payrun on has sub-payrolls below it. Please move to one of the sub-payrolls and add the payrun there. }] } } /907020050328135320 { .title "Attempted to create a payrun but the payroll anchor date has not been set." .id 907020050328135320 .tags {error} .body { [p { The payroll's Pay Period End Anchor Date has not been set, therefore you cannot add any Payruns. }] [p { Please set this date on the payroll settings and then try to create the Payrun again. }] } } /907020050328135330 { .title "Attempted to create a payrun but the pay frequency has not been set." .id 907020050328135330 .tags {error} .body { [p { The payroll's pay frequency has not been set, therefore you cannot add any Payruns. }] [p { Please set the pay frequency on the payroll settings and then try to create the Payrun again. }] } } /907020050328135340 { .title "Attempted to create a payrun on a payroll that has no employees." .id 907020050328135340 .tags {error} .body { [p { The payroll either has no employees. Since there are no active employees, a Payrun will not be created. }] } } /907020050328135410 { .title "Attempted to manually add a pay check transaction." .id 907020050328135410 .tags {error} .body { [p { Paychecks are created by NewViews Payroll, and cannot be created "by hand". }] } } /907020050328135520 { .title "Percentage base contains unknown account suffix(es)." .id 907020050328135520 .tags {error} .body { [/* { _s_args .suffix_list */ }] [p { The expression you have entered contains suffixes that do not exist in this employee's accounts. }] [p { [::sargs::get $_s_args .suffix_list] }] } } /314120061116123927 { .title "You cannot clear the employee id if the employee has accounts." .id_old 907020050328135540 .id 314120061116123927 .tags {error} .body { [p { You cannot clear the employee id of employee [qw_field_value [qw_s_args .employee_id]] because this employee has [qw_field_value [qw_s_args .account_count]] accounts. }] [p { Employees have accounts used to track their accounting information and these accounts use the employee id as a prefix in their account names to keep them unique and to associate them with the employee. Therefore the employee must have a non-empty employee id if there are accounts associated with the employee. }] } } /314120061116124657 { .title "Employee id XXX contains invalid characters." .id_old 907020050328135550 .id 314120061116124657 .tags {error} .body { [p { Employee ids can have only letters and digits. They cannot contain spaces or special characters. }] } } /314120061116125817 { .title "XXX payroll already has an employee with employee id XXX." .id_old 907020050328135600 .id 314120061116125817 .tags {error} .body { [p { Each employee must have a unique employee id. An employee already exists with employee id [qw_field_value [qw_s_args .after]]. }] } } /907020050909144740 { .title "Attempted to delete an employee's payroll reference." .id 907020050909144740 .tags {error} .body { [p { Every employee must belong to a payroll. You can change the payroll by pressing [qw_key F3] to pick. }] } } /907020060309152217 { .20060207_build_change {} .title "Cannot process the Payrun: Pay period has invalid length." .comment {s_args==.pay_frequency .start_date .end_date .days .minimum .maximum} .id 907020060309152217 .tags {error} .body { [p { The payrun start and end dates are set to [::sargs::get $_s_args .start_date] and [::sargs::get $_s_args .end_date], which results in a pay period length of [::sargs::get $_s_args .days] days. }] [p { [::sargs::get $_s_args .days] days is either less than the minimum pay period length of [::sargs::get $_s_args .minimum] days, or greater than the maximum pay period length of [::sargs::get $_s_args .maximum] days. }] [p { To process this payrun you must first edit the pay period start and/or end dates so that the length of the pay period is [::sargs::get $_s_args .minimum] days or more, and [::sargs::get $_s_args .maximum] days or less. }] [p { (For semi-monthly payrolls, the minimum is the minimum number of days in a half-month, which is 14, and the maximum is the maximum number of days in a half-month, which is 16. For monthly payrolls, the minimum is the minimum number of days in a month, which is 28, and the maximum is the maximum number of days in a half-month, which is 31.) }] } } /907020060309152928 { .20060207_build_change {} .title "Cannot process the Payrun: The pay period start date is after the end date." .comment {s_args==.start_date .end_date} .id 907020060309152928 .tags {error} .body { [p { The payrun start date [::sargs::get $_s_args .start_date] is after the end date [::sargs::get $_s_args .end_date]. }] [p { To process this payrun you must first edit the pay period start and/or end dates so that the start date is before the end date. }] } } /907020060309154257 { .20060207_build_change {} .title "Cannot process the Payrun: There is another payrun for the same pay year & period but the pay period start date is not the same." .comment {s_args==.this_year .this_number .this_start_date .this_end_date .other_year .other_number .other_start_date .other_end_date} .id 907020060309154257 .tags {error} .body { [p { This payroll contains another payrun with the same pay period year ([::sargs::get $_s_args .this_year]) and number ([::sargs::get $_s_args .this_number]). }] [p { Payruns for the same pay period must have the same start and end dates, but the start date of the other payrun is [::sargs::get $_s_args .other_start_date], which is different from the start date of this payrun [::sargs::get $_s_args .start_date]. }] [p { To process this payrun you must first edit the pay period start date to [::sargs::get $_s_args .other_start_date] so that it matches the other payrun. }] } } /907020060309154401 { .20060207_build_change {} .title "Cannot process the Payrun: There is another payrun for the same pay year & period but the pay period end date is not the same." .comment {s_args==.this_year .this_number .this_start_date .this_end_date .other_year .other_number .other_start_date .other_end_date} .id 907020060309154401 .tags {error} .body { [p { This payroll contains another payrun with the same pay period year ([::sargs::get $_s_args .this_year]) and number ([::sargs::get $_s_args .this_number]). }] [p { Payruns for the same pay period must have the same start and end dates, but the end date of the other payrun is [::sargs::get $_s_args .other_end_date], which is different from the end date of this payrun [::sargs::get $_s_args .end_date]. }] [p { To process this payrun you must first edit the pay period end date to [::sargs::get $_s_args .other_end_date] so that it matches the other payrun. }] } } /907020060309154458 { .20060207_build_change {} .title "Cannot process the Payrun: The payrun begin date must be one day after the prior pay period end date." .comment {s_args==.this_year .this_number .this_start_date .this_end_date .other_year .other_number .other_start_date .other_end_date} .id 907020060309154458 .tags {error} .body { [p { A payrun exists for the prior pay period [::sargs::get $_s_args .other_number] of [::sargs::get $_s_args .other_year], and the pay period end date specified in that payrun is [::sargs::get $_s_args .other_end_date]. }] [p { This payun (for pay period [::sargs::get $_s_args .this_number] of [::sargs::get $_s_args .this_year]) has a start date of [::sargs::get $_s_args .this_start_date], which is not the day after the prior period ended. }] [p { To process this payrun you must first edit the pay period start date to [::sargs::get $_s_args .correct_date] so that it follows the other pay period correctly. }] } } /907020060309154615 { .20060207_build_change {} .title "Cannot process the Payrun: The payrun end date must be one day before the next pay period start date." .comment {s_args==.this_year .this_number .this_start_date .this_end_date .other_year .other_number .other_start_date .other_end_date} .id 907020060309154615 .tags {error} .body { [p { A payrun exists for the next pay period [::sargs::get $_s_args .other_number] of [::sargs::get $_s_args .other_year], and the pay period start date specified in that payrun is [::sargs::get $_s_args .other_start_date]. }] [p { This payun (for pay period [::sargs::get $_s_args .this_number] of [::sargs::get $_s_args .this_year]) has an end date of [::sargs::get $_s_args .this_end_date], which is not the day before the next period started. }] [p { To process this payrun you must first edit the pay period end date to [::sargs::get $_s_args .correct_date] so that it predates the next pay period correctly. }] } }