Skip to main content

Standards and accountability

Editorial Guidelines

These guidelines govern every page published on FinanceOpsClub. They cover sourcing, accuracy, freshness, attribution, independence from sponsors, and writing style.

The goal is simple: a finance team reading any page on this site should be able to trust the facts, see where they came from, and know whether money changed hands.

Who we write for

Controllers, CFOs, FP&A, AP/AR, payroll and accounting teams choosing software. Every page should move a reader from browsing to a short, defensible list of options. Learn more about who we are and why we publish on the about page.

Principles

Clarity beats hype. We organize pricing, features, integrations and trade-offs so a buyer can compare tools without reading marketing copy. If a product is hard to understand, we make it legible. You can see this in practice on any accounting software or AP automation category page.

Buyers deserve the trade-offs. We say what a product is good at, where it falls short, and when a different option is the better fit. Every shortlist names a runner-up and a poor fit.

Research should lead to action. The goal is a sharper set of options, faster. We cut anything that does not help a reader decide or test.

Sources and claims

Primary sources first. We rely on vendor documentation, pricing pages, help centers, release notes, public filings and regulators. Third-party sites may only be cited as "reported by" with attribution.

Every number needs a source. Prices, fees, limits, implementation times, customer counts, percentages and market figures must trace to a source checked on a stated date. If a figure cannot be verified, we rewrite the sentence without it. The full evaluation criteria are documented in how we review software.

Prices are shown with the date they were checked and a link to the vendor's pricing page. If a vendor does not publish prices, we say "quote-based" and never estimate.

We do not use puffery or rankings language we cannot prove: "leading", "#1", "best-in-class", "most popular", "industry standard", award claims, or analyst-quadrant claims unless the report is cited.

Vendor names follow the vendor. Rebrands and acquisitions are reflected on the page without changing URLs.

Disallowed as evidence: G2 or Capterra star ratings as ranking inputs, vendor claims that cannot be corroborated publicly, and anonymous summaries presented as proof.

Dates and freshness

We show "Updated" or "Reviewed" only when the content changed substantively, meaning new facts, a rewrite, or re-verified pricing. Copy edits and link fixes do not count.

"Prices checked on" dates must be the real check date. We never backdate or invent dates.

Sitemap lastmod values follow the same rule.

People and accountability

Every page is attributed to a real, named person or to the FinanceOpsClub Research Desk.

Author pages state real roles and real credentials. No invented personas, titles, credentials or proof points.

"Fact-checked by" appears only on pages a named fact-checker actually reviewed.

Money and independence

Buyers never pay. Research, comparisons, pricing pages and templates are free.

Revenue may come from sponsored placements, affiliate or referral links, listing fees and content partnerships. All are disclosed on the sponsored disclosure page.

Paid placements are labelled "Sponsored" wherever they appear.

Money cannot buy editorial verdicts, pros and cons, pricing facts, FAQs, or the content of comparisons. Vendors cannot edit or approve our copy.

Payment never changes editorial order. Rankings, "best of" picks and shortlists follow the same method whether or not a vendor pays. Sponsored products appear only in separate, clearly labelled "Sponsored" slots, and paid outbound links carry rel="sponsored". For the full ranking methodology, see how rankings work.

Writing style

Plain practitioner English, second person, short paragraphs.

We answer the question in the first sentence of each section and FAQ, because readers and AI answer engines both use it.

No internal notes appear on public pages, including keyword research, SERP notes, or research file paths.

Structure

One H1 per page, H2 sections, H3 only under an H2, and no skipped levels.

One FAQPage schema per page, listing exactly the visible questions.

Internal links use descriptive anchors to pages that exist. We never use "click here".

AI assistance

AI tools may help research and draft. A named person is responsible for every published page, every fact is checked against a primary source, and AI output is never published unedited.

Corrections

Readers and vendors can report errors via the contact page. Factual errors are fixed and the page's reviewed date updated. Material corrections, such as a wrong price or wrong capability, are noted on the page.