Credit card statement document profile
Track card balances and due payments.
The Credit card statement profile helps you track card balances and due payments. It belongs to the personal finance family.
Recognize the source
Revolving card bill with due payment, distinct from bank deposit account statement.
Review the document itself before applying the profile. Similar labels, dates, parties, or amounts can appear in another document type with a different meaning. Use the source context to distinguish them.
Expected fields
Core fields form the profile’s main structure. Recommended and optional fields add supported detail. None of these designations permits guessing a value that is absent or ambiguous.
| Field | Type | Inclusion | Meaning and extraction rule |
|---|---|---|---|
| Issuer | text | Core | The source-stated issuer for this document and its identified subject. Copy exact source spans for this one scalar field, preserving their order, ownership and qualifications. Ordered spans may continue across segments. Do not synthesize a summary or combine unrelated fields or repeated records; return unresolved when the scalar meaning is ambiguous. |
| Source masked account reference | text | Core | Copy an account reference only if already masked in the source (for example, a suffix with asterisks). Otherwise leave null; do not output the full account identifier or create a redacted transformation. |
| Statement period | text | Core | The source-stated statement period for this document and its identified subject. Copy exact source spans for this one scalar field, preserving their order, ownership and qualifications. Ordered spans may continue across segments. Do not synthesize a summary or combine unrelated fields or repeated records; return unresolved when the scalar meaning is ambiguous. |
| Statement balance | number | Core | The explicitly stated new or statement balance for this statement period, in the stated currency. Do not substitute the minimum payment, past-due amount or current live balance; do not infer how much must be paid. |
| Currency | text | Core | The currency explicitly associated with the selected monetary fields. Preserve source representation; do not infer a currency from an ambiguous symbol or company location. Conflicting currencies require separate fields or unresolved values. |
| Minimum payment | number | Optional | The minimum payment explicitly stated for this statement period. Do not substitute the full statement balance or calculate a minimum from account terms. |
| Payment due date | date | Optional | The source-stated payment due date for this document and its identified subject. Normalize an explicitly stated date only when unambiguous. Do not infer missing day, month, year or timezone. |
| Stated interest charge | number | Optional | The source-stated interest charge for this document and its identified subject. Use an explicitly stated value with safe numeric normalization only. Preserve its currency, unit, scale and basis in evidence metadata; do not calculate, estimate or combine values. |
Missing, ambiguous, and repeated values
Missing or ambiguous fields remain null with a reason. Null is not zero, false, an empty statement, or proof that a document-wide fact does not exist. Inspect unresolved states and their supporting passages before accepting the table. This document type can contain repeated records such as card transactions. The profile uses one row per document; do not compress repeated records into a scalar field or confuse a line value with a document-level total. Additional supported fields can be considered when the extraction experience allows them. Review their definitions and types explicitly; changing a field’s meaning requires a new extraction preview.
Review the result
Select evidence-backed cells and read the retained source. Text should preserve the relevant source spans and qualifications. Numbers and dates must be stated unambiguously and normalized safely; do not calculate unstated values or infer missing units, currency, scale, date parts, or time zones.
Verify the result against the captured document before acceptance. Source support does not independently establish perfect OCR, exhaustive field discovery, or correct domain interpretation.
See profile modes, table review, and captured evidence.