Access Official Technical PDF

Share Summary:LinkedInEmail

Pre-trade mid-mark data is a reference input for assessing equity basket and index swaps—not a manufacturing process value or an instruction to execute a trade. For technical teams responsible for integrating financial data into operational systems, its meaning depends on understanding how the mark is calculated, which benchmark applies, and when the published values are valid.

A file of this kind can contain thousands of instruments across currencies and markets. Its tabular appearance may make it seem straightforward to ingest, but the fields carry distinct meanings. Preserving those meanings through parsing, validation and downstream display is essential to avoid treating a reference value as something it is not.

What a pre-trade mid-mark represents

For equity basket swaps and equity index swaps, the described calculation takes the midpoint between the interest rate applicable to a long swap and the rate applicable to a short swap on the same index or basket. The result is expressed in basis points above or below the relevant reference benchmark.

For example, if the long-swap rate is the benchmark plus 20 basis points and the short-swap rate is the benchmark minus 20 basis points, their midpoint is the benchmark itself. The resulting pre-trade mid-mark is therefore flat to the reference benchmark. “Flat” describes a zero spread relative to that benchmark; it does not mean that the benchmark’s underlying interest rate is zero.

This method is specifically described for basket and index swaps. The accompanying security-level file reports mid values for individual listed instruments and funds, along with identifiers, currency and benchmark fields. A reader should not assume that every line item is itself a basket or index swap, or that the example calculation explains every instrument-specific value.

How to read the fields in the reference file

The file combines identifiers and pricing context. Common columns include CUSIP, symbol, SEDOL and ISIN, followed by a security description, underlying currency, reference benchmark and a mid value in basis points. The identifiers help distinguish instruments; the description provides a readable label; and the currency and benchmark establish important context for interpreting the number.

For example, entries in the supplied data include securities denominated in AUD with RBACOR as the listed reference benchmark, and BRL entries with OBFR01. Other rows use different currencies and benchmark labels, including EUR with ESTRON and CAD with CAONREPO. These labels should be retained as supplied rather than replaced with a generic benchmark assumption.

The mid column is expressed in basis points, not as a percentage or currency amount. A value of 2.25 bps is therefore a small spread value in basis-point units; converting it to another representation requires an explicit, consistent unit conversion. The benchmark and currency columns should remain associated with the value wherever it is displayed or passed to another system.

Timing and validity are part of the data

The file states that its values were calculated as of 12:00 noon New York time on November 11, 2026, and are valid until 12:00 noon New York time on November 12, 2026. That timestamp and validity window are not incidental document details. They define the period to which the published reference values apply.

In a data pipeline, retain the calculation time, time zone and stated end of validity alongside the records. If a file is loaded after its validity window, users need to be able to identify that fact rather than unknowingly treating the values as current. Systems should also avoid silently interpreting a missing value, a dash or an incomplete row as a numeric zero.

Practical checks for data integration

For system integrators and technical decision-makers connecting reference files to internal applications, a small set of controls can reduce avoidable interpretation errors:

  • Validate the schema: confirm that identifiers, descriptions, currency, benchmark and mid-value fields land in the intended columns.
  • Preserve units: record that the mid field is in basis points and prevent downstream displays from presenting it as a percentage without conversion.
  • Keep record context: retain the instrument identifier, currency and reference benchmark with each value.
  • Check publication timing: capture the calculation timestamp and validity end, including the stated New York time basis.
  • Handle exceptions explicitly: flag missing identifiers, malformed rows or unexpected values for review instead of silently filling or transforming them.

These are data-handling practices, not claims about the file’s trading use or a guarantee of valuation accuracy. They help keep the source fields interpretable as information moves through ingestion, storage, reporting and review workflows.

Conclusion: preserve meaning from ingestion to use

Pre-trade mid-mark data is useful only when its values remain connected to their calculation context. The basis-point unit, reference benchmark, underlying currency, instrument identifiers and validity window all contribute to the meaning of a record. For technical teams integrating this type of file, the practical priority is disciplined data handling: validate structure, preserve context and make timing visible. That approach helps downstream users distinguish a benchmark-relative reference mark from an execution price or an unqualified number.

Access Official Technical PDF

About The Author