Record for this area

Invoice to payment

The path from what a machine is documented doing to the party holding the record that makes the result official, with how well each step is backed. Where the sources settled nothing, the step says so.

What a machine is documented doing

Established by the evidence. SAP Joule releases an invoice from a payment block and cancels a posted document - human-initiated
The record it touches

Established by the evidence. Supplier invoice; payment block; posted document; payment instruction; release; settled entry
What still has to happen first

Established by the evidence. STRUCTURAL for approval and payment routing; the Joule capability is human-initiated

A source describes this step a document describes this step at the point where it matters The vendor's own denial

Draft recommendations offers and schedules always require user review and confirmation before any action is taken
the source's own words, quoted exactly
What makes the change count

Established by the evidence. Institutions - OpenPeppol, the EU, Nacha, the Federal Reserve
Who holds the official record

Established by the evidence. The ERP holds the invoice the block and the posted document; ACH and FedNow hold the settled state
What the area relies on

Established by the evidence. SAP S/4HANA Cloud Public Edition — financial system of record holding the supplier invoice, its payment block and its posted document; Oracle Fusion Cloud ERP — financial system of record holding supplier invoice distributions and accounting; ACH Network — the rules regime governing origination, receipt and return of credit entries; FedNow Service — instant payment transaction infrastructure

The action that makes it official Release and settlement on the payment rail Done by The originator's approvers; the RDFI for return. It counts because of a record state held by the rail. No machine is documented doing this.

What this area could not settle

What could this area not settle?

What this area recorded against its own findings, in its own words.

Recorded against itself by this area

6 of 12 events institutional; 2 of 12 carry no publication_date, declared; PR-02 produced the programme's first explicitly-absent on an authorization cell

12 dated acts by institutions or vendors

6 searches recorded here that found nothing

8 capabilities examined

8 systems examined

Can the act be undone, and by whom?

DECISIVE - coded per unit and per participant on all 16 rows; the irreversibility line is the area's central finding An inspected source states this directly.

Question by question

What did the evidence settle, dimension by dimension?

Eighteen structural dimensions, each carrying its own evidence state and what it does not establish.

What the evidence settled for this area, question by question
Question asked	What the evidence says	What it does not tell you
consequential-object `D01`	Established by the evidence. Supplier invoice; payment block; posted document; payment instruction; release (O-6); settled entry	Not recorded by the method used for this area
object-holder `D02`	Established by the evidence. The ERP holds the invoice, the block and the posted document; ACH and FedNow hold the settled state	Not recorded by the method used for this area
grammar-or-form-setter `D03`	Established by the evidence. Institutions: OpenPeppol, the EU, Nacha, the Federal Reserve	Not recorded by the method used for this area
composer `D04`	Established by the evidence. The originator and the AP function; agents draft but do not commit	Not recorded by the method used for this area
validator `D05`	Established by the evidence. The RDFI accepts or rejects the credit entry; a Peppol access point accepts or rejects the transmitted invoice	Not recorded by the method used for this area
binder `D06`	Established by the evidence. Release and settlement on the payment transaction infrastructure	Not recorded by the method used for this area
deterministic-automation `D07`	Established by the evidence. Approval and payment routing are structurally gated; deterministic workflow reaches routing and stops before release	STRUCTURAL for approval and payment routing.
agentic-capability `D08`	Established by the evidence. SAP Joule releases an invoice from a payment block and cancels a posted document - human-initiated	THE IN-ARGUMENT COUNTEREXAMPLE. Survives on reversibility and human instigation.
furthest-deterministic-action `D09`	Established by the evidence. Payment routing and approval workflow; the transaction infrastructure performs release and settlement once instructed	Not recorded by the method used for this area
furthest-agentic-action `D10`	Established by the evidence. STATE 4 of an eleven-state sequence frozen before retrieval - a payment proposal a person must confirm	The stop is DESCRIBED - the vendor states the boundary as a boundary.
reversibility `D11`	Established by the evidence. DECISIVE and coded per unit and per participant on all 16 rows: after origination the ODFI may only REQUEST a return and compliance by the RDFI remains optional; after payment confirmation only void remains, and a void is an accounting reversal, not a recall of funds	THE ONLY AREA OF TEN where reversibility is a first-class coded property. Never exported to any other area.
externality-radius `D12`	Established by the evidence. The payment transaction infrastructure reach beyond the two transacting parties: Nacha and the Federal Reserve set rules binding every participating institution	Not recorded by the method used for this area
counterparty-assent `D13`	Established by the evidence. Required at the transaction infrastructure: the RDFI accepts or rejects the credit entry	Not recorded by the method used for this area
rule-codifiability `D14`	A source states this does not happen: A source addressed it and said no.. The vendor states the boundary as a boundary: draft recommendations, offers and schedules always require user review and confirmation before any action is taken	Not recorded by the method used for this area
institutional-closure `D15`	Established by the evidence. ACH, FedNow and Peppol must recognize the state for settlement to occur	Not recorded by the method used for this area
authoritative-state-centralization `D16`	Established by the evidence. SPLIT: the ERP holds the invoice, block and posted document; the transaction infrastructure hold the settled state	The irreversibility line runs exactly along this split.
consequence-of-error `D17`	Established by the evidence. Once settled, the error is not undoable by the acting party: compliance by the RDFI with a return request remains optional; a void does not recall funds	THE ONLY AREA where consequence of error is established from inspected evidence.
accountability `D18`	Not answered by the evidence we checked: We looked and the sources we inspected did not settle it.. No stable answerable party evidenced. PR-02 produced the programme's first explicitly-absent on an authorization cell We looked and the sources we inspected did not settle it.	An explicitly-absent authorization cell is not an answerable party.

