Established
The controlled public record identifies the EU/ERDF connection for the MYND/GC/836/P06 project.
5 MARCH → 11 JUNE → 19 AUGUST 2026
The third response limits the Comptroller’s remit. It does not certify that no other funding or files existed.
Outgoing 699645/2026 must be read with 184368/2026 and 497011/2026. The safe institutional conclusion is narrow: the General Comptroller will not open an all-encompassing audit at a third party’s request and says it does not fiscalise the RIC suitability declaration. It reached no merits conclusion on the remaining funding sources and did not clear any person, entity or public body.
ERDF / FEDER · evidence → traceability → action
ERDF / EU funds: what is established, what remains open and what to do next
How to use this page. Narrow institutional reading: the response limits remit; it does not certify non-existence of other aid, payments or files.
Still to produce
Exact operation and percentage, eligible expenditure, invoices, payment/certification, verifications, audits, corrections and recovery.
Keep separate
RIC tax relief, RICPE investment, Regional Incentives, State aid and FEDER/ERDF are not one funding source.
Minimum production needed to close the ERDF question
- operation identifier and programme/fund
- beneficiary and title/availability record
- eligible-cost schedule and invoices/supporting records
- funding sources and other aid declared
- certifications, payments and verified employment
- verifications, audits, issues, corrections or recoveries
Directive (EU) 2024/1260 · FEDER/ERDF · EPPO/OLAF: Editorial action-routing aid; it does not establish fraud, corruption, duplicate funding, EU-budget loss, a PIF nexus, EPPO/OLAF competence or individual liability.
The three-response sequence
1 · 5 March · 184368/2026
The Office delimited its functions and recorded activation of the internal integrity route for the communication received, subject to confidentiality. That was not a general audit or a determination of the truth of every reported fact.
2 · 11 June · 497011/2026
It identified the RIC lane: competent Finance body, prior binding AEAT report and Canary Government decision. It said RIC suitability is not itself a Canary autonomous subsidy or direct regional-treasury disbursement and transferred the material to the competent Vice-Ministry.
3 · 19 August · 699645/2026
It declined an all-encompassing audit or certificate at a third party’s request and expressly clarified that June was not a general certificate that no other aid, regional incentive, European funding, payment, certification or file existed.
Mandatory interpretive correction
It is inaccurate to say the General Comptroller confirmed that “there was no public funding”. What it confirmed is only that a RIC suitability declaration is not, by itself, an autonomous subsidy or direct Canary treasury payment and that the Office does not participate in fiscalising it.
The August letter says the June reply cannot be used as a general nonexistence certificate for other aid, subsidies, regional incentives, European or ERDF funding, payments, certifications or separate files.
Result: questions concerning GC/836/P06, ERDF, payments, employment, Series F/G, other support and possible overlap remain open and must be resolved through native files. This does not prove that any such instrument existed, was paid or was irregular.
What is and is not confirmed
Confirmed by the institution
- Its perimeter is internal control of the Canary public sector through legally prescribed procedures, plans and files.
- The described RIC route involves the competent Finance body, a binding AEAT report and Canary Government declaration.
- The June material was referred to the competent Vice-Ministry on subject-matter grounds.
- The letter does not prejudge truth, irregularity or liability.
- It notes SIINF availability for objective indications within the Canary-administration scope.
Not established
- That no other aid, European funding, payment or file existed.
- That any such support existed or was irregular.
- That a specific Comptroller control file does or does not exist.
- That the June referral produced a merits investigation or decision.
- That general confidentiality proves a “hidden” file.
- That the letter clears RICPE, CAM, HNT, MYND or any other actor.
Questions that remain open
| Question | Status after 699645/2026 | Document capable of closing it |
|---|---|---|
| What did the RIC file, AEAT report and Decree 224/2022 cover? | Not resolved by the Comptroller. | File 02/2022, application, memorandum, report, proposal, decree, annexes and amendments. |
| What did Series F and G finance? | Unresolved. | Agreements, drawdowns, bank records, invoices, works certificates, liabilities and payroll. |
| Did GC/836/P06, ERDF or other aid exist or pay out? | No general nonexistence certificate exists. | Grant/managing files, ERDF operation, certifications, payments, controls and closure. |
| Was there overlap in costs, assets, value or employment? | Not verified. | Consolidated source-and-use and invoice, property and employment tables. |
| What followed the June referral? | Traceability pending. | Receiving entry, unit, file, status and reasoned response. |
Access, SIINF and separate routes
The letter argues that complainant or third-party status does not by itself confer access to a possible financial-control file and invokes reservation and confidentiality. This page records that institutional position; it does not present it as a universal court ruling on transparency, whistleblower protection, criminal procedure or other sector-specific rights.
SIINF is for objective indications connected with the activity or functioning of Canary autonomous-administration bodies. It does not replace access requests concerning RIC, regional incentives, ERDF, tax, local or judicial files.
Source, custody and privacy
This update is based on the text of outgoing 699645/2026 supplied on 20 August 2026 and the two earlier communications recovered from email. The native signed August PDF remains necessary for primary custody and hashing.
The public repository retains a redacted institutional derivative. The unredacted full text and native binary belong in a private, access-controlled evidence layer—not on a public page containing personal data.
POR DERECHO · Reward careful examination, not agreement.
Test the argument
Optional · inspect the evidence and compare the reasoning. No account, saved answer, transmission, score or voting. Reader responses are not evidence.
TTA-001 · V1 · Reviewed 2026-09-12
What does this document actually establish?
Classify this precise proposition: the public derivative of outgoing 699645/2026 records a limited institutional remit and says the June reply is not a general certificate that other funding or files did not exist.
Source and status
This is a controlled public digest of supplied institutional text, not a quotation from an authenticated native PDF. Its canonical event still leaves the native signed binary open.
Try this exercise · inspect, choose, compare
Project Position
The response must not be used as a universal “no public funds” certificate. Whether other support existed, was paid or was irregular must be tested through the relevant records.
Strongest Contrary Explanation
The institution may be accurately delimiting its competence while the competent bodies hold separate files; this need not imply concealment or a merits rejection.
Best lawful/contrary explanation we can presently formulate; not attributed to the affected party unless and until adopted by them.
Contrary Evidence
The stated competence and confidentiality limits, and the express absence of any merits determination, limit what can be inferred from this correspondence.
Read every choice and its explanation
Documented, with the derivative-source limit
That is the current classification of this narrow proposition. It reports the controlled derivative’s content; it does not turn that content into a finding about other funding.
Only a project allegation
The project’s wider allegations remain allegations, but this proposition concerns what a located institutional derivative says. Keep the two layers separate.
An inference that other funding existed
That changes the proposition. A limit on the letter’s scope does not establish the existence of another funding instrument.
An open question about the native original
Authentication of the native original is indeed open. The derivative’s recorded wording can still be classified, with that limit explicitly attached.
What the source establishes
What the located derivative records: the institution’s competence position, its clarification of the June reply and the absence of a merits determination in this response.
What it does not establish
It proves neither the existence nor the absence of other support, payment, misuse or responsibility. It does not authenticate the missing native PDF or establish a later investigation.
Lawful Alternative
Separate lawful competence and access rules may explain the response.
Decisive Test
Obtain and authenticate the native signed 699645/2026 response; for each funding proposition, inspect the competent programme’s decision, payment and use records.
Evidence Gap
Native signed PDF; programme-specific files; verified outcome of any onward referral. Existing gaps: PD-GAP-UCF-009, 012, 015 and 016.
What Would Change Our View?
An authenticated original that materially differs would require correction; a reasoned programme-file decision and payment trail could resolve a specific funding question.
Proof Ceiling
Documented content of a public derivative, with native-source authentication pending. Other funding and merits questions remain unresolved.
Current evidential classification: Documented, with a derivative-source limitation