EPISODICICCE

Layer 2 · operating responsibility

System Components

ICCE separates its principal responsibilities across distinct operating environments. Each Component applies the Mechanics relevant to its role, owns a defined area of control and produces reliable outputs for the next permitted part of the system.

Component register

Defined components6
Exception pathways2
Connected records184
01
Access ControlsIdentity, permissions and participation boundary
Ready
02
Funding ControlsFinancial-readiness conditions
Ready
03
Engagement ControlOperational record and multi-party activity
Active
04
Payroll ExecutionPAYE calculation and statutory outputs
Active
05
Reporting & IntelligenceEvidence, reconciliation and stakeholder views
Connected
06
Payment Trust CentreControlled execution and payment evidence
Connected

Component topology

Separated control areas, connected transaction flow.

Component separation prevents employment, payroll, reporting and payment activity from becoming one opaque process. Each area owns a defined responsibility while the connected record continues across the system.

Principal operating environmentsConceptual sequence
01

Access Controls

Trusted participation and role permissions.

02

Funding Controls

Relevant financial-readiness checks.

03

Engagement Control

Operational activity and engagement truth.

04

Payroll Execution

PAYE calculation and statutory consequence.

05

Reporting & Intelligence

Evidence, reconciliation and permissioned views.

06

Payment Trust Centre

Controlled payment execution and outcome evidence.

01 Trusted participation boundary

Onboarding and Access Controls

Onboarding and Access Controls ensure that workers, agencies and other authorised stakeholders do not enter ICCE through informal registration alone. Identity, organisational information, required evidence and participation conditions are processed through controlled validation pathways before access is activated.

Once admitted, each participant receives role-appropriate permissions governing the functions they may use, the information they may submit and the records they may view. Every material interaction remains attributable to a verified identity.

Controls
  • identity and organisational validation
  • minimum evidence requirements
  • role allocation
  • access activation and restriction
Produces

A verified participant identity, active status and permission scope that can be relied upon by the rest of the system.

Why it matters

Reliable employment, payroll, reporting and payment records cannot be created where the identity or authority of the parties producing them remains uncertain.

Participant onboardingIllustrative interface
Pending review14
Active identities842
Restrictions3
Northgate Labour LtdAgency · organisation evidence complete
Active
Worker ID W-48201Identity and right-to-work review
Review
Westline ProjectsBuyer · role permissions configured
Approved
Supplier contact U-1094Evidence refresh overdue
Restricted

02 Financial readiness

Funding Controls

Funding Controls provide the financial-readiness layer supporting relevant engagement activity. Defined parameters are applied programmatically so the system can determine whether required financial conditions are present before controlled activity proceeds.

Conditions can continue to be monitored while the system operates, allowing future activity to be restricted where the requirements supporting it are no longer satisfied. The public description remains outcome-led and does not disclose the protected internal calculation or allocation logic.

Controls
  • financial-readiness checks
  • permitted operating conditions
  • continuing condition monitoring
  • future-activity restriction
Produces

A controlled readiness outcome that the Engagement Control environment can enforce before relevant activity proceeds.

Why it matters

Conventional labour processes may identify financial weakness only after work has taken place and payroll obligations already exist. ICCE introduces readiness assessment earlier.

Financial readinessProtected logic abstracted
Ready contexts28
Under review4
Restricted2
Project AlphaRequired conditions present
Ready
Project DeltaUpdated information being validated
Review
Works Package 17Future activity temporarily restricted
Hold

03 Operational truth

Engagement Control Module

The Engagement Control Module provides the principal operating environment for each ICCE engagement. It converts an approved requirement into a structured, system-managed record through which controlled employment activity can be initiated, progressed and evidenced.

Temporary labour is inherently multi-party. Agencies or engagers define and administer requirements, workers review and acknowledge relevant information, authorised parties confirm work-related data and the system applies its own validation and progression controls. The record is therefore not based on one participant’s unilateral account.

The resulting operational truth shows who participated, what was agreed, what activity occurred, what was confirmed and how the engagement concluded. That controlled information becomes the real-world input passed into payroll processing.

Coordinates
  • engagement setup
  • participant attribution
  • controlled employment records
  • time-related activity
  • disputes and corrections
  • completion and cancellation
  • event and evidence history
Produces

A corroborated operational record formed from attributable actions, confirmations and system-enforced checks.

Why it matters

Payroll should not be asked to reconstruct reality from disconnected timesheets, emails and declarations. It should receive a controlled engagement record.

