ifrCoworker

Compute a multi-period amortisation / depreciation / EIR amortisation schedule by rolling reportingDate forward one period at a time. Supported standards: ias16 (PPE depreciation), ias38 (intangible amortisation), ias40 (investment property — cost model), ias23 (borrowing cost capitalisation), ifrs9 (EIR amortisation), ifrs16 (lessee ROU + lease liability). Each period uses the closing carrying amount of the previous period as the opening balance — no manual carry-forward required. Returns a schedule array: [{period, reportingDate, carryingAmount, journalEntries, charges:{depreciation, interest, pnlImpact}}]. Cost: 1 credit per successfully computed period. Cap: 60 periods.

Apply IAS 10 (Events After Reporting Period) overlay to a prior calculation output. Classifies events as adjusting/non-adjusting, assesses going concern, generates adjusted journal entries. Most standards auto-trigger IAS 10 when subsequentEventDate + subsequentEventKind are provided — use this tool only for manual overlay or multi-standard combinations.

FREE pre-flight validator for ifr_period_end_batch. Validates every item in one call and returns all missing required fields across the batch. A field an item's standard does not declare is refused here exactly as ifr_period_end_batch refuses it (FIELD_UNRECOGNISED, naming the field and the item — G-1795). A fact the settlement classification requires is refused here as the batch refuses it (SETTLEMENT_FACTS — G-1841): an IFRS 16 finance lessor's instalments need accountingPolicy.ifrs18SpecifiedMainBusinessActivities (groupErrors: MISSING_REQUIRED, naming the items). STRICT GATE: do not call ifr_period_end_batch if allValid is false. Relay agentMessage to the user, collect missing data, re-run ifr_batch_validate, and only proceed once allValid is true. Zero credits — validation is credited inside the subsequent batch call.

