Financial risk: the assessment template
Whether the vendor can keep delivering: its accounts, its insurance, its ownership, and what happens to your data and service if it fails. 7 questions; each names the clause it comes from or says "general practice, not a held regulation". The assessor rates the domain, inherent and residual, with a rationale; Vendor Register never sets a rating.
- fin-01 Provide your most recent audited financial statements, or say why none are available (for example, a private company that does not file them). vendor answersgeneral practice, not a held regulationEvidence that helps: Statements, period end, the auditor and the type of opinion.
- fin-02 Has an auditor's report on your accounts for either of the last two financial periods carried a going-concern emphasis or a qualification? vendor answersgeneral practice, not a held regulationEvidence that helps: The auditor's report, or a signed statement that there was none.
- fin-03 What insurance do you hold that would respond to a failure of the service you provide to us (professional indemnity, cyber), with the insurer, limit and expiry? vendor answersgeneral practice, not a held regulationEvidence that helps: Certificate of currency, with its expiry.
- fin-04 Has there been, or is there pending, a change of ownership, a merger, or an insolvency, restructuring or administration proceeding? vendor answersgeneral practice, not a held regulationEvidence that helps: A signed statement, or the announcement.
- fin-05 If this vendor became insolvent or entered resolution, does the contract give us access to, recovery of and return of our data? internal
DORA Art. 30, Key contractual provisions
Contracts set out the rights and obligations of both parties in one written document, available on paper or another durable, downloadable format, including the service levels. Every ICT services contract covers at least: the functions and services and whether and how subcontracting is permitted; service and data processing locations, with advance notice of changes; data protection provisions; access, recovery and return of data on insolvency, resolution, discontinuation or termination; service level descriptions; incident assistance at no cost or a cost fixed in advance; cooperation with competent and resolution authorities; termination rights and minimum notice periods; and participation in security awareness training. Contracts for services supporting critical or important functions add: full service levels with quantitative and qualitative targets, notice and reporting duties, provider contingency testing and security measures, participation in the entity's TLPT, unrestricted access, inspection and audit rights for the entity and the authority, and exit strategies with a mandatory transition period (Art. 30(3)). A microenterprise may agree with the provider that its access, inspection and audit rights are handed to an independent party that the provider appoints, from which it can request information and assurance at any time (Art. 30(3), final subparagraph). Standard contractual clauses from public authorities should be considered.
Our statement of the clause, read from the published text, not the instrument verbatim. The standard on compliance.theartofservice.com · official source
Applies when you are a DORA financial entity. Until you answer, it reads "depends on an answer" and stays on the assessment.Evidence that helps: The contract clause, by section number. - fin-06 What share of our spend does this vendor carry, and what share of the vendor's revenue do we represent (dependence in both directions)? internalgeneral practice, not a held regulationEvidence that helps: The register's spend share; the vendor's revenue from its accounts.The register computes our side from the spend column.
- fin-07 For a service supporting a critical or important function: is there an exit strategy for the case where this vendor fails, and has it been tested? internal
DORA Art. 28, ICT third-party risk: general principles
Financial entities manage ICT third-party risk as part of ICT risk inside the ICT risk management framework, remain fully responsible for their obligations when they use ICT services, and apply proportionality according to the nature and importance of ICT dependencies and the criticality of each service. They keep a register of information on all ICT service arrangements at entity, sub-consolidated and consolidated level, distinguishing those supporting critical or important functions; report at least yearly to the authority on new arrangements, provider categories, contract types and services; provide the full register or sections of it on request; and inform the authority in time of planned arrangements for critical or important functions. Before contracting they assess criticality, supervisory conditions, risks including concentration, due diligence and conflicts of interest; they use only providers meeting appropriate security standards, set risk-based audit frequencies, ensure contracts can be terminated in the listed cases, and keep tested exit strategies for services supporting critical or important functions. The ICT third-party risk strategy with its policy on critical or important functions (Art. 28(2)) is required only of entities other than Article 16(1) entities and microenterprises.
Our statement of the clause, read from the published text, not the instrument verbatim. The standard on compliance.theartofservice.com · official source
Applies when you are a DORA financial entity, and the vendor supports a critical or important function. Until you answer, it reads "depends on an answer" and stays on the assessment.Evidence that helps: The exit plan and the record of its last test.
Use it as it is, reword a question (it then becomes your own and cites nothing), add your own, or save your own template, on Solo and Team. Pricing.