Extract credit reports to structured JSON
Credit reports compile tradeline history, public records, inquiries, and scores from the major bureaus. Each bureau formats reports differently. Use Sensible to get structured credit data for lending decisions, risk assessment, and compliance documentation.
Why credit reports challenge automated extraction
Bureau-specific formats, dense tradeline tables, and coded status indicators make extraction complex.
Equifax, Experian, and TransUnion each use different layouts, status codes, and terminology. A 'paid' account at one bureau has a different code than at another. Sensible normalizes bureau-specific conventions into your target schema.
A single report may list 30+ tradelines across multiple pages, each with account details, payment history, and status codes. Multi-page tables are stitched without duplication and returned as structured arrays.
Tri-merge reports present all three bureaus side by side. Each bureau's section gets extracted separately, preserving bureau-level tradeline detail for your credit decisioning logic.
Fields we extract
Standard fields cover lending decisioning. Customize the schema for your credit analysis pipeline.
Credit score, score model, score range, number of tradelines, total balance, credit utilization, derogatory marks count
Creditor name, account number (partial), account type, date opened, credit limit, current balance, payment status, payment history (24-month)
Hard inquiries (date, creditor), soft inquiries, bankruptcies, liens, judgments, collections, public records
Combined report from all three bureaus, common in mortgage lending.
TransUnion report with account details, disputes, and credit utilization.
Experian consumer credit report with tradelines, inquiries, and score.
Equifax format including payment history, balances, and public records.
Supported credit report formats
Sensible processes reports from all three major bureaus plus tri-merge formats. Hybrid extraction handles the visual differences between bureaus while SenseML enforces consistent output for your credit analysis pipeline.
Equifax, Experian, TransUnion, tri-merge (all three combined)
Consumer credit reports, mortgage credit reports, auto lending reports, business credit reports



Common Questions
Answers about bureau support, tradeline parsing, and tri-merge handling.
Yes. Sensible captures hard and soft inquiries with dates and creditor names, plus public records such as bankruptcies, liens, and judgments when present on the report.
Yes. Sensible extracts the credit score, score model (e.g. FICO 8, VantageScore 3.0), score range, and any risk factors listed on the report.
Sensible extracts creditor name, account number (partial), account type, balance, credit limit, payment status, date opened, and payment history for each tradeline on the report.
Sensible processes credit reports from Equifax, Experian, and TransUnion. Each bureau formats reports differently, and Sensible's configuration handles these variations.
Yes. Sensible sends extraction results to your webhook endpoint when processing completes. You can also poll the API for status.
Yes. Sensible flags extractions with low confidence for human review. You can configure review thresholds and workflows.
Sensible is SOC 2 Type II certified and HIPAA compliant. Data is encrypted in transit and at rest.
Document data is stored indefinitely by default. Custom retention policies are available and can be configured for same-day deletion if needed.
Yes. Sensible offers a 14-day free trial on the Growth plan. No credit card required to start.
Sensible uses per-document pricing for predictable costs. No token-based billing or usage surprises. Volume discounts are available for higher throughput.
Sensible provides REST APIs and SDKs for Python and Node.js. Most integrations take a few hours. Webhooks, Zapier, and direct API calls are all supported.
Sensible processes PDFs (native or scanned), Microsoft Word (DOC, DOCX), spreadsheets (XLSX, XLS, CSV), single-page images (JPEG, PNG), multi-page images (TIFF), and email bodies with attachments.
Accuracy depends on document quality and configuration. Most production deployments achieve 95%+ accuracy with proper validation rules and confidence signals.
Processing speed depends on document size, page count, OCR requirements, and which extraction methods are used. Simple single-page documents process in seconds. Larger or more complex documents that use LLM-based extraction take longer.