If you know the economic object type but not the standard, pass `elementType` instead of `standard`. The discriminator field (`assetClass` for 'asset', `investmentType` for 'equity-method-investment') must be included in the `input` object. Run a full IFRS/IAS calculation. Returns journal entries, disclosures, measurements, and compliance notes. REQUIRED INPUT FIELD: `id` — include in the `input` object (e.g. input.id:"MACHINE-A"). Stamped as Reference on every journal entry and CSV row. Before calling this tool, call ifr_input_schema (fast, free, typed JSON Schema) or ifr_schema (full documentation with copy-paste examples). Boolean recognition gates require explicit true — absent = gate closed. Measurement inputs (discountRatePreTax, expectedSettlementDate, usefulLifeEndDate) have no engine defaults. Cross-standard redirects fire automatically when relevant fields are provided. CASCADE TRACE: every response includes `context.cascadeTrace` — an array of every standard chain evaluated: { child, mode:"PRE_CALCULATION"|"POST_CALCULATION", status:"fired"|"skipped", skipReason?, result? }. PRE_CALCULATION = satellite inputs resolved before the primary calc (e.g. IAS 23 borrowing costs → capitalised into IAS 16 cost). POST_CALCULATION = consequential standards applied to the primary result (e.g. IAS 12 deferred tax on the asset temporary difference). status:"skipped" entries carry a machine-readable skipReason — the chain was considered, not merely omitted. This is audit-grade completeness evidence. CONSIDERATION TIERS (three-state conditionality): schema.cascades entries carry considerationTier MANDATORY or CONDITIONAL. A MANDATORY consideration (IAS 36.9 indicator assessment; IAS 12 temporary differences; IAS 23 borrowing costs and IAS 37 dismantling/restoration at initial recognition; IFRS 16.9 embedded-lease assessment on IFRS 15 contracts) must be addressed on every applicable call: supply the data evidence fields OR explicit denial evidence (dismantlingEstimate: 0, impairmentIndicatorsPresent: false, leaseInContract: false, deferredTaxAssessment: "HANDLED_CENTRALLY"|"NOT_APPLICABLE"|"NO_TEMPORARY_DIFFERENCE") — omitting both FAILS validation. Denial evidence is human judgment: ASK THE USER for it, never fabricate it. Explicit denials appear in cascadeTrace as skipReason JUDGED_NOT_APPLICABLE with the evidence quoted; CONDITIONAL chains stay presence-based (TRIGGER_FIELDS_ABSENT / CONDITION_NOT_MET). Response includes correlationId — pass it to ifr_flag_result if the output looks incorrect. DOWNLOAD: context.calculationSheetsUrl contains a direct download link for an 8-sheet Excel workbook (Journal Entries, Movements Balance, Movements in SoFP, Financial Performance, OCI, Movements in Equity, Cashflow, Disclosure Checklist) valid for 24 hours. It is fetched with the IFRS token (Authorization: Bearer <token>) and each download costs 15 credits; opened in a browser without the token it answers 401 — so do not hand it to the user as a link to click: fetch it yourself if you can send the header, or tell the user the workbook is waiting under 'Downloadable workbooks' at https://ifrcoworker.app/#downloads (signed in). INPUT COVERAGE: data.ignoredInputs lists every submitted field the taken calculation path did not use (CF 2.13 completeness). When non-empty, the engine AUTOMATICALLY flags the answer for quality check server-side (context.ignoredInputsAlert carries the flagId) — review the listed fields and, if a different branch was intended, adjust the activating fields and recalculate. COMPANION EVENTS — after every standard call, check whether any of these signals are present in the scenario. Standard controllers compute measurements (depreciation, fair value, interest) but do NOT produce journal entries for: (1) CASH TRANSACTION — "paid cash", "cash consideration", "cash purchase", "cash settled": add ASSET_PURCHASE_CASH via general-journal, OR set acquisitionPaymentMode:CASH + acquisitionPaymentDate on IAS 16 / IAS 38 / IAS 40 / IFRS 6 and the companion JE is auto-generated. (2) EQUITY / SHARE TRANSACTION — "share issuance", "rights issue", "bonus shares", "warrant exercise": use general-journal with eventType SHARE_ISSUANCE_WITH_PREMIUM / BONUS_ISSUE / RIGHTS_ISSUE / WARRANT_EXERCISE. (3) REALISED FX SETTLEMENT — "FX settled", "realised exchange gain/loss", "foreign currency transaction settled": set settlementMode:CASH + settlementDate on IAS 21 for auto-generated companion JE, or use general-journal FX_GAIN_REALISED / FX_LOSS_REALISED. (4) ACCRUALS / PREPAYMENTS — "accrued expense", "period-end accrual", "prepayment paid", "advance payment": use general-journal ACCRUAL_RECOGNISED / ACCRUAL_REVERSED / PREPAYMENT_PAID. (5) BAD DEBT — "write off receivable", "bad debt written off", "recover bad debt": use general-journal BAD_DEBT_WRITE_OFF / BAD_DEBT_RECOVERY. (6) PROVISION UTILISED — "provision paid", "utilised against provision", "provision settled in cash": use general-journal PROVISION_UTILISED. (7) INTERCOMPANY — "loan to subsidiary", "intragroup loan", "management fee recharge": use general-journal INTERCOMPANY_LOAN_ADVANCED / INTERCOMPANY_LOAN_REPAID / INTERCOMPANY_RECHARGE. (8) WITHHOLDING TAX / PAYE / DEDUCTIBLE VAT — "WHT on dividend", "PAYE remittance", "income tax withheld from salary", "input VAT reclaimable", "deductible VAT on purchase": these are cash-settled government remittances not produced by the measurement controllers — use general-journal WITHHOLDING_TAX or EXPLICIT entries (DR WHT Payable / CR Cash; DR Input VAT / CR Cash). NOTE: "deferred tax" does NOT require a companion event — IAS 12 auto-fires from the main input. "Current/non-current reclassification" is a presentation change only — no JE. Call ifr_schema({ standard: "general-journal" }) to discover all available general-journal event types.

Retrieve the calculation-sheets workbook for a prior ifr_calculate or ifr_period_end_batch call. Returns a downloadUrl for the XLSX workbook (GET /api/ifrcoworker/calculation-sheets/{correlationId} with Bearer token) and a structured JSON summary of each sheet's data (journalEntries count, trialBalance accounts, financialStatements sections, disclosureNotes). The workbook also includes an editable valuation pack (analytical, not IFRS-required): a DCF model sheet with pre-filled assumptions (3% growth, 12% discount rate — amber editable cells), a standard-tagged net-debt bridge (IFRS 16 leases, IAS 19 pension, IAS 37 provisions, IFRS 3 consideration) and a multiples/EV-bridge sheet. Records are persisted in MongoDB for 24 hours — no re-calculation needed. This tool is free; downloading the workbook from downloadUrl costs 15 credits. Token required.

Check your remaining ifrCoworker credits without consuming any. Returns creditsRemaining, creditsUsedToday, fullAccess flag, and a cost estimate for batch calls. FREE — does not decrement quota. Call before a large batch to verify you have enough credits. batchCostEstimate.perItem = credits per successfully computed batch item; batchCostEstimate.preflightFree = true (validation phase never charges).