Capabilities

What is each capability evidenced doing?

The mode records that a named subject performs an operation. It does not record what kind of performer that subject is, and several rows disclaim an agentic mechanism in their own limitation.

Capabilities examined in this area
Capability	How far it goes	What it does	Human work still needed	What this does not tell you
Payables Agent for Invoice Ingestion, Compliance, and Control. Passage (E-01): "Powered by Gen AI, the Payables Agent automates invoice ingestion, compliance, and control across multiple sources and formats." `C-001`	the sources do not settle whether it acts or only prepares	Two inspected artifacts attribute the same agent's action differently and BOTH readings pass the qualification threshold, so the outcome is recorded as established and only the mode is left unresolved (I-06). Reading 1, E-01: "Document IO interprets invoice documents, extracts and labels relevant information, and intelligently maps extracted data to supplier invoice attributes" — this mutates the invoice record; operational preparation. Reading 2, E-02: "create distributions and accounting" — this creates the posting; execution.	E-01: "users can verify exceptions or violations observed on invoices and quickly take the appropriate action on them, whether it be resolving invoice rejections or making other required invoice corrections." E-02: approval and payment remain downstream of the agent.	Does NOT establish that the agent approves an invoice, releases a payment, or changes any object after payment release. Does NOT establish a date for the capability: E-01 carries no visible date and its "26B" label is not admissible as a date under T-02. Does NOT establish which of the two mode readings is correct. The cutoff outcome carries no independent information because the frozen contract set the cutoff equal to the register date — see DV-02.
Payments Agent. Passage (E-02): "Payments Agent: Helps finance teams optimize cash outflows and expand payment choices." `C-002`	prepares the work, stops before it counts	Prepares and orchestrates; does not change an record in scope for the area's state. Decisive passages (PR02-E-01, Oracle Release 26B readiness): "Draft recommendations, offers, and schedules always require user review and confirmation before any action is taken." / "The assistants support evaluation, guidance, and orchestration but do not replace standard payment setup, approvals, or controls." / "The assistant guides users through the submission of payment process requests." Under frozen-contract boundary B-3 financing arrangements remain outside the area, and no inspected passage states that the agent mutates an existing payment instruction.	Review and confirmation of every draft, and submission of the payment process request. PR02-E-01: "always require user review and confirmation before any action is taken".	Does NOT establish that Oracle has no execution-grade payment capability elsewhere; it establishes only that THIS named offering does not authorize or release a payment. The offering's name is not evidence of its operation — the same document that names a "Payment Execution Assistant" scopes it to "inquiries, scheduling, and lifecycle management". PR02-E-01 carries NO page-visible date; the release label 26B is refused under T-02, so this row establishes current state only and adds no dated evidence. cutoff_outcome carries no independent information — see the area's DV-02.
Joule supplier invoice verification capability in SAP S/4HANA Cloud Public Edition. Passage (E-03): "The supplier invoice verification capability in SAP S/4HANA Public Cloud enables accountants to interact with Joule using natural language to get immediate updates on supplier invoices, such as identifying the current approver or checking a payment status." `C-003`	performs the operation itself	Changes the state of the payment block on a supplier invoice, and cancels a posted document. Both are state changes on records in scope for the area, not recommendations. Passage as above (E-03).	The act is initiated by a human accountant in natural language. E-03: "enables accountants to interact with Joule using natural language". The agent is the surface and executor; the accountant is the instigator. This row therefore qualifies as execution WITHOUT establishing autonomous action.	Does NOT establish that the capability approves an invoice, constructs a payment instruction, or releases a payment. CRITICAL: the artifact's word "releasing" denotes release from a payment block (O-8), NOT the record in scope for the area O-6 release; this row is not evidence of any operation on O-6. Does NOT establish autonomous action independent of a human accountant. The cutoff outcome carries no independent information — see DV-02.
Dispute Resolution Agent for SAP S/4HANA Cloud Public Edition. Status on the artifact: "Beta release". `C-004`	advises only	Produces an identification and a recommendation, not a state change. Passage (E-04): "detects incorrect charges and recommends compliant solutions, such as credit memo creation". Detecting and recommending leave every record in scope for the area in its prior state (I-05).	Deciding whether to accept the recommendation, and creating any credit memo.	Does NOT establish that the capability is incapable of a state change, only that the inspected artifact evidences none. Beta status is recorded but is not the ground of exclusion; the ground is the evidenced operation.
AI Approval Agent. `C-005`	advises only	Produces a likelihood assessment and a recommendation. The approval state is changed by the customer, not the agent. Decisive passage (E-05): "While the AI agent delivers intelligent suggestions and transparency into how each recommendation was made, customers remain in full control of final approval decisions—ensuring human oversight remains part of the process."	The entire approval decision. Stated by the vendor in the passage above.	Does NOT establish that AvidXchange has no execution-grade capability elsewhere; it establishes only that THIS named offering does not change the approval state. The offering's name is not evidence of its operation.
AI PO Matching Agent. `C-006`	the sources do not settle whether this belongs in scope	Not established. The inspected artifact names the agent but carries no sentence describing the operation it performs on the match result.	Not established.	Does NOT establish participation or non-participation. Excluded from both analytical populations per T-10 while retained in the master register (I-15).
Coupa Navi AI agents, November 2025 platform release. Named agents on the artifact: Navi Cost Formula Assistance Agent; Navi Request Creation Agent; Navi Supplier Assistance Agent; Navi Supplier Discovery Agent; plus Category Strategy Integration and an expanded Supplier Workbench. `C-007`	does not apply here	Every operation named on the inspected artifact acts outside the area boundary: cost and scoring formulas ("uses AI to transform plain language into accurate cost and scoring formulas"); requests and Statements of Work ("expands AI conversion to fully support complex Statements of Work (SOWs) and upload files"); supplier questions ("automates instant, 24/7 responses to common supplier questions"); supplier discovery ("uses natural language queries to help sourcing managers find the best-fit suppliers"); and category strategy ("connects strategic planning directly to event execution within a single platform").	Not assessed — the offering does not enter the area.	Does NOT establish that Coupa has no invoice or payment capability anywhere in its platform; it establishes only that this dated release, despite its Source-to-Pay title, names no operation on an record in scope for the area. This is the area's expected exclusion and it was confirmed on a retrieved and inspected primary artifact, not on a search summary.
Agentic AI AP Automation — named by the actor, but no primary artifact establishing a specific operation on a named record in scope for the area was retrieved within the source-estate plan. `C-008`	the sources do not settle whether this belongs in scope	Not established. No claim is carried from search summaries (I-10).	Not established.	Does NOT establish participation or non-participation. Carries NO evidence row by design; this is the one row in the file with an empty evidence_ids array, and it is therefore excluded from both analytical populations per T-10. Recorded rather than dropped, so that the thin area is visible in the evidence boundary rather than silently absent. NOTE for T-01: T-01 requires evidence on qualified and excluded rows; this row is neither.

