Help
Search for a message or symptom from the Payroll tasks. Messages in quotation marks are shown verbatim in the application; %1 is replaced by a value, such as a payout number. If you are unsure about the accounting treatment, ask your accountant or system administrator to confirm it before repeating an action.
Employees and pay types
| Message or symptom | Explanation | What to do |
|---|---|---|
| An employee or pay type appears as undefined after importing vacation and sickness entries. | The import skips a row if it cannot find the employee or pay type, or if the pay type has no vacation import type. | Create or correct the employee/pay type and configure its import type, then import a file with only the rejected rows. Importing the whole file again doubles the hours of the accepted rows. See register vacation, sickness, and sick-child entries. |
| Pay types appear on one line instead of several. | Prerequisite lines with the same pay type are combined unless the pay type is configured to keep them separate. | Review Don't combine on paycheck on the pay type. See the pay type reference. |
| A salary group or salary step cannot be found. | The agreement, salary group, step, or effective period does not cover the payout date. | Review the agreement, group, step, and validity period. See set up salary agreements. |
| Paytypes with code below 900 are reserved for system paytypes, are you sure you want to create a paytype with this code? | This confirmation appears when a numeric pay-type code is below 900. Payroll Setup skips the confirmation. | Enter a code that is not reserved for system pay types, or confirm only if you intend to create a system pay type. |
| Cancelled by user | This appears after a user declines the confirmation for a numeric pay-type code below 900. | Enter a different code, or confirm only if you intend to use a reserved code. |
| Specify "Def. Customer Posting Group" in Payroll Setup | This prevents creating a customer from an employee when the default customer posting group is missing from Payroll Setup. | Enter the default customer posting group in Payroll Setup, then try again. |
| Specify "Def. Gen. Bus. Posting Group" in Payroll Setup | This prevents creating a customer from an employee when the default general business posting group is missing from Payroll Setup. | Enter the default general business posting group in Payroll Setup, then try again. |
| Specify "Def. VAT Bus. Posting Group" in Payroll Setup | This prevents creating a customer from an employee when the default VAT business posting group is missing from Payroll Setup. | Enter the default VAT business posting group in Payroll Setup, then try again. |
| Create customer …? | This confirmation appears when Payroll is about to create a new customer from an employee. | Confirm only if you intend to use the employee number as the new customer number. See create a customer from an employee. |
| Are you sure you want to erase all values for this pay type? | This confirmation appears when you are applying a new value of zero. If you confirm, Payroll erases the values for every employee wage component that uses this pay type. | Select No unless you intend to clear all those values. See update an employee pay type. |
Paychecks
| Message or symptom | Explanation | What to do |
|---|---|---|
| The paycheck is gone after selecting Fetch Again from Prerequisites. | The action rebuilds all lines and deletes the paycheck if no pay is found. It also deletes manually entered lines. | Check the prerequisites and the employee's pay types. Re-enter manual lines if they are still needed. See reviewing paychecks. |
| A paycheck cannot be emailed. | Payroll needs the Paycheck report and the employee's email address to create and send a PDF paycheck. | Check the report in Payroll Setup and the email address on the Employee Card. See emailing paychecks. |
| Bank sending stops or the payment journal does not open. | Employee bank details or Payroll Banking setup is missing or invalid. | Review the employee's bank details and Payroll Banking fields in Payroll Setup. See set up bank payments. |
Tax cards
| Message | Explanation | What to do |
|---|---|---|
| Tax Card Out can not be in the same month as Tax Card In. | The tax card handout and receipt dates are in the same month. | Choose a handout date in a different month from the receipt date. See registering a tax card as handed out. |
Payouts
| Message | Explanation | What to do |
|---|---|---|
| Payout … is closed. | The payout is locked. Actions that change prerequisites or create payment journal lines are not allowed. | Reopen the payout if its status allows it, or create a correction according to your organization's procedure. Do not repeat a payment until you have confirmed whether it was already made. |
| The Payout needs to be closed before posting. | The posting action requires a closed payout. | Run the error check and close the payout before posting. See close a payout. |
| Payout … has been posted and cannot be reopened. | A posted payout cannot be reopened with the regular reopen action. | Review the posted payout. If a correction is needed, use the appropriate reversal process and ask an accountant to review the impact. See process a posted payout. |
| This payout is only for employee group … | The payout is assigned to a category that does not match the employee the action is trying to process. | Select the correct category or use a payout for that employee. See set up employee categories. |
| Payout … has not been error checked. Print Test Report? | This confirmation appears when you close a payout that has not been error checked. | Select Yes to run the test report before closing. If you select No, the payout does not close. |
| Payout … can not be closed, needs to be error checked. | This appears if you decline to error-check the payout when prompted. | Run the test report and correct any issues before trying again. |
| Error in Payout. Review Payout? | The test report did not mark the payout as error checked, so closing stops. | Review the test report results and resolve the findings before trying again. |
| Close Payout …? | This confirmation appears after the payout has been error checked. | Select Yes only when you have finished reviewing and are ready to lock the payout against changes. |
| Only a posted payout can be reversed | The reversal action is only for posted payouts. | Confirm the payout status. Correct an unposted payout in the processing workflow, not by reversing it. |
Vacation and sickness
| Message or symptom | Explanation | What to do |
|---|---|---|
| The import reports undefined employees or pay types. | The entries are shown in the result but are not imported. | Correct the employee/pay type codes or the Vacation Import Type setting, then import a file with only the rejected rows. Importing the whole file again doubles the hours of the accepted rows. |
| Payout … is closed. | Vacation and sickness imports cannot change a locked payout. | Select an open payout or reopen it if allowed. See register vacation, sickness, and sick-child entries. |
IRS
| Message or symptom | Explanation | What to do |
|---|---|---|
| A salary statement is missing a line, or a pay type does not appear on it. | The pay type is not linked to an IRS statement line, or the line is not mapped for that year. | Review Tax Submission Line on the pay type and the field mapping for the year. See create salary statements. |
| The IRS statement or deduction is rejected. | IRS submission requires correctly configured email addresses, claim parties, and pay types; the web service may also return its own error. | Review IRS setup, the payout response, and the data being sent. For a web-service error, check with the tax authority or your system administrator. See IRS setup, send a withholding-tax statement, and send an IRS deduction. |
| Payout … is closed. | The submission action is working with a locked payout, which cannot be changed while locked. | First confirm whether the submission was already sent. If not, follow your organization's process to reopen or correct the payout. |
Pension submissions
| Message or symptom | Explanation | What to do |
|---|---|---|
| Submissions stop before all pension funds have been sent. | Submissions are sent to claim parties in sequence. An error for one claim party can stop later submissions. | Review the payout responses, correct the claim-party error first, and send only what is still unsent. See send pension contributions. |
| The web service rejects the submission. | Claim-party credentials, web-service details, or required employee data may be missing, or the service may return an error. | Review the claim party, credentials, and employee SSN. Use the payout response to identify the data to correct. |
| Payout … is closed. | Pension submissions require a closed payout. | Error-check and close the payout before sending. |
Bank payments
| Message | Explanation | What to do |
|---|---|---|
| Missing Bank Account Number information in Payroll Setup | The bank-payment action could not find the account to pay from. | Review the bank account number in Payroll Banking setup or the payroll bank account. See set up bank payments. |
| Not all paychecks are sent to the bank at once. | PDF paycheck delivery can use multiple batches. The result can therefore show that some batches succeeded and others did not. | Check the unsent paychecks and retry after resolving the sending error. |
| Payment journal lines already existed when paychecks were moved. | Payroll asks whether to clear the lines before creating new ones. If you decline, the existing lines can remain in the journal. | Confirm that the lines are correct for this payment. Do not remove lines that belong to another process. |
User access
| Message or symptom | Explanation | What to do |
|---|---|---|
| A user cannot access Payroll. | Access control may be enabled, and the user's access-list entry, access validity, or user role may not allow access. | Ask an administrator to review user access in Payroll Setup and confirm the applicable Business Central permissions. See set up user access. |
Posted payouts
| Message | Explanation | What to do |
|---|---|---|
| Only a posted payout can be reversed | A reversal is only available for a posted payout. | Confirm that the payout is posted. If it is still in process, correct it before posting. |
| The G/L lines of payout … have not been posted. Post them in the payroll journal, or choose Recreate G/L Lines if they were deleted, before reversing the payout. | The payout's payroll entries have not been posted to the general ledger. | Post or recreate the G/L lines according to your organization's process before reversing. Do not repeat posting if it has already occurred. |
| The G/L lines of payout … have already been posted. | The payout's G/L lines have already been posted and cannot be recreated. | Review the G/L entries and posted payout before making further changes. |
Payroll prerequisites
| Message or symptom | Explanation | What to do |
|---|---|---|
| Create a period first: enter Valid From as the first day of the month the rates apply from, then choose Get Data. | Get Data requires a payroll period whose Valid From date is the first day of the month. | Enter the correct first day of the effective month in Valid From, then select Get Data. |
| A prerequisite row is not imported from Excel. | The import reads specific columns and stops if quantity multiplied by rate does not equal the total amount. | Compare the file with the payroll prerequisite import format, correct the row, and import it again. |
| An employee or pay type is missing from an imported prerequisite. | Payroll cannot match the code in the row to an employee or pay type. | Confirm the codes and that the records exist before importing the file again. |
Vacation debt posting
| Message or symptom | Explanation | What to do |
|---|---|---|
| Vacation debt is not calculated or no ledger entry is created. | The calculation depends on active setup, selected pay types, and the claim party's posting details. | Review the setup, selected pay types, and posting accounts. See set up vacation debt posting. |