Generate a disclosure-needs checklist for the period-end. FREE — no credit charged. Input: entityProfile fact flags (same shape as ifr_period_checklist) → returns the core MANDATORY disclosure requirements per applicable standard, each with its IAS/IFRS paragraph reference and category (policy / reconciliation / judgement / amount / risk). Optionally pass prior results inline via `calculations` (full ifr_calculate responses or a whole ifr_period_end_batch result) and each requirement is reconciled against the disclosures the engine actually produced: status per item = complete (value computed) | needs-entity-data (emitted but value null — narrative needed) | incomplete (calculated but requirement not addressed — investigate) | pending-calculation (standard applies, nothing supplied yet) | not-applicable. Use at period-end sign-off: run the batch, pass the batch result here, and work the non-complete items. Catalogue covers effective standards only.

IFRS 9 Simplified Approach — ECL provision matrix for trade receivables, IFRS 15 contract assets, and IFRS 16 lease receivables. Ages each receivable into buckets (current / 1-30 / 31-60 / 61-90 / 91-180 / 180+ days past due). Applies entity-supplied historical loss rates per bucket. Returns per-invoice ECL, portfolio summary, movement schedule (opening→closing provision, P&L charge), and IFRS 7.35H disclosure stub. NOT for the general 3-stage approach (loans, bonds) — use ifr_calculate with standard "ifrs9" for those. Token required; costs 10 credits.

Return a human-readable explanation of a previously computed calculation. Pass the correlationId from any ifr_calculate or ifr_period_end_batch response (this tool reads a 10-minute result cache; the workbook of the same id stays downloadable for 24 h), OR pass the full prior response object as `calculation` — the stateless path, works at any time with no expiry. Returns a plain-language summary of the journal entries, IFRS paragraph references, and suggested next steps. FREE — no credit charged.

Flag a calculation result you believe is incorrect for expert review. Call immediately when the server output appears to contradict IFRS — wrong amount, missing journal entry, incorrect OCI/P&L routing, wrong paragraph, or missing disclosure. FREE — no credit charged. MINIMUM REQUIRED: standard + severity + aiReasoning (where it is wrong and why, citing the IFRS paragraph) + correlationId. The correlationId is sufficient — the server auto-attaches the full calculation from its cache. Do NOT copy the entire server response into serverOutput. RECOMMENDED: schemaVersionControlHash — pass the 12-char hex from the ifr_schema response you used when building the input. This lets the review team reproduce the exact schema version that generated the error. Severity: CALCULATION_ERROR | MISSING_DISCLOSURE | WRONG_JE | WRONG_PARAGRAPH | WRONG_OCI_PL_ROUTING | OTHER.

Generate a structured audit working paper JSON from one or more prior ifr_calculate results. Aggregates across standards: accounting policies (IAS 1.117), key estimation uncertainties (IAS 1.125), calculation workings, journal entries, and a disclosure completeness checklist. Reference prior results EITHER by correlationIds (server-side cache, 10-minute TTL from calculation time) OR by `calculations` (inline prior ifr_calculate response objects — stateless, no expiry; mix freely with correlationIds). If any correlationId has expired, the call fails with CORRELATION_EXPIRED — pass those results inline via `calculations` instead. Token required; costs 5 credits per included calculation on success (e.g. 3 standards = 15 credits). Failed calls (CORRELATION_EXPIRED, INVALID_INPUT) are not charged.

Extract structured data from a PDF (contract, invoice, lease, bond indenture) using Google Document AI. Requires docuScanAccess on the token — returns 403 otherwise; do NOT retry or offer document scanning again this session if access is denied. PROTOCOL: (1) offer PDF processing to the user, (2) receive pdf as base64, (3) call this tool with pdf_base64 + the label of the value to extract, (4) call ifr_propose_mapping, (5) review the mapping WITH THE USER before calling ifr_calculate — OCR is never 100% accurate.

Returns the JSON Schema for the input to ifr_calculate for a given standard. Use this to discover required fields, enum values, and defaults without calling ifr_schema. Returns a standard JSON Schema object suitable for programmatic validation. Derived from the controller FIELD_DEFINITIONS — always reflects the current engine version. FREE — no usage charge.

