When posting payroll batches to the General Ledger (GL), errors can occur if payroll redirection settings, cost types, or GL account analysis categories do not match the job or contract configuration. This article covers the most common errors and how to resolve them.
đNote: For general GL batch posting errors not related to payroll, such as batches stuck in Posting status or account restriction failures, see Troubleshoot stock and GL batch posting errors.
Error JC187: cost type class not valid for job
Error JC187 appears when a payroll batch tries to post to a job using a cost type whose class is not permitted for that job. The error message typically includes the job reference and the cost type that failed validation.
Check the payroll redirection cost type masks
Go to Payroll, then Setup, then Payroll Redirection.
Review the cost type masks configured for the affected payroll group or company (KCO).
Confirm that the cost type being redirected is valid for the job class configured on the affected job.
If there is a mismatch, update the cost type mask in the Payroll Redirection setup to use a cost type that is permitted for the job class.
Reset payroll for the affected employees and recalculate before reposting.
Check the job cost type class configuration
Go to the relevant module (for example, Job Costing or Contract Management) and open the affected job.
Check the cost type classes permitted for the job.
If the required cost type class is missing, add it, or confirm with your project manager whether the cost type used in payroll redirection is correct for this job.
â ď¸Important: If the same payroll redirection configuration works in one KCO but fails in another with JC187, compare the cost type class settings between the two KCOs. A mismatch in how cost type classes are defined per KCO is a common cause of this error across multi-company setups.
Error: 'Invalid Analysis' when posting to GL
An Invalid Analysis error appears when a GL posting line uses an analysis category (for example, OT - overtime) that does not match the analysis categories permitted for the target GL account.
Identify the analysis category shown in the error and the GL account it was being posted to.
Go to General Ledger, then Chart of Accounts, and open the affected account.
Review the analysis categories permitted for that account.
If the analysis category used in the payroll batch is not in the permitted list, either add it to the account's permitted analysis categories, or update the payroll configuration to use a different analysis category for that posting line.
After making the correction, reset the payroll batch and repost.
đNote: If your payroll redirection maps overtime (OT) or other pay types to a GL account that does not allow that analysis category, you will see this error on every posting for the affected employees. Resolving it requires either updating the GL account's permitted analysis categories or changing the analysis category used in the payroll redirection setup.
BACS payment file errors and XML mismatches between KCOs
If BACS export files differ between KCOs using the same BACS file definition, or if you receive errors related to ISO 20022 format compliance, the cause is typically a BACSMED parameter mismatch or an incorrect file definition assignment.
Check the BACSMED parameter
Go to Parameter Maintenance in each affected KCO.
Search for the BACSMED parameter (or PL/BACSFILE/EFT/BACS for ISO 20022 format).
Confirm that the parameter value in each KCO points to the correct BACS file definition code, not a numeric format identifier.
If the values differ between KCOs and should be the same, update the affected KCO to match the working one.
Update for ISO 20022 (pain.001.001.09)
Go to Parameter Maintenance in the affected KCO.
Search for PL/BACSFILE/EFT/BACS.
Update the parameter value to the file definition code that generates SEPA XML in pain.001.001.09 format.
Contact Access Coins support if you are unsure which file definition code to use, include your bank name and the format required.
Raise a support ticket
Raise a support ticket if:
Error JC187 persists after reviewing and correcting the payroll redirection cost type masks and job cost type class configuration.
An Invalid Analysis error cannot be resolved by updating the GL account's permitted analysis categories or the payroll redirection setup.
A BACS export file continues to produce incorrect output after checking the BACSMED parameter.
Include the KCO number, the batch reference, the exact error message, and details of the payroll redirection configuration you have already checked.