ifrCoworker

com.spocont/ifrCoworkerVersion 3.4.0

IFRS engine: 31 standards, 20 tools. Journal entries, XBRL tags, ECL, CGU impairment, deferred tax.

Status

Responds97 msNov 14, 2026, 14:16 UTCAnswered our handshake without sign-in.

Registry data may be out of date

We could not refresh it, so this page shows the last copy.

Last checked: Nov 14, 2026, 14:16 UTC
Latency: 97 ms
Remotes responding: 1 of 1
Sign-in: No sign-in
Hosting: EU hosting detected (detected, not a legal statement)
Registry data as of: Nov 14, 2026, 22:14 UTC

Data from the official MCP Registry, checked by run.zero. How we check

Connect

Streamable HTTP

https://mcp.ifrcoworker.app/Responds97 msNov 14, 2026, 14:16 UTC

No sign-in

Claude Code

claude mcp add --transport http ifrcoworker https://mcp.ifrcoworker.app/

Claude Desktop and claude.ai

1
2
3

Settings > Connectors > Add custom connector
Name: ifrcoworker
Remote MCP server URL: https://mcp.ifrcoworker.app/

Cursor

{
  "mcpServers": {
    "ifrcoworker": {
      "url": "https://mcp.ifrcoworker.app/"
    }
  }
}

VS Code

code --add-mcp '{"name":"ifrcoworker","type":"http","url":"https://mcp.ifrcoworker.app/"}'

Built your own server? run.zero hosts MCP servers on European infrastructure.

Host your own MCP server on run.zero

Tools

20 tools

Tools of ifrCoworker
	Description		Read-only	Idempotent	Open world
