Devancore Inc.
Devancore Post-Trade Glossary
Glossary
Performance Attribution Record
A performance attribution record is the controlled operating record that explains portfolio return using positions, weights, prices, cash flows, benchmarks, classifications, FX, corporate actions, and evidence.
Document source: https://devancore.com/glossary/performance-attribution-record/
Devancore Post-Trade Glossary
Performance Attribution Record
A performance attribution record is the controlled operating record that explains portfolio return using positions, weights, prices, cash flows, benchmarks, classifications, FX, corporate actions, and evidence.
Definition
A performance attribution record is the controlled operating record that explains portfolio return using source data that can be reviewed. The performance number alone is not enough. A firm needs to know which positions, weights, benchmark constituents, prices, FX rates, classifications, corporate actions, cash flows, model settings, and overrides created the explanation.
Performance attribution should be connected to the performance book of record, but it should not be treated only as analytics output. Institutional teams use attribution to explain investment decisions, client reporting, composite performance, risk review, mandate oversight, and recurring performance questions. Those outputs depend on operating data quality.
Attribution record inputs
Attribution record inputs
The record should explain both the result and the data used to produce it.
| Input | Examples | Control question |
|---|---|---|
| Portfolio state | Positions, weights, cash, unsettled trades, accrued income, and corporate actions | Does the attribution use the same operating state as IBOR and PBOR? |
| Benchmark state | Constituents, weights, returns, rebalances, classifications, and version | Can the benchmark used for the calculation be reconstructed? |
| Classification | Sector, industry, asset class, strategy, issuer, country, currency, and custom sleeves | Are portfolio and benchmark labels aligned? |
| Market data | Prices, FX rates, curves, yields, spreads, and valuation inputs | Which source and timestamp created the return input? |
| Model output | Allocation, selection, interaction, factor, income, currency, curve, spread, and residual effects | Can each effect be traced to data and method? |
| Evidence | Source files, versions, adjustments, approvals, comments, exceptions, and reports | Can the report be supported without reconstructing the workflow manually? |
The portfolio state is the foundation. Positions, weights, cash, unsettled activity, accrued income, fees, corporate actions, and account hierarchy determine what is being measured. If the PBOR does not align with IBOR and ABOR where expected, attribution may explain a data difference rather than an investment result.
The benchmark state is the comparison set. Constituents, weights, returns, rebalances, classifications, and versions should be preserved. A benchmark reconstitution, sector reclassification, or stale file can change allocation and selection effects without any portfolio decision changing.
Classifications are control data, not labels added for presentation. Sector, industry, issuer, country, currency, strategy, sleeve, asset class, and custom taxonomies determine how attribution buckets are calculated. If a security has one sector in the portfolio book and another in the benchmark file, attribution residuals may be operational noise.
Market data supplies the return inputs. Prices, FX rates, curves, yields, spreads, and valuation timestamps should be tied to source and version. Fixed income attribution is especially sensitive because return can be decomposed across rates, curve, credit spread, income, carry, roll-down, and currency effects.
Evidence completes the record. Source files, API events, versions, manual adjustments, approvals, exception comments, methodology versions, and report outputs should remain attached to the calculation. Without this chain, a team can show an attribution report but cannot defend how it was produced.
Performance attribution record — daily control loop
Devancore Glossary · devancore.com
How it works
A performance attribution record works by turning portfolio and benchmark data into an explainable return record. The process starts before the model runs. It starts with controlled inputs.
Performance attribution control points
Performance attribution control points
The workflow should control the inputs before it explains the return.
| Control point | Record checked | Failure mode |
|---|---|---|
| Position basis | IBOR, ABOR, PBOR, settled state, unsettled trades, cash, accruals, and corporate actions | Attribution uses a position set that does not match the operating books |
| Benchmark version | Constituents, weights, returns, rebalance date, and provider file version | Client report uses a benchmark state that cannot be reproduced |
| Classification alignment | Sector, industry, asset class, issuer, country, strategy, sleeve, and custom taxonomy | Selection or allocation effect is caused by mismatched labels |
| Price and FX source | Price file, FX rate, valuation timestamp, curve input, and fallback rule | Return differs because sources or timestamps differ |
| Override review | Manual adjustment, reason, owner, approver, expiry, and affected accounts | Performance result includes unsupported intervention |
| Reporting package | Calculation version, methodology, inputs, exception state, and client-reporting output | Attribution number cannot be tied to evidence |
Position basis control checks whether the calculation uses the correct operating state. Some attribution workflows use beginning-of-period weights. Some use daily linked returns. Some need settled positions. Others need expected IBOR state. The record should show which basis was used.
Benchmark control preserves the comparison set. The benchmark file should carry constituent list, weights, returns, rebalance date, classification, and version. If a benchmark provider updates a file, the attribution record should show which version supported the report.
Classification control aligns portfolio and benchmark categories. Allocation and selection effects depend on buckets. Sector, industry, country, currency, asset class, strategy, issuer, and sleeve mappings should be governed because a label change can move basis points across attribution categories.
Price and FX control explains return input differences. A position return can differ because of price source, valuation timestamp, FX rate, holiday calendar, stale price, or fallback method. Those fields should be part of the record, not hidden in downstream analytics.
Override review is a controlled event. A price correction, benchmark adjustment, classification change, cash-flow correction, or model setting change may be appropriate. It still needs owner, reason, approver, effective date, affected accounts, and reporting impact.
Reporting package control ties the result to evidence. Client reporting, performance review, composite support, and supervision should point to a calculation version, input set, methodology, exception state, and approval trail.
In Devancore™
Devancore — attribution evidence chain
Devancore · evidence stack
Operating state
Positions, cash, accruals, unsettled activity, corporate actions, and portfolio hierarchy enter from controlled IBOR, ABOR, and PBOR records.
Reference alignment
Benchmark constituents, classifications, FX, prices, curves, issuer data, and custom sleeves carry source, timestamp, and version.
Calculation context
Attribution method, model version, return basis, benchmark version, and effect categories remain tied to the calculation run.
Exception review
Residuals, classification differences, stale benchmark data, price overrides, and unexplained effects carry owner, reason, approval, and resolution state.
Report evidence
Client reporting, performance review, supervision, composite support, and audit trail consume the same controlled attribution record.
Devancore supports performance attribution records by maintaining controlled operating data around positions, cash, accruals, benchmark state, prices, FX, classifications, corporate actions, model context, exceptions, approvals, and reporting outputs. The platform should be framed as a post-trade record and workflow layer, not as a performance consultant, investment adviser, index provider, pricing vendor, accountant, fund administrator, or reporting authority.
In a Devancore-style workflow, attribution starts from records that already carry lineage: IBOR positions, ABOR-confirmed state, PBOR performance state, cash flows, corporate action effects, benchmark files, classification versions, price sources, FX rates, and curve data. The attribution record can show which inputs fed the calculation and which output consumed the result.
This helps teams identify residuals caused by data issues, benchmark version mismatches, stale prices, incorrect classifications, missing corporate actions, FX timing, unsettled activity, or manual overrides. A performance analyst should not need to reconstruct those causes from separate systems after a client question arrives.
The same record can support performance review, client reporting preparation, mandate oversight, composite support, risk review, regulatory reporting support, and audit trail. The practical value is that the attribution result stays connected to the operating record rather than becoming a disconnected analytics artifact.
Conversational finance becomes useful when the attribution record is structured. A user may ask which securities drove selection effect, which benchmark version was used, which classification changes affected allocation, which fixed income positions moved because of credit spread, which FX rates were applied, or which reports include manual overrides. The answer should resolve to positions, benchmark records, source data, model context, owners, and evidence.
Related terms
- Performance Book of Record
https://devancore.com/glossary/performance-book-of-record-pbor/
The PBOR — a position record that extends the IBOR with return attribution, risk analytics, and benchmark data, providing the authoritative basis for investment performance measurement and client reporting.
- Investment Book of Record
https://devancore.com/glossary/investment-book-of-record/
The IBOR — a real-time position record used by investment managers, capturing unsettled trades, accruals, and corporate actions ahead of custodian confirmation and ABOR settlement.
- Accounting Book of Record
https://devancore.com/glossary/accounting-book-of-record/
The ABOR: custodian-confirmed settled positions used as the authoritative basis for NAV calculation, financial statements, and regulatory reporting.
- IBOR vs ABOR Reconciliation
https://devancore.com/glossary/ibor-vs-abor-reconciliation/
The daily process of comparing the forward-looking investment book of record (IBOR) against the custodian-confirmed accounting book of record (ABOR) to identify and resolve position differences arising from the settlement cycle.
- Credit Curve Reference Data
https://devancore.com/glossary/credit-curve-reference-data/
Credit curve reference data is the governed fixed income data used to support spread curves, valuation controls, P&L explain, collateral marks, accounting inputs, and review evidence.
- Fixed Income Post Trade Data
https://devancore.com/glossary/fixed-income-post-trade-data/
Fixed income post-trade data is the instrument, trade, pricing, accrual, settlement, reporting, and evidence data required to move a bond trade from execution into controlled operating records.
- Fixed Income OMS Post Trade Controls
https://devancore.com/glossary/fixed-income-oms-post-trade-controls/
Fixed income OMS post-trade controls verify bond trade records after execution across price, yield, accrued interest, coupon terms, maturity, settlement path, allocation, confirmation, reporting, and reconciliation.
- Portfolio Accounting System
https://devancore.com/glossary/portfolio-accounting-system/
A portfolio accounting system is the controlled architecture that maintains transactions, positions, cash, accruals, valuation inputs, tax lots, reconciliation, and audit evidence for portfolio accounting workflows.
- Portfolio Accounting Software
https://devancore.com/glossary/portfolio-accounting-software/
Software that converts portfolio transactions, positions, cash, income, accruals, prices, tax lots, and realized gains into controlled accounting and reporting views.
- Fund Accounting Platform
https://devancore.com/glossary/fund-accounting-platform/
A fund accounting platform is the controlled operating layer that organizes fund-level records, NAV inputs, expenses, income, allocations, investor activity, reconciliation, approvals, and reporting evidence.
- Investment Accounting Software
https://devancore.com/glossary/investment-accounting-software/
Software that turns institutional trades, positions, cash, accruals, corporate actions, tax lots, reconciliations, and close controls into accounting-ready investment records.
- Cloud Native Investment Accounting
https://devancore.com/glossary/cloud-native-investment-accounting/
Cloud native investment accounting is an event-driven accounting architecture for institutional portfolios, using controlled APIs, scalable processing, data lineage, reconciliation evidence, security controls, and resilient cloud infrastructure.
- Regulatory Reporting — Securities
https://devancore.com/glossary/regulatory-reporting-securities/
The post-trade obligation to submit structured trade data — transactions, positions, and order lifecycle events — to regulators under MiFID II, EMIR, Dodd-Frank, and CAT to establish the supervisory record of each trade.
- Financial Transaction Reconciliation
https://devancore.com/glossary/financial-transaction-reconciliation/
The three-way match between sub-ledger, general ledger, and external statement that validates balance sheet integrity — with every break tracked as gross exposure for Rule 17a-5 and Rule 15c3-1 compliance.
- Position Reconciliation Software
https://devancore.com/glossary/position-reconciliation-software/
Software that automates daily comparison of internal position records against custodian statements, prime broker reports, and on-chain ledger state, surfacing breaks before they affect Rule 15c3-3 determinations, NAV, or securities count obligations.
- Cash Reconciliation Software
https://devancore.com/glossary/cash-reconciliation-software/
Software that matches a broker-dealer's internal cash ledger against bank statements and clearing utility records in real time, surfacing breaks for resolution before they create reserve formula errors, missed sweeps, or Rule 15c3-3 violations.
- Corporate Action Processing
https://devancore.com/glossary/corporate-action-processing/
Corporate action processing is the operational workflow that captures issuer events, calculates per-account entitlements, and reconciles cash and position changes against custodian records.
- Broker-Dealer Audit Trail
https://devancore.com/glossary/broker-dealer-audit-trail/
The immutable, chronologically linked record of every trade lifecycle event — from order receipt through settlement — maintained to satisfy SEC Rules 17a-3 and 17a-4, FINRA clock synchronization requirements, and CAT reporting obligations.
Contact
Request a briefing or platform walkthrough with the Devancore team.
Request access https://devancore.com/access/