An ESEF reviewer at a national competent authority opens a fresh extension taxonomy on a Monday morning. The first thing they look for is restraint. The good filings extend three or four times across the entire annual report. The bad ones extend forty, often because somebody re-typed the IFRS label to match the issuer's preferred wording and the agent dutifully created a new concept around it. Stylistic preference is the wrong reason to extend. Authoring an extension is a permanent act: every consumer of the filing now has to learn a new local concept, and your auditor has to defend why it was needed.
The tension lives in two directions. On one side, the base taxonomy genuinely cannot anticipate every entity-specific reporting line, especially in industries with idiosyncratic line items (mining royalties, biological assets, regulated utility deferrals). On the other side, IFRS already covers most of what most issuers report, and the SEC Sample Letter and ESEF Reporting Manual both push filers toward base concepts before extension. The discipline is simple: search the base taxonomy first, find the closest concept, and only extend when no concept honestly fits.
There are two extension shapes worth distinguishing. The first is a true specialisation: an entity-specific concept like a provision for a particular regulated activity, where the meaning is genuinely narrower than any single base concept. The second is a subtotal: an aggregation of base concepts that the issuer wants to total. Reporting Manual paragraph 1.4.1 paragraph 10 exempts pure subtotals from wider anchoring, but they still have to participate in the calculation linkbase so the consumer arithmetic adds up.
Mechanically, declaring an extension is straightforward but unforgiving. The local name is PascalCase with no spaces, derived from xbrli:item or xbrli:tuple, and the concept must declare its periodType (instant for stocks, duration for flows). Monetary concepts must declare balance debit or credit, because that single attribute drives sign convention everywhere downstream. Get the balance wrong and every consumer reads your filing inverted.
Use a base concept when one fits. Extensions exist for genuinely entity-specific concepts that the base taxonomy does not cover, not for stylistic preference.
ESEF Reporting Manual 1.2.2 permits replicating IFRS concepts that are not yet incorporated into the ESEF taxonomy. SEC EDGAR pushes filers toward base concepts via Sample Letter guidance.
Subtotals are extensions of a different kind: they aggregate base concepts. ESEF does not require wider anchoring on pure subtotals (Reporting Manual 1.4.1 paragraph 10), but they must still participate in the calculation linkbase.
Authoring an extension means defining the concept (PascalCase local name, derived from xbrli:item or xbrli:tuple), wiring it into presentation, calculation, and definition linkbases, and supplying labels in the reporting language plus English.
Concept names: PascalCase, no spaces. Monetary concepts must declare balance debit or credit. periodType is mandatory. Derived from xbrli:monetaryItemType (or appropriate item type).
<xs:element name="ProvisionForRestructuringWasteManagement"
id="acme_ProvisionForRestructuringWasteManagement"
type="xbrli:monetaryItemType"
xbrli:periodType="instant"
xbrli:balance="credit"
substitutionGroup="xbrli:item"
abstract="false"
nillable="true"/>3 questions. Druk op 1 tot 4 om te kiezen, Enter om te bevestigen.
Door deze quiz af te ronden, markeer je deze sectie als voltooid.
Tip: kies met 1 tot en met 4 en bevestig met Enter.