See clearer error handling and reporting for file and batch runs
Also listed as: Error handling & reporting
What is it?
Xelence records errors from file and batch runs in more detail and reports them, so teams can see what failed and why.
Why does it matter?
Faster diagnosis and less time spent chasing failed runs.
Start thinking about
- Which files and batch jobs are critical to your business cycle, such as contributions or payment runs?
- How are bad records in inbound files handled today, and who corrects them?
- Which partners exchange files with you, and which formats do they expect now and in future?
- What processing windows must your batch jobs fit, and what happens when one runs late?
- Where should staff sign off before automated file or batch steps take effect?
- How will you plan regression testing of your critical batch jobs around an upgrade?
Terms used on this card
- Batch job
- A scheduled task that processes many records at once, such as nightly payments or file imports, without anyone clicking through each one.