The accounting outcome is fixed before the trade settles, so the agent drafts the designation at inception, records the evidence under it, and holds the memorandum for the officer who signs.
A hedge is struck, and ASC 815-20-25-3 wants the document written at inception, not later.
02
A memorandum lands after the trade, and no later filing makes that relationship a hedge.
Reason
03
IFRS 9 paragraph 6.4.1 asks the same at inception, so both records are raised together.
04
ASU 2025-09 widens what may be designated from 2027, and leaves the inception deadline untouched.
05
An order accepted under the agreed security procedure binds the company, authorised or not.
Decide
06
A covenant falls due on or before the reporting date, and a later waiver is logged, not applied.
07
IAS 1 paragraph 72B becomes IFRS 18 paragraphs B99 to B108 for periods from 1 January 2027.
Out
08
A position cannot be evidenced at inception, and that is recorded as the finding.
09
Execute write actions only under the approval boundaries set at implementation.
→Product statement
Drafting, evidencing and holding belong to the agent. Designation belongs to a named officer, who signs on the trade date. Payment duties stay outside it: entrust them and the UCC 4A-203(a)(2) way out shuts, and the loss stays with the company.
Example workflow
One designation, ticket to memorandum
AgentHuman
1Evidence receivedDealer confirmations, the board hedging policy, exposure schedules and the forecast schedule
2Relationship fixed and datedThe hedged item, the hedging instrument, the risk being hedged and the day inception falls on
3Memorandum raised at inceptionThe risk-management objective, the hedge ratio, the effectiveness method and its weak points
4Date checks appliedPolicy-instrument checks, functional-currency checks, date checks and drafting confidence
No human action required
Stages 1 to 4 run unaided, and nothing is designated at any of them — the agent is drafting, and the officer lane opens at the designation gate.
5DecisionSplits at the designation gate
Complete against the policy
Goes to the named treasury officer to designate.
Anything thin
Adds a technical-accounting read first.
Treasury review
The memorandum is held with its evidence, its inception date and the policy clause it was drawn under.
Designate · Append evidence · Send to technical review
Designated — by the named treasury officer▼
6Treasury and hedge records updatedOnly where write access and the records policy allow it
7Designation evaluatedInception dating, evidence completeness, officer corrections and what technical review found
Designation corrections
Each correction the officer makes is counted in the evaluation.
What should not run autonomously
Human approval stays in control
Outside the boundary — human approval required8 items
Designating a hedging relationship.
Authorising a payment order to leave.
Concluding that a hedge is effective.
Classifying the debt in the accounts.
Automation boundaryAgent acts unaided
✓Draft the designation before the trade settles.
✓Record the effectiveness method the memorandum names at inception.
✓Date each record against the executed dealer ticket.
✓Hold the position, the exposure and the documentation together.
Nothing is designated and no order is sent except by a named officer, inside the agreed boundaries.
Judging whether a forecast transaction is probable.
Telling a lender the covenant test was met.
Choosing which exposure the company hedges.
Changes to the position, the policy or the memorandum.
Example output
One hedge designation, annotated
This serves a corporate treasury whose accounting outcome is fixed by a document dated at inception; below is one designation exactly as the agent leaves it.
Hedge designation · single relationshipIllustrative example
Designation
Recorded as
Relationship
Evidence of record
Confidence
Held for
Cash flow hedge, one forecast exposure
Drafted on the trade date
Inception, evidenced
Dealer ticket, 6 August 2026
Held undesignated
The treasury officer, by name
As receivedBuilt from the dealer confirmation and the board hedging policy under it, and it claims nothing past them.
What the designation record holdsDealer confirmationBoard hedging policyExposure schedule
Why no designation hereDesignating a hedging relationship is a call a named officer makes.
ActionDesignateAppend evidenceSend to technical review
What the score decidesBelow the configured threshold a memorandum gets a technical read before the officer sees it.
Value
Where AI adds value
The same four claims, placed at the point in the workflow where each one applies.
Where the value landsValue 01 – 04
Each designation draftedFrom the evidence that carries it
03Evidence
Where the evidence sits
The agent vouches for no counterparty, only for what the evidence said and the day it was dated; the Adani Enterprises finding of 18 May 2026 reached payments cleared on a payee name alone.
01Approved path
Documented, or not a hedge
SEC v. General Electric, 3:09-cv-1235 (D. Conn.), filed 4 August 2009, turned on hedging parameters written after the interest payments they were said to cover had already occurred.
02Human review
Looked for, and not found
No independent published benchmark for corporate cash-forecast accuracy was located, and each accuracy figure that surfaced came from a vendor selling forecasting software, so none is quoted here. No enforcement action for calling a holding a cash equivalent was found either.
04Build an evidence trail
The position, the document that existed at inception and the officer who designated it stay together.
Integrations
Typical integrations
Five system groups connect to the same agent. Which of them are in scope is decided in discovery.
Bank and dealer systemsBank portals · dealer tickets Balances and the executed trades
Treasury and ledger recordsTMS · general ledger records Debt, holdings and positions
Policy and mandate documentsBoard policy · mandate list Authorised instruments and stated limits
Agent
Treasury position and designation
Reads the evidence Drafts at inception Holds for the treasurer
Forecast and exposure feedsFP&A schedules · entity records Forecast exposures by legal entity
Cross-currency designations absorb the corrections
A treasury-level correction figure can read clean while cross-currency designations carry most of the rework. Nestack reports the correction rate by exposure class, not across the book alone.
Slice performance — reported separately, not only in aggregateIllustrative example
Slice
Failure rate
Lift
Lift vs. threshold
Status
Cross-currency designations
13.4%
3.7×
Review
Covenant-linked facilities
9.5%
2.6×
Review
Money market fund holdings
5.9%
1.6×
Watch
Single-currency term debt
2.7%
0.7×
Normal
Bar: correction-rate lift vs. single-currency baseline · scale 0–4.0× · tick marks the 2.0× review threshold2 of 4 slices over threshold
Evidence-linked improvement
What a memorandum written late costs
A cycle ends when the relationship documented after the trade is a standing case. That suite is what the next designation is measured against.
Improvement cycle · five stagesSwitchback — the path turns at Improve and returns at Learn
01Detect
Correction rate rises on cross-currency designations.
02Diagnose
The designation that was dated to the trade because the evidence caught up a week afterwards is worked backwards until one cause is left standing.
03Improve
The position goes out numbered, and the documents beneath it ride with it.
04Verify
One designation case still failing is enough to hold the pack back.
05Learn
It is kept for good, and the designation rules are amended in the same commit.
Learn → DetectThe return edge. The next designation is measured against a suite one case longer.
Typical build scope
Twelve workstreams across six weeks
The build scope read against the delivery timeline. Week structure follows the six-week plan — discovery, sources, designation drafting, evaluation, integration, then production validation and handover.
WorkstreamWeek 1Week 2Week 3Week 4Week 5Week 6
01Designation-evidence and automation-boundary scope.
02Bank, dealer and policy sources.
03Evidence-to-position and exposure-coverage mapping.
04Dealer-ticket ingestion.
05Relationship, risk and date binding.
06Evidence scoring and review routing.
07Officer designation workflow.
08Treasury-system integration.
09Designation and inception cases.
10Guardrails and settlement controls.
11Position-trail instrumentation.
12Deployment, documentation and Agent Care handover.
12 workstreams · 6 weeks · bar shows the weeks a workstream is active — several run in parallelFinal scope and sequence confirmed in discovery
Engagement tiers
What each tier includes
Rows are the capabilities named in each tier's scope. Higher tiers include everything below them.
Capability✓ in scope · — not at this tierPilotOne exposure class, one cycleProductionProduction treasury workflowAdvancedMultiple exposures / currencies
Introduced at Pilot
Designation drafting to your policy✓✓✓
Named officer designation✓✓✓
Account-and-mandate baseline✓✓✓
Introduced at Production
Reporting by exposure class—✓✓
Technical review workflow in your systems—✓✓
Approved treasury write-back—✓✓
Bank-and-dealer integration—✓✓
Introduced at Advanced
Multi-entity exposures——✓
Cross-currency designation packs——✓
Dense trading calendars——✓
Multi-currency exposure controls——✓
Build priceFrom $5,000From $8,000Custom quote
Final build priceConfirmed after discovery based on integrations, workflow complexity, trade volume, approval controls and deployment requirements.
Separate from buildBuild pricing is separate from recurring Agent Care, which covers managed monitoring, evaluations, incidents and verified improvements after launch.
What we need from you
What you bring, and what we build with it
Each input maps to a piece of build scope and a week in the delivery timeline.
You bringWe build with it
01Your live exposures and the policy each one is hedged under→Policy capture and inception-date versioningWeek 1
02Representative dealer, policy and exposure material→Evidence binding, drafting logic and the position baselineWeek 2
03Your trading calendar and the officers it names→Hedging-policy mapping, evidence binding and the automation boundaryWeek 1
04Access to the relevant portals, feeds or exports→Bank, dealer and policy source assessment, then integration setupWeek 2
05Positions you would not want re-designated→Inception cases and the failure roundWeek 4
06What no forecast may promise→Evidence scoring, review routing, guardrails and release controlsWeek 3
07A named treasury officer who designates→Release to the named officer, then pilot and production validationWeeks 5–6
Nothing else is requiredDeployment, documentation and Agent Care handover are ours.
Delivery timeline
Four phases across six weeks
These bands are counted, never evened for looks; the fifth week carries two because those two coincide.
PhaseW1W2W3W4W5W6
DiscoveryW1
BuildW2 – W3
EvaluateW4 – W5
Pilot & LaunchW5 – W6
Week focusW1Policy discovery, inception dating and the automation boundaryW2Bank and dealer integration, and the account-and-mandate baselineW3Drafting logic, evidence checks and release controlsW4Evaluation suite, designation cases and failure-mode testingW5Treasury-system integration, pilot designations and targeted correctionsW6One reporting cycle run under the treasurer, then Agent Care handover
Reading the bandNo bar runs past the weeks its own work is named for, and week five is shared by design.
At the end of W6When the position record validates, Agent Care takes the agent on.
DurationSix-week plan shown · typical delivery 4–6 weeks depending on scope confirmed in discovery.
Next step · Finance AI agent
Build a treasury support agent around the document your last hedge was designated without.
Show us one hedging relationship you designated last quarter and the memorandum dated to the trade. If that document was assembled the week after, hedge accounting was never available. A covenant note citing IAS 1 alone will name a withdrawn standard within sixteen months.
