The SEC’s 2015 pay ratio rule made a payroll median a filed figure, and a privacy carve-out a legal opinion

The SEC’s August 2015 pay ratio rule let companies find a median employee by sampling and payroll records. The result was filed, and leaving out staff under foreign privacy law required a filed legal opinion.

Looking Back revisits past weeks one at a time, up to the most recent, and asks what it meant for the banks, health systems and public agencies we serve. The series was written in 2026, with the benefit of hindsight, and each article says which week it looks back on.

Two-minute summaryThe dek and the first sentence of each section, quoted from the article

The SEC’s August 2015 pay ratio rule let companies find a median employee by sampling and payroll records. The result was filed, and leaving out staff under foreign privacy law required a filed legal opinion.

  1. The week The rule text carries its own dates.
  2. The population: every employee of every consolidated subsidiary The definition excluded workers employed, and whose compensation is determined, by an unaffiliated third party but who provide services as independent contractors or “leased” workers. [2] That exclusion turned on who sets the pay.
  3. The method: finding a median without totaling everyone Sampling changes the work.
  4. The border: privacy law and the 5 percent allowance The proposal had included non-U.S. employees, and commenters argued for excluding them.
  5. The liability: a filed figure, with its method attached The release declined to exempt the pay ratio disclosure from the certification requirements of Exchange Act Rules 13a-14 and 15d-14 or Section 906 of the Sarbanes-Oxley Act. [2] In our reading, that placed the figure within the reports that chief executives and chief financial officers certify.
  6. How the rule reached different financial firms A bank holding company that files an annual report with Item 402 disclosure was squarely inside the rule, unless it was a smaller reporting company or emerging growth company. [1] [2] Its population included every consolidated subsidiary’s staff. [2] For a holding company with a branch network, the population is large and mostly domestic; the work lies in reconciling payrolls and choosing the measure.
  7. The objections, and what the record shows Commenters raised concerns about imprecision and liability, the 2017 guidance said. [5] The Commission’s answer, in 2015 and again in 2017, was disclosure of method rather than precision. [2] [5] The 2015 release said the rule was designed to help shareholders understand a particular registrant’s pay practices rather than to compare registrants, as the 2017 guidance later recounted. [5] On that design, imprecision that is explained is acceptable; imprecision that is hidden is not.
  8. Checks a data or human resources leader could run These checks are our suggestions, not requirements of the rule.
  9. With hindsight The rule’s first compliance year was preceded by a reconsideration.

The week

On August 5, 2015, the Securities and Exchange Commission adopted a final rule requiring a public company to disclose the ratio of its chief executive officer’s compensation to the median compensation of its employees. [1] The release said the rule was mandated by the Dodd-Frank Wall Street Reform and Consumer Protection Act and gave companies flexibility in calculating the ratio. [1]

The rule text carries its own dates. The adopting release, Release No. 33-9877, is dated August 5, 2015. [2] It set an effective date of October 19, 2015, and required registrants to comply for the first fiscal year beginning on or after January 1, 2017. [2] The Commission had proposed the rule on September 18, 2013. [2]

The statutory instruction was narrow. Section 953(b) of the Dodd-Frank Act directed the Commission to amend Item 402 of Regulation S-K. [2] The amended item had to require three numbers: the median of the annual total compensation of all employees except the chief executive, that executive’s annual total compensation, and the ratio between them. [2]

The comment record was large. The release said that of the over 287,400 comment letters the Commission received, over 285,900 were form letters of 12 types, which either supported the proposal or supported adopting a rule under Section 953(b). [2] It said the vast majority of the over 1,500 unique comment letters came from individual commenters who took the same positions. [2] Comments addressed, among other things, the rule’s application to foreign, part-time, temporary and seasonal employees. [2]

The release described what the final rule changed from the proposal. It listed exemptions for non-U.S. employees, the treatment of employees of consolidated subsidiaries, a determination date within three months of fiscal year-end, identifying the median employee once every three years, and transition periods. [2]

