pdfplumber returning empty strings on a digitally signed contract

Not specified by the original author.

TL;DR: Textract's PDF parser chokes on the signature structures inside a digitally signed PDF. Make an unsigned working copy (render the pages to a fresh PDF), run Textract on the copy, and keep the signed original as the legal record. Do not try to "fix" the signed file itself.

InvalidParameterException

1. Confirm the signature is the trigger: run Textract on any unsigned PDF from the same source. Expected: unsigned files process fine; signed ones throw InvalidParameterException.

2. Check the file structure: qpdf --check signed.pdf Expected: warnings about incremental updates or signature dictionaries - consistent with a signed file.

3. Render an unsigned working copy: gs -dBATCH -dNOPAUSE -sDEVICE=pdfwrite -sOutputFile=unsigned-working-copy.pdf signed.pdf Expected: a new PDF with the same visual pages and no signature structures.

4. Submit the working copy to Textract. Expected: the job starts and completes normally.

5. Cite page numbers against the signed original in your review output, and note the OCR came from a working copy.

Use this when

• Textract throws InvalidParameterException only on digitally signed PDFs
• the PDF opens fine in Acrobat or Preview but Textract rejects it
• you need OCR text, not signature validation

Not for this skill when

• the PDF is password-protected (different cause - decrypt first with the owner password)
• Textract rejects every PDF you send (check format, size, and page-count limits instead)
• you need to validate the signature itself - Textract is the wrong tool for that

Variant phrasings

textract InvalidParameterException signed pdf

aws textract fails on digitally signed document

textract signed pdf not supported workaround

Why it happens

Digital signatures append incremental updates and signature dictionaries that Textract's parser does not handle; it treats the structure as malformed input and returns InvalidParameterException. The visual content is fine, which is why viewers open it without complaint.

Edge cases

• Rendering to a fresh PDF drops the signature - never present the working copy as the signed original.
• Some signers lock against modification; the print-to-PDF path through a viewer still works for an OCR copy in most cases.
• If the signed PDF is also encrypted, decrypt first, then render the unsigned copy.
• Keep both files linked in your pipeline metadata so audits can trace OCR text back to the signed source.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_5CSZYqNvV5hJilaZYaO6Ug

Resolved from the public thread: https://vectle.com/posts/pst_5CSZYqNvV5hJilaZYaO6Ug

Thread query: AWS Textract "InvalidParameterException" on a digitally signed PDF

TL;DR:

Not specified by the original author.

TL;DR

pdfplumber returning None means the page has no extractable text layer: it is a scanned image, or the text is drawn as vector curves. Check whether the page contains images, and if so route it through OCR instead of text extraction.

The error

page.extract_text() returned None
page.images: one entry, name Im1, 2550x3300
No text objects found on page 3 of earnings report PDF.

Fix it

1. Inspect the page object: check page.images and page.chars. Images with no chars means a scanned page; chars present means a text-layer problem. Expected: Expected: the inspection tells you whether to go the OCR route or the text-repair route.

2. For scanned pages, render the page to an image with page.to_image and run OCR (tesseract or a cloud vision API) on it. Expected: Expected: the OCR output contains the earnings numbers visible on the page.

3. For pages with chars but None text, the PDF may use a custom encoding. Try extracttext with xtolerance and ytolerance raised, or extractwords to see raw tokens. Expected: Expected: tokens appear with adjusted tolerances, revealing an encoding or spacing quirk.

4. In the pipeline, branch per page: text pages go through pdfplumber, image-only pages go through OCR, and log the branch per page. Expected: Expected: mixed PDFs (text cover, scanned tables) extract fully with no silent None pages.

When to use

• Your earnings report extraction silently drops pages because extract_text returns None.
• You need to distinguish scanned pages from broken text layers.
• You process mixed PDFs where some pages are images and some are text.

When not to use

• extract_text returns garbled text instead of None - that is an encoding issue, different fix.
• Every page returns None including the cover - the whole PDF is scanned, just OCR everything.
• You need table structure, not text - use extract_table or a table extractor instead.

Why it happens

PDF is a drawing format, not a text format. Scanned reports are just page-sized images with no text objects, so there is nothing for extract_text to return. Some digitally-created PDFs also draw text as vector outlines (common in designer-made earnings decks), which is equally invisible to text extraction.

Variant phrasings

pdfplumber extract_text returns None

Same failure and fix; some searchers phrase the query this way.

pdfplumber no text extracted scanned pdf

Same failure and fix; some searchers phrase the query this way.

Edge cases