Planning tool for a full period-end close. Pass an entityProfile of fact flags (hasInventory, hasPPE, hasLeases, hasFinancialInstruments, isGroup, isListed, incomeTaxApplicable, etc.) and get back the exact ordered list of IFRS/IAS standards to run for this entity — each with its requiredInputFields and its opening* carry-forward fields. Run the standards in executionOrder, or submit them together as an ifr_period_end_batch (which sorts internally). For each standard, carry the prior period's closing* outputs into the matching opening* inputs — the engine is stateless and holds no entity config or prior balances. FREE — no usage charge. Call this BEFORE ifr_batch_validate / ifr_period_end_batch to know what to assemble.

THE period-end execution tool — process multiple IFRS calculations for a reporting period in one call (year-end, quarter-end, or month-end). One tool, three modes: (1) PLAIN BATCH (default): items + accountingPolicy → per-item results, every item's journal entries in one list, trial balance, and all financial statements. (2) SUMMARY: leave includeWorkings false (the default) for the compact ~200KB response; set includeWorkings:true only when step-by-step workings are needed (~600KB). (3) CLOSE: additionally pass entityProfile (fact flags) for a one-call period-end close — the response gains the applicability checklist, recommendedOrder, and a coverage analysis flagging any standard the profile implies but no item was supplied for (the checklist/coverage portion is free). REQUIRED: each item's `input` object must include an `id` field (e.g. { type:"ias37", input:{ id:"PROV-LEGAL-001", ...otherFields } }) — validated by the controller schema; stamped as Reference on every journal entry for that item. GROUP vs BATCH (G-1700): items of ONE entity → its separate statements; items of TWO OR MORE entities (input.entityId) + the group block (parent, entities[] with the control facts, intragroup rows) + previousPeriodBalances with row.entity → each entity's separate statements AND the consolidated set in one call (the IFRS 10 group cascade fed with the statements derived from the entities' own items). An ifrs10 item in a one-entity batch is refused. With the entities' statements already in hand, call the group cascade directly (ifr_calculate, elementType "group"). CASCADE TRACE: each item result carries `context.cascadeTrace` — every cross-standard chain evaluated (PRE satellite inputs + POST consequential standards), each with status "fired" or "skipped" and a skipReason when skipped. This is the per-item completeness record. MANDATORY CONSIDERATIONS: every item must address its tier-1 cascade considerations (data OR explicit denial evidence — impairmentIndicatorsPresent: false, deferredTaxAssessment enum, dismantlingEstimate: 0...); preflight validation rejects silent omissions and these judgment fields are EXCLUDED from auto-fill — collect the answers from the user (ifr_period_checklist lists them per standard under mandatoryConsiderations). INPUT COVERAGE: each item's data.ignoredInputs lists submitted fields the taken path did not use; affected items are rolled up in the batch-level ignoredInputsAlerts and each was AUTOMATICALLY flagged for quality check server-side. UNDECLARED FIELDS (G-1795): a field on an item that its standard does not declare is REFUSED before anything is calculated (FIELD_UNRECOGNISED, naming the field and the item) — the same answer ifr_batch_validate gives; nothing is silently ignored. input.entityId is the batch's entity dimension and is never refused. ACCOUNTING POLICY — build the accountingPolicy block BEFORE calling this tool. Always include at top level: functionalCurrency, presentationCurrency, reportingDate, previousReportingDate. Each standard that appears in items[] may also need its own policy block (measurement model, cost formula, presentation method...). Do NOT guess these: the ifr_schema response for a standard carries `batchAccountingPolicySchema` with that standard's required policy fields and their allowed values, generated from the engine itself. For the whole table in one place, read ifrs://reference/accounting-policy-choices. RATE GOVERNANCE: discount/interest rates are explicit inputs — preflight rejects (free, no credits) any item whose required rate is missing. Supply rates per item, or once for the whole batch via accountingPolicy.reportingInterestRates { corporateBondYield (IAS 19.83), riskFreePreTax (IAS 37.47 — provisions, dismantling/restoration), governmentBondYield, riskFreePostTax }. Lease rates (IFRS 16.26 implicit rate / IBR) and instrument EIRs are lease/instrument-specific — always per item, never a policy default. Which rate type applies where: read ifrs://reference/discounting-and-interest-rate-guide; each schema response lists its rateRequirements. ASSEMBLY WORKFLOW: (1) IDENTIFY — for each item whose standard is not explicitly named, call ifr_route_event in parallel to resolve the slug. (2) FREE VALIDATE LOOP — assemble all items[] plus accountingPolicy, then call ifr_batch_validate (free). Fix all reported errors and repeat until allValid: true. Never call ifr_period_end_batch until allValid is true — the validate loop costs zero credits. (3) CALCULATE — once allValid: true, submit to ifr_period_end_batch in the DEFAULT mode (do NOT pass mode). The default mode is the one that assembles and returns the consolidated output; only it returns the trial balance, the financial statements and the workbook link. It returns every item's journal entries in one list (batchJournalEntries), trial balance grouped by XBRL section (Assets, Liabilities, Equity, PL, OCI), financial statements, cash flow statement and disclosure notes. DOWNLOAD (default mode only): the response includes calculationSheetsUrl — a direct link to an 8-sheet Excel workbook (Movements in SoFP, Financial Performance, OCI, Movements in Equity, Cashflow, Disclosure Checklist, Journal Entries, Movements Balance) valid for 24 hours. It is fetched with the IFRS token (Authorization: Bearer <token>) and each download costs 15 credits; opened in a browser without the token it answers 401 — so do not hand it to the user as a link to click: fetch it yourself if you can send the header, or tell the user the workbook is waiting under 'Downloadable workbooks' at https://ifrcoworker.app/#downloads (signed in). RESILIENCE FALLBACK — mode: "partial": pass this ONLY to stop one bad item rejecting the whole batch. It validates-then-calculates each item independently and returns per-item results in results[i].result.data (status "ok" | "validation_error" | "calculation_error"); it does NOT assemble or return batchJournalEntries, trialBalance, financialStatements, cashFlowStatement, disclosureNotes, crossChecks/selfCheck or calculationSheetsUrl, and it persists no workbook. Use it to isolate the failing item, fix that item, then re-run the whole batch in the default mode to obtain the consolidated statements and the download link. SIZE CONTROL: the response defaults to compact. includeWorkings, includeXbrlEnrichment and exportXbrl each enlarge it — read their field descriptions in this tool's input schema before setting any of them. The trial balance always carries xbrlElement, xbrlSection and xbrlLabel regardless of those flags. DELIVERY TO A GOOGLE SHEET — BEFORE you call this tool, ask the user explicitly whether they want the output (the .csv journal entries AND the financial statements) delivered back into a Google table (Google Sheet), or just returned inline. If the user says yes: FIRST verify that you (the calling agent) have a working Google Sheets / Drive connector and can actually write to it — perform a real write test (create or append a throwaway cell), not just a capability assumption. If no Google Sheets connector is connected or the write test fails, tell the user and DO NOT run the batch — this call is billable and the result could not be delivered where requested; resolve the connection first. Only once the export path is confirmed: call this tool with exportJournalCsv: true, then write the returned journalCsvFile content and the financialStatements into the Google Sheet. BATCH SIZE GUIDANCE: aim for ≤50 economic events (line items) per call to stay within context window limits and receive full workings. Above 50 items the response grows rapidly; above 200 items you will very likely receive a compact response (workings and disclosures stripped, journal entries + statements + trial balance remain intact). If the user has more than 50 economic events, split into multiple calls of ≤50 items each, then merge the trial balances and journal entry lists in your context — do not attempt a single call with 200+ items unless the user explicitly accepts compact output.