The fact sheet published with the release described the method in steps. A company could use its total employee population or a statistical sampling of it, and other reasonable methods. [1] It could identify the median using annual total compensation under the existing executive pay rules, or “any consistently-applied compensation measure” from its payroll or tax records. [1] It could apply a cost-of-living adjustment, but then had to show the figures without it as well. [1]

The fact sheet also set the population. Subject to exceptions, a company had to include all employees, “U.S. and non-U.S., full-time, part-time, temporary and seasonal,” employed by it or its consolidated subsidiaries. [1] Workers employed by unaffiliated third parties, and independent contractors, were not counted as the company’s employees. [1]

Two exceptions reached non-U.S. staff. A company could exclude employees in a jurisdiction whose data privacy laws made it unable to comply without violating them, if it obtained a legal opinion from counsel. [1] It could also exclude up to 5 percent of its total employees who were non-U.S. employees, counting any excluded under the privacy exemption. [1]

The release named the companies outside the rule. It did not apply to smaller reporting companies, emerging growth companies, foreign private issuers, filers under the multijurisdictional disclosure system or registered investment companies. [1] The rule placed the disclosure in registration statements, proxy and information statements and annual reports that already required executive compensation information. [1] Current and quarterly reports did not need it. [1]

For a public bank holding company, a listed broker-dealer parent or a listed insurer, the week’s news was therefore specific. From its first fiscal year beginning on or after January 1, 2017, its filings would carry a figure built from the payroll of every consolidated subsidiary. [1] [2] The method could be chosen; the number would be filed. [2]

The 2015 pay ratio rule is remembered as a governance disclosure, a single number about executive pay. For a technology, data or human resources leader at a public financial company, its more useful feature is structural. It turned a statistic drawn from payroll systems in every country where the company employed people into a figure in an SEC filing. [2]

Our argument is that the rule made payroll data a disclosure input and wrote the limits of that data into the filing itself. The Commission let companies choose their method, sample their workforce and use records they already kept. [2] In exchange, it required them to describe the method, identify estimates and, where privacy law stood in the way, file a lawyer’s opinion saying so. [2] In our reading, the rule did not ask for a precise median. It asked for a defensible one, with the defense in the filing.

That framing matters because the work fell to people who do not write proxy statements. The inputs came from payroll platforms, human resources information systems, tax records, and the subsidiaries that run them. [2] The rule made those systems part of the reporting chain of a public company. [2]

We take the rule in four parts, each a different layer of the data it created:

  1. The population: who counted as an employee, on which date and in which entities.
  2. The method: how a company could find the median without computing everyone’s total compensation.
  3. The border: how foreign privacy law could take employees out of the count, and what that cost in documentation.
  4. The liability: how the finished figure was treated once it entered a filing.

The parts do not overlap. The first is scope, the second calculation, the third exclusion and the fourth accountability. After them we look at how the rule reached different financial firms, take the objections in order and end with checks a data or human resources leader could run.

The population: every employee of every consolidated subsidiary

The definition

The rule defined an employee as an individual employed by the registrant or any of its consolidated subsidiaries. [2] The definition covered full-time, part-time, seasonal and temporary workers. [2] The count was taken as of a date the registrant chose within the last three months of its last completed fiscal year. [2]

The definition excluded workers employed, and whose compensation is determined, by an unaffiliated third party but who provide services as independent contractors or “leased” workers. [2] That exclusion turned on who sets the pay. In our reading, it made the employment relationship, as the company’s own records showed it, the line between counted and not counted.

Why the consolidated perimeter mattered for financial firms

The registrant, for the rule’s purposes, meant the registrant and its consolidated subsidiaries. [2] A bank holding company that consolidates a bank, a broker-dealer, an insurance agency and an offshore operations center had to treat all of their staff as one population. [2] Each of those entities can run its own payroll, its own pay calendar and its own definition of compensation.

