Why my automation failed to run

If clicking Run Zato produces an error or the automation completes with missing or incorrect results, work through the checks below before raising a ticket. Most failures trace back to one of these issues.

1. Chart of Accounts (CoA) mapping incomplete

Automation will not run successfully if accounts remain in the Unmapped tab. Open Job Setup, go to CoA Mapping, and ensure every account from the client's Trial Balance (TB) is mapped to a Zato parent account.

2. Trial Balance (TB) not uploaded or incorrect format

Confirm a TB has been uploaded under Data Sources (Ledger). The file must be in CSV or XLSX format. If you uploaded one but it is not appearing, refresh the page and re-upload.

3. Required data sources missing

Some workpapers require specific files to populate. If the Goods and Services Tax (GST) Reconciliation is empty, check that the GST Return Summary report from Inland Revenue Department (IRD) has been uploaded under Data Sources (IRD). If the Fixed Assets workpaper is empty, check that the Depreciation Schedule from Xero has been uploaded under Data Sources (Ledger).

4. Job Setup not completed

The Run Zato button only becomes active after Job Setup is complete. Verify the questionnaire review, CoA mapping, and data sources steps have all been finished.

5. Browser cache issues

Outdated browser cache can occasionally prevent automation from running correctly. Clear your browser cache, refresh the page, and try again.

If the issue persists

If automation still fails after these checks, raise a support ticket using the steps in the Zato Support article. Include the job name, the steps you have already tried, and any error messages displayed on screen.