`ifr_amortisation_schedule`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 is the same item with its dates moved on — no manual carry-forward required. ias16 / ias38 / ias40 (cost model): the cost, dates, residual value and method are kept, and the closing accumulated depreciation (amortisation) and accumulated impairment carry into the next period (IAS 16.30, IAS 38.74, IAS 36.63); an opening the engine derives from the dates is left to it. A period's IAS 36 test (indicators, fair value, value in use, recoverable amount) is not carried: a clean assessment (impairmentIndicatorsPresent: false) is assumed for the later periods and stated in that row's assumptions; after a positive one the next period asks for its own assessment — state it in periodFacts, keyed by that period's reportingDate, and the schedule rolls on it (IAS 36.9, 36.63). Deferred tax: the closing deferred tax balance carries as the next opening (IAS 12.58); the tax base is an amount at each reporting date and is not carried (state it per period in periodFacts); the tax rate and the recoverability judgement are carried as stated assumptions unless periodFacts states them. ias40 under the fair value model is refused (each period is measured at the fair value at its own reporting date, IAS 40.33, 40.35) — call ifr_calculate per period. ifrs16: the lease is rolled on its own dates; a restoration obligation measured at commencement becomes restorationAtCommencement (IFRS 16.24(d)) and the current estimate is carried as a stated assumption (IAS 37.59). ifrs9 (amortised cost only — an instrument at fair value is refused from period 2, its measurement being the fair value at each reporting date, IFRS 9.5.2.1, IFRS 13	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 is the same item with its dates moved on — no manual carry-forward required. ias16 / ias38 / ias40 (cost model): the cost, dates, residual value and method are kept, and the closing accumulated depreciation (amortisation) and accumulated impairment carry into the next period (IAS 16.30, IAS 38.74, IAS 36.63); an opening the engine derives from the dates is left to it. A period's IAS 36 test (indicators, fair value, value in use, recoverable amount) is not carried: a clean assessment (impairmentIndicatorsPresent: false) is assumed for the later periods and stated in that row's assumptions; after a positive one the next period asks for its own assessment — state it in periodFacts, keyed by that period's reportingDate, and the schedule rolls on it (IAS 36.9, 36.63). Deferred tax: the closing deferred tax balance carries as the next opening (IAS 12.58); the tax base is an amount at each reporting date and is not carried (state it per period in periodFacts); the tax rate and the recoverability judgement are carried as stated assumptions unless periodFacts states them. ias40 under the fair value model is refused (each period is measured at the fair value at its own reporting date, IAS 40.33, 40.35) — call ifr_calculate per period. ifrs16: the lease is rolled on its own dates; a restoration obligation measured at commencement becomes restorationAtCommencement (IFRS 16.24(d)) and the current estimate is carried as a stated assumption (IAS 37.59). ifrs9 (amortised cost only — an instrument at fair value is refused from period 2, its measurement being the fair value at each reporting date, IFRS 9.5.2.1, IFRS 13	No	Yes	Yes	No
`ifr_apply_ias10`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.	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.	No	Yes	Yes	No
`ifr_batch_validate`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). A fact the settlement classification requires is refused here as the batch refuses it (SETTLEMENT_FACTS): an IFRS 16 finance lessor's instalments need accountingPolicy.ifrs18SpecifiedMainBusinessActivities (groupErrors: MISSING_REQUIRED, naming the items). When every item passes, the batch itself is run on the same request (nothing stored, nothing charged), so the checks it makes after calculating — the bank and cash-box balances footed against the general journal (IAS 7.45), among others — are answered here too: such a refusal comes back as allValid: false with groupErrors and batchRefusal. allValid: true therefore means ifr_period_end_batch will not refuse the same request. 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.	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). A fact the settlement classification requires is refused here as the batch refuses it (SETTLEMENT_FACTS): an IFRS 16 finance lessor's instalments need accountingPolicy.ifrs18SpecifiedMainBusinessActivities (groupErrors: MISSING_REQUIRED, naming the items). When every item passes, the batch itself is run on the same request (nothing stored, nothing charged), so the checks it makes after calculating — the bank and cash-box balances footed against the general journal (IAS 7.45), among others — are answered here too: such a refusal comes back as allValid: false with groupErrors and batchRefusal. allValid: true therefore means ifr_period_end_batch will not refuse the same request. 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.	No	Yes	Yes	No
`ifr_calculate`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"). Carried as itemId on every journal entry and in the Item column of the CSV and the workbook (Reference is the IAS/IFRS paragraph). 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. IFRS 19 (EARLY ADOPTER: effective 2027-01-01): input.accountingPolicy.ifrs19Election is an explicit yes or no, { apply: false } or { apply: true, isSubsidiary, hasPublicAccountability, parentPublishesIfrsConsolidatedStatements } (IFRS 19.7); omitted, it counts as no. Elected, the disclosures answer on the reduced IFRS 19 requirements; nothing measured or posted moves (IFRS 19.2). 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 (th	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"). Carried as itemId on every journal entry and in the Item column of the CSV and the workbook (Reference is the IAS/IFRS paragraph). 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. IFRS 19 (EARLY ADOPTER: effective 2027-01-01): input.accountingPolicy.ifrs19Election is an explicit yes or no, { apply: false } or { apply: true, isSubsidiary, hasPublicAccountability, parentPublishesIfrsConsolidatedStatements } (IFRS 19.7); omitted, it counts as no. Elected, the disclosures answer on the reduced IFRS 19 requirements; nothing measured or posted moves (IFRS 19.2). 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 (th	No	Yes	Yes	No
`ifr_calculation_sheets`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.	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.	No	Yes	Yes	No
`ifr_check_quota`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).	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).	No	Yes	Yes	No
`ifr_disclosure_checklist`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). With accountingPolicy.ifrs19Election: { apply: true, … } (EARLY ADOPTER: effective 2027-01-01; IFRS 19.7) it answers from the reduced IFRS 19 requirements instead; omitted or apply: false, the full ones. 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.	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). With accountingPolicy.ifrs19Election: { apply: true, … } (EARLY ADOPTER: effective 2027-01-01; IFRS 19.7) it answers from the reduced IFRS 19 requirements instead; omitted or apply: false, the full ones. 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.	No	Yes	Yes	No
`ifr_ecl_provision_matrix`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 the entity's historical loss rates per bucket, adjusted by its stated forwardLookingAdjustment for current conditions and forecasts (IFRS 9.B5.5.35, B5.5.52). Returns per-invoice ECL, portfolio summary, movement schedule (opening − write-offs → closing allowance, 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.	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 the entity's historical loss rates per bucket, adjusted by its stated forwardLookingAdjustment for current conditions and forecasts (IFRS 9.B5.5.35, B5.5.52). Returns per-invoice ECL, portfolio summary, movement schedule (opening − write-offs → closing allowance, 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.	No	Yes	Yes	No
`ifr_explain_result`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.	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.	No	Yes	Yes	No
`ifr_flag_result`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.	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.	No	No	No	No
`ifr_generate_workpaper`Generate a structured audit working paper JSON from one or more prior ifr_calculate results. Aggregates across standards: accounting policies (IAS 8.27A), key estimation uncertainties (IAS 8.31A), 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_VALUE) are not charged.	Generate a structured audit working paper JSON from one or more prior ifr_calculate results. Aggregates across standards: accounting policies (IAS 8.27A), key estimation uncertainties (IAS 8.31A), 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_VALUE) are not charged.	No	Yes	No	No
`ifr_ingest_document`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.	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.	No	Yes	No	Yes
`ifr_input_schema`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.	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.	No	Yes	Yes	No
`ifr_period_checklist`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.	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.	No	Yes	Yes	No
`ifr_period_end_batch`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: 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, def	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: 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, def	No	Yes	Yes	No
`ifr_propose_mapping`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.	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.	No	Yes	Yes	No
`ifr_replay`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.	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.	No	Yes	Yes	No
`ifr_route_event`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 the autoCascades 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.	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 the autoCascades 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.	No	Yes	Yes	No
`ifr_schema`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` (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.	No	Yes	Yes	No
`ifr_validate`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 judgement (0 / false / enum). These judgement values must come from the USER — never invent them.	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 judgement (0 / false / enum). These judgement values must come from the USER — never invent them.	No	Yes	Yes	No

Details

Registry status: Active
Published: Oct 13, 2026
Updated: Oct 13, 2026
Website: Not given
Repository: Not given
Categories (suggested): Documents Knowledge and notesSuggested categories are assigned automatically from the registry text and may be wrong. Verified operators can correct them.
GDPR: Not declared

Are you the operator? Claim this listing