Format your manuscript to the Proceedings of the London Mathematical Society requirements — abstract, numbered references, and required declarations — and submit through Research Exchange (Wiley's submission system) without a formatting rejection.
4.4
Authored by Sumalatha Gangadhar | Published on 19 August, 2026
A strong study can still bounce at Proceedings of the London Mathematical Society before review if the manuscript ignores the journal’s formatting requirements. This template is built around Proc. LMS’s actual requirements — its abstract rules, numbered references, and the required declarations — so your submission clears screening on the first pass. Everything below tracks the Proc. LMS author guidelines; check it directly if anything looks out of date by the time you submit.
It’s a manuscript shell set up to Proc. LMS’s specifications for pure and applied mathematics. Proceedings of the London Mathematical Society is published by Wiley on behalf of the London Mathematical Society. The shell covers the title page, the abstract, a body in Introduction, Methods, Results, and Discussion (IMRaD) order, and a reference list in numbered style.
Start with the title page (authors, affiliations, and ORCID iDs). The abstract is an abstract of about 200–250 words (structured or unstructured per the journal's guidelines). Proc. LMS also expects a manuscript prepared in LaTeX. The body follows Introduction, Methods, Results, and Discussion (IMRaD), and the reference list uses numbered. Close with the declarations block: ethics approval, conflict of interest, funding, and data availability.
The details that trip up most first submissions: no ORCID registered for the corresponding author, reference formatting inconsistent with the guidelines, and a missing data availability statement. Beyond that, match your article type’s specific limits rather than assuming the defaults apply, keep numbered formatting consistent from the first draft, and submit only through Research Exchange (Wiley's submission system) — email submissions aren’t processed.
The shell mirrors what Proc. LMS’s editorial staff check first: abstract format and length, numbered reference formatting, and a complete declarations block. For the journal’s full aims and scope, see the Proc. LMS journal home page. Proc. LMS offers an open-access option; check the current article-processing charge and any waiver before you commit. Manuscripts go in through Research Exchange (Wiley's submission system), which also tracks your paper through peer review.
| Element | Proc. LMS requirement |
|---|---|
| Abstract | an abstract of about 200–250 words (structured or unstructured per the journal's guidelines) |
| Main text | Introduction, Methods, Results, and Discussion (IMRaD) |
| Declarations | Ethics approval, conflict of interest, funding, and data availability |
| Figures / tables | Captioned, cited in order; check format and resolution rules in the guide |
| Supplemental | Large datasets, extra tables, code — uploaded separately and cited in text |
| Submission | Research Exchange (Wiley's submission system) |
Read the Proc. LMS author guidelines once before drafting and once before upload. Draft the abstract after your results are stable so it matches the paper. Set numbered as your reference style before adding a single citation — retrofitting it later is where errors creep in. Prepare a manuscript prepared in LaTeX early rather than leaving it to the end.
Skim two or three recent Proc. LMS papers to calibrate depth, structure, and figure style. State your contribution in the first two paragraphs, not on page ten. Write a data-availability statement that names a real repository rather than a placeholder, and disclose any preprint or conference version with identifiers in your cover letter. Confirm current open-access pricing and any institutional agreement before committing to a fee.
Do one focused pass against the Proc. LMS author guidelines: scope fit, abstract format, length, numbered references, required declarations, and figure quality. Re-check the items that most often cause a bounce here — no ORCID registered for the corresponding author, reference formatting inconsistent with the guidelines, and a missing data availability statement. Then submit through Research Exchange (Wiley's submission system).