What to do when Jarvis pauses your submission because contributions may already have been processed for this pay period.
The warning you'll see
Contributions already submitted: [Frequency] period ending [YYYY-MM-DD]
What this means
Jarvis has paused your submission because contribution records appear to have already been processed for this pay period. This is a safety check to help prevent duplicate contributions.
Why this happens
There are two common causes:
The same file was uploaded a second time, and the first upload had already processed some or all of its records (in other words, it was not fully rejected).
A corrected file was uploaded to re-submit records that previously failed, but it still includes records that were already processed successfully.
How Jarvis processes a file
Jarvis processes each record in a file individually and independently of the others. A record that has already been processed successfully should never be included in a later submission. This matters most when you are re-uploading failed records: the new file should contain only the records that failed, and none of the records that already went through.
What to do
Check whether this is a duplicate. Confirm that the file you are submitting is not one that has already been submitted, for example an old CSV selected by mistake. If it is a duplicate, click Abort. No further action is needed.
If you are re-submitting to fix failed records, check that the file contains only the records that previously failed. If it also includes any records that were already processed successfully, click Abort, then create a new submission containing only the failed records.
If you are confident the file is correct and not a duplicate, click Release to continue processing.
Best practice for correcting failed records
Always build a fresh file that contains only the failed records. Never re-upload the original file in full, because records that have already been processed successfully should not be submitted again.