The rule did not require a single payroll system. It required a single population on a single date. [2] In our reading, that put the burden on reconciliation: proving that the list of employees used for the median matched the consolidated group on the chosen day.

The determination date

The proposal had measured employees on the last day of the fiscal year. The final rule let a registrant pick any date within the last three months of that year. [2] If it changed the date from one year to the next, it had to disclose the change and give a brief explanation. [2]

For a data team, the date choice is a design decision. A date that matches an existing headcount extract, such as a quarter-end census, avoids building a new snapshot. A date inside a hiring season, or just after a large reduction in staff, changes the population. The rule allowed either, and asked only that the date be disclosed. [2]

New hires and part-timers

The fact sheet set out how to treat partial years. A company was permitted, but not required, to annualize the pay of a permanent employee who did not work the entire year, such as a new hire. [1] It could not make full-time equivalent adjustments for part-time workers, or annualize pay for temporary and seasonal workers. [1]

Those two rules pull in different directions for a data model. Permanent new hires could be adjusted upward. Part-time, temporary and seasonal staff had to stay at actual pay. [1] A payroll system that stores employment type reliably makes that distinction easy. One that does not makes it a manual review.

Acquisitions

The fact sheet said a company could omit employees obtained in a business combination or acquisition for the fiscal year in which the transaction became effective. [1] It then had to identify the acquired business and disclose the approximate number of employees omitted. [1] For an acquisitive bank or wealth manager, that created a one-year window before an acquired payroll had to be folded into the count.

Where the population data lives

In a financial group, the facts the rule needed sit in different places. Legal entity structure is held by finance and corporate secretarial teams. Employment records sit in human resources systems. Pay sits in payroll, which may be run in-house in one entity and by an outside provider in another. [2] The rule’s single population on a single date asked those records to agree. [2] Where they did not, the reconciliation itself became evidence of how the count was made.

What the population part asked of systems

Taken together, the population rules asked three things of a firm’s data. It needed a list of every individual employed across the consolidated group on one date. It needed each person’s employment type and jurisdiction. It needed a way to separate employees from contractors and leased workers whose pay a third party sets. [2] None of those is new data. The rule made their accuracy matter to a filing.

The method: finding a median without totaling everyone

Sampling and other reasonable methods

The rule let a registrant use its full employee population or statistical sampling, and other reasonable methods, to identify the median employee. [2] It allowed reasonable estimates both in identifying the median employee and in calculating total compensation for employees other than the chief executive. [2]

Sampling changes the work. A firm with a clean, consolidated payroll extract might simply sort every employee by one pay measure. A firm with several payroll systems in several countries might sample within each and combine the results. The rule did not prescribe a technique. [2] It required a brief description of the methodology and of material assumptions, adjustments and estimates. [2]

The consistently applied compensation measure

The second flexibility was the measure used to rank employees. The rule allowed annual total compensation, or “any other compensation measure that is consistently applied to all employees included in the calculation,” such as information derived from tax or payroll records. [2] If the measure was kept on a period other than the fiscal year, the registrant could use that period. [2] It had to disclose the measure it used. [2]

This part of the rule is tied closely to data quality. A measure such as taxable wages from payroll records is available, but its meaning varies by country. A measure built from base salary alone is simpler but leaves out bonuses and overtime. The rule left that choice to the registrant, on the condition that it be applied consistently. [2]

From ranking to the median employee’s total pay

Once the median employee was identified, the company had to compute that person’s annual total compensation using the same rules that apply to the chief executive’s pay, under Item 402(c)(2)(x). [1] For non-salaried employees, the rule let references to “salary” be read as “wages plus overtime.” [2] The current text also lets registrants include personal benefits under $10,000 and non-discriminatory benefit plans for the median employee, if they include them for the chief executive too. [6]