Map OCR data from ifr_ingest_document into an IFRS standard's input schema and validate it. Returns proposedInput, unmappedFields, missingRequiredFields, validation errors/warnings, needsUserInput[], and a confidence score. CRITICAL: proposedInput is a suggestion — every entry in needsUserInput[] must be confirmed by the user before calling ifr_calculate. Never auto-calculate from unverified OCR data. FREE — no usage charge.

Deterministic audit replay — recompute a prior calculation from its input and verify it reproduces the stored output. FREE — no credit charged. The engine is stateless and pure: identical input + identical engine/schema version always produces identical output. Every ifr_calculate response carries an `audit` envelope { inputEcho, inputSha256, outputSha256, engineVersion, schemaVersionControlHash } — pass audit.inputEcho as `input` and audit.outputSha256 as `expectedOutputSha256` at ANY later time (no expiry, nothing stored server-side). match:true = cryptographic-grade evidence the stored numbers re-derive from the stored inputs. match:false = engine or schema evolved since the original calculation (compare engineVersion / schemaVersionControlHash), or the stored output was altered — pass the original response `data` as expectedOutput to get a field-level diff of every changed value. Use cases: external audit evidence, period-end sign-off re-verification, regression checking stored results after engine upgrades.

ROUTER — the entry point for every business event. Describe what happened in plain language ("bought a machine", "signed an office lease", "customer went bankrupt") and get back the exact call to make. FREE — no usage charge. Each match carries an `endpoint` block with the EXACT next call: the ifr_calculate arguments (economic elementType + discriminator where a cascade-element route exists, otherwise the standard slug), the REST cascade endpoint, and `autoCascades` — the child standards that fire automatically inside that one ifr_calculate call. CRITICAL: never call autoCascade standards separately — they execute inside the primary call and their results appear in `context.cascadeTrace`. Calling them again would duplicate journal entries. Copy `endpoint.mcpCall` instead of deriving routing yourself. The matched standards (top 3, with rationale and copy-paste-ready minimal examples) are supporting detail — the endpoint block is the answer. UTILITY SLUG (use ifr_schema + ifr_calculate with this when no IFRS standard applies): "general-journal" — universal "else" controller for ALL journal entries not covered by a dedicated IFRS/IAS standard. Four input modes: (1) EVENT-LABEL: expenseCategory (PERSONNEL, DIVIDEND_DECLARED, VAT_OUTPUT, WITHHOLDING_TAX, etc.; the IFRS 5.33(a) single amount of a discontinued operation is measured and posted by ifrs5, not here) + amount — auto-fills accounts and XBRL; (2) EXPLICIT: entries[] with DR/CR lines — per-line XBRL enrichment, statementPlacement, xbrlFacts[]; (3) PATTERN: pattern keyword string — matches one of 18 named JE_PATTERNS (associate dividend, salary+PAYE, VAT settlement, period close, etc.); (4) LINE-ITEMS: lineItems[] array for multiple independent event-label items. BEFORE calling ifr_calculate with standard "general-journal": read the MCP resource ifrs://reference/direct-je-patterns — it lists all 18 named scenarios with keywords and DR/CR account pairs.

