A separate web app that runs alongside your settlement system—no integration or migration required. Documents from any Pennsylvania county.
Pennsylvania closings involve document work that generic title software doesn’t handle: tax certifications from thousands of municipalities, commitments in every underwriter’s format, and state transfer tax rules of their own. Two of the three tasks below work now and are in use by beta agencies. The third is in development.
Title Commitments
Available nowUpload a title commitment and each Schedule B-I requirement is extracted into a clearing plan—grouped into action needed, to order, and cleared—with who to contact and a status your processor advances from open to requested, received, and cleared.
Municipal Tax Certs
Available nowCerts arrive in different layouts from Berkheimer, Keystone Collections, county treasurers, and local collectors. The first time a layout appears, a processor maps its fields once. Every cert in that layout afterward parses automatically: base amount due, penalty dates, paid-through status, per-diem.
Transfer Tax
In developmentPlanned: answer plain-English questions about a transfer to identify the applicable exemption and pre-fill the REV-183 Statement of Value. The demo below shows the intended flow with sample outcomes; the rules engine behind it is not built yet.
Sample data — no signup required
The Schedule B-I and tax cert demos show what the product does today. The REV-183 wizard previews a feature in development.
The parser isn’t tied to one underwriter’s layout. This sample is a Lancaster County commitment.
Parsing Schedule B-I requirements…
Schedule B-I Requirements Extracted (Lancaster County sample file)
Next steps we’re building — pick the one you’d use first
These take you to the beta form and tell us which to prioritize.
How PA File Velocity works under the hood
Format Library
Each layout is mapped once
When a tax cert layout—Berkheimer, Keystone Collections, a county treasurer, a local collector—is mapped by any agency, every matching document afterward parses automatically for everyone. The library starts with the layouts beta agencies map and grows with every file processed.
Privacy by Default
Sensitive numbers are never stored
Social Security numbers and full account numbers are redacted from extracted text before it is saved—only the last four digits of an account number are kept. Each agency sees only its own files; the format library shares layout hints, never document contents.
No Migration
A separate app beside your settlement system
You upload PDFs; results appear on screen for your processor to review and carry into SoftPro, Qualia, RamQuest, or whatever you use today. There is no integration to set up and nothing to migrate. Direct export to settlement systems is on the roadmap.
Each utility works on its own. Beta agencies get everything marked available now and help decide the order of what comes next.
What It Does
Turns Schedule B-I of a title commitment into a checklist: each requirement extracted, categorized (mortgage, tax certification, affidavit, judgment, and so on), and listed with the party, recorded date, and amount where the commitment states them.
How It Works
Upload the commitment PDF. Requirements are extracted and grouped into a clearing plan (action needed, to order, cleared, standard conditions). Each carries who to contact—the current mortgage assignee, the taxing authority—and a status your processor advances as the file moves. Boilerplate conditions stay folded out of the way. Planned next: drafting payoff request letters and seller affidavits from the extracted requirements.
What It Does
Reads returned tax certifications—from Berkheimer, Keystone Collections, county treasurers, school districts, and local collectors—and extracts the base amount due, penalty dates, paid-through status, and per-diem into one consistent structure, whatever layout they arrived in.
How It Works
Upload the cert. If its layout is already in the format library it parses immediately. If not, it goes to a mapping queue where a processor maps the fields once—after which that layout parses automatically for every agency. Planned next: proration computed to your closing date, and export to your settlement statement.
What It Will Do
Determine whether a transfer is taxable or exempt, identify the applicable PA Department of Revenue exemption, and pre-fill the REV-183 Statement of Value for review.
Where It Stands
The question flow exists as a preview above. The exemption rules, county Common Level Ratios, and form generation behind it are not built yet. Beta agencies will see it first.
We haven’t measured this across agencies yet—that is part of what the beta is for. This is the estimate we are testing, with its assumptions shown, for one processor’s commitment and tax cert workup.
Manual Process (assumed)
= 30 hours / month on transcription.
With PA File Velocity (target)
= 2 hours / month, spent reviewing instead of typing.
Estimate: About 28 Hours Per Processor, Per Month.
We’ll publish measured results from beta agencies as they come in.
Document automation software for Pennsylvania title and settlement agencies, currently in beta. You upload the PDFs from a closing file; the software classifies each document, extracts Schedule B-I requirements from title commitments into a reviewable checklist, and parses municipal tax certifications into structured amounts, dates, and per-diems.
Available now: document classification, Schedule B-I requirement extraction into a clearing plan with per-requirement status tracking, tax cert parsing through the shared format library, automatic redaction of SSNs and account numbers, and per-agency data isolation. In development: the REV-183 exemption wizard, drafting of payoff request letters and seller affidavits, proration computed to a closing date, OCR for scanned documents, and export to settlement systems.
Any digital PDF certification—Berkheimer, Keystone Collections, county treasurers, school districts, local collectors. The first time a layout appears, a processor maps its fields once; every cert in that layout afterward parses automatically, for every agency on the platform. The library starts with the layouts beta agencies map and grows from there. Scanned or faxed certs are held for manual mapping until OCR is added.
Neither. PA File Velocity is a separate web application that runs alongside whatever settlement production system you use. Results appear on screen for your processor to review and carry into your existing system. There is no direct integration or export today; export to settlement systems is on the roadmap.
Social Security numbers and full account numbers are automatically redacted from extracted text before anything is stored—only the last four digits of account numbers are kept. Each agency can see only its own uploaded files. The format library shares layout keywords and field hints between agencies, never document contents.
Documents from any Pennsylvania county can be uploaded and parsed; the parsers are not county-specific. The beta is onboarding agencies in Lancaster, Lebanon, York, Dauphin, Chester, and Bucks counties first. County-specific transfer tax rules and Common Level Ratios are not built yet and are part of the planned REV-183 wizard.
We’re onboarding a small group of Pennsylvania title agencies, starting with Lancaster, Lebanon, York, Dauphin, Chester, and Bucks counties. Beta agencies get everything that’s built today and direct input on what we build next.