So the method had two stages. The first ranked employees on a measure the company chose. The second calculated full compensation for one person, the median, under the executive compensation rules. [2] The first stage needs a broad dataset. The second needs a deep record for one individual, from payroll, benefits and equity systems.

Cost-of-living adjustments

The rule allowed cost-of-living adjustments to employees in jurisdictions other than the one where the chief executive resides. [2] A registrant that used them had to apply the same adjustment to the median employee’s total pay, disclose the median employee’s jurisdiction and describe the adjustments. [2] It also had to disclose the median and the ratio without the adjustment, which meant identifying the median a second time without it. [2]

For data teams, an adjustment doubles the computation and adds an external input, the cost-of-living index. The rule asked the registrant to describe the measure used as the basis for the adjustment. [2] That index then became part of the record behind a filed number.

Once every three years

Instruction 2 to Item 402(u) required the median employee to be identified only once every three years, with total compensation calculated each year. [2] The exception was a change in the employee population or compensation arrangements that the registrant reasonably believed would significantly change the disclosure. [2] If the original median employee’s circumstances changed, the registrant could substitute another employee with substantially similar compensation on the original measure. [2]

The three-year cycle reduced work and created a judgment to record. In years two and three, a registrant had to disclose that it was using the same median employee and briefly describe the basis for its reasonable belief that nothing significant had changed. [2] In our reading, that belief needs evidence: headcount by jurisdiction, pay changes and corporate transactions since the last identification.

What the method part asked of systems

The method rules gave flexibility in exchange for description. A firm could sample, estimate, adjust and reuse, provided it said how. [2] The practical artifacts are a written methodology, the extract or sample used, the measure chosen and the calculation for the median employee. The rule asked for a brief overview and said technical analyses or formulas were not necessary. [2] It did not require the working files to be filed. Keeping them is a choice we discuss below.

A hypothetical sampling design

A hypothetical regional bank holding company shows how the method part could be applied. Suppose it runs one payroll system for its bank, another for its broker-dealer and a third for a small insurance agency. Its staff are almost all in the United States.

It could choose a determination date matching an existing quarter-end headcount file, then rank every employee in all three systems by annual taxable wages. [2] No sample would be needed, because the full population is available. The work would lie in merging three extracts and agreeing on what each system calls wages.

A second hypothetical firm, with operations staff in several countries and separate local payrolls, faces a different choice. It might rank employees within each country on local payroll records and combine the results, or draw a sample from each. The rule permitted either if described. [2] The firm’s description, its measure and its sample would all have to be explained in brief in the filing. [2]

Neither design is prescribed. The point of the example is that the rule converted a design decision into a disclosure, which in our reading made the design part of the firm’s disclosure controls.

The border: privacy law and the 5 percent allowance

Why the Commission kept non-U.S. employees in

The proposal had included non-U.S. employees, and commenters argued for excluding them. The Commission declined a wholesale exemption. [2] It called their inclusion “the policy choice that most closely captures what Congress directed us to do” in requiring a ratio for “all employees.” [2] It rejected the argument that including them was an extraterritorial application of the statute, because the focus of Section 953(b) is disclosure by registrants that use U.S. markets. [2]

What commenters said about privacy law

The release recorded commenters’ concerns about data transfer. Commenters said several countries had data privacy laws that prevent transferring payroll data outside their borders, even within the same company. [2] They noted that the E.U. prohibited transfers to third countries without adequate privacy protection, and that the United States was considered not to ensure it. [2] They listed other countries that had adopted or were considering similar rules. [2]

One commenter, the release said, acknowledged that registrants employing workers abroad would already understand their obligations under those laws. [2] The same commenter noted that data made truly anonymous might fall outside the E.U. Directive. [2] The release went on to say it “would seem” that a registrant with hundreds or thousands of employees in an E.U. jurisdiction could collect the data anonymously. One with a handful might not. [2]

The data privacy exemption

