Choose a supported connection first
Check whether the destination supports an API, structured import or vendor connector. Screen-based automation may be possible where those options are absent, but layout changes, login requirements and session expiry create maintenance work. Decide how failures will be detected before replacing the manual task.
Recover from an interrupted invoice import
An automation enters an invoice, then loses its connection before receiving a success response. Retrying the entire operation can create a duplicate. Define the record identity and the recovery decision before automating the screen clicks.
| Observed state | Next action |
|---|---|
| No matching supplier + invoice ID | Validate and submit once; save the resulting record ID |
| Matching ID and identical amount | Treat as already processed and reconcile the outcome |
| Matching ID but different amount | Stop and send both versions to a reviewer |
Validate before writing
A successfully extracted field is not necessarily a correct business record. Check required values, formats and relationships such as supplier codes or invoice totals. Use a stable identifier to detect duplicates, and retain the original input so staff can investigate disagreements between the source and the destination.
Give exceptions an owner
Unreadable documents, conflicting records and failed writes should enter a review path. Record which steps completed so retries do not repeat an action that already succeeded. Start with a limited batch, compare results with manual processing and expand only after the correction process works.
Before you proceed
- Collect normal, duplicate and incomplete sample records.
- Define validation rules and a stable record identifier.
- Test interrupted runs and controlled retries.
