logologo
  • How it works
  • Why It Matters
  • Statistics
  • Pricing
  • FAQ
  • API
logologo
  • How it works
  • Why It Matters
  • Statistics
  • Pricing
  • FAQ
  • API
HTPBE?

Structural PDF tamper detection API. Catches edits your KYC stack misses.

Product

  • How It Works
  • Use Cases
  • Metadata Viewer
  • Pricing

Developers

  • API Reference
  • GitHub/docs
  • Changelogv2.48.3

Resources

  • About
  • Blog
  • Comparisons
  • Legal & Imprint

© 2024–2026 TMI Iurii Rogulia · VAT ID: FI29845875 · Made in Finland

Status

Algorithm v2.48.3

Tool profile

Microsoft Reporting Services

Microsoft Reporting Services reads as a institutional generator — its modification rate in our corpus does not sit meaningfully above the baseline. The name alone is never the verdict; each file is judged on its own structure.

Back to all statistics
Forensic verdict

Legitimate origin

Based on this tool’s share of the HTPBE? corpus.

Modification rate
45%-4pp below baseline
Corpus baseline: 49%
Corpus share
3.5%
Share of all analyzed appearances
Modification rate
45%
-4pp below baseline
Role split
63%C/37%P
Creator vs Producer share of appearances

Corpus profile

How Microsoft Reporting Services shows up in HTPBE? corpus

Microsoft SQL Server Reporting Services (SSRS) is an enterprise reporting platform that emits PDFs server-side from parameterized report templates — common in healthcare, government, and large back-office workflows.

SSRS output is rendered on a server from report templates, typically in healthcare, government and back-office settings. The name is a starting point; the verdict depends on what the rest of the file shows.

The signal
SSRS output is rendered on a server from report templates, typically in healthcare, government and back-office settings.

Reading guide

How to read this page

Every PDF stores two software labels: the Creator, which names the application that first produced the document, and the Producer, which names the software that last wrote the file out. This page counts the files HTPBE? has analysed where Microsoft Reporting Services fills one of those labels, and shows how often those files carry modification markers, which PDF versions they use and which other tools sit next to them.

A tool name tells you where a file passed through, not whether anyone changed its content. A Creator and Producer that agree usually point to a single pass; a Producer that differs from the Creator means the file was written out again by another program, which has many ordinary explanations such as compression, merging or a print-to-PDF step.

Caveats

  • The figures cover 962 files. Larger than a handful, but still a sample of what was submitted, not of all PDFs in the world.
  • The statistics describe files HTPBE? analysed. They are not a judgement of the quality or trustworthiness of Microsoft Reporting Services.
  • Submitted files lean towards documents that someone wanted checked, so rates here can sit higher than in everyday document flows.
  • Metadata can be rewritten by anyone, so a producer name on its own is never treated as proof either way.
Read a PDF’s metadata for freeAll tool statisticsCreator vs Producer explainedPDF metadata fields referenceCheck PDFs through the API

Role in the workflow

How Microsoft Reporting Services shows up in metadata

Every PDF carries a Creator (the application that produced the original document) and a Producer (the engine that wrote the PDF). The same tool can appear in either slot, with very different modification profiles.

CAs Creator · 63%
As Producer · 37%P
CAs Creator
  • Share of appearances
    63%
  • Modification rate
    57%
  • Avg file size
    380 KB
PAs Producer
  • Share of appearances
    37%
  • Modification rate
    26%
  • Avg file size
    375 KB

How to read this

The Creator slot typically reflects where a document started life. The Producer slot reflects whatever wrote the final file, which is not always the same software.

A higher modification rate as Producer than as Creator usually means the tool is acting as a re-saver on documents that originated elsewhere. A higher rate as Creator points to fragile workflows around the original authoring app.

Name fingerprints

Also goes by

Different version strings and spellings observed for Microsoft Reporting Services in the wild. All are merged into the same canonical profile.

Microsoft Reporting Services 2019.11.0.059.4%
Microsoft Reporting Services PDF Rendering Extension 2019.11.0.033.5%
Microsoft Reporting Services 2022.1.0.01.0%
Microsoft Reporting Services 14.0.0.00.9%
Microsoft Reporting Services PDF Rendering Extension 2022.1.0.00.8%
Microsoft Reporting Services 11.0.0.00.6%
Microsoft Reporting Services PDF Rendering Extension 11.0.0.00.6%
Microsoft Reporting Services PDF Rendering Extension 14.0.0.0; modified using iTextSharp™ 5.5.13.4 ©2000-2024 iText Group NV (AGPL-version)0.5%
Microsoft Reporting Services 15.0.0.00.4%
Microsoft Reporting Services PDF Rendering Extension 15.0.0.00.4%
Microsoft Reporting Services PDF Rendering Extension 14.0.0.00.4%
Microsoft Reporting Services 12.0.0.00.3%
Microsoft Reporting Services PDF Rendering Extension 12.0.0.00.3%
Microsoft Reporting Services 10.0.0.00.2%
Microsoft Reporting Services PDF Rendering Extension 10.0.0.00.2%
Microsoft Reporting Services 13.0.0.00.1%
Microsoft Reporting Services PDF Rendering Extension 13.0.0.00.1%
Microsoft Reporting Services PDF Rendering Extension 2019.11.0.0; modified using iTextSharp™ 5.5.13.3 ©2000-2022 iText Group NV (AGPL-version)0.1%