The final rule created a tailored exemption. A non-U.S. employee could be excluded if employed in a jurisdiction whose data privacy laws were such that, despite reasonable efforts, the registrant could not obtain or process the necessary information without violating them. [2] Reasonable efforts had to include, at a minimum, using or seeking an exemption or other relief under the governing privacy law. [2]

The exemption came with four disclosure duties. The registrant had to list the excluded jurisdictions, identify the specific law, explain how compliance would violate it and give the approximate number of employees exempted. [2] It had to exclude all non-U.S. employees in that jurisdiction if it excluded any. [2] And it had to obtain a legal opinion from counsel on its inability to obtain or process the data, and file the opinion as an exhibit. [2]

The release explained the safeguard. To prevent “any potential manipulation,” the rule required reasonable efforts to obtain or process the information. [2] For filings other than proxy or information statements, the opinion was to be filed under Exhibit 99. [2]

The de minimis exemption

The second exemption was numerical. A registrant whose non-U.S. employees were 5 percent or less of its total employees could exclude all of them, and if it excluded any it had to exclude all. [2] A registrant with more than 5 percent non-U.S. employees could exclude up to 5 percent of its total employees, jurisdiction by jurisdiction. [2] It could not exclude employees from a jurisdiction holding more than 5 percent of its total employees. [2]

The two exemptions interacted. Employees excluded under the privacy exemption counted against the 5 percent. [2] If privacy exclusions alone reached 5 percent, the de minimis exemption was unavailable. [2] A registrant using the de minimis exemption had to disclose the jurisdictions, approximate numbers excluded, and its total U.S. and non-U.S. employees both before and after exclusions. [2]

The Commission said its staff in the Division of Economic and Risk Analysis had analyzed the effect of excluding different percentages of employees and posted two memoranda to the comment file. [2] It said the 5 percent threshold would limit the exemption to an amount that was “in fact, de minimis.” [2]

What the border part asked of systems and counsel

The privacy exemption made a legal conclusion into a filed document. In our reading, a registrant could not rely on a general sense that privacy law was strict. It needed a jurisdiction-specific analysis, an attempt at relief and an opinion that could be read by anyone with access to the filing. [2]

That reverses a usual sequence. Privacy teams assess a transfer and decide how to make it lawful. Under this rule, a decision that a transfer could not be made lawful became a disclosure, with the law named. [2] For a firm with operations staff in several countries, the choice was between building a compliant data flow, including anonymized or aggregated reporting, and documenting why it could not.

In our reading, the release’s own discussion pointed to one design: where anonymous data could be collected, the exemption might not be needed. [2] A firm could compute the ranking measure locally and send only what the method required. Whether that met a given country’s law was, and remains, a question for counsel in that country.

A security cost of collecting payroll centrally

The rule did not say where the ranking had to be done. A firm could pull every employee’s pay into one central dataset, or compute locally and send only the results. [2] The first approach is simpler to describe. It also creates a new, consolidated copy of compensation data for the whole workforce.

A copy like that is sensitive. It holds names or identifiers, pay and jurisdiction for every employee in the group. In our reading, a firm building it for the pay ratio would need the same access controls, retention limits and monitoring it applies to other payroll data. A firm computing locally would need less central data, at the cost of more coordination.

This is a trade-off the rule left open. The privacy exemption addressed whether data could lawfully be processed at all. [2] It did not address how a lawful process should be secured. That remained a matter for the firm’s own security program.

What an exclusion tells an outside reader

The disclosures attached to the exemptions are public. A registrant using the privacy exemption had to name the excluded jurisdictions and give approximate employee numbers for each. [2] One using the de minimis exemption had to name jurisdictions, approximate numbers excluded and its total U.S. and non-U.S. employees. [2]

For some firms, headcount by country is information they had not published before. A compliance team weighing the exemptions would therefore weigh what the disclosure itself reveals. In our reading, that is a reason to involve the teams that manage external communications about operations, alongside the payroll and legal teams.

