Chapter 1 done. Ask for the rest.

You have finished chapter 1 of 10.

A colleague reads every request and opens the remaining chapters, usually within one working day. You then get an email with a link that picks the course up where you left off.

Still to come

  1. The XBRL ReportTake an XBRL report apart into facts, contexts, units and decimals, and learn what each one must state before a tagged number means anything.
  2. Concepts and SchemasPick the right XBRL concept for a line item, read a taxonomy schema, and spot the tag that quietly reports something other than what the row says.
  3. LinkbasesWork out which XBRL linkbase controls presentation, calculation, labels, definitions or references, and what breaks in a filing when one of them is wrong.
  4. Dimensions (XDT)Read a dimensional XBRL fact with its axes, members and typed dimensions, and see why a total can legitimately disagree with the rows above it.
  5. Inline XBRLFind the inline XBRL tags inside a rendered iXBRL document, and tell a properly tagged figure from one that only looks tagged.
  6. Validation and ErrorsTrace an XBRL validation error back to the fact that caused it, from a calculation inconsistency to an xbrldie dimension error. This chapter turns a validation report into a short list of things to fix.
  7. Taxonomies in the WildTell the Dutch SBR, ESEF, IFRS and US-GAAP taxonomies apart, and find which entry point and filing rules your annual report is judged against.
  8. Extensions and AnchoringDecide when a filing needs an XBRL extension element, and anchor it to the base taxonomy so the report stays comparable.
  9. Reading iXBRL and Prompting AgentsReview a tagged iXBRL annual report at speed, open an .xbri package in a reader, and brief an AI assistant so it fixes real validation errors instead of inventing plausible ones.

This is where your access link goes once the request is approved.

Doc2iXBRL uses your details to give you access to the course and to answer questions about it. We use your email address for iXBRL tips and product news only if you ask us to below. Read our privacy statement to see how we handle your data.

Back to chapter 1