polis-recognizer
A deterministic field extractor for Russian KASKO insurance policy PDFs.
Pulls 7 structured fields without LLMs — text-layer extraction
(pypdf) plus optional table-aware reading (pdfplumber), with
Tesseract OCR fallback for scanned policies.
Status: pre-stable (0.x). API may change before 1.0.
What it extracts
| Field | Type | Example |
|---|---|---|
policy_number |
str |
"AC524160804" |
policy_period |
{start, end} (date) |
{"start": date(2025, 2, 27), "end": date(2026, 2, 26)} |
franchise |
{value, currency, absent} |
{"value": 30000, "currency": "RUB", "absent": False} |
limit |
{value, currency} |
{"value": 5525000, "currency": "RUB"} |
premium |
{value, currency} |
{"value": 220000, "currency": "RUB"} |
sum_type |
"aggregate" / "non_aggregate" |
"non_aggregate" |
repair_mode |
"dealer" / "service" / "cash" |
"dealer" |
policyholder |
{type, name, inn, ogrn, kpp, passport, birth_date} |
{"type": "legal_entity", "name": "ООО \"Альфа\"", "inn": "7707083893", "ogrn": "1027700132195", "kpp": "770701001", "passport": None, "birth_date": None} |
policyholder_contacts |
{phones, emails, address, postal_code} |
{"phones": ["+74951234567"], "emails": ["contact@alpha.ru"], "address": "101000, г. Москва, ул. Ленина, д. 1", "postal_code": "101000"} |
Quick start
from polis_recognizer import PolicyExtractor
extractor = PolicyExtractor()
result = extractor.extract_from_pdf("/path/to/polis.pdf")
print(result.policy_number)
# → "AC524160804"
print(result.policy_period)
# → {"start": date(2025, 2, 27), "end": date(2026, 2, 26)}
print(result.franchise)
# → {"value": 30000.0, "currency": "RUB", "absent": False}
Input methods:
extractor.extract_from_pdf("polis.pdf")
extractor.extract_from_bytes(pdf_bytes, filename="polis.pdf")
extractor.extract_from_text("сырой текст полиса") # bypass PDF/OCR
Installation
pip install polis-recognizer
System dependencies
polis-recognizer shells out to Tesseract for OCR and to poppler
for PDF→image conversion. These are NOT pip-installable; install them
through your OS package manager.
Linux (Debian/Ubuntu):
sudo apt-get install -y tesseract-ocr tesseract-ocr-rus poppler-utils libgl1
macOS (Homebrew):
brew install tesseract tesseract-lang poppler
Windows: best-effort. Install Tesseract for Windows and add it to PATH; install Poppler binaries for PDF support. We don't test on Windows in CI.
The Russian language pack (tesseract-ocr-rus / tesseract-lang) is
required — without it, OCR silently falls back to English and Cyrillic
documents come back as garbage. The library logs a CRITICAL warning at
import time if the pack is missing.
How it works
The extractor runs three stages:
- PDF ingestion —
PdfExtractionRoutertries text-layer extraction first (pypdf for text, pdfplumber for tables on the same page). If the result is too short (fewer than 100 chars by default) or detected as glued/EDI-envelope text, it falls back to Tesseract OCR. - Text normalization — Unicode NFKC, NBSP stripping, hyphenated line-break healing, runs of multiple spaces collapsed.
- Field extraction — 7 deterministic parsers (one per field) run
regex + table-aware patterns and emit
Candidates with confidence scores. A ranker picks the winner per field.
There's no LLM and no cloud dependency. Everything runs locally.
PDF extractor choice
The default is "hybrid" — pypdf text plus pdfplumber tables in one
pass. Two alternatives:
| Option | When to use |
|---|---|
"hybrid" (default) |
Best for KASKO. pypdf preserves date/period text quality, pdfplumber's tables fix the column layout for limit/franchise/premium. |
"pypdf" |
Faster, no tables. Use when document quality is uniform and tables aren't needed. |
"pdfplumber" |
Fully layout-aware. Slower; on KASKO it slightly regresses date parsing. Use for table-heavy non-KASKO formats. |
extractor = PolicyExtractor(pdf_extractor="pypdf")
Supported insurer formats
The parser ships with patterns for these Russian insurers' KASKO templates: АльфаСтрахование (XLS form-mask), СОГАЗ-АВТО, Чулпан, Ингосстрах, ВСК, АбсолютСтрахование, Росгосстрах, СОГАЗ Diadoc-wrapped PDFs. Recall on real-world KASKO corpora is ~50-65% per field; pulling above that requires per-format parser additions.
If you have a policy from an insurer not on this list — see CONTRIBUTING.md for how to add a parser pattern.
Configuration
Constructor arguments:
extractor = PolicyExtractor(
ocr_language="rus+eng", # Tesseract language string
ocr_timeout_seconds=300,
ocr_page_limit=50,
ocr_max_text_size=500_000,
pdf_extractor="hybrid", # "pypdf" | "pdfplumber" | "hybrid"
image_preprocessing="fallback", # "never" | "fallback" | "always"
psm=None, # Tesseract --psm (None = auto)
oem=None, # Tesseract --oem (None = auto)
max_image_size_bytes=None, # reject images larger than this
extract_pii=False, # opt-in for passport + birth date
)
extract_pii
PolicyExtractor does not extract passport or birth date by default
— with extract_pii=False, policyholder.passport and
policyholder.birth_date are always None even when the source
text contains them. This keeps the default output safe to log /
cache / persist without extra redaction work. Set extract_pii=True
to opt in. Operational contact data (phone, email, address) is not
gated — those handle data the caller has a legal basis to process
under 152-ФЗ ст. 6 ч. 1 п. 5 (исполнение договора).
License
MIT © Grigorii Grachev. Free for any use, including commercial.
Roadmap
Active (0.4.x): finish out the policyholder + contacts feature — five known failure classes remaining after the 0.3.4 corpus pass (ВСК «Классика» 2-col layout, lizingodatel ИНН substitution, АльянсЛизинг "См. Особые условия", ВСК signature-only anchor, pdfplumber column flattening). Design, risks, and per-limitation fix approach: docs/roadmap-known-limitations.md.
Next minor (0.5.0): corpus eval harness + schema additions
(policyholder.insurer_template, per-field diagnostics).
Further out: ОСАГО support — the underlying field model already accommodates it; only parser patterns need adding.
Past releases — see CHANGELOG.md. The design and implementation plan for the policyholder + contacts work shipped in 0.3.0 is preserved in docs/roadmap-policyholder.md for reference.
Release files for polis-recognizer 0.3.5
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| polis_recognizer-0.3.5.tar.gz | 125.3 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| polis_recognizer-0.3.5-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 244.1 kB
Release files / polis_recognizer-0.3.5.tar.gz
| Download URL | polis_recognizer-0.3.5.tar.gz |
|---|---|
| Size | 125.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
754e10c66ff0cdc85fa7adb3128151041a8841a0fc2155fd468f9752c01f1a00
|
|
BLAKE2b-256 checksum How to use checksums |
6b188af28057d83135b167bf5cb96c8beeaea42e37deb4056e9fa1ce62a5fd2b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 25, 2026.
Transparency logRelease files / polis_recognizer-0.3.5-py3-none-any.whl
| Download URL | polis_recognizer-0.3.5-py3-none-any.whl |
|---|---|
| Size | 118.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
eac7a8684a6dc0a5c3245d1f3794acc4366e5315e2f3731f87e97955d662f6f1
|
|
BLAKE2b-256 checksum How to use checksums |
8b7721e0c4f7158c4cfa7916262c62c19cad19844e0ec2bd963c797929ae7946
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 25, 2026.
Transparency log