Journal of Accounting Research Submission Guide

The official page directs new manuscripts through Wiley Authors and asks authors to address the journal's current ethics, authorship, funding, conflict, prior-history, and research-transparency policies. It also distinguishes article types and contains specific rules for submission fees and resubmissions.

Do not copy a remembered fee or portal address into a lab checklist. Open the live JAR page immediately before submission and record the date, payer, manuscript category, and any applicable exception.

Suppose a study links a new disclosure rule to financing outcomes. A weak package says the paper is the first to use a large post-rule dataset. A stronger JAR package names the accounting problem, shows how the design separates the rule from contemporaneous changes, explains what the estimates reveal about disclosure behavior, and states where institutional or measurement limits remain.

The cover letter can summarize that chain. It cannot manufacture identification that the manuscript does not contain.

• The dataset is rare, but the accounting question is familiar and unchanged.
• The identification language is stronger than the design.
• Main and supplementary analyses do not share one claim hierarchy.
• Data or code restrictions are discovered too late to build a credible transparency plan.
• The cover letter describes importance while the abstract describes technique.

In our pre-submission review work on accounting manuscripts, the most expensive problem is usually not formatting. It is a break between the question the paper says it owns and the inference the design can support. We use the following checks because they produce an actionable revision decision rather than a generic recommendation to “strengthen the contribution.” These are Manusights observations, not private JAR acceptance data and not a claim about how an editor will decide one paper.

We audit each headline claim against its decisive table, assumption, and transparency boundary. We observe that this usually reveals whether the fix belongs in identification, contribution framing, or the research record rather than in surface-level prose.

The institutional event does too much work

A new rule, shock, database, disclosure regime, or enforcement action creates a compelling setting, but the paper never separates the accounting explanation from the event chronology. We ask the author to remove the institutional nouns from the abstract and state what accounting relationship becomes newly understood. If nothing distinctive remains, the paper needs a contribution repair rather than a different cover letter.

Identification and contribution are narrated in separate documents

The methods section explains why the estimate may be credible, while the introduction promises a larger mechanism that the design never observes. We map each contribution sentence to the exact table, test, or qualitative evidence that supports it. Unsupported sentences are narrowed; decisive evidence is moved closer to the claim.

Transparency is treated as a future production task

Proprietary data, field access, code restrictions, confidentiality, and institutional agreements can all be legitimate. The failure is waiting until a policy form appears to decide what can be audited. A credible plan identifies what can be shared publicly, what can be shared under controls, what cannot be shared, why, and which alternative evidence lets a reader evaluate the analysis.

A practical revision sequence

1. Write the accounting question without mentioning the dataset or method.
2. State the strongest inference the design can honestly support.
3. Name the closest competing explanation and where it is tested.
4. Connect every headline claim to one decisive exhibit.
5. Draft the data-and-code plan while the analysis can still be reorganized.
6. Rebuild the abstract and cover letter from that audited chain.

This sequence often shortens the manuscript because redundant robustness tests stop competing with the evidence that actually establishes the result.

JAR does not publish a guaranteed, case-specific timetable. Treat this as an event map, not a promise:

• Technical intake: the journal record, files, author data, fee status, and declarations are checked.
• Editorial triage: an editor tests accounting ownership, contribution, design authority, and package completeness.
• External review: reviewers evaluate the claim, methods, evidence, transparency, and boundary conditions when the paper is sent onward.
• Decision and revision: the editor communicates a decision and, when relevant, the evidence work required for a new version.

Before upload, confirm the cover letter, data availability statement, ethics approval or statement where applicable, conflicts of interest, author contributions, funding statement, supplementary material, ORCID records, and suggested reviewers when the live system requests them.

Check whether the evidence ledger survives a skeptical first read before freezing the upload record.

Preserve the submitted PDF, editable files, code and data snapshot, cover letter, declarations, fee confirmation, and the converted proof. Record the exact policy-review date. If a later revision changes the sample, model, exclusions, or headline claim, update the evidence ledger rather than silently replacing the original rationale.

Before pressing submit, run one adversarial read with no access to the authors' intentions. Give the reader only the abstract, contribution paragraphs, principal tables, and transparency statement. Ask them to mark every inferential jump, undefined construct, and claim whose supporting exhibit is unclear. Resolve the marks in the manuscript itself. Do not explain them away in a response note that the editor will never see. This compact test is especially useful for JAR because it evaluates whether the paper's contribution and research authority survive outside the full literature and methods narrative.

Where are Journal of Accounting Research manuscripts submitted?

The current JAR author guidelines direct new manuscripts to Wiley Authors. Verify the live author page immediately before upload because portal routes can change.

Does JAR charge a submission fee?

The current author guidelines include a submission-fee section with rules that depend on author and resubmission circumstances. Check the live fee table rather than relying on a saved amount.

Does JAR require data and code sharing?

JAR publishes a detailed data and code sharing policy. The appropriate package depends on data rights, privacy, contracts, and the research design, so resolve access constraints before submission.

What makes a paper a strong JAR fit?

A strong fit changes accounting knowledge through an important question, credible design, and evidence whose identification and limits are transparent. An accounting dataset alone does not establish the contribution.

Official sources accessed August 20, 2026.

1. Journal of Accounting Research author guidelines and policies, Wiley.
2. Journal of Accounting Research journal page, Wiley.
3. Wiley research integrity and publishing ethics guidance, Wiley.