Infrastructure

Whose systems does this area run on?

What part each system plays was decided by what it does to the area's records, never by what kind of company runs it. Where the sources leave that open the entry says so, because an open question is not a kind of system.

Systems examined in this area
System	Who runs it	What part it plays	What it does to the official record
SAP S/4HANA Cloud Public Edition — financial system of record holding the supplier invoice, its payment block and its posted document `C-009`	SAP SE	authoritative-transaction-rail	holds — the supplier invoice, the payment block and the posted document, within SAP S/4HANA Cloud Public Edition; mutates — the payment block and the posted document, within SAP S/4HANA Cloud Public Edition
Oracle Fusion Cloud ERP — financial system of record holding supplier invoice distributions and accounting `C-010`	Oracle Corporation	authoritative-transaction-rail	holds — the supplier invoice record and its distributions, within Oracle Fusion Cloud ERP; creates — the accounting entries, within Oracle Fusion Cloud ERP
ACH Network — the rules regime governing origination, receipt and return of credit entries `C-011`	Nacha	authoritative-transaction-rail	accepts-or-rejects — the credit entry, at the RDFI within the ACH Network; holds — the settled state of the entry, within the ACH Network and its participating financial institutions
FedNow Service — instant payment transaction infrastructure `C-012`	Federal Reserve Financial Services	authoritative-transaction-rail	holds — the settled credit transfer, within the FedNow Service; accepts-or-rejects — the credit transfer, at the sending financial institution's configured limits
Phixius by Nacha — peer-to-peer payment information network `C-013`	Nacha	transaction-enablement-layer	observes — the payee bank account, which is held by the account-holding depository institution, not by Phixius; constructs-for — the validation response supplied to a requester constructing or checking a payment instruction held in the requester's own system
Kinexys Liink — information exchange network, Confirm application `C-014`	J.P. Morgan	transaction-enablement-layer	observes — the payee bank account, held by the account-holding institution, not by Kinexys Liink; submits-to — validation requests routed to responders including Phixius, whose responses are held by the responders
Peppol network — Peppol BIS Billing v3 specification and its validation rules `C-015`	OpenPeppol AISBL	transaction-enablement-layer	accepts-or-rejects — the transmitted invoice, at a Peppol access point; the invoice itself is held by the sending and receiving parties' own systems; submits-to — the receiving party's system, which holds the received invoice
AvidPay Network — payment execution network `C-016`	AvidXchange Holdings, Inc.	unresolved	none-established

