A platform may advertise support for IFRS 9 and FASB Accounting Standards Codification Topic 815, often called ASC 815, yet still fail because it cannot represent the entity’s elections, reproduce a valuation, generate controlled entries or preserve evidence across system handoffs.
Turn the accounting policy, hedge population and close architecture into acceptance tests before demonstrations begin. Where the hedge journal has to land inside a governed period-end sequence, test it against the close platform that owns task and journal state. This guide addresses software selection, not whether a specific instrument, hedged item, risk component or relationship qualifies. It does not approve an effectiveness method, valuation, journal, presentation or disclosure conclusion. Those judgments remain management’s responsibility and require a qualified hedge-accounting practitioner engaged by the company. Treat every standards reference here as a pointer to the source text, not as an accounting opinion.
Quick answer
A standards label without configuration, valuation, posting and evidence proof can hide material accounting errors, manual close work and audit gaps until implementation.
Decision: Approve, condition or reject the shortlist only after the proof of concept demonstrates the entity’s approved rule set, accounting policy, controlled outputs and system handoffs.
Key takeaways
- Treat every standards claim as a company statement until the configured product proves the entity’s current policy, elections and adoption status.
- Run separate IFRS and US GAAP cases where designation, effectiveness, rebalancing, de-designation, transition or presentation differs.
- Test valuation, accounting, disclosures, interfaces and audit replay as one controlled chain, not as isolated modules.
- Use mandatory evidence gates before weighted scoring; dashboards and user experience cannot offset a failed accounting or control requirement.
Freeze the applicable rule set before evaluating software
Build a dated rule matrix by reporting entity. The IFRS Foundation’s IFRS 9 standards page states that IFRS 9 is effective for annual periods beginning on or after 1 January 2018. It also permits an entity to apply IFRS 9 hedge accounting or continue applying IAS 39 hedge accounting. IFRS 9-only support is therefore not sufficient for every IFRS reporter.
For US GAAP, the current FASB Accounting Standards Codification is authoritative. FASB’s ASU 2017-12 says an Accounting Standards Update communicates Codification amendments; it is not itself authoritative. There is no single “ASC 815 effective date.” Identify the current Topic 815 content, entity class, relevant amendments, early adoption and transition elections.
| Source or amendment | Current status | Software consequence |
|---|---|---|
| IFRS 9 hedge accounting and IAS 39 policy choice | IFRS 9 has been effective from 1 January 2018; IAS 39 hedge accounting remains available through the policy choice. | Record the entity’s selected model and prevent an IFRS 9 configuration from being applied to an IAS 39 book. |
| Contracts Referencing Nature-dependent Electricity | The IFRS 9 and IFRS 7 amendments are required for annual periods beginning on or after 1 January 2026, with earlier application permitted. | Test the amendments only for in-scope electricity contracts and related disclosures; do not treat them as a universal hedge-accounting change. |
| IFRS 18 | IFRS 18 is effective for annual periods beginning on or after 1 January 2027, with earlier application permitted. | Assess presentation, disclosure and mapping effects. Do not infer that IFRS 18 changes IFRS 9 Chapter 6 qualification criteria. |
| ASU 2017-12 effective dates | ASU 2019-10 confirms effectiveness for public business entities for fiscal years beginning after 15 December 2018, and for other entities for fiscal years beginning after 15 December 2020, with later interim application for those other entities. | Treat the amended Topic 815 model as the baseline for affected entities in 2026, while retaining the entity’s adoption and transition record. |
| ASU 2025-09, Hedge Accounting Improvements | ASU 2025-09 is effective for public business entities for annual periods beginning after 15 December 2026 and for other entities after 15 December 2027. Early adoption is permitted on or after issuance. | Test both pre-adoption and adopted rule sets where relevant, including transition for existing relationships and the permitted modification of specified critical terms. |
| IFRS 9 hedge-accounting post-implementation review | The IASB’s July 2026 project update records tentative decisions for a forthcoming request for information. It does not amend IFRS 9. | Monitor the project, but do not configure staff feedback or tentative decisions as issued requirements. |
Qualified-practitioner review required: Approve the rule matrix, elections, adoption dates, transition choices and interpretations before configuration. A supplier can evidence implementation, not approve the buyer’s accounting policy.
Start with the accounting policy and hedge population
Begin with the conclusions the system must execute. Inventory entities, frameworks, elections, currencies, instruments, hedged risks, hedge types, designation practices, assessment methods, excluded components, valuation sources, journal treatments and disclosures. The hedged risks in that inventory arrive from the exposure and policy decisions treasury makes before execution, and the system inherits them rather than defining them.
The 2026 issued IFRS 9 requires formal designation and documentation at inception. The record must identify the instrument, hedged item, risk, objective, strategy and effectiveness method. Expected ineffectiveness and the hedge-ratio method also belong in controlled data that drives testing, accounting and disclosures.
Build the population at transaction and relationship level: current and expected hedges, portfolio cases, inactive relationships with reserve balances, forecast transactions, firm commitments, net investments, partial designations, layers and excluded components. Add rare material and framework-only cases. A dual reporter should not copy one result into both books.
Qualified-practitioner review required: Confirm eligible instruments, hedged items, risk components, hedge types, forecast-transaction assertions, excluded components and policy elections. The buyer guide can identify data and control requirements, but it cannot decide eligibility for a specific fact pattern.
Hedge accounting software requirements at a glance
Turn broad product claims into evidence requests. Adapt the rows to the entity’s policies and do not award points for a capability the approved hedge population does not need.
| Area | What the configured platform must demonstrate | Evidence to retain | Reject signal |
|---|---|---|---|
| Standards and versions | Separate rule sets, elections and effective dates by entity and book | Version matrix, release notes, configuration export and update process | “Global compliance” is the only description |
| Designation | Structured relationship data, policy validations, approvals and versioned documents | Completed designation, field lineage, approval log and amendment history | A detached document is the system of record |
| Effectiveness | Policy-approved qualitative and quantitative methods with reproducible inputs and exceptions | Input snapshot, method version, calculation, result and review record | Only a pass or fail badge can be exported |
| Valuation | Controlled market data, models, adjustments, overrides and independent comparison | Curve and rate lineage, model version, timestamp and tolerance review | Historical values cannot be rerun from frozen inputs |
| Accounting | Framework-specific entries, reserves, reclassifications, basis adjustments and reversals | Calculation-to-journal trace, mapping version, batch status and ledger response | Entries are an unbalanced or unaudited spreadsheet export |
| Lifecycle | Amendment, rebalancing, de-designation, discontinuation, maturity and correction logic | Before-and-after state, trigger, approval, calculation and posting effect | A prior relationship can be overwritten |
| Disclosures | Source-linked, framework-specific disclosure data and rollforwards | Disclosure-to-ledger reconciliation and manual-adjustment register | Reports cannot be tied to relationships and accounts |
| Integration | Controlled TMS, market-data, ERP and consolidation handoffs | Identifiers, control totals, acknowledgements, rejects, retries and reconciliation | File delivery is treated as successful accounting |
| Audit evidence | Immutable period packs, approvals, change history and independent export | Complete replay package retained outside the live user interface | The evidence disappears when a user or vendor account is closed |
Representative products with specialist hedge-accounting functions, documented as of 18 August 2026
This representative, unranked set covers specialist products, treasury-platform modules and software-plus-service offerings. It records only capabilities stated in official supplier documentation checked on 18 August 2026. Those pages do not prove that a configured product fits the buyer’s policy, produces accounting, operates controls or will satisfy an auditor.
| Platform | Officially documented capabilities, company-stated | What the buyer must demonstrate |
|---|---|---|
| Ripple Treasury (formerly GTreasury) | States support for ASC 815, IFRS 9 and IAS 39; designation through disclosure; effectiveness analytics; major hedge types; and ERP-connected workflow. | Licensed version, elections, methods, journals, disclosures, interface responses, data export and software-versus-service ownership. |
| Kyriba Derivative & Hedge Accounting | Lists ASC 815, IFRS 9 and IAS 39; designation, testing, valuation, entries, audit trails, de-designation and OCI reclassification. | Method settings, framework-specific de-designation, valuation controls, journal mapping, disclosure tie-out and retained history. |
| Derivative Path | Its page foregrounds ASC 815, interest-rate and FX hedges, designation memoranda, testing, journals, reports, regressions and Portfolio Layer Method cases. | IFRS scope if needed, asset classes, methods, advisory-versus-system ownership, calculation replay, disclosures and ERP results. |
| ION Treasury accounting and hedge accounting | States designation, testing, regression, valuation, journals, GL balances, lifecycle support and API or file exports across several treasury products. | Exact product, module, deployment and version; rule-release timing; interfaces; valuation governance and framework-specific outputs. |
| Bloomberg MARS HEFF | States documentation, US and international testing, multiple methods, reporting, disclosure output, valuation-adjustment integration and APIs. | Framework coverage, methods, journal scope, disclosure mapping, data entitlements, ERP or GL integration and change controls. |
| Wolters Kluwer OneSumX Hedge Accounting | The primer describes IFRS 9 and US GAAP orientation, designation, valuation, tests, generated journals, modular operation and financial-institution use. | Licensed modules, entry scope, jurisdiction, instruments, valuation ownership, interfaces, disclosures and evidence for the exact use case. |
Use the table to choose tests, not rankings. Recheck official pages and contract schedules before selection.
Designation and documentation controls
Hold each relationship as structured data controlled by framework, hedge type, risk, entity and policy version. Link instrument, hedged item or risk component, objective, designation time, hedge ratio, method, expected ineffectiveness and accounting treatment.
Under Topic 815, FASB’s designation amendments retain formal designation and documentation at hedge inception. The initial prospective quantitative assessment uses inception-date information, but ASU 2017-12 provides timing relief that can treat the assessment as concurrent if it is completed by the earliest specified deadline. That relief does not mean the team can delay the designation itself or apply one deadline to every fact pattern.
Test invalid combinations: an unapproved instrument, late designation, quantity above exposure, missing policy assertion or inapplicable method. A dismissible warning without reason, approval and evidence is not a control.
Generate documents from the relationship record. An approved-field change should create a version, identify the change, route approval and preserve the prior state. Document and data must agree.
Qualified-practitioner review required: Approve the designation template, timing interpretation and validation rules for each hedge type and framework, including any Topic 815 timing relief. Configuration staff should not infer those conclusions from a generic supplier template.
Effectiveness assessment under IFRS 9 and ASC 815
Do not treat effectiveness assessment as one feature. Under IFRS 9, a qualifying relationship must have an economic relationship, credit risk must not dominate the value changes resulting from that relationship, and the designated hedge ratio must satisfy the standard’s requirements. The issued standard says an economic relationship generally produces opposite value movements because of the same risk; statistical correlation alone is not enough.
IFRS 9 requires assessment at inception and on an ongoing basis, at least at each reporting date or when circumstances affecting the requirements change significantly, whichever occurs first. The assessment is forward-looking. IFRS 9 does not prescribe a single method, so the selected qualitative or quantitative approach must capture the relationship’s relevant characteristics and expected sources of ineffectiveness.
Topic 815 uses different conditions, elections and timing. ASU 2017-12 permits later qualitative assessments when specified criteria are met. When that route is used, the entity must verify and document the continuing facts whenever financial statements or earnings are reported and at least every three months; changed facts can require a quantitative assessment. The software must execute the approved US GAAP method and eligibility conditions, not relabel an IFRS result.
For each method, retain formula, variables, source, period, observations, excluded-component treatment, credit inputs, decision rule, result and exception. Regression, dollar-offset, critical-terms, shortcut, hypothetical-derivative and qualitative approaches are not interchangeable labels.
Qualified-practitioner review required: Select the permitted method, define its assumptions and exceptions, interpret the output and approve any change from qualitative to quantitative assessment. Software can calculate and retain evidence; it cannot supply the accounting judgment merely by returning a status.
Valuation, market data and model governance
Test the full valuation chain: trade economics, market data, curves, interpolation, day-count and calendars, discounting, volatility, optionality, collateral, credit effects where applicable, and the model assigned to each instrument.
The 2026 issued IFRS 13 requires fair value to use assumptions market participants would use and identifies relevance and observability of inputs as important to the measurement. A mark-to-market figure alone does not prove those requirements have been met. US GAAP buyers should map the same software tests to their approved current Topic 820 policy.
Identify whether valuation is native, imported or split by instrument. Retain source, timestamp, convention, identifier, model or price type, units, currency and status. Detect missing, stale, duplicate or out-of-range inputs. Approve and evidence overrides.
Compare system values with an independently controlled benchmark and set tolerances by instrument. Include off-market trades, amortizing notionals, non-standard calendars, optionality, collateral changes and material valuation adjustments in the real portfolio.
Qualified-practitioner review required: Approve the accounting valuation policy, model use, input hierarchy, credit adjustments, tolerances and treatment of differences. A valuation specialist may also be required for complex instruments; this article does not establish that need for a particular entity.
Journals, OCI or AOCI, basis adjustments and close controls
The accounting engine should consume approved relationship, valuation and effectiveness data, then apply framework, hedge type, elections, chart and period rules. Trace each material amount through journal, ledger response, reconciliation and disclosure.
Test fair value, cash flow and net investment hedges separately. Include derivative fair-value changes, hedged-item adjustments, other comprehensive income or accumulated other comprehensive income, recognized ineffectiveness, excluded components, cost-of-hedging balances where relevant, reclassifications, settlements, accruals, basis adjustments and subsequent releases. The mechanics differ by framework and election, so one universal posting template is a warning sign.
Each batch needs a unique ID, source relationships, book, entity, period, date, currency, balanced lines, mapping version and approval. The ERP should return accepted and rejected totals, journal IDs and reasons. Retain failures and prevent duplicate resubmission.
Fit hedge accounting into the entity’s close dependency design. A technically delivered file is not a completed close task if valuation approval, effectiveness assessment, journal acceptance or reconciliation remains unresolved.
Qualified-practitioner review required: Approve journal mechanics, presentation, OCI or AOCI treatment, basis adjustments, reclassification triggers and disclosure mapping. A software result should remain provisional until those policy outputs have been reviewed against the entity’s facts.
Rebalancing, de-designation and discontinuation
Preserve history rather than edit the original relationship into its current form. Model active, amended, rebalanced, partially or fully discontinued, matured and terminated states, including framework-specific consequences.
IFRS 9 defines rebalancing as adjusting the designated quantities of the hedged item or hedging instrument in an existing relationship to maintain a qualifying hedge ratio. It requires the analysis of expected sources of ineffectiveness and the documentation to be updated. The system should retain quantities, values, assessment and approval immediately before and after the event.
Do not use “de-designation” as a framework-neutral action. IFRS 9 says an entity must not de-designate a relationship that still meets its risk-management objective and all other qualifying criteria after any applicable rebalancing. Topic 815, by contrast, permits a relationship to be de-designated at any time; changing critical terms generally requires de-designating the original relationship and designating a new one, subject to specified exceptions.
ASU 2025-09 adds a version boundary. On adoption, amendments apply prospectively and may be elected for existing relationships; specified critical terms may be modified without de-designation. Require rule-version and transition controls, not a roadmap.
Qualified-practitioner review required: Determine whether an event is rebalancing, modification, de-designation, discontinuation or correction under the applicable model, and approve the resulting reserve and journal treatment. A shared event label across IFRS and US GAAP is not enough.
Disclosures and the audit evidence pack
Design disclosures from the data model. The 2026 issued IFRS 7 requires information about risk-management strategy, cash-flow effects and hedge-accounting effects on financial position, comprehensive income and equity. Map each disclosure to framework, entity, risk, hedge type, population, calculation, ledger account, adjustment and owner.
Reconcile disclosure totals to the ledger and relationship population. Retain continuing and discontinued relationships in rollforwards where required by the approved policy. Generate a frozen-period package and explain every manual adjustment. The July 2026 IASB staff feedback analysis identifies application challenges involving effectiveness, cost of hedging, basis adjustments, rebalancing, discontinuation and disclosures. It is evidence about reported practice issues, not an amendment to IFRS 9.
“Audit ready” is not an acceptance criterion. PCAOB AS 1105 distinguishes evidence quantity from relevance and reliability, and requires evaluation of company-produced information. PCAOB AS 2501 treats fair value as an accounting estimate and addresses evidence over the company’s methods, data and assumptions. Management should define and retain a complete pack; the auditor independently determines whether the evidence is sufficient and appropriate.
Require designation, linked trades and exposures, source data, valuation inputs and models, assessment calculations, approvals, journals, ledger acknowledgements, reconciliations, disclosures, exceptions, overrides and change logs. Apply the same identity, provenance, completeness and reproducibility tests used in strong account-reconciliation evidence controls.
Qualified-practitioner review required: Approve the disclosure interpretation and tie-out logic. Neither this guide nor a supplier’s “audit-ready” claim determines what the entity’s auditor will accept.
ERP, TMS, market-data and consolidation integrations
Draw the architecture first. A TMS may own exposures and instruments, a specialist engine designations and calculations, market-data services inputs, the ERP posted accounting, and consolidation group reporting. Give every object and status one owner. For the currency side of that picture, how the five FX solution categories divide that architecture sets out what each can and cannot own on its own.
The finance technology stack boundary is a useful starting rule: a specialist product earns its place through distinct process depth only when write rights, handoffs and evidence are clear. A suite module should face the same test. Fewer interfaces do not compensate for weak valuation, accounting or lifecycle support.
For each interface, specify object, systems, identifiers, grain, timing, convention, currency, entity, period, mapping, control totals and status. Separate receipt, business acceptance, posting and reconciliation. Use a finance systems integration map to test acknowledgements, retries, rejects and ownership.
Do not mark a journal complete before the ERP returns a controlled posting result. Rejected records need an owner, reason, correction route and escalation. Test inbound amendments, terminations, exposure changes, corrected rates and revised forecasts.
Proof-of-concept scenarios and acceptance criteria
Run buyer-authored cases from source data through evidence export. Use anonymized transactions that preserve real complexity and define expected outputs first. Supplier demonstrations do not replace observed evidence.
| Scenario | What to test | Required evidence |
|---|---|---|
| New FX cash flow hedge | Exposure import, designation, assessment, valuation, OCI treatment, journal and disclosure | End-to-end trace with approvals and ledger acknowledgement |
| Interest-rate fair value hedge | Hedged-risk definition, instrument valuation, hedged-item adjustment and presentation | Calculation and mapping trace tied to the approved relationship |
| Dual-framework relationship | Separate IFRS and Topic 815 designations, methods, entries and lifecycle actions | Framework-specific outputs with no overwritten shared result |
| Excluded component | Policy election, component valuation, reserve or earnings treatment and release | Component-level valuation and accounting rollforward |
| Market-data correction | Period rerun, superseded result, approval and downstream adjustment | Both data versions, variance explanation and controlled replacement |
| Rebalancing or de-designation event | Framework-specific trigger, quantities, reserve treatment and continuing relationship | Before-and-after state, practitioner-approved conclusion and complete accounting effect |
| ERP rejection and retry | Rejected line, correction, duplicate prevention, resubmission and reconciliation | Interface log, reason, new status and final tie-out |
| Audit replay | Reproduce a closed-period result from retained inputs and configuration | Independent evidence pack matching the approved and posted period |
Set mandatory gates before weighted criteria. Record expected and observed result, variance, evidence, owner and disposition. A conditional pass needs a bounded gap, control, owner, due date and retest. An uncommitted roadmap remains a failed requirement.
Qualified-practitioner review required: Approve the expected accounting output for every material case before the proof of concept and sign off any accounting variance or workaround. This review is still outstanding; the assigned editorial reviewer is not a substitute for it.
Implementation, ownership and commercial due diligence
Assign ownership before configuration. Technical accounting owns policy and methods; treasury owns exposures and instruments; valuation owns models and data; the controller owns journals and tie-outs; finance systems owns interfaces and access; security owns technology-risk review. Supplier consultants should not become undocumented control owners.
Migrate required designations, valuations, reserves, basis adjustments, tests, journal references and documents. Reconcile by relationship, instrument, reserve, account and entity. Preserve excluded legacy evidence. Run a controlled parallel close and investigate differences.
Identify commercial dependencies: users, entities, instruments, relationships, valuations, interfaces, data, environments and services. Separate license, implementation, migration, testing, support, advisory and upgrades. Record required modules and third parties. Contract for standards updates, defect handling, data ownership, retention, export, sub-processors, availability, recovery, security notification and termination assistance.
Require relationship data, calculations, documents and audit evidence in usable export formats. Test export before signing, not only at exit. Confirm which controls remain with the buyer when the supplier provides valuation, accounting advisory or managed services.
Pass, condition or reject the shortlist
A product should pass only when it supports every in-scope rule set and material hedge case, reproduces valuation and effectiveness results, generates controlled accounting outputs, ties disclosures to source and ledger data, operates required interfaces, and exports complete evidence. A high usability score should not offset failure in one of those areas.
Condition only bounded gaps with affected cases, materiality, workaround, owner, date, acceptance test and remedy. Reject when policy-level support is unproved, calculations cannot be reproduced, history can be overwritten, ledger responses are absent, disclosures do not reconcile, or evidence depends on the live interface.
The final decision record should pair each mandatory requirement with observed evidence, test result, accepted condition and owner. Before approval, a qualified hedge-accounting practitioner must review the rule-set matrix, policy interpretations, expected accounting outputs and unresolved technical judgments. That specialist review has not been performed or implied here.
