Batch Register

Payment file and settlement batch

None of the published texts sets a fixed period on this consumer; every row below reads no period set by the text. Paste one job that feeds this consumer, for example settlement_file_batch, weekly, and the register reads its period against the clocks below, names the gap in hours, and carries the question for its owner.

Matched on the job name or the consumer column by these words: payment file, settlement, direct entry, clearing, payment batch, aba file, pay run, disbursement, settlement batch. A backup, replication, feed or return job in this class is expected to name a fallback; a blank one is a finding.

The clock each rule sets

RegimeClockClause
DORAno clockDORA Art. 11 Response and recovery
ISO 22301no clockISO 22301 8.4.4 Business continuity plans
ISO 27001no clockISO 27001 8.14 Redundancy of information processing facilities

Questions this page answers

How often does DORA (Regulation (EU) 2022/2554) require payment file and settlement batch?

The text of DORA Art. 11 (Response and recovery) sets no fixed period: no period set by the text. Financial entities adopt an ICT business continuity policy within their overall continuity policy and implement it through documented arrangements that keep critical or important functions running, contain and resolve incidents, estimate preliminary impacts, and drive crisis communication and reporting under Articles 14 and 19; they run a business impact analysis, keep ICT response and recovery plans, test, at least once a year and after substantive changes, the continuity and response plans for the systems behind every function, test crisis communication plans, and keep records of activity during disruptions. Entities other than microenterprises additionally have the response and recovery plans reviewed by independent internal audit (Art. 11(3)), include cyber-attack and switchover scenarios in testing (Art. 11(6)), run a crisis management function (Art. 11(7)), and estimate aggregated annual costs and losses of major incidents when the authority asks (Art. 11(10)). Central securities depositories also send continuity test results to the authority (Art. 11(9)). Entities listed in Article 16(1) are outside this Article and follow the simplified framework of Article 16 instead.

How often does ISO 22301:2019 require payment file and settlement batch?

The text of ISO 22301 8.4.4 (Business continuity plans) sets no fixed period: no period set by the text. Document and maintain business continuity plans that guide teams through response and recovery, collectively containing the actions to continue or recover prioritized activities within predetermined time frames, the means of monitoring the disruption and the response, the pre defined thresholds and process for activating the response, procedures to deliver products and services at agreed capacity, and how the immediate consequences are managed with regard to individual welfare, prevention of further loss and environmental impact; each plan must state purpose, scope and objectives, the roles and responsibilities of the implementing team, the actions implementing the solutions, the supporting information needed to activate, operate, coordinate and communicate including activation criteria, internal and external interdependencies, resource requirements, reporting requirements and a stand down process, and must be usable and available at the time and place it is needed.

How often does ISO/IEC 27001:2022 require payment file and settlement batch?

The text of ISO 27001 8.14 (Redundancy of information processing facilities) sets no fixed period: no period set by the text. Build enough redundancy into processing facilities to meet availability requirements.

What does the register ask the owner of a payment file and settlement batch job?

Which cut-off does this file meet, and what is the fallback path if the primary fails before it?

The clauses in full

DORA Art. 11 Response and recoverythe standard's page

Financial entities adopt an ICT business continuity policy within their overall continuity policy and implement it through documented arrangements that keep critical or important functions running, contain and resolve incidents, estimate preliminary impacts, and drive crisis communication and reporting under Articles 14 and 19; they run a business impact analysis, keep ICT response and recovery plans, test, at least once a year and after substantive changes, the continuity and response plans for the systems behind every function, test crisis communication plans, and keep records of activity during disruptions. Entities other than microenterprises additionally have the response and recovery plans reviewed by independent internal audit (Art. 11(3)), include cyber-attack and switchover scenarios in testing (Art. 11(6)), run a crisis management function (Art. 11(7)), and estimate aggregated annual costs and losses of major incidents when the authority asks (Art. 11(10)). Central securities depositories also send continuity test results to the authority (Art. 11(9)). Entities listed in Article 16(1) are outside this Article and follow the simplified framework of Article 16 instead.

What an assessor asks to see: ICT business continuity policy and the business impact analysis it rests on; ICT response and recovery plans with yearly test reports and tests after substantive changes; Crisis communication plan test record and records kept during actual disruptions; Internal audit review of the response and recovery plans, crisis management function terms of reference and cyber-attack and switchover test scenarios (entities other than microenterprises). Where it usually falls short: Plans tested only for critical systems, not for systems supporting all functions

ISO 22301 8.4.4 Business continuity plansthe standard's page

Document and maintain business continuity plans that guide teams through response and recovery, collectively containing the actions to continue or recover prioritized activities within predetermined time frames, the means of monitoring the disruption and the response, the pre defined thresholds and process for activating the response, procedures to deliver products and services at agreed capacity, and how the immediate consequences are managed with regard to individual welfare, prevention of further loss and environmental impact; each plan must state purpose, scope and objectives, the roles and responsibilities of the implementing team, the actions implementing the solutions, the supporting information needed to activate, operate, coordinate and communicate including activation criteria, internal and external interdependencies, resource requirements, reporting requirements and a stand down process, and must be usable and available at the time and place it is needed.

What an assessor asks to see: Plan set with each plan carrying every required element; Activation criteria and thresholds stated in the plan itself; Interdependency and resource sections reconciled to the BIA; Stand down process defined. Where it usually falls short: Plans that cover activation and response but have no stand down, so the organization never formally returns to normal

ISO 27001 8.14 Redundancy of information processing facilitiesthe standard's page

Build enough redundancy into processing facilities to meet availability requirements.

Guidance beside it, ISO 27002 8.14: Requires information processing facilities to be implemented with redundancy sufficient to meet the availability requirements placed on them.

What an assessor asks to see: redundancy_design; capacity_planning; failover_testing; maintenance_records. Where it usually falls short: reliance on undocumented manual backups

Requirement text is our own statement of each clause, from the standards published at compliance.theartofservice.com, the same publisher as this register, read against the published text of each standard: our statement of each clause, not the instrument verbatim. Run this job through the register