After a file passes validation, Acclaim processes it asynchronously: rows become payees and payouts, then payouts move through execution. This page is the operational view of that pipeline.
Overview
The flow has these stages:
- File upload
- Validation
- Row processing
- Payout creation
- Execution and completion
Step 1: File upload
You upload the file through the Acclaim Console and select the correct template.
At this stage:
- The file is received and stored for processing.
- The chosen template is applied.
- Work is queued asynchronously—the UI may return before all rows finish.
Step 2: Validation
The system runs:
- File-level validation (structure, headers, mapping).
- Row-level validation (fields, formats, method rules).
Results:
- Valid rows continue.
- Invalid rows are rejected with errors you can use to fix the file.
Step 3: Row processing
Each valid row is transformed into:
- Payee data (create or update as your setup allows).
- A payout instruction with amount, currency, and destination details.
This step includes mapping fields, applying defaults from the template, and normalizing values.
Step 4: Payout creation
For each successful row:
- A payout is created.
- It is queued for execution on the appropriate rail.
You can track payout records and statuses in the Console.
Step 5: Execution
Payouts execute according to:
- Payout method and corridor.
- Processing windows and banking cutoffs.
Statuses typically progress through stages such as pending, processing, completed, or failed—use the Console as the source of truth for wording in your org.
Large files take longer. Plan communications and cutoffs so finance and operations know processing is not instantaneous.
Tracking progress
You can monitor:
- Upload / job status at the file level.
- Row outcomes (success vs error).
- Payout status for each created payout.
Partial success
Mixed results are normal:
- Some rows succeed and become payouts.
- Others fail validation or later processing steps.
Failures on one row do not roll back successful rows in the same upload (unless product behavior states otherwise—confirm for your tenant if needed).
Reprocessing failed rows
For failed rows you should:
- Fix the data using the reported errors.
- Re-upload only the corrected rows in a new file when that fits your process.
You do not need to re-upload rows that already succeeded.
Smaller batches give faster feedback when you are tuning templates or onboarding a new corridor.
Next steps