The liability: a filed figure, with its method attached

Filed, not furnished

Commenters asked that the disclosure be “furnished” rather than “filed,” which would have changed its liability treatment. [2] The final rule treated it as filed, like other Item 402 information, and so subject to potential liabilities under the Securities Act and Exchange Act, including Exchange Act Section 18. [2]

The release acknowledged that identifying the median and calculating pay could require reviewing a large amount of data and making a significant number of estimates, assumptions and judgment calls. [2] It said that fact alone did not justify exempting the information. [2] It pointed to the required description of methodology and assumptions as the way registrants could explain “where potential imprecisions may be introduced.” [2]

Certifications

The release declined to exempt the pay ratio disclosure from the certification requirements of Exchange Act Rules 13a-14 and 15d-14 or Section 906 of the Sarbanes-Oxley Act. [2] In our reading, that placed the figure within the reports that chief executives and chief financial officers certify. Their certifications rest on the processes that produce the information, which here began in payroll.

What Section 18 required, as the release described it

The release said Section 18 does not create strict liability for filed information. [2] A person is not liable if it acted in good faith and had no knowledge that the statement was false or misleading. [2] A plaintiff would also need to show a purchase or sale at a price affected by the statement, reliance and damages. [2] The release added that failure to comply could also violate Exchange Act Sections 13(a) and 15(d). [2]

Timing

Instruction 3 let the ratio for the last fiscal year wait until the annual report on Form 10-K or, if later, the proxy or information statement for the next annual meeting. [2] The rule set an outer limit in its own words: “not later than 120 days after the end of such fiscal year.” [2] That deadline tied the payroll work to the annual reporting calendar.

What the liability part asked of the record

The rule’s structure gave a registrant a way to defend a number that was, by design, approximate. The defense was the disclosed method and the good faith behind it. [2] In our reading, that defense is only as strong as the records showing the method was followed: the extract, the date, the measure, the exclusions and the calculation. A filed description with no working papers behind it would be a weak position if the number were challenged.

Controls a disclosure committee could expect

The rule does not list internal controls for the pay ratio. In our reading, the filed status and the certifications point to a familiar set. A disclosure committee could expect a documented methodology approved before the calculation and a reconciliation of the population to the consolidated group. It could also expect a review of the median employee’s total pay by someone outside the team that computed it. [2]

It could also expect change control. The rule requires a brief description of any significant change in methodology, assumptions or estimates from the prior year, with the reasons. [2] A firm can describe changes only if it knows it made them. Version history for the method document and the extracts is the simplest way to know.

How the rule reached different financial firms

Public bank and financial holding companies

A bank holding company that files an annual report with Item 402 disclosure was squarely inside the rule, unless it was a smaller reporting company or emerging growth company. [1] [2] Its population included every consolidated subsidiary’s staff. [2] For a holding company with a branch network, the population is large and mostly domestic; the work lies in reconciling payrolls and choosing the measure.

Broker-dealer and asset management parents

A listed parent of a broker-dealer or investment adviser faced the same rule, with a compensation structure that can lean heavily on bonuses and deferred pay. The choice of ranking measure matters more where variable pay is a large share of compensation. [2] The rule did not apply to registered investment companies themselves. [1]

Insurers, payment companies and other listed financial firms

The rule made no distinction by industry. A listed insurer, payment processor or consumer lender that gave Item 402 disclosure was covered on the same terms as a bank. [2] What differed was the shape of the workforce. A firm with a large call center, a commissioned sales force or seasonal processing staff had to apply the rule’s treatment of part-time, temporary and seasonal workers. That treatment barred full-time equivalent adjustments and annualization for those groups. [1]

A firm that relies on agents or brokers had a classification question. Workers whose pay is set by an unaffiliated third party were outside the count. [2] Agents paid directly by the firm could be employees or contractors depending on their arrangement. The 2017 guidance later said firms could apply widely recognized tests, such as those used for tax purposes, to decide. [5]