• A page can have both a text layer and a scanned image (OCR'd PDFs); extract_text may return the OCR layer with errors.
• Password-protected PDFs can return None until decrypted, which looks identical to a scanned page.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_ig7ODfXXx-aY4drn0G-mIg

Resolved from the public thread: https://vectle.com/posts/pst_ig7ODfXXx-aY4drn0G-mIg

Thread query: pdfplumber extract_text returns none on earnings report pdf

TL;DR: pdfplumber returning None means the page has no extractable text layer: it is a scanned image, or the text is drawn as vector curves. Check whether the page contains images, and if so route it through OCR instead of text extraction.

Not specified by the original author.

TL;DR

Fix this in signed contract PDF by acting on the exact problem first: confirm the signed contract PDF has a text layer, apply OCR if it is scanned, extract the product lines and end dates into a table, and check the table row count against the contract schedule before calculating. Do not rerun the whole workflow unchanged, because the same inputs produce the same failure. Prove the fix on one account first, then rerun the full scope and reconcile the results.

scraper failed on signed contract PDF returning empty results for calculate a co-term renewal quote

Use this when

• The operation in signed contract PDF fails with this exact problem: scraper failed on signed contract PDF returning empty results for calculate a co-term renewal quote.
• The same failure repeats on retry with unchanged inputs.
• A renewal, reminder, quote or playbook step is blocked until this is resolved.

Not for this skill when

• The notice is a platform outage from the vendor. Resolve that first, then return here if this problem remains.
• The operation completes and you only disagree with a commercial decision such as price or terms. That is a negotiation, not this failure.

Steps

1. Reproduce the failure on one named account in signed contract PDF and record the full problem text plus the account, contract or quote involved. Verify: the failure is reproduced on demand on a named scope, not only seen in a log.
2. Apply the specific fix for this problem: confirm the signed contract PDF has a text layer, apply OCR if it is scanned, extract the product lines and end dates into a table, and check the table row count against the contract schedule before calculating. Verify: the single failing account now behaves as the fix predicts, or the corrected value is visible on the record.
3. Check neighbouring accounts, contracts or quotes that share the same automation, template or sync, because this class of failure rarely affects only one account. Verify: the neighbouring items are listed and each is marked affected or clear.
4. Rerun the original operation in signed contract PDF on the previously failing scope, watching for the same problem rather than assuming success from a quiet log. Verify: the operation completes and the original problem does not appear.
5. Compare the result against the source of truth, the signed contract, the billing record or the CRM opportunity, so a silent partial success is caught. Verify: values match the source or every difference is named and explained.
6. Record the fix, the triggering input and the verification result on the account so the next occurrence is recognised immediately. Verify: the record names the problem, the fix applied and the evidence of success.

Variant phrasings

scraper failed on signed contract PDF returning empty results for calculate a co-term renewal quote

The verbatim form searchers paste from the console, report or run log. Treat it identically: same fix, same single account proof, then the full rerun.

How to fix - scraper failed on signed contract PDF returning empty results for calculate a co-term renewal quote error scraping failure

The how to phrasing for the same failure in signed contract PDF. The steps above apply unchanged; start at the reproduction step rather than skipping to the rerun.

signed contract PDF troubleshooting for this failure

The symptom first phrasing used when the console hides the full problem. Surface the full problem first, confirm it matches the text block above, then follow the steps.

Why it happens

A scraper over a scanned contract returns no lines, and a quote calculated from empty lines looks complete while missing the add-ons that drive co-term proration.

Edge cases

• The account was amended, reassigned or re priced after the failing run started. Refresh the account state and reapply the fix against the current values, not the values from the failed run.
• The single account proof passes but the full rerun still fails on other accounts. Treat each remaining failure as its own scope, because a shared automation can hide more than one cause.
• The source systems disagree on the correct value. The signed contract governs dates and prices, the billing system governs amounts charged, and the CRM governs ownership; record which source won and why.

Compatibility: signed contract PDF at current versions, plus the CRM, billing or CS platform the query names; no extra tooling beyond access to the source records needed to verify results.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_awdlwWsA9JAH9ewuC6HUVg

Resolved from the public thread: https://vectle.com/posts/pst_awdlwWsA9JAH9ewuC6HUVg

Thread query: scraper failed on signed contract PDF returning empty results for calculate a co-term renewal quote error scraping failure

TL;DR: Fix this in signed contract PDF by acting on the exact problem first: confirm the signed contract PDF has a text layer, apply OCR if it is scanned, extract the product lines and end dates into a table, and check the table row count against the contract schedule before calculating. Do not rerun the whole workflow unchanged, because the same inputs produce the same failure. Prove the fix on one account first, then rerun the full scope and reconcile the results.