Internet Appendix (rfs-internet-appendix)

When to trigger

• The main paper is bloated with secondary tables, proofs, or derivations
• Referees will want 15–25 additional checks that cannot fit in the main text
• You have proofs, data-construction detail, or extra robustness to house
• You are unsure what RFS expects in the supplementary file vs. the article

What the Internet Appendix is at RFS

RFS hosts an Internet Appendix (IA) alongside the published article. It is the standard home for material that supports the paper but would crowd the main text. Treat it as part of the submission, refereed alongside the manuscript — not a dumping ground.

Two RFS facts shape what goes here:

• Code-release is mandatory. RFS requires authors to publicly release all code underlying a published paper as a condition of publication (an exception must be requested in the cover letter to the editor). Plan the replication package from the start — do not treat it as a post-acceptance chore. This is a harder rule than the softer "available on request" norms at some journals.
• Registered Reports change the IA's role. RFS was the first finance/economics journal to run Registered Reports (pre-results review). For a Registered Report, the Stage 1 protocol — design, sample, pre-specified tests — is the locked commitment; the IA then documents adherence and any deviations rather than housing a post-hoc specification search.