Troubleshoot the Third-Party Involuntary Payment Interface

When running this interface, you might find errors in your data.

In these cases, you might find the following helpful.

Finding errors in the exception report
Fixing errors after you processed the periodic archive
Fixing errors before you upload the disbursement file
Correcting data after you uploaded the disbursement file
Resolving missing data in the disbursement file
Resolving rejected disbursement files

For further info, see the following sections.

Caution: The Third-Party Involuntary Payment Interface keeps no records of the files you send to your involuntary deductions processing provider or when you send them. You must ensure the accuracy of the data you capture and submit. Regardless of what you do to resolve the errors, the data in Oracle Fusion Human Capital Management must remain your source of truth.

How You Resolve Errors Detected by the Exception Report

After you complete running the extract process, check the exceptions report. The process logs any errors it detects in this file.

In case of error:

Use the Roll Back Process flow to roll back the interface process.

This extract applies locks to the deductions transactions it processes to ensure they aren't processed again in subsequent runs. If an error occurs on a transaction, you must roll back the process before you can rerun the transaction.
If the error pertains to the periodic archive, or to the data archived, roll back the archive.

Note: In addition to the extract, there are other processes that consume the archive's data, such as the payslip and tax filing. If you have run these processes as well, you must resolve their data locks before you can roll back the archive.
Resolve any data errors, as listed in the exception report.
Rerun the Third-Party Involuntary Payments Extract process.
Ensure all processes have completed without additional errors.

Fixing Errors After Processing the Archive

If you find an error in your deduction data after you have run the periodic archive, but before you have run the third-party involuntary deductions extract process:

Roll back the periodic archive.

Note: In addition to the extract, there are other processes that consume the archive's data, such as the payslip and tax filing. If you have run these processes as well, you must resolve their data locks before you can roll back the archive.
Correct your info.
Rerun the archive process.
Run the third-party involuntary deductions extract process.

Fixing Errors Before Uploading the Disbursement File

In this case, you must make corrections to your deductions data, but you have already generated the extract file.

If you haven't yet uploaded the file to your provider, you must:

Roll back the third-party involuntary deductions extract process and then the periodic archive.

Note: In addition to the extract, there are other processes that consume the archive's data, such as the payslip and tax filing. If you have run these processes as well, you must resolve their data locks before you can roll back the archive.
Correct your info.
Rerun the periodic archive process.
Run the third-party involuntary deductions extract process.

Correcting Data After Uploading the Disbursement File

After uploading your tax-filing extract to your provider, you must work with them to resolve issues and correct any errors. You must also ensure all corrections are reflected in the data maintained in Oracle Fusion Global Payroll.

Resolving Missing Data in the Disbursement File

After running the extract process and checking the audit report, you discover it's missing expected deduction data.

Both the periodic archive and third-party involuntary deduction extract applies locks to the data when you run them. If you make changes, they can impact an extract you've already run. When you rerun the extract, the process captures only the new data.

To create an output file consisting of all changes, rather than submitting multiple files:

Roll back the extract and periodic archive processes.
Rerun them.

Resolving Rejected Disbursement Files

ADP might reject the file you submit to them for a number of reasons. They are primarily due to configuration or data corruption issues that result in malformed extract files. Some things you can check:

Fields required by ADP are undefined or incorrect, such as:

Field label	Where you can find it in My Client Groups
Client Identifier	Workforce Structures > Manage Legal Reporting Unit HCM Information
Branch Identifier	Workforce Structures > Manage Legal Reporting Unit HCM Information
Registry ID	Payroll > Third-Party Payees
Third-Party Involuntary Deduction Number	Payroll > Calculation Cards

For further info, see Set Up the Third-Party Involuntary Payment Interface in the Help Center.

The fields provided in the file exceed ADP's character limits.
Your historical or disbursement XML extract files include special characters in the start of the text stream

ADP can't process these characters. Some third-party XML editors insert a byte order mark into the file, and this renders the file unusable to ADP.

If you view your extract files with such an editor, ensure you do one of the following:
- Don't save any changes
- Select an encoding option that saves the file without the byte order mark