How Togra handles Section 481
# How Togra handles Section 481
The product-side companion to Section 481 — the Irish scripted tax credit: which Togra surface owns each step of the credit, from structuring the entities to handing the final claim to your filing accountant. If you want the law, read that entry; this one is the workflow.
1. The shape of it
S481 runs on two parallel tracks — the cultural certificate (DCCS, one certificate per the May 2024 Guidance Note) and the tax claim (Revenue, interim and final claims under the Film Regulations 2019 schedules). Togra mirrors that split:
- Airgead → Tax credits → S481 Tracker is the spine: eligibility, the claim progression, the statutory timeline, and a withdrawal & cessation risk panel that watches for claw-back triggers.
- Iarratas → DCCS generates the documents you actually submit.
- The skills suite, state-aid engine, DAC compliance and Accounts feed both tracks along the way.
2. Structuring — before you apply
- Regime detection. Togra reads the project type: scripted film / TV drama / animation / scripted documentary route to S481; unscripted routes to S487A — one project, one credit, and the trackers cross-check so you can't run both. A documentary series is S481-eligible for Series 1 only; later series route to S487A by series number.
- The DAC. A qualifying project needs a Designated Activity Company alongside the Producer Company (when a DAC is required). Togra registers the DAC as a legal entity in Teoranta (it then appears across Accounts and Cúram once the project is in motion), and DAC compliance tracks the CRO side — B1 annual returns and the statutory diary.
- Pre-submission health check. The SI/DCCS health checks flag the gates that get applications bounced — missing broadcaster commitment on TV drama, team roles unfilled, thresholds breached — each with a fix-link to the surface that closes the gap.
3. The application — Iarratas
The DCCS pack assembles the full Tab A + Tabs B–M bundle from data already in Togra — project, entities, finance plan, budget — including the Film Outline with the Culture Test criteria (three minimum; see the S481 Cultural Test) and the Industry Development Test. You review and export rather than re-key. S481 submissions keeps the log: what went to DCCS when, against the 21-working-days notice requirement.
4. The money — one calculation engine
A single shared engine (used identically by the budget tool, the finance plan, the tracker and every pack, so the figure can never drift between surfaces) computes the credit as 32% of the lowest of three values — eligible Irish creative expenditure, 80% of the total budget, and the €125m statutory cap — with the Scéal Uplift 40% rate where certified.
- Eligible spend is tagged at budget-line level: Budget → Irish-creative tagging marks each line, and the running qualifying-spend rollup follows actuals on the Production Accountant dashboard, so the eligible figure is a live number, not a year-end reconstruction.
- State aid has its own surface: the cumulation engine applies the 50% standard cap with S481's two mitigation routes (EU low-budget, "difficult" film — certified via DCCS / Screen Ireland), the 60% intra-EU co-production ceiling, and per-line tier overrides for the awkward cases. Post-Brexit UK funding (AVEC, BFI, NI Screen) sits outside the EU cumulation pool. See the state-aid cap.
5. During production — skills and the timeline
Projects above the spend threshold owe Screen Ireland a Skills Development Plan; Togra carries the whole workflow (the plan, the SDO role), and it runs plan-first — Tab F is applied for before any participant exists:
- Roles before people. From the budget you define the skills roles the plan commits to, each with its own training & development plan. The participant floor scales with the tagged budget's eligible spend (from 2 participants on the smallest productions to 30 above €70m); above €2m eligible spend the plan needs Screen Ireland approval. Floors compute from eligible spend, never from the gross budget — and when eligible spend isn't computable yet, the surfaces warn instead of silently computing from zero. Where SI has agreed a qualitative plan instead of the numeric floor, the floor stands down only when the note records what was actually agreed — a bare tick changes nothing.
- Fill the roles. Participants — New Entrants / Trainees (+ Animation Juniors) / Upskillers — fill the planned roles, with each Individual Learning Plan seeded from the role's plan, plus supervisor and shadowing relationships. Mandatory courses track per participant against the 80% / 2-of-3 thresholds; the SI engagement log records the three required engagement meetings.
- Evidence as you go. Participants write their own journals, task sheets and feedback from their Cast & Crew portal login; supervisors and mentors sign off through a standing channel; the SDO hub queues every blocker (unfilled roles near the shoot, unsigned ILPs, stale journals, courses under threshold) with a link to the page that clears it; and a revocable read-only progress link can be shared with SI between meetings.
- The artifacts. Tab F generates on Screen Ireland's own XLSX template (the current S481 Dec25-V6), plan-first — unfilled roles ride as TBC rows, activities land in SI's own grids, and the totals reconcile with the workbook's built-in formulas. Tab Z covers the DCCS skills annex with plan-vs-actual variance per role and your explanation attached. At close-out, the Stage 3 QA Compliance Report pre-drafts on SI's own document — facts and counts filled from recorded data, judgement slots left as explicit "[Producer to complete]" placeholders — and the evidence bundle ZIPs with named warnings for any gaps. The Stage 3 deadline (12 weeks from production completion) is tracked through the hub.
Meanwhile the tracker's statutory timeline keeps the Film Regulations clock honest — commencement triggers, the 68% bank-lodgement rule, claim windows — and the risk panel fires on withdrawal/cessation conditions.
6. Claims and close-out
- Interim and final claims (Schedules 2 and 3 of the Film Regulations) progress on the tracker.
- The Final Cost Statement publishes from the cost report (FCS) and hands off through a filing engagement: the external accountancy firm that prepares the Cost of Production accounts and files the claim works through Firm Hub — see the final-claim engagement. (The external firm prepares and files; it is not an independent audit.)
- Accounts keeps the production's books in the DAC — Cuntasaíocht's entity policy posts S481 production cost to the DAC's ledger, which is what the COP accounts and the compliance report (Schedule 4) draw on. Records retention: six years.
7. Where things live
| Step | Surface |
|---|---|
| Claim lifecycle, timeline, risk panel | Airgead → Tax credits → S481 Tracker |
| DCCS application bundle (Tab A + B–M) | Iarratas → DCCS |
| Submission log | S481 submissions |
| Eligible-spend tagging | Budget → Irish-creative tagging |
| State-aid cumulation | State aid |
| DAC statutory diary | DAC compliance (+ Teoranta entities, Cúram) |
| Skills plan (roles → participants), Tab F / Tab Z, engagement meetings, Stage 3 QA report | Skills suite |
| FCS + filing handoff | Cost report → FCS publish → Firm Hub |
Related
Sources
- · s481-tracker.php (claim lifecycle · statutory timeline · withdrawal & cessation risk panel)
- · lib/s481_pack.php (the DCCS Tab A + Tabs B–M application bundle, Culture / Industry Development Test sections)
- · budget-tag.php · state-aid.php · dac-compliance.php · s481-submissions.php · s481-fcs-publish.php · firm-hub.php
- · the skills suite: skills-setup / skills-participants (plan layer) / skills-engagement / skills-compliance / tab-z + the Tab F XLSX generator (SI Dec25-V6 template) + the Stage 3 QA report