Jfi Replication And Data Policy

---
name: jfi-replication-and-data-policy
description: Use to prepare the data-sharing materials a Journal of Financial Intermediation submission expects under Elsevier norms — a published Data Statement, deposited and linked datasets, and [dataset]-tagged references — without inventing a mandatory code archive the journal does not require. It prepares the package; it does not deposit for you.
---

# Replication & Data Policy (jfi-replication-and-data-policy)

## When to trigger

- Preparing data/code materials before submitting or at acceptance
- Writing the Data Statement or handling restricted/proprietary banking data

## What JFI actually requires (verified 2026-06-01; re-confirm on the official page)

JFI follows **Elsevier's research-data** framework. Research data here includes **software, code, models,
algorithms, protocols, and methods** — not just datasets. Authors are:

- **Encouraged to provide a Data Statement** on data availability, which is **published with the article**.
- Encouraged to **deposit data in a repository** and **link it via Editorial Manager**.
- Encouraged to **cite datasets** in the text and reference list using the **`[dataset]` tag**.

Crucially, JFI has **no journal-specific mandatory replication-code archive** — there is **no** equivalent
of the Journal of Applied Econometrics Data Archive or the American Economic Review replication mandate.
Do **not** tell authors a code/data deposit is compulsory; it is expected and enabled, not mandated.

## How to prepare

- **Empirical papers:** write a clear Data Statement (sources, access conditions, what is shared); deposit
  shareable data and code in a general-purpose repository (Mendeley Data, Zenodo, ICPSR/openICPSR) and link
  it. For **restricted bank/supervisory data** (Call Reports extracts under license, FR Y-14, DealScan),
  state the access route and share the code plus any constructed, non-proprietary derivatives.
- **Theory papers:** lighter — share the **code that generates numerical examples/figures** so they are
  reproducible (fixed seeds/parameters); a Data Statement can note that no empirical data underlie the
  results.

## Anti-patterns

- Asserting a mandatory JFI code archive that does not exist
- A Data Statement that hides restricted-data access conditions
- Citing datasets in prose without the `[dataset]` reference tag
- Depositing data but never linking it in Editorial Manager

## Output format

```
【Data Statement】drafted, access conditions stated? [Y/N]
【Deposit + link】repository chosen and linked in EM? [Y/N]
【[dataset] tags】data cited in references? [Y/N]
【Restricted data】access route + shareable code noted? [Y/N]
【Note】no mandatory JFI archive — sharing expected, not mandated
【Next skill】jfi-review-process
```