Build a SAP margin history without filling the gaps

A longer history can still be incomplete

Our stored SAP sample spans 2015–2025. Its 2017 row has operating income but no revenue, so an operating-margin calculation for that period has no denominator. Replacing the missing value with zero would create a meaningless result; interpolating revenue would introduce an estimate that is not in the source record.

Resolve SAP and check the annual statement periods available. Build an operating-margin history using operating income divided by revenue. Keep missing values missing, leave gaps in the chart, and identify each row’s source and currency. Flag changes of source, accounting basis and report version. Do not describe the series as complete or comparable until those checks pass.

Keep the missing year visible

The table preserves the requested period even when the calculation is unavailable. A line should stop at the missing observation and resume at the next complete one. Connecting the points across 2017 would suggest continuity that we have not established.

This sample combines SEC XBRL, Bundesanzeiger and ESEF records. The source column describes the stored records; it does not prove that every historical value was manually reconciled to a specific original document.

Check comparability before telling a story

Consistent field names are useful, but they do not settle accounting comparability. Ask whether the observations cover the same reporting entity, consolidation scope, annual duration, currency and measure definition. An acquisition, discontinued operation or restatement may change the interpretation of a trend even when every cell is populated.

1. Ask for all required years and compare that list with the returned periods.
2. Check for multiple records for the same year. Choose a report version deliberately rather than averaging duplicates.
3. Retain source labels and filing identifiers. Locate the original report when the comparison matters.
4. State which observations are missing or still require reconciliation.

A useful answer includes the unresolved work

A defensible answer could say: “The stored series contains eleven annual periods and ten calculable margins; 2017 revenue is missing. Sources differ, so this is a starting table for reconciliation.” That is more useful than presenting a smooth chart as a finished accounting comparison.

For a simpler calculation with direct ESEF source links, use the ASML example.

A report-period history is not a point-in-time backtest

A row for 2015 tells you which reporting period it describes. It does not, by itself, tell you when that version of the number became available to an investor. Later reports can restate earlier periods, and a source-normalization change can alter an imported field.

Before a backtest, establish the publication/availability date and report vintage for every observation. This dated mixed-source sample is a missing-data demonstration, not a validated point-in-time series. Downloading it does not remove that distinction.

For an accounting comparison, inspect original reports and choose a consistent definition. Keep 2017 as a visible gap until the relevant source and mapping are verified.