Firms with offshore operations

Financial firms that run operations, technology or service centers outside the United States brought the border part into play. The de minimis exemption could cover a small foreign footprint. [2] A larger one, or one concentrated in a single country above 5 percent of total staff, could not be excluded under it. [2] Those firms had to collect the data, or use the privacy exemption with its opinion and disclosures. [2]

Smaller and newer registrants

Smaller reporting companies and emerging growth companies were outside the rule. [1] The fact sheet described transition periods for companies that cease to be smaller reporting companies or emerging growth companies, and for new registrants. [1] A fintech that went public as an emerging growth company would meet the rule only on leaving that status, in our reading giving it time to build the data.

Institutions outside the rule

The rule reaches registrants required to provide Item 402 executive compensation disclosure. [2] An institution without that duty, such as a mutual savings institution or a credit union that does not file such reports, had no pay ratio obligation, in our reading. Their payroll data teams faced none of this work, though the questions it raises about data lineage apply to any figure an institution reports.

The objections, and what the record shows

“The number is too imprecise to be useful”

Commenters raised concerns about imprecision and liability, the 2017 guidance said. [5] The Commission’s answer, in 2015 and again in 2017, was disclosure of method rather than precision. [2] [5] The 2015 release said the rule was designed to help shareholders understand a particular registrant’s pay practices rather than to compare registrants, as the 2017 guidance later recounted. [5] On that design, imprecision that is explained is acceptable; imprecision that is hidden is not.

“Foreign privacy law makes compliance impossible”

The Commission did not accept that as a general rule. It accepted it case by case, with reasonable efforts, a named law and a filed opinion. [2] The strongest form of the objection is cost: obtaining relief and opinions in several countries is expensive. The rule’s response was the de minimis allowance for small foreign populations. [2] For larger ones, the cost was the price of an exclusion.

“The rule should have been furnished, not filed”

The release rejected this. It noted that all other Item 402 information is filed and that the pay ratio is information about the registrant’s operations and workforce. [2] The objection still has force for compliance teams: a filed number invites the same controls as other filed numbers. In our reading, that was the intended effect.

“It is a compensation matter, not a data matter”

The rule is located in the executive compensation item. [2] Its inputs are not. They are headcount, employment type, jurisdiction and pay from systems that compensation committees do not run. [2] The 2017 guidance confirmed this by addressing the use of tax and payroll records directly. [5] The strongest case against our argument is that the work, once designed, became a routine annual calculation. Even so, a routine calculation feeding a certified filing still needs lineage.

“Sampling invites cherry-picking”

A skeptic could argue that flexibility lets a registrant choose the method that produces a more favorable ratio. The rule’s answer had three parts. Methods had to be described, estimates identified and significant changes from year to year explained. [2] The privacy exemption also carried a reasonable-efforts requirement that the release said was meant to prevent manipulation. [2] Whether those answers were enough is a judgment. They do mean that a method chosen for its outcome would leave a disclosed trail.

Checks a data or human resources leader could run

These checks are our suggestions, not requirements of the rule. Registrants should confirm disclosure questions with securities counsel.

  • Population reconciliation: keep a record showing that the employee list used for the median matches the consolidated group on the determination date, including part-time, temporary and seasonal staff.
  • Worker classification: document how the firm separates employees from contractors and leased workers whose pay a third party determines.
  • Measure definition: write down the compensation measure used to rank employees, its source system in each country and the period it covers.
  • Jurisdiction file: for each country excluded, keep the analysis, the attempt to obtain relief and counsel’s opinion together, and review them when the law changes.
  • De minimis count: keep the headcount by jurisdiction used to test the 5 percent allowance, and the one-jurisdiction limit, with the date of the count.
  • Three-year basis: in years two and three, record the facts behind the belief that nothing significant changed, such as headcount shifts and acquisitions.
  • Working papers: retain the extract or sample, the median calculation and any cost-of-living index, so the filed description can be shown to match what was done.
  • Certification chain: make sure the people who sign subcertifications for the pay ratio know which systems and staff produced it.

