| Absences shift group code |
The shift group code that contains shifts that are considered to be absences. |
Select the shift group that identifies the shifts that are considered absences |
String value |
Time; Shifts |
| Advance recovery deduction code |
The deduction code used to recover an advance. |
Usually, "Advance Recovery"; the benefit/deduction code used for the deductions that recover an advance |
String value |
Advances |
| Allow backdated late changes |
Indicates if late backdated changes are allowed/required. |
When a worker has time or earning transactions that have not yet been included in a payment, Payroll always prevents HR users from making worker employment or position assignment date changes that would result in the worker no longer being active in the related position on the dates of those transactions. An exception message appears, and those unprocessed transactions must be deleted, or updated with a date within the assignment date range or negated and paid out.
This parameter controls how HR behaves when users make worker employment or position assignment date changes that would result in the worker no longer being active in the related position on the dates of transactions that have already been paid. A worker has time or earning transactions that have already been paid.
Select "No" to prevent HR users from making the change until a Payroll user has negated the value of earnings associated with that position on all dates that the worker will no longer be assigned to the position. Select "Yes" to allow HR to make the change. The transactions will remain with their original dates, and any adjustments will need to be made using a date on which the worker was active in the position.
|
String value |
HR; Employment; Termination; Position assignments; Earnings |
| Allow employment factor total to exceed 1.00 |
Whether the total of employment factors from all of a worker’s active positions exceeds 1.00. |
If the "Use HR position's full-time equivalent factor" parameter in this list is "No", then set this parameter to "Yes" if the total of the Employment factor (FTE) values from a worker who has multiple positions active at the same time can exceed 1.0. Set this parameter to "No" if you would like the system to ensure that the total for a single worker does not exceed 1.0. |
String value |
FTE |
| Allow Intercompany project postings |
Indicates whether Intercompany project postings are allowed/required |
Usually, "No"; set to "Yes" if you want to associate earnings and their cost burdens to projects in legal entities other than the one in which you are processing those earnings in Anthology Payroll. |
String value |
Project posting |
| AP postings separate invoice/voucher |
Indicates if a separate invoice and voucher is created for each vendor and worker reference. |
"Yes" is recommended |
String value |
Accounts Payable; Postings |
| Cancelled payment type code |
The payment type to be used for cancelled payments. |
Select the payment type that holds the reversing transactions when you cancel a payment |
String value |
Cancel Payments |
| Check accumulators against enrollments |
Indicates if accumulated amounts will be checked for associated ben/ded or gen earning enrollments. |
Select "Yes" if you want the system to advise you if you have not run the "Check accumulated amounts" process before generating payments. |
String value |
Accumulators; Check accumulated amounts; Validation |
| Check clearing account |
The bank account number for the clearing accounts for checks. |
Select the Cash and Bank module bank account that payroll checks will be drawn from. |
String value |
Checks; Cheques |
| Company address type |
Company address type |
The company address for statutory reporting comes from your Legal entity configuration (Organization administration > Legal entities > Addresses). Because a legal entity can have multiple addresses, used for different purposes, you must specify which "Name or description" value identifies the address record that Anthology Payroll should use. It is also used for US work address assessment if a workplace address has not been otherwise specified. |
String value |
Address; Local taxes |
| Company electronic contact type for email |
Company electronic contact type for email |
For statutory reporting of the company email, enter the Type of the Contact information record associated with the legal entity (Organization administration > Legal entities > Contact information). |
String value |
Email |
| Company electronic contact type for telephone |
Company electronic contact type for telephone |
For statutory reporting of the company telephone number, enter the Type of the Contact information record |
String value |
Telephone |
| Database version number |
The version number of the database. This should be the same as the version of the application. |
The software version number from the most recent run of Anthology Payroll > System update utilities > Other > Perform database upgrade. It should match the version number in the title of this General Definitions form. |
String value |
Version |
| Date to be used for AP postings |
Indicates which date is to be used for AP posting transactions. |
Select either Pay period end date or Statement date for the date of Accounts Payable invoices and related posting transactions |
String value |
Accounts Payable; Postings |
| Date to be used for GL postings |
Indicates which date is to be used for GL posting transactions. |
Select either Pay period end date or Statement date for the date of General ledger postings for payments, earnings, deductions, and employer benefits. Note that "GL postings to be summarized" impacts the date of earning-related postings. |
String value |
General ledger; Postings |
| Date to be used for Project postings |
Indicates which date is to be used for Project posting transactions. |
Select either the Pay period end date or Statement date for the date of postings to Project Management and Accounting Hours and Expense journals. |
String value |
Project posting |
| Debug level |
Trace execution. |
Should be 0, unless otherwise directed by the Anthology Support team. |
Integer value |
System |
| Default active date for new code entries. |
Set this date as the active date that is to be placed on all new code entries in the setup tables. |
Usually "1/1/2005"; select a default date for new setup records. |
Date value |
Default |
| Default AP worker vendor text type |
The worker information to be defaulted into the vendor text for AP worker vendors. |
If you want all Accounts Payable invoices to have line items for each worker, select either "Worker Name" or "Worker ID" to determine how individual workers are identified. |
String value |
Accounts Payable; Postings |
| Default payment method code for batch payment run |
The default payment method code used for pay processing. |
Select the default payment method for the Generate Payments and Approve payment process. "Direct deposit" is the usual selection. This default can be overridden when initiating a process. |
String value |
Payment method |
| Default payment method code for checks |
The default payment method code used for checks. |
Select the check payment method to be used when Direct deposit is the default payment method, but a worker does not have a direct deposit bank account. |
String value |
Payment method; Checks; Cheques |
| Default payment method code for manual payment |
The default payment method code for manual payments. |
Select the payment method that will be selected by default when you create a manual payment. If you select direct deposit for a worker who has no bank account information, the default payment method will be what is selected in the "Default payment method code for checks" row. |
String value |
Payment method; Manual payments |
| Default Prenotified value |
Default Prenotified value in new Anthology Payroll worker bank accounts for NACHA direct deposit |
Select "Yes" if you want to create a Prenote file for new worker bank accounts and pay their first payment by check. Otherwise, select "No." |
String value |
Prenotification; Direct deposit; Checks |
| Default union affiliation |
The default union affiliation code. |
If most payroll worker positions share the same Union affiliation code, select it here so that it is automatically selected on Worker Position records when selecting an Occupation, if that Occupation setup record has no Union affiliation selection. |
String value |
Union affiliation; Hours |
| Delete earnings imported by integration |
Indicates if users can delete uncommitted earnings created by your company's custom integration code |
Select "No" to prevent users from deleting records from the Commit Earnings import form that came from Anthology Time Management or Anthology External Earning Lines import. Select "Yes" to enable Anthology Payroll users to delete these records. |
String value |
Integration; Earnings imports |
| Delete time imported by integration |
Indicates if users can delete uncommitted time created by your company's custom integration code |
Select "No" to prevent users from deleting records from the Commit Time import form that came from a custom import, rather than a text file. Select "Yes" to enable Payroll users to delete these records. |
String value |
Integration; Time imports |
| Dims on time and import earns override org splits |
By default, whether dimensions on time and import earnings override org splits |
Select "Yes" if the default setting for the processes that create earnings should populate an earning's dimension set with any dimension set found on the earning import record or time record from which an earning is being generated, overriding the default dimension set defined by the organization split.
Select "No" if the default setting for the processes that create earnings should, when an organization split has been defined, always populate an earning's dimension set with the dimension set defined in that organization split, and ignore any dimension set found on the earning import record or time record from which that earning is being generated.
|
String value |
Postings; Organization splits |
| Direct deposit clearing account |
The bank account number for the clearing accounts for direct deposits. |
Select the Cash and Bank module bank account that direct deposit payments will be drawn from. |
String value |
Emailed payslips |
| Direct deposit email bank account |
Indicates if you want to include the employee's bank account (e.g. ****123) in the email. |
If "Direct deposit email option" is "Yes", select "Yes" if a masked version of the employee's bank account should be included in emails that deliver employee direct deposit pay slips |
String value |
Emailed payslips |
| Direct deposit email company password |
The password to be set on the PDF files so they can be accessed by payroll office staff. |
If "Direct deposit email option" is "Yes", enter a password that administrators can use to open an emailed direct deposit payslip PDF. |
String value |
Emailed payslips |
| Direct deposit email contact message |
The message to be placed in the email telling employees how to contact the payroll office. |
If "Direct deposit email use default wording" is "No," enter instructions for employees wanting to contact your payroll team. |
String value |
Emailed payslips |
| Direct deposit email contact name and telephone |
The name and/or telephone number that is to be placed in the email for contact purposes. |
If "Direct deposit email option" is "Yes", select a payroll contact name and/or telephone number that will be included in the email delivering direct deposit payslips to employees. |
String value |
Emailed payslips |
| Direct deposit email default email communication |
The default email communication type to be used if the email address is to come from address book. |
If "Direct deposit email option" is "Yes", select the Default Email communication type to be used if the email address is coming from an address book. |
String value |
Emailed payslips |
| Direct deposit email default employee password |
The default password to be set on the PDF files so they can be accessed by each employee. |
If "Direct deposit email option" is "Yes", enter a default password that can be used for the PDF in case no password has been configured for the worker. |
String value |
Emailed payslips |
| Direct deposit email opening message |
The opening message to be placed in the email telling employees what they are receiving. |
If "Direct deposit email use default wording" is "No," enter a brief message stating that a direct deposit payslip is attached. |
String value |
Emailed payslips |
| Direct deposit email option |
Indicates if you want to email the direct deposit to employees. |
Usually "No" since employee self-service is a more secure mechanism for online distribution of payslips. Select "Yes" if you want the direct deposit approval process to automatically email payslips to workers with email addresses. |
String value |
Emailed payslips |
| Direct deposit email password protect PDF file |
Indicates if you want to password protect the direct deposit files emailed to the employees. |
Select "Yes" |
String value |
Emailed payslips |
| Direct deposit email use default wording |
Indicates if you want to use the default wording for the email instead of providing messages. |
If "Direct deposit email option" is "Yes", select "Yes" to use the default wording or "No" use the wording in these parameters. |
String value |
Emailed payslips |
| Direct deposit sender's email |
The valid email address that will send the direct deposit emails to the employees. |
If "Direct deposit email option" is "Yes", enter a valid email address that will be used to email direct deposit payslips to workers with email accounts |
String value |
Emailed payslips |
| Earning code for adding salaried time |
The amount-based earning code used for salary earnings. |
Usually "Salary"; select the earning code that will be generated automatically for salaried workers. It should be an amount-based earning. |
String value |
Salary |
| Employer identification number |
The code identifying the Employer - EIN. |
For statutory reporting, enter your company's federal employer identification number (EIN in the United States) |
String value |
Social Security Number; Social Insurance Number; HR |
| Enable Payroll CfMD metadata caching |
Only used in CfMD version. Set to 'Yes' in Production, it can be set to 'No' during CfMD development |
"Yes" is recommended |
String value |
System |
| Export postings to the Accounts Payable module |
Indicates how the module's posting transactions will be processed by Approve Postings. |
Usually "Yes", so that the system will not let users close a pay period before approving Accounts Payable postings of all transactions that should contribute to Accounts Payable invoices. Select "Create CSV file" if Accounts Payable postings should be exported to a text file, for integration with an Accounts Payable system outside of Microsoft Dynamics Finance. Select "No" to let users close a pay period without approving Accounts Payable postings of all transactions that should contribute to Accounts Payable invoices. |
String value |
Postings; Accounts Payable postings; Invoices; Close pay period |
| Export postings to the General Ledger module |
Indicates how the module's posting transactions will be processed by Approve Postings. |
Usually "Yes", so that the system will not let users close a pay period before approving General Ledger postings of all payment, earning, and benefit/deduction transactions and, optionally, entitlement accruals. Select "Create CSV file" if GL postings should be exported to a text file, for integration with an accounting system that is not Microsoft Dynamics Finance. Select "No" to let users close a pay period without approving GL postings of all payment, earning, and benefit/deduction transactions and, optionally, entitlement accruals. |
String value |
Postings; Close pay period |
| Full day time reversal option |
Indicates if all imported time for the whole day must be reversed before applying replacement time. |
Select "Yes" if you are importing time from an integrated system that corrects a day's time entries by negating all of the time for the day and providing a new set of records for that day. The import will fail if any previously-imported time for a day is not fully offset by negating entries when importing shifts for that day. Otherwise, select "No." |
String value |
Time; Shifts; Integration |
| GL postings to be summarized |
The worker's earning postings to GL are summarized by pay period end date instead of date earned. |
Usually "Yes"; so that all earning posting transactions use the date selected in the "Date to be used for GL postings" parameter. Select "No" to use the earning date for earning postings to the General ledger. |
String value |
Postings; Earnings postings |
| Government reporting date type |
The date type used to set the reporting date. This date controls what is included on reports. |
Select "Statement date" for the US or Canada. This selection determines the default value of the Reporting date, which is the date used for statutory reporting. |
String value |
Statutory reporting |
| Identification type used for determining national |
Global address book Identification type used for workers' national ID number. |
The HR Identification type used to record the Social Security Number (US) or Social Insurance Number (Canada), used in statutory reporting. |
String value |
Social Security Number; Social Insurance Number; HR |
| Include blank projects and categories cost |
Include costs from blank projects and categories to create expense journal in project module |
Select "Yes" to include the value of earnings that have no project attributes in the burden being added to earnings that have project attributes when posting burdened costs to Project management and accounting. Select "No" to not include the value of earnings without project attributes in postings to Project management and accounting Hours and Expense journals. |
String value |
Project posting |
| Include occupation code on journal transactions |
Include occupation code when creating journal transactions in project module |
Usually "No". Select "Yes" if you need to populate the Occupation field in Payroll's postings to Project management and accounting Hours and Expense journals. |
String value |
Project posting |
| Include shift code on journal transactions |
Include shift code when creating journal transactions in project module |
Usually "No". Select "Yes" if you need to populate the Shift field in Payroll's postings to Project management and accounting Hours and Expense journals when a payroll Time transaction was the source of an earning being posted to Project. |
String value |
Project posting; Shifts |
| Large currency amounts |
Indicates if the company's currency results in large amounts for reporting. |
Select "Yes" if you want users processing payroll to be alerted when the value of an earning exceeds $10,000. |
String value |
Earnings |
| Last direct deposit number |
The last number used on a printed direct deposit advice. |
Contains the most recent direct deposit statement number that Payroll has used; the next direct deposit will use the next higher unused number. |
Integer value |
Direct deposit |
| Late first payments option |
Indicates if the system will check for the possibility of late first payments for new workers. |
Usually "No"; set to "Yes" if you routinely need to process salaried workers starting in the previous pay period and want to enable Late First Payment processes. |
String value |
Backdated changes |
| Local tax adjust amts exclude manual txns |
Statutory reports add overridden local tax BenDed amts to local tax adjustment worker, emplr amts |
If you have local tax transactions that were manually entered or imported, select "Yes" if the values of those transactions should be included in local tax reporting or "No" if those values have also been recorded in Local Tax adjustment records. |
String value |
Local taxes |
| Local taxes additions to income amount used |
The type of amount to be used for additions to income when deriving local taxes. |
Usually "Full amount". Set to "Apportion" if "Multi-state tax processing" row is "Yes" and you have individual workers subject to local taxes in multiple states. This selection will be the default setting of the "Additions amount used" field for any new Local tax type rule group that the local tax assessment creates automatically in Anthology Payroll > Setup > Tables > Local taxes > Local tax type rule groups. |
String value |
Local taxes |
| Local taxes benefit/deduction group |
The benefit/deduction group that will contain all auto-generated local tax benefit/deductions. |
Should be "US Local Taxes". Used to identify benefit/deduction codes that are local taxes. |
String value |
Local taxes |
| Local taxes deductions from income amount used |
The type of amount to be used for deductions from income when deriving local taxes. |
Usually "Full amount". Set to "Apportion" if the "Multi-state tax processing" row in this table is "Yes" and you have individual workers subject to local taxes in multiple states. This selection will be the default setting of the "Deductions amount used" field for any new Local tax type rule group that the local tax assessment creates automatically in Anthology Payroll > Setup > Tables > Local taxes > Local tax type rule groups. |
String value |
Local taxes |
| Local taxes exemption amount used |
The type of amount to be used for calculation exemptions when deriving local taxes. |
Usually "Full amount". Set to "Apportion" if the "Multi-state tax processing" row in this table is "Yes" and you have individual workers subject to local taxes in multiple states. This selection will be the default setting of the "Exemption amount used" field for any new Local tax type rule group that the local tax assessment creates automatically in Anthology Payroll > Setup > Tables > Local taxes > Local tax type rule groups. |
String value |
Local taxes |
| Local taxes taxable income |
The earning group that will contain all earnings that are taxable for local taxes. |
The earning group that will be the default selection of the "Income earnings" field for any new Local tax type rule group that the local tax assessment creates automatically in Anthology Payroll > Setup > Tables > Local taxes > Local tax type rule groups. |
String value |
Local taxes |
| Locations mandatory on positions |
Indicates if locations are to be mandatory when employee positions are created. |
Usually "No"; select "Yes" to require users to populate the "Location" field of Anthology Payroll worker position records, for example, if it is used to define work addresses for local tax assessment. |
String value |
Locations |
| Manual payment type code |
The default payment type to be used for manual payments. |
Select the default payment type that will be selected when a user opens the Manual payment journal. |
String value |
Manual payments |
| Multiple jurisdiction workers |
Indicates if positions require a Position Filter. |
Select "Yes" if you withhold taxes for multiple US states or Canadian provinces, so that the Position filter field will be required on Worker position records. Otherwise, select "No." |
String value |
Position filter |
| Multi-state tax processing |
Indicates if multiple state/province tax rules are to be applied for state/prov tax calculations. |
Select "Yes" if you withhold taxes for multiple US states in which your workers live and work. Otherwise, select "No." |
String value |
State taxes |
| NACHA Company Description |
Value to be used for populating Company Entry Description for NACHA file. MAX Limit: 10 characters including 'PAYROLL'. |
For NACHA File, enter the value to be used for Company Entry Description. By Default it is 'Payroll' |
String value |
Payment Methods, Bank |
| Negative net deduction code |
The deduction code used to recover negative net payments. |
Usually, "Negative Net Recover"; the benefit/deduction code used for the deductions that recover a negative net. |
String value |
Negative nets |
| Organization split refines recorded earning rate |
Recorded earning rate is Amount divided by hours/units as adjusted by split instead of original rate |
Organization splits may divide a single earning transaction into multiple transactions to allocate its expense to multiple dimension sets. For example, an earning may be split 50/50 between two dimension sets. The Amount of the original earning is divided across those new transactions. If the original earning was $100.25, the split earnings will be $50.12 and $50.13. If the earning is hours-based or unit-based, the number of hours or units will also be divided between the new transactions, using the same proportions. If this example earning was for 1 hour at a rate of 100.25 per hour, then it will be transformed into 2 earning transactions of 0.5 hours each. If this parameter is "No", then the Rate from the original earning will be used on all the earnings created by the split. In this example, $100.25. Note that because of rounding each earning to a whole penny, that original rate multiplied by the Hours or Units and Rate Factor might not exactly match the Amount. If this parameter is "Yes", the Rate of each of the earnings will be recalculated by dividing its Amount by its Hours or Units and Rate Factor. In that case, the Rate of the multiple split earnings can be slightly different from the original earning and each other, again because those earnings needed to be rounded to a penny. In this example, the half-hour $50.12 earning would have a rate of $100.24 and the half-hour $50.13 earning would have a rate of $100.26. |
String value |
Organization splits |
| Override occupation option |
Indicates if an override occupation can be used to control the expense financial dimensions. |
Usually "No". Select Yes to make selections in the "Expense occupation" field on worker Time transactions override the standard "Occupation" field value to identify any applicable Earning account exception rule. |
String value |
Occupations; Earnings postings |
| Pay processing lock override user group |
The user group that is allowed to override pay processing locks. |
If "Pay processing lock override user ID" is empty, you can select a user group. Members of that user group will be able to delete user lock rows (Anthology Payroll > System update utilities > Other > Worker processing locks) and create transactions after the processing threshold selected in the "Pay processing locking type" row in this form, if "Pay processing locking option" is "Lock out users". |
String value |
Locks; Permissions |
| Pay processing lock override user id |
The user who is allowed to override pay processing locks. |
If "Pay processing lock override user group" is empty, you can select a user ID. That user will be able to delete user lock rows (Anthology Payroll > System update utilities > Other > Worker processing locks) and create transactions after the processing threshold selected in the "Pay processing locking type" row in this form, if "Pay processing locking option" is "Lock out users". |
String value |
Locks; Permissions |
| Pay processing locking option |
The locking option to use to control pay processing. |
"No lock out required" means that the system will provide users no feedback if they try to add, modify, or process transactions while pay period processing is underway, as selected in the "Pay processing locking type" parameter.
"Warn users" means that alert messages will be generated, but users will be able to proceed with adding, modifying, or processing transactions while pay period processing is underway, as selected in the "Pay processing locking type" parameter.
"Lock out users" means that only users who are members of the user group selected in the "Pay processing lock override user group" or the user who is selected in the "Pay processing lock override user id" parameter will be able to add, modify, or process transactions while pay period processing is underway, as selected in the "Pay processing locking type" parameter.
|
String value |
Locks; Permissions |
| Pay processing locking type |
The type of locking option to use to control pay processing. |
"Accumulator updates to payment generation" will alert or prevent users adding, modifying, or processing transactions while the following processes are running for the same pay group:
- Update accumulators
- Generate earnings
- Generate payments
"Accumulator updates to pay period close" will alert or prevent users adding, modifying, or processing transactions while the following processes are running for the same pay group:
- Update accumulators
- Generate earnings
- Generate payments
- Generate entitlements
- Approve postings
- Approve project postings
"Payment generation only" will alert or prevent users adding, modifying, or processing transactions while the Payment generation process is running for the same pay group.
Whether users are alerted or prevented from creating transactions is determined by the "Pay processing locking option " parameter.
|
String value |
Locks; Permissions |
| Payroll jurisdiction applicable to the company |
Payroll jurisdiction applicable to the company |
Select the country whose statutory payroll withholding and reporting rules apply. |
String value |
US taxes; Canada taxes |
| Payroll Service Client ID |
Client ID of the Payroll Service as registered in the Azure Active Directory (Azure AD). |
Anthology will provide you the appropriate setting to support your US local tax calculations and reporting |
String value |
US taxes; Local taxes |
| Payroll Service Client Secret |
Secret string shared with Azure Active Directory (Azure AD) to prove the client requesting the token |
Anthology will provide you the appropriate setting to support your US local tax calculations and reporting |
Encrypted value |
US taxes; Local taxes |
| Payroll Service Scope |
The set of resources that the access applies to the Payroll Service. The scopes should be in the form |
Anthology will provide you the appropriate setting to support your US local tax calculations and reporting |
String value |
US taxes; Local taxes |
| Payroll Service Tenant ID |
The unique identifier (ID) of the Payroll Service instance in the Azure Active Directory (Azure AD). |
Anthology will provide you the appropriate setting to support your US local tax calculations and reporting |
String value |
US taxes; Local taxes |
| Payroll version and hot fix currently installed |
Payroll version and hot fix currently installed |
The Anthology Payroll version number, automatically updated when the software is updated. |
String value |
Version |
| Payslip address format |
The address format to be used for payslip. |
Select the Microsoft Dynamics Global address book format to use when printing worker addresses on payslips |
String value |
Payslips |
| Post benefit/deductions based on department |
Indicates if the benefit/deduction postings are prorated by payments' earnings' departments. |
Select "Yes" if departments are used in benefit/deduction account exceptions. Otherwise, select "No" to enhance the performance of the Post Payment and Post Benefits processes. |
String value |
Benefit/deduction postings |
| Post benefit/deductions based on financial dims |
Indicates if the benefit/deduction postings are prorated by payments' earnings' financial dimensions |
Select "Yes."
Select "No" if, for all benefit/deduction postings, the full account string is specified on benefit/deduction setup records and/or benefit/deduction account exceptions.
|
String value |
Benefit/deduction postings |
| Post benefit/deductions based on occupation |
Indicates if the benefit/deduction postings are prorated by payments' earnings' occupations. |
Select "Yes" if occupations are used in benefit/deduction account exceptions. Otherwise, select "No" to enhance the performance of the Post Payment and Post Benefits processes. |
String value |
Benefit/deduction postings |
| Post benefit/deductions based on relief reason |
Indicates if the benefit/deduction postings are prorated by payments' earnings' relief reasons. |
Select "Yes" if relief reasons are used in benefit/deduction account exceptions. Otherwise, select "No" to enhance the performance of the Post Payment and Post Benefits processes. |
String value |
Benefit/deduction postings |
| Post benefit/deductions based on task |
Indicates if the benefit/deduction postings are prorated by payments' earnings' tasks. |
Select "Yes" if tasks are used in benefit/deduction account exceptions. Otherwise, select "No" to enhance the performance of the Post Payment and Post Benefits processes. |
String value |
Benefit/deduction postings |
| Post benefit/deductions based on work reason |
Indicates if the benefit/deduction postings are prorated by payments' earnings' work reasons. |
Select "Yes" if work reasons are used in benefit/deduction account exceptions. Otherwise, select "No" to enhance the performance of the Post Payment and Post Benefits processes. |
String value |
Benefit/deduction postings |
| Prior period shift negation |
Handle unmatched prior period shift negations manually |
Select "Yes" if Time to earnings processing should validate that a Time transaction with negative hours is negating a corresponding positive hours Time transaction on the same date. If there is no corresponding positive transaction, the negative transaction should not be translated into an earning, and it should log an exception so that a user can investigate and correct the problem.
Select "No" if the Time to earnings process should generate an earning with a negative value for a shift transaction with a negative number of hours that does not have a corresponding shift transaction with positive hours.
|
String value |
Time; Shifts; Integration |
| Prior period time can trigger pay period salary |
Time to Earnings adds pay period salary if processing time on salaried position not paid that period |
Usually "Yes"; when processing earnings dated in a previous pay period for a salaried position, the salary earnings for the whole pay period will be verified and adjusted if necessary. Select "No" to limit the recalculation of salary to the date of the prior period earning being processed. |
String value |
Backdated changes |
| Project expense journal name |
Project expense journal name |
To post burdened costs of amount-based and unit-based earnings to Project Management and Accounting, select the destination Expense journal. |
String value |
Project posting |
| Project hours earning group |
Hours associated with earnings in this earning group will be sent to project module. |
Usually, all hours-based earnings whose costs are being posted to Project should contribute to the number of hours. If, however, there may be hours-based earning codes whose hours should NOT be added to the count of hours in the Hours journal, create an earning group of only the earnings whose hours SHOULD be counted and select that earning group here. The Amount value of hours-based earnings that don't belong to this group will be included in the total value posted to Project, without contributing to the total hours. |
String value |
Project posting |
| Project hours journal name |
Project hours journal name |
To post burdened costs of hours-based earnings, as well as any unit-based or amount-based earning codes that originated as Shift transactions, to Project Management and Accounting, select the destination Hours journal. |
String value |
Project posting |
| Project hours postings include zero-cost records |
Postings to Project hour journals include all non-zero hour transactions, even when cost is 0. |
Select "Yes" if you have hours-based earnings whose hours should be posted to Project Hours journal, even when their Amount is zero. Select "No" if these earnings' hours should not be posted to project when their Amount is zero. |
String value |
Project posting |
| Project reversal expense journal name |
Project reversal expense journal name |
No longer used |
String value |
|
|
Project reversal hour journal name
|
Project reversal hour journal name |
No longer used |
String value |
|
| Regular payment type code |
The payment type to be used for regular payments. |
Select the default payment type to be used by the Payments Generation process. Usually "Regular". This default can be overridden when generating payments. |
String value |
Payments |
| Revised payment net deduction code |
The deduction code used to recover revised payment amounts. |
Select the benefit/deduction code to be used to deduct the balance owing when the Revised Payment process has identified an under-deduction. |
String value |
Revised payments |
| Rotation days option |
Indicate which days will be used to determine rotation shifts. |
If you use the Time from Rotations process, then select "Rotation shifts on position's work days" if, by default, shifts should be created for only the days of the week that are set to "Yes" on the payroll worker position record.
Select "All rotation shifts" if most of your rotations are multi-week rotations that don't follow a days-of-the-week pattern, so the days of the week selections on the payroll worker position record should be ignored.
Note that this selection can be overridden for individual worker positions."
|
String value |
Rotations; Time; Shifts; Create time from rotation |
| Salary calculation option |
How the pay period's salary is divided among the days in a pay period. |
Salary earning transactions have an implied number of hours and a rate, which are used when calculating the value of included and replacement earnings for the same day. This parameter identifies the usual mechanism for dividing salary earnings across the days in the pay period. This default can be overridden on individual payroll worker positions.
Select "Work day hours from daily hours" to have payroll use the "Daily hours" from the payroll worker position or its Union affiliation. Note that for monthly or semi-monthly pay periods, which divide the consistent salary total across a varying number of work days in the period, this means that the Rate will be slightly lower in periods with more days, but the number of hours per day will be constant.
Select "Work day hours from pay period hours" to have payroll use the "Pay period hours" from the payroll worker position or its Union affiliation. Note that for monthly or semi-monthly pay periods, which divide the consistent salary total across a varying number of work days in the period, this means that the number of hours will be slightly lower in periods with more days, but the Rate will be constant.
Select "Rotation hours with same pay for each day" if most worker positions have rotations, to have payroll pay the same salary amount each day, use the hours indicated by the rotation, and calculate the rate by dividing the daily salary value by those hours.
Select "Rotation hours with pay based on rate times hours" if most worker positions have rotations, to have payroll use the hours indicated by the rotation for all the days in the pay period, divide the pay period salary by teh total of those hours in the pay period to determine a consistent rate for the pay period, resulting in different salary amounts on days with a different number of hours in the rotation.
|
String value |
Salary |
| Salary rotation shift filter |
Rotation shifts that should be included in salary calculations or excluded (see role). |
If you have workers whose salary is based upon their rotation and one or more rotations include shifts that should NOT generate salary, select a shift group identify which should or should not generate salary. Use the "Salary rotation shift filter role" parameter to specify whether this group of shifts contains the ones that are included in or excluded from salary. |
String value |
Salary; Rotations |
| Salary rotation shift filter role |
Whether filter shifts should be included in or excluded from salary calculations. |
If you have workers whose salary is based upon their rotation and one or more rotations include shifts that should NOT generate salary, use the "Salary rotation shift filter" parameter to select a shift group. If that group of shifts are the shifts that should NOT create salary, then select "Excluded". If that group of shifts are the shifts that identify time that should be paid by salary, then select "Included". |
String value |
Salary; Rotations |
| Salary use FTE |
Indicates if new workers/positions will default to having salary adjusted by FTE employment factor. |
Select "Yes" if, by default, the worker position's assigned salary should be multiplied by their FTE/Employment factor. Select "No" if, by default, the assigned salary should be applied, regardless of FTE/Employment factor. Note that this selection can be overridden on individual worker positions. |
String value |
Salary |
| Save report days |
The number of days to keep extracted report information |
The number of days that the reports retrieved from the Report Runs form (Anthology Payroll Reports > Report runs) should be retained.
This setting does not impact the files available in the Download files to local network form (Anthology Payroll > Periodic > Download files to local network).
|
Integer value |
Reporting; System |
| Separate deposits from pay statements |
Indicates if deposits and pay statements will be created by separate runs of approve payments. |
In the "Approve selected payments" form, users can
- select one or more check payments to approve and print
- select one or more direct deposit payments to approve and generate direct deposit files and pay slips for
If this parameter is set to "No," all those steps happen when you select the "Approve" button in the "Approve selected payments" form.
If this parameter is set to "Yes," the "Approve selected payments" form has both an "Approve" button and a "Create/print pay statements" button.
The "Approve" button does the equivalent of the Create bank information menu item:
- For check payments, approves payment and allocates check number from Cash and Bank management, but does not print the checks yet.
- For direct deposit payment, approves payments and generates direct deposit file.
The "Create/print pay statements" button does the equivalent of the "Prepare pay statements" and "Print pay statements" menu items:
- For check payments, prints the checks.
- For direct deposit prints the payslips.
|
String value |
Approve payments; Direct deposits; Checks; Cheques; Payslips; Background processing |
| Should national IDs be unique |
Should national IDs be unique |
"Yes" prevents you from saving a worker's national ID if it duplicates the selection for another worker.
"No" allows duplicates, which may be required if using a temporary ID.
|
String value |
Social Security Number; Social Insurance Number; HR |
| Start date to be used for HR worker bank accounts |
Indicates which start date is to be used for HR worker bank accounts. |
Select the date to be used as the worker account active date in Payroll when initializing the worker bank account integration between HR and Payroll (the "Synchronize Anthology Payroll with HR worker bank accounts" process). |
Date value |
HR; Bank accounts; Worker bank accounts; Direct deposits |
| Summarize bank deposits |
Indicates if the direct deposit transactions are to be summarized when sent to the bank module. |
Usually, "Yes", to create one transaction in the Cash and Bank management module for the full value of a direct deposit file.
"No" will create one transaction in the Cash and Bank module for each payment within a direct deposit file.
|
String value |
Postings; Post payments; Cash and bank module |
| Tax lookup engine name |
Name of the tax lookup engine to be used to derive local taxes. |
Anthology will provide you the appropriate setting to support your US local tax calculations and reporting |
String value |
US taxes; Local taxes |
| Tax lookup engine option |
Indicates if a tax lookup engine will be used to derive local taxes. |
Select "Yes" to withhold US local taxes. Otherwise, select "No". |
String value |
US taxes; Local taxes |
| Tax lookup engine web service URL address |
URL address for web service that calls the tax engine for determining local taxes. |
Anthology will provide you the appropriate setting to support your US local tax calculations and reporting |
String value |
US taxes; Local taxes |
| The same worker account code is used for different |
Allow same employee bank account number for different account types. |
"Yes" allows a worker to have direct deposit go to different bank account types (e.g., Checking and Savings) with same bank account number.
"No" prevents a worker from using the same bank account number for different bank account types.
|
String value |
Bank accounts; Worker bank accounts; Direct deposits |
| US Payroll Jurisdiction database version number |
The version number of the database. This should be the same as the version of the US Payroll Jurisdiction |
The Anthology Payroll localization version number, automatically updated when the software is updated. |
String value |
Version |
| Use bank's financial dimensions on payments debits |
Indicates if bank's fin dims will be used on payment's debit entry if no fin dims could be derived. |
"Yes" uses the financial dimension set defined for the bank account in Cash and Bank Management module for the debit transaction generated by payroll's Post Payments process, unless a dimension set is defined for the Payroll Clearing Account row in the Pay group ledger account form (Anthology Payroll > Setup > Tables > Payroll > Pay group ledger accounts).
"No" means that both the main account and dimension set for the debit transaction generated by payroll's Post Payments process is defined by the Payroll Clearing Account row in the Pay group ledger account form (Anthology Payroll > Setup > Tables > Payroll > Pay group ledger accounts).
|
String value |
Postings; Post payments; Cash and bank module; GL postings |
| Use debit financial dimensions |
Indicates if the debit's fin dims will be used on the credit entry where fin dims not specified. |
"Yes" means that, unless there is another dimension set source, the dimension set used for the credit transaction will match the dimension set used for the debit transaction.
"No" means that unless the credit dimension set is specified on the relevant payroll setup table, the credit transaction will not have dimension values.
|
String value |
Postings |
| Use HR benefit plans |
Indicates if the benefit plans in HR are to be used for payment generation. |
Select "Yes" to enable HR Benefits Management to manage worker enrollments in the benefit/deductions configured in the ***Benefits integration*** setup form. |
String value |
Benefits; Integration; HR |
| Use HR Compensation Module option |
Indicates if the HR Compensation Module plans are used to control salary/generated earnings. |
Usually "Yes"; Payroll uses wage rates defined in HR Compensation. Select "No" if you wish to manage worker position wage rates within Payroll |
String value |
Wage rate |
| Use HR position's full-time equivalent factor |
Indicates if the HR position's full-time equivalent factor is used instead of Anthology Payroll FTE. |
Select "Yes" to have Payroll calculations use the HR position's "Full-time equivalent" field and make the payroll worker position's "Employment factor (FTE)" field inactive. Select "No" to have Payroll calculations use the payroll worker position's "Employment factor (FTE)" field. |
String value |
FTE; Wage rate |
| Use HR worker bank accounts |
Indicates if the worker bank accounts in HR are to be used in the Anthology Payroll module. |
Select "Yes" to use HR worker bank account and bank account disbursement records for payroll direct deposits and make that information view-only in Anthology Payroll's worker bank account form. Select "No" to manage workers' direct deposit accounts in Anthology Payroll's worker bank account form. |
String value |
Direct deposit; Worker bank accounts |
| Use HR worker's financial dimensions |
Indicates if the HR worker's financial dimensions will be considered for an expense's dimensions. |
Select "Yes" to use the HR worker financial dimension set when there is no relevant worker position dimension set or overriding organization splits. |
String value |
Postings |
| Use project address for local taxes |
Indicates if project address will be used to derive local taxes. |
Usually "No"; you do not need to refer to project addresses to determine work addresses for local tax assessment. Select "Yes" if you have workers who work at a variety of locations subject to local taxes, and you are using project addresses to track those locations. |
String value |
Local taxes; Project |
| Use Talent |
Indicates if the Talent module is used to maintain workers/positions instead of the HR module. |
Select "No" |
String value |
HR |
| Vendor invoice journal name |
The journal name used to create AP invoices. |
Select the Journal in which Payroll should post its Accounts Payable invoices |
String value |
Accounts Payable; Postings |
| Work location address type |
The location's address type code to be used to derive the work address for local taxes. |
In Location address lists (Anthology Payroll > Setup > Tables > Organization > Locations > Setup > Addresses), the "Address type" value that identifies work addresses used for US local tax assessment. |
String value |
Local taxes; Address |
| Worker checking account type |
The account type representing worker's checking account for direct deposit. |
Select the Account type that means Checking accounts. Used when populating direct deposit files. |
String value |
Direct deposit; Worker bank accounts |
| Worker electronic contact type for email |
Worker electronic contact type for email |
In HR worker Contact information lists, the "Description" value that identifies the "Email address" type record used for payroll-related emails, including US W-2 online access and emailed direct deposit payslips. |
String value |
Emailed payslips; Email; HR |
| Worker home electronic contact |
The electronic contact type code that represents the worker's home telephone. |
In HR worker Contact information lists, the "Description" value that identifies the "Phone" type record used for the worker's home phone number in the Worker list report. |
String value |
HR |
| Worker savings account type |
The account type representing worker's savings account for direct deposit. |
Select the Account type that means Savings accounts. Used when populating direct deposit files. |
String value |
Direct deposit; Worker bank accounts |
| Working set option |
Indicates if you want to use working sets for processing workers on client. |
"Yes" is recommended for improved performance in processes that can be multi-threaded |
String value |
Performance; Batch processing |
| Working set size |
Indicate the number of workers to be placed in each working set for multi-threading. |
Enter a number of workers for each multi-threaded working set. 10 is recommended. |
Integer value |
Background processing; Batch processing; Performance |
| Working set size batch accumulators |
Indicate the number of accumulators per working set for batch multi-threading delete/set accumulators |
Enter a number of accumulators for each multi-threaded working set when re-calculating accumulators. 5 is recommended |
Integer value |
Background processing; Batch processing; Performance |
