What ISCC-EU actually requires from a software
ISCC-EU is governed by a small set of system documents — ISCC-EU 201 (System Basics), 203 (Mass Balance), 205 (System Documents) and 206 (Risk Assessment) being the ones that bite during audits. Together they require a documented mass balance per booking period (typically 12 months) and per group of products, with sustainability characteristics tracked at the batch level, supplier self-declarations on file before each delivery, and a documented risk assessment of the supply base.
What this means in practice is that software claiming to support ISCC-EU has to do four things well: ingest supplier self-declarations against the ISCC Annex templates, run a mass-balance ledger that follows the ISCC group-of-products rules, calculate GHG with eec/etd/ep/eccs/eccr per batch using ISCC-aligned defaults, and produce the exact audit pack the certification body asks for. GooClear was built specifically against these four obligations.