The 2015 rule let registrants be approximate and required them to be explicit. [2] The checks above follow that line: keep the evidence that the approximation was reasonable, and keep the reasons for every person left out.

One more test ties them together. If a regulator or shareholder asked how the median employee was chosen, could the firm answer from records rather than recollection? The rule made that answer part of the filing. [2] The working papers decide whether the answer holds.

With hindsight

The rule’s first compliance year was preceded by a reconsideration. On February 6, 2017, Acting Chairman Michael S. Piwowar issued a statement seeking public input on unexpected challenges that issuers had met in preparing to comply. [3] The statement said issuers were then implementing and testing systems and controls to collect and process the necessary information. [3] It asked for comments within 45 days and directed the staff to reconsider the rule’s implementation. [3]

The compliance date did not move. On September 21, 2017, the Commission approved interpretive guidance on pay ratio disclosure. [4] The guidance said registrants must provide the disclosure for the first fiscal year beginning on or after January 1, 2017, which meant disclosures in early 2018. [5] It cited comment letters from March 2017, including from the Financial Services Roundtable and The Insurance Coalition. [5]

The 2017 guidance addressed the data questions directly. It addressed estimates first. If a registrant uses reasonable estimates, assumptions or methodologies, it said, the resulting disclosure would not provide the basis for enforcement action unless it lacked a reasonable basis or was not given in good faith. [5] It clarified that a registrant may use appropriate existing internal records, such as tax or payroll records, to decide whether the 5 percent de minimis exemption is available. [5]

It also said a registrant may use internal records that reasonably reflect annual compensation to identify the median employee, even if they do not include every element of compensation. [5] Its example was equity awards widely distributed to employees. [5] It said registrants could use widely recognized tests, such as one drawn from Internal Revenue Service guidance on independent contractors, to decide who is an employee. [5] The release said the staff was separately providing guidance with examples of reasonable estimates and statistical methods. [4]

The guidance also recalled how the 2015 rule had been published. It cited the release as published in the Federal Register at 80 FR 50103 on August 18, 2015. [5]

The rule itself has stayed in place. As checked on November 16, 2026, the eCFR text of 17 CFR 229.402, up to date as of November 12, 2026, includes paragraph (u), pay ratio disclosure. [6] Its data privacy exemption still requires reasonable efforts, including seeking relief under the privacy law, a list of excluded jurisdictions and a legal opinion filed as an exhibit. [6] Its instruction on identifying the median employee once every three years reads as adopted in 2015. [6]

What held up from August 2015 is the bargain at the center of the rule. Registrants could sample, estimate and use the records they had, and the Commission later confirmed that payroll and tax records were acceptable inputs. [5] The disclosure of method stayed mandatory, and the figure stayed filed. [2] [6]

What changed was the tone of enforcement risk. The 2017 guidance tied enforcement to a lack of reasonable basis or good faith. [5] That narrowed the concern commenters had raised about imprecision. It did not remove the need to show a reasonable basis, which in our reading is a matter of records.

The privacy question also held. The exemption remains drafted around a jurisdiction’s laws governing data privacy, not around any named statute. [6] The test a registrant has to meet is the one set in 2015: reasonable efforts, relief sought, an opinion filed. [2] [6]

In our view, the durable lesson for a public financial company is in the rule’s structure. A statistic drawn from payroll became a filed figure with a disclosed method. The quality of the underlying employee data, and the record of every exclusion, became part of the quality of the filing.

Spotted an error? Tell us and we will check it and correct the article where needed.

  • pay ratio
  • SEC
  • Regulation S-K
  • payroll data
  • data privacy
  • Dodd-Frank