Claims

What may be said from this area, and what may not?

Each one carries how far it is backed and, where it was recorded, the exact stronger sentence that may never be written from it.

CL-01 Observed

In every artifact inspected in this pilot, no agentic capability was evidenced as itself conferring an invoice approval.

The strongest thing against it None was found for approval. The nearest is EV-06, in which a capability does change record in scope for the area state — but the object changed is the payment block, not the approval.

What may not be said from this NEVER: 'AI does not approve invoices', 'agents cannot approve invoices', 'approval remains human across the market', or any formulation dropping 'in the artifacts inspected'.

CL-02 Observed

AvidXchange's AI Approval Agent, announced 2025-04-02, produces an assessment of approval likelihood, and the vendor states that customers retain the approval decision.

The strongest thing against it None was found.

What may not be said from this NEVER: 'AvidXchange's AI cannot approve invoices' or 'AvidXchange has no execution capability'.

CL-03 Observed

Oracle's announcement of 2025-10-15 describes a Payables Agent that creates distributions and accounting and then routes for approval and payment.

The strongest thing against it None was found. The two Oracle artifacts differ in how they attribute the agent's action, which is recorded as an unresolved participation mode on C-001 rather than as a conflict about the outcome.

What may not be said from this NEVER: 'Oracle's Payables Agent creates accounting entries' stated as present fact, or any use of 2025-10-15 as the date a capability began operating.

CL-04 Observed

One inspected capability does change the state of an record in scope for the area: SAP's Joule supplier invoice verification, generally available in Q3 2025, can release an invoice from a payment block and cancel a posted document.

The strongest thing against it This claim is itself the counterexample to CL-07.

What may not be said from this NEVER: 'SAP's agent releases payments', 'Joule releases invoices for payment', or any wording that lets 'release' attach to the payment rather than the block.

CL-05 Observed

Under Nacha rules effective 2026-03-20 and extended 2026-06-19, the duty to monitor originated ACH credits for fraud falls on the originating enterprise and its ODFI, while the power to return an entry falls on the receiving institution.

The strongest thing against it None was found.

What may not be said from this NEVER: 'buyers are liable for supplier payment fraud', 'the rules make originators responsible for losses', or any statement of liability allocation.

CL-06 Pattern

In this area the irreversibility line is not a wall but a handover: crossing it does not remove the possibility of reversal, it transfers that possibility from the party that acted to a party that did not.

The strongest thing against it FedNow, where the inspected artifact evidences no reversal mechanism at all, so the reading of a 'handover' is weaker than for ACH — the possibility may simply end rather than transfer. Recorded rather than smoothed over.

