Capital call notice document profile
Track a fund's requested investor contribution.
The Capital call notice profile helps you track a fund's requested investor contribution. It belongs to the investment family.
Recognize the source
Requests money from investor to fund; distinguish distribution to investor.
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 |
|---|---|---|---|
| Fund | text | Core | The source-stated fund 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. |
| Investor reference | text | Core | The source-stated investor reference 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. |
| Amount due | number | Core | The source-stated amount due 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. |
| 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. |
| Due date | date | Core | The source-stated 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. |
| Notice date | date | Optional | The source-stated notice 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. |
| Purpose | text | Optional | The source-stated purpose 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. |
| Remaining commitment | number | Optional | The source-stated remaining commitment 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 contribution components. 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.