A row can be valid and still be outside the activity you intend to add in this batch. When the saved import offers an individual decision, choose Skip to leave that row out while preserving its source and check history.
- Confirm why the row should be excluded, such as an intentional overlap already handled through another supported source.
- Find the row in the checked batch and choose Skip.
- Review the remaining eligible count before committing, then confirm the skipped outcome in Results log.
Do not delete or rewrite the source row merely to hide it from review. A recorded decision makes the batch’s outcome easier to explain.
Check whether the exclusion is appropriate
A real company movement still needs a complete accounting treatment somewhere. Skipping it here should be consistent with how the source period is covered, not a way to make an inconvenient transaction disappear.
If the issue is the wrong company, account or file, correct the batch setup instead of skipping large groups blindly. If a category is uncertain, that is usually a later review question; it does not automatically mean the movement should be omitted from the source import.
Was this article helpful?
Tell us whether this answered the question you came with.