Batch Register

Prudential regulatory return

None of the held 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 regulatory_return_apra, 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: regulatory return, apra return, prudential, return to regulator, reporting return, ers return, d2a, regulatory return. 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
BCBS 239 named referenceno clockBCBS 239 Principle 5 Timelinessquoted below
BCBS 239 named referenceno clockBCBS 239 Principle 7 Accuracy (Reporting)quoted below

Named reference beside this class, BCBS 239 Principle 5 Timeliness: A bank should be able to generate aggregate and up-to-date risk data in a timely manner while also meeting the principles relating to accuracy and integrity, completeness and adaptability. The precise timing depends on the nature and potential volatility of the risk, including timely production under stress/crisis conditions.

Named reference beside this class, BCBS 239 Principle 7 Accuracy (Reporting): Risk management reports should accurately and precisely convey aggregated risk data and reflect risk in an exact manner. Reports should be reconciled and validated.

Questions this page answers

What does the register ask the owner of a prudential regulatory return job?

Which return does this job produce, what is its due date, and who signs it before submission?

The clauses in full

BCBS 239 Principle 5 Timelinessnamed referencethe standard's page

A bank should be able to generate aggregate and up-to-date risk data in a timely manner while also meeting the principles relating to accuracy and integrity, completeness and adaptability. The precise timing depends on the nature and potential volatility of the risk, including timely production under stress/crisis conditions.

What an assessor asks to see: Defined timeliness requirements per risk type for normal and stress/crisis conditions; Evidence of meeting reporting deadlines (production logs, SLAs); Capability to accelerate aggregation under stress/crisis (tested); Time-to-produce metrics for key risk reports. Where it usually falls short: No defined timeliness requirements differentiating normal vs stress conditions

BCBS 239 Principle 7 Accuracy (Reporting)named referencethe standard's page

Risk management reports should accurately and precisely convey aggregated risk data and reflect risk in an exact manner. Reports should be reconciled and validated.

What an assessor asks to see: Reconciliation and validation procedures for risk reports prior to distribution; Defined accuracy requirements and validation sign-offs for reports; Documentation of report data sources and calculation methods; Error log and correction process for risk reports. Where it usually falls short: Reports distributed without validation or reconciliation

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