SEPA collection date in the past
Last updated: 28 October 2026
If the requested collection date in your file has already passed, the bank rejects the direct debit; a credit transfer is executed at once or rejected. A date written as 16.03.2030 fails even earlier, at the schema check. Upload the file below to check every date and get the earliest possible collection date as a suggestion.
Check your file for a collection date in the past
Choose fileChecking is free. Repair if needed: €14.95 excl. VAT per file.
Our server checks your file in memory only, never saves it to disk and deletes it after 30 minutes at the latest.
- Error
- Date error
- Where
- ReqdColltnDt or ReqdExctnDt in each batch
- Repair
- New date on request, never chosen silently
What the error message looks like
Banks and validators report date problems in English. A date in the past is reported by the bank, in its portal or in the status file pain.002; a wrong notation is already caught by schema validators and by your software. For credit transfers our check says “Execution date … is in the past; the bank will execute immediately or reject it.”
XML schema validator (libxml2, for example xmllint and many online validators)
15: Element '{urn:iso:std:iso:20022:tech:xsd:pain.008.001.08}ReqdColltnDt': '16.03.2030' is not a valid value of the atomic type '{urn:iso:std:iso:20022:tech:xsd:pain.008.001.08}ISODate'.
Java validators (Xerces)
cvc-datatype-valid.1.2.1: '16.03.2030' is not a valid value for 'date'.
Your bank (status report pain.002)
DT01InvalidDateCH04RequestedExecutionDateOrRequestedCollectionDateTooFarInPast
In the status report, banks put the reason in the Rsn/Cd field. Online banking often shows a translation of it. DT01 means the date is invalid; CH04 that the requested execution or collection date is too far in the past.
Our check
- Collection date 15 January 2024 is in the past.
- <ReqdColltnDt> (collection date) does not have a valid date format (expected YYYY-MM-DD).
- The collection date '16.03.2030' is not in a valid format (expected YYYY-MM-DD).
Cause
Each batch (PmtInf) in a direct debit file carries one requested collection date, ReqdColltnDt. For credit transfers the field is ReqdExctnDt, and in pain.001.001.09 the date sits in ReqdExctnDt/Dt. If that date has passed, the bank rejects the direct debit.
For SEPA Core direct debits the earliest possible collection date is one TARGET2 business day after the bank has received the file. Banks also have their own cut-off times, so ask your bank when a file has to be in on the day itself.
A second date problem looks similar but is a different error. The date must be written as YYYY-MM-DD, for example 2030-03-16. A date such as 16.03.2030 does not match the schema: the validator reports that it “is not a valid value of the atomic type 'ISODate'”.
How to fix it by hand
Change the date in every batch and make sure the bank does not take the file for one it already has.
- Find
<ReqdColltnDt>in each<PmtInf>block; for credit transfers<ReqdExctnDt>. - Enter a date far enough in the future, in the notation YYYY-MM-DD.
- Create a new file or give it a new MsgId, so it is not taken for a duplicate of the earlier submission; see SEPA file errors on duplicate references.
- Validate the file again and upload it.
Before
<PmtInf>
<PmtInfId>BATCH-001</PmtInfId>
<PmtMtd>DD</PmtMtd>
...
<ReqdColltnDt>2024-01-15</ReqdColltnDt>After
<PmtInf>
<PmtInfId>BATCH-001</PmtInfId>
<PmtMtd>DD</PmtMtd>
...
<ReqdColltnDt>2030-03-16</ReqdColltnDt>In the example the batch had 15 January 2024 as its collection date. After the correction it is 2030-03-16, in the correct notation.
How the tool repairs it
The check reports every date that has passed, for example “Collection date 15 January 2024 is in the past.” When you repair the file, the tool asks you for a new date and suggests the earliest possible one. It then writes that date into the batches concerned. It never picks a date silently, because the collection date is your decision.
A date in the wrong notation is converted automatically when it is unambiguous; the change report then says “Date 16.03.2030 converted to 2030-03-16.” If the notation is ambiguous, as in 05/06/2026, the tool asks which date you mean instead of guessing between 5 June and 6 May.
What the repair writes in the change report:
- Date 16.03.2030 converted to 2030-03-16.
The tool does not know your bank's cut-off times. The suggested date is the earliest one under the scheme rules; if you submit late in the day, choose a later date.
Related pages
- Control sum incorrect – check the totals too if you split or merge batches.
- XML schema error – for pain.001.001.09 files where
ReqdExctnDtlacksDt. - SEPA mandate template – the basis for every collection you submit.
- All SEPA file errors – including duplicate references when you resubmit a file.
Frequently asked questions
What is the earliest collection date for a SEPA Core direct debit?
One TARGET2 business day after your bank has received the file. Your bank's own cut-off time on the day comes on top of that.
Why is 16.03.2030 not accepted?
SEPA files use the ISO notation YYYY-MM-DD. Write 2030-03-16; the tool converts an unambiguous date for you.
Do I need a new MsgId when I resubmit the file?
It is advisable. A bank may reject a file whose MsgId it has already received as a duplicate.
Sources
- European Payments Council: SDD Core Customer-to-PSP Implementation Guidelines 2025 – fields, lengths and the SEPA character set for direct debit files
- European Payments Council: 2025 SDD Core Rulebook, version 1.1 – rules of the SEPA Core scheme, including the earliest collection date
- ISO 20022: External Code Sets – the list of reason codes such as AM10, FF01 and CH16 used in status reports