Why variants matter

The same tool publishes itself under 18 different metadata strings – version bumps, locale tags, build IDs. We canonicalize them so the corpus reflects one identity, not noise.

Most common
Microsoft Reporting Services 2019.11.0.0
59.4% of appearances
Variant spread
18 distinct strings
Long-tail share: 40.6%
Observed range
30.05.2019 → 17.09.2026

Distributions

What ships alongside Microsoft Reporting Services

The PDF versions Microsoft Reporting Services writes when acting as Producer, and the other tools that appear in the same documents.

PDF versions written

Most output is PDF 1.7 (93% of files where Microsoft Reporting Services is the Producer).

PDF 1.793.2%
PDF 1.36.2%
PDF 1.50.6%

Common Producers when Microsoft Reporting Services is the Creator

pdf-lib writes 0% of these files – read this row as ‘what these documents most often pass through on the way out’.

pdf-lib0.5%
iLovePDF0.2%

Common Creators when Microsoft Reporting Services is the Producer

Microsoft Reporting Services sits upstream in 99% of cases — read this row as “what kinds of documents end up routed through Microsoft Reporting Services.”

Microsoft Reporting Services99.2%
LT Check Printing Report0.6%
GOAT Logistics0.3%

Related profiles

Tools you’ll see next to Microsoft Reporting Services

Other tools that frequently share metadata with Microsoft Reporting Services in the same documents. Each card links to its own forensic profile.

P0% co-occurrence
pdf-lib
Corpus share0.47%
Mod rate91%
P0% co-occurrence
iLovePDF
Corpus share2.7%
Mod rate91%
C0% co-occurrence
LT Check Printing Report
Corpus share0.01%
Mod rate0%
C0% co-occurrence
GOAT Logistics
Corpus share0.00%
Mod rate100%

Long tail

Notable observations

Smaller cuts of the Microsoft Reporting Services corpus – useful context, but treat each row as a single data point rather than a strong signal.

Avg pages per document
2.0
Oldest observed
30.05.2019 — over 7 years ago

FAQ

Microsoft Reporting Services in PDF metadata: common questions

What is Microsoft Reporting Services?

Microsoft SQL Server Reporting Services (SSRS) is an enterprise reporting platform that emits PDFs server-side from parameterized report templates — common in healthcare, government, and large back-office workflows.

Why does Microsoft Reporting Services appear in the metadata of a PDF?

A PDF can record the software that created it (Creator) and the software that last wrote the file out (Producer). When Microsoft Reporting Services generated the file, or re-saved it, it can leave its name in one of those fields. The field is filled in by software, not checked by anyone, so it is a hint about the file’s history rather than a guarantee.

Does Microsoft Reporting Services in the metadata mean the PDF was edited?

No. A producer name alone proves nothing about whether a document was changed. Many Microsoft Reporting Services files are original output, and a file that was edited can name any tool at all. What matters is the whole picture: how the file is built, how its dates and structure line up, and whether the Creator and Producer fit together.

How should I read the Microsoft Reporting Services statistics?

The figures describe the 962 files in the HTPBE? corpus that list Microsoft Reporting Services as Creator or Producer. The modification rate is the share of those files that carry modification markers. It is a base rate for this particular set of files, not a property of Microsoft Reporting Services and not a prediction for any single document.

Can I compare Microsoft Reporting Services with other tools using these numbers?

Only loosely. The corpus consists of PDFs people chose to submit for checking, which skews towards documents someone had a reason to doubt. A tool popular for legitimate bulk output can still show a high rate here, and a rarely seen tool can show an extreme rate from a handful of files. These pages are not a quality ranking of the tools themselves.

How do I check a PDF that lists Microsoft Reporting Services?

Upload it to HTPBE? for a modification check, or open it in the free PDF Metadata Viewer to see the Creator, Producer and dates stored in the file. The same check is available through the HTPBE? API.

Secure your workflow

Create your account – check PDFs on the web or with an API key, both ready on signup.
No sales call. Cancel any time.

Start Free – Close the Structural Fraud GapSee Pricing
Read API Docs →