Engagement ENG-28419Operational record
Participants4
Confirmed actions12
Open issues0
Requirement accepted into controlled processingAgency user · 08:14
Worker information acknowledgedWorker identity W-48201 · 08:26
Work information confirmedEngager representative · 17:42
Operational record completedSystem-issued outcome · 17:45

04 Financial and statutory consequence

Payroll Execution Module

The Payroll Execution Module receives completed engagement information and finalised time data from the controlled operational environment and converts them into authoritative PAYE payroll outcomes.

It consumes validated inputs and applies deterministic payroll rules so that identical authoritative inputs produce reproducible financial and statutory results. Gross pay, tax, National Insurance, pensions, other deductions, net pay, employer liabilities and related records are produced as a connected payroll outcome.

The payroll architecture is also designed to support HMRC-aligned RTI processing, including FPS and EPS outputs and the controlled maintenance of year-to-date information, without asking a separate payroll system to reinterpret the underlying employment activity.

Calculates
  • gross and net pay
  • PAYE income tax
  • employee and employer NIC
  • pension treatment
  • other lawful deductions
  • employer statutory liabilities
  • year-to-date values
Produces

An authoritative payroll record connected directly to the operational activity that created the obligation.

Why it matters

The Engagement Control Module establishes what happened operationally. Payroll Execution establishes the resulting financial and statutory consequence.

Payroll batch PR-0626Deterministic calculation
Payroll items126
Calculation exceptions0
RTI-ready126
Gross pay
£94,280
PAYE / NIC
£22,614
Net pay
£71,666
Status
Final

05 Evidence and intelligence

Reporting and Intelligence Module

The Reporting and Intelligence Module converts controlled system activity into usable evidence, reconciled records and stakeholder-specific insight. It receives the operational record formed through Engagement Control and the financial and statutory record formed through Payroll Execution.

It does not create a competing version of events. It translates existing system outputs into transaction-level views, aggregated reporting, audit records, project attribution, payment-status views, fair-work evidence, responsible-procurement reporting and other permissioned representations while preserving source attribution.

Different stakeholders can therefore receive different views of the same underlying activity without each party having to reconstruct the transaction independently.

Supports
  • engagement reporting
  • payroll and statutory reporting
  • payment reconciliation
  • project and supply-line visibility
  • worker-treatment evidence
  • social value and ESG evidence
  • exception and discrepancy reporting
  • audit and assurance outputs
Produces

Permissioned views of one system-generated transaction record, from individual drilldown to authorised portfolio-level analysis.

Why it matters

The record is not assembled for the report. The controlled record becomes the report.

Reporting workspaceRole-based view
Transactions1,284
Reconciled99.4%
Exception pathways8
Project attributionAll active engagement records mapped
Complete
Payment reconciliation4 items pending returned status
Monitoring
Evidence packBuyer reporting period Jun 2026
Ready

06 Controlled execution

Payment Trust Centre

The Payment Trust Centre provides the controlled execution environment for payroll-related payments. It receives verified payroll outcomes and connects them to authorised payment processing through a structured, tracked and reconciled pathway.

The arrangement is designed to preserve a clear separation between ICCE operating funds and money intended for worker wages. ICCE can govern the instructions and evidence surrounding payment without obtaining unrestricted ability to redirect or misuse money intended for workers.

The Component records the relationship between the payroll outcome produced, the payment activity authorised, the returned payment status and the final reconciled evidence retained by ICCE.

Connects
  • verified payroll outcomes
  • authorised payment instructions
  • tracked execution status
  • returned payment outcome
  • reconciled payment evidence
Produces

A traceable evidence relationship between what should have been paid, what was instructed and the final recorded payment outcome.

Why it matters

Correct payroll calculation alone does not prove that the resulting obligation was handled correctly. The Payment Trust Centre completes the transaction-evidence chain.

Payment reconciliationControlled execution
Instructions126
Settled122
Pending status4
Worker payment W-48201Payroll item PAY-06137
Settled
Statutory payment batchInstruction group ST-0612
Accepted
Worker payment W-48318Awaiting returned execution status
Pending
Reconciliation group R-0626122 of 126 outcomes confirmed
In progress

System outcome

Clear ownership without loss of connection.

System Components give ICCE an operating structure in which every principal responsibility has a defined home. The environments remain separate enough to preserve accountability and connected enough to create one progressive record of employment, payroll, payment and evidence activity.