What may not be said from this NEVER: 'payments are irreversible', 'reversal is impossible after release', or any presentation of this as an Observed finding rather than a Pattern.

CL-07 Pattern

Every agentic capability inspected in this pilot operates on the reversible side of that line, and every change observed on the irreversible side within the window came from institutional rule-making rather than from agentic capability.

The strongest thing against it EV-06 — an agent surface performing a real state change. It does not break the pattern, because the objects changed are reversible, but it is the nearest thing to a breach and must be stated alongside.

What may not be said from this NEVER: 'agents stop at the payment', 'AI cannot cross the irreversibility line', 'no agent moves money', or any forecast about whether this will continue.

CL-08 Observed

Three structurally different kinds of body were observed setting the permitted form of the invoice while holding no invoice: a member-state finance ministry, a supranational legislature, and a private standards association.

The strongest thing against it None was found within the inspected set.

What may not be said from this NEVER: 'regulators control invoicing', 'the state controls the invoice', or any use of the word 'controls' without naming the object and the holding system (I-13, T-08).

CL-09 Observed

Both the EU directive of 11 March 2025 and the German regime effective 1 January 2025 remove the recipient's consent as a precondition for the mandated electronic invoice form, while leaving it in place for other electronic formats.

The strongest thing against it None was found.

What may not be said from this NEVER: 'buyers can no longer refuse invoices', or any statement that the option has been exercised in a jurisdiction not named.

CL-10 Not established

Settlement status was tested as a candidate consequential object and is NOT ESTABLISHED as an object that any party inside this area changes; in the inspected evidence it is state that parties observe.

The strongest thing against it The nearest contrary evidence is the RDFI's power to return an entry, which changes the disposition of a credit after receipt. It was considered and judged to change the entry, not the settlement status of a buyer's payment.

What may not be said from this NEVER: 'settlement status does not matter', 'nobody changes settlement status', or any presentation of this absence as a property of procurement rather than of the inspected evidence.

CL-11 Not established

This pilot establishes no share, rate, proportion, ranking, momentum or forecast of agentic capability in invoice to payment, and its evidence cannot support one.

The strongest thing against it Not applicable.

What may not be said from this NEVER any sentence containing a share, a percentage of actors, 'most', 'leading', 'growing', 'accelerating' or a projection.

CL-12 Observed

A payment network described by its operator as having processed payments to more than 1.3 million suppliers could not be structurally classified on the inspected evidence, because no artifact named the object it holds or the external system it submits to.

The strongest thing against it None.

What may not be said from this NEVER: 'AvidPay is not a transaction infrastructure', 'AvidXchange does not hold funds', or any classification of the unit.

CL-13 Pattern

The operational-versus-advisory boundary was observed running between two capabilities of a single vendor's product line rather than between vendors.

The strongest thing against it None was found, but the sample is one vendor and the reading should not be treated as established until a second within-vendor pair is observed.

What may not be said from this NEVER: 'vendors mix advisory and execution', stated as a general property, or any ranking of SAP against another vendor.

CL-14 Not established

No agentic capability in the inspected set is established as acting without a human instigator.

The strongest thing against it None was found. Oracle's 26B readiness document states 'In 26B this feature is enabled by default', which concerns enablement of a feature, not autonomous action, and was considered and rejected as contrary evidence.

What may not be said from this NEVER: 'agents are not autonomous', 'these systems require human approval by design', or any claim about system architecture.

Dated acts

What dated acts touch this area's records?

A list, in date order. It is not a timeline and carries no rate: the collection capped each publisher, so this is a floor on what was retrievable rather than a count of what occurred.