If you know the economic object type but not the standard, pass `elementType` (e.g. 'lease', 'asset', 'financial-instrument') instead of `standard`. For multi-standard types (asset, equity-method-investment), also pass `assetClass` or `investmentType` to get the specific standard's schema. The recurring IFRS 10 group close is elementType 'group'; the IFRS 3 day-1 acquisition is 'business-combination'. This tool returns the input schema for a specific standard: field definitions, IAS/IFRS paragraph references, and a copy-paste-ready `exampleRequests.default` template. Use ifr_route_event if unsure which standard applies. CHOOSING THE RIGHT FIELD-DISCOVERY TOOL: (A) ifr_input_schema — lightweight, fast, free; returns a typed JSON Schema (required fields, types, enum values, defaults) with no prose; use when you need to validate your input programmatically or see which fields are required. (B) ifr_schema (this tool) — full documentation; returns field descriptions, IAS paragraph references, copy-paste `exampleRequests`, `exampleIndex`, and chaining guidance; use when you need to understand WHAT each field means, pick the right example variant, or onboard to a new standard. Both tools are safe to call in parallel. EXAMPLE SELECTION — after calling ifr_schema: (A) If the response contains `exampleIndex`: scan every key and pick the one whose description best matches your scenario — copy `exampleRequests[thatKey]` verbatim, do NOT default to `exampleRequests.default` when a more specific key exists. (B) If only `exampleRequests` is present: copy `exampleRequests.default`. In both cases revise every field to real business values. Field meanings are in `fields[fieldName].description` in the same response. SCHEMA VERSION CONTROL HASH: if reusing a cached input, compare the returned `schemaVersionControlHash` (12-char hex) against your previously recorded value — a changed hash means FIELD_DEFINITIONS were updated, discard the cached input and rebuild from the current schema.

If you know the economic object type but not the standard, pass `elementType` instead of `standard`. The discriminator field (`assetClass` for 'asset', `investmentType` for 'equity-method-investment') must be included in the `input` object. OPTIONAL pre-flight validator — only use when you need to surface errors to the user before attempting ifr_calculate. REQUIRED INPUT FIELD: `id` — include in the `input` object, same value as used in ifr_calculate. ifr_calculate validates internally and returns the same structured errors; calling ifr_validate first adds a round-trip without new information. Use when: user explicitly asks to check data, or when unsure about a complex array structure before committing. Returns errors, warnings, and missingFields with paragraph references. No silent defaults in MCP mode — all fields must be explicit. MANDATORY CONSIDERATIONS: validation rejects requests that leave a tier-1 cascade consideration unaddressed (UNADDRESSED errors) — e.g. no impairment-indicator assessment, no deferred-tax position, no dismantling decision at initial recognition. The error text names both cures: supply the data fields, or record the explicit judgment (0 / false / enum). These judgment values must come from the USER — never invent them.