Debit note document profile
Track additional debit adjustments.
The Debit note profile helps you track additional debit adjustments. It belongs to the commerce family.
Recognize the source
Debit adjustments are direction-sensitive; record issuer and stated meaning rather than reversing amounts automatically.
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 |
|---|---|---|---|
| Debit note number | text | Core | The source-stated debit note number 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. |
| 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. |
| Issue date | date | Core | The source-stated issue 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. |
| Debit amount | number | Core | The source-stated debit amount 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. |
| Original invoice reference | text | Optional | The source-stated original invoice 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. |
| Reason | text | Optional | The source-stated reason 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. |
| Recipient | text | Optional | The source-stated recipient 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. |
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 adjusted lines. 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.