Dated acts touching this area
Date	Kind of act	Consequence recorded	Source
2025-01-01 `day precision`	institutional accommodation	Removes the recipient's veto over the invoice format for the mandated form, while preserving it for every other electronic form. Passage: "eine sonstige Rechnung in einem anderen elektronischen Format als eine E-Rechnung (z. B. E-Mail mit einer PDF-Datei) kann – wie bisher – nur verwendet werden, wenn der Empfänger diesem Format zustimmt."	source
2025-03-11 `day precision`	institutional accommodation	Two operative amendments with effect from entry into force. Passage: "Member States may, in accordance with the conditions they lay down, require taxable persons established within their territory to issue electronic invoices for supplies of goods and services within their territory". And: "Member States which exercise the option set out in Article 218, second paragraph, may provide that the use of electronic invoices issued by taxable persons established within their territory is not to be subject to the acceptance of the recipient established in their territory."	source
2025-04-02 `day precision`	workflow expansion	none was established on this artifact.	source
2025-11 `month precision`	transaction infrastructure access	Relocates the binding ceiling: the payment network sets a maximum, the institution sets the operative maximum, and the buyer sets neither.	source
2025-10-15 `day precision`	area entry	none was established on this artifact.	source
2025-Q3 `quarter precision`	workflow expansion	none was established on this artifact.	source
2025-11 `month precision`	institutional accommodation	Sets a dated conformance deadline on parties who are not the rule-maker. Passage: "Mandatory to use from: 2026-02-23".	source
2026-01-27 `day precision`	institutional accommodation	Shares the same stated deadline as EV-07: "Mandatory to use from: 2026-02-23".	source
2026-02-05 `day precision`	transaction infrastructure access	none was established on this artifact.	source
2026-03-20 `day precision`	institutional accommodation	Places a duty on parties by reference to their 2023 volume, and expressly declines to resolve liability. The artifact poses as an open FAQ: "Do the requirements to identify entries suspected to be unauthorized/authorized under False Pretenses impose obligations on ODFIs, non-Consumer Originators, TPS/TPSP to prevent wrongful activity, or change the allocation of liability between parties?"	source
2026-Q1 `quarter precision`	workflow expansion	none was established on this artifact.	source
2026-06-19 `day precision`	institutional accommodation	Converts a large-participant duty into a universal one within the network.	source

Routes that returned nothing

Where did the search stop, and why?

A route that returned nothing establishes that the route returned nothing. A missing capture is a property of the archive, never a property of the world.

Retrieval routes that returned nothing
Source checked	How it failed	What was recorded
Coupa newsroom, dated corporate announcement estate	Not recorded by the method used for this area	NIL — no event admitted. A dated release titled for "Source-to-Pay" whose five named agents operate on cost formulas, requests and SOWs, supplier questions, supplier discovery and category strategy. No passage names an record in scope for the area. Excluded under I-02. Recorded because an omitted nil route would make the vendor estate look richer than it is.
Nacha Operating Rules, same rule package as EV-10	Not recorded by the method used for this area	NIL — no event admitted. The new mandatory Company Entry Descriptions PAYROLL and PURCHASE looked area-placed from the label. On inspection the artifact defines PURCHASE for consumer e-commerce: "an e-commerce purchase is a debit Entry authorized by a consumer Receiver for the online purchase of goods", and PAYROLL for "payment of wages, salaries and similar types of compensation", which the frozen contract excludes. Neither touches a supplier invoice payment. This is the clearest demonstration in the pilot of why I-10 exists: the label suggested admission and the artifact refused it.
Federal Reserve Financial Services press releases	Not recorded by the method used for this area	NIL — no event admitted. The artifact is dated and describes a limit increase to $1 million and new sender-parameter controls, but its only scope wording is "higher-value use cases, including business-related transactions", which names no record in scope for the area. Excluded under I-08: area placement is never inherited from a sibling artifact, and EV-04's supplier-payment passage may not be borrowed to place this one.
Nacha summary of upcoming rule changes	Not recorded by the method used for this area	NIL — outside the observation window. "Funds Availability Requirements for Non-Same Day ACH Credit Entries" and "Definition of IAT Entries" take effect 2026-09-18, after the frozen cutoff of 2026-08-15. Recorded so that the window boundary is visible rather than silent. Also outside the window on the same artifact: 2027-01-01, 2027-03-19, 2027-09-17 and 2028-03-17 rule changes.
Oracle Fusion release-readiness estate	Not recorded by the method used for this area	NIL for the dated register. The artifact substantively documents the Payables Agent and states "In 26B this feature is enabled by default", but carries no visible date of any kind. "26B" is a release label, and T-02 rejects dates inferred from a label. The artifact supports the current-state row C-001 with its limitation stated; it dates nothing. This is the area's evidence-dating calibration case.
HighRadius area-relevant estate	Not recorded by the method used for this area	NIL — thin estate. The actor's located area-relevant material is undated product and blog pages at estate rank 7, which the frozen contract designates leads-only and inadmissible. No claim is carried from search summaries (I-10). Recorded as the area's designated thin-evidence case rather than dropped, so that the thin area appears in the evidence boundary.