VA Form 21P-534EZ ยท v2.4
Survivor benefits application
Survivors upload the documents they already have. The reader suggests answers and the survivor confirms each one.
1 field has no downstream target
Those answers are captured on the intake record but are not sent anywhere yet. A person has to choose the mapping before they can flow downstream.
8 fields in v2.4
Each field records where it came from on the paper form, so a reviewer can always trace a digital answer back to the box it replaced.
| Type | Required | On the paper form | Maps to | |
|---|---|---|---|---|
| claimant_full_nameYour full name | Text | Yes | Marriage certificate, spouse name | claimant.fullName |
| claimant_dobYour date of birth | Date | Yes | Marriage certificate, spouse date of birth | claimant.dateOfBirth |
| veteran_full_nameVeteran's full name | Text | Yes | Death certificate, decedent name | veteran.fullName |
| date_of_deathDate of death | Date | Yes | Death certificate, date of death | veteran.dateOfDeath |
| cause_of_deathCause of death | Text | No | Death certificate, part I, handwritten | veteran.causeOfDeath |
| marriage_dateDate of marriage | Date | Yes | Marriage certificate, date solemnized | relationship.marriedOn |
| monthly_incomeMonthly household income | Currency | Yes | Not on the uploaded documents | income.monthlyTotal |
| burial_expenses_paidBurial expenses you paid | Currency | No | Not on the uploaded documents | Unmapped |
Field schema for VA Form 21P-534EZ
- Field
- claimant_full_nameYour full name
- Type
- Text
- Required
- Yes
- On the paper form
- Marriage certificate, spouse name
- Maps to
- claimant.fullName
- Field
- claimant_dobYour date of birth
- Type
- Date
- Required
- Yes
- On the paper form
- Marriage certificate, spouse date of birth
- Maps to
- claimant.dateOfBirth
- Field
- veteran_full_nameVeteran's full name
- Type
- Text
- Required
- Yes
- On the paper form
- Death certificate, decedent name
- Maps to
- veteran.fullName
- Field
- date_of_deathDate of death
- Type
- Date
- Required
- Yes
- On the paper form
- Death certificate, date of death
- Maps to
- veteran.dateOfDeath
- Field
- cause_of_deathCause of death
- Type
- Text
- Required
- No
- On the paper form
- Death certificate, part I, handwritten
- Maps to
- veteran.causeOfDeath
- Field
- marriage_dateDate of marriage
- Type
- Date
- Required
- Yes
- On the paper form
- Marriage certificate, date solemnized
- Maps to
- relationship.marriedOn
- Field
- monthly_incomeMonthly household income
- Type
- Currency
- Required
- Yes
- On the paper form
- Not on the uploaded documents
- Maps to
- income.monthlyTotal
- Field
- burial_expenses_paidBurial expenses you paid
- Type
- Currency
- Required
- No
- On the paper form
- Not on the uploaded documents
- Maps to
- Unmapped
Validation rules
A rule can block a submission, warn the person filling it out, or flag the record for a person to review. No rule approves, denies, or prices anything.
| Field | Rule | When it fires | Effect |
|---|---|---|---|
| date_of_death | Must be on or after the date of marriage | When the survivor confirms extracted answers | Blocks submission |
| cause_of_death | Low-confidence reads must be confirmed by a person before submission | On the confirm step | Blocks submission |
| monthly_income | Never extracted from a document - the survivor always enters it | Always | Warns the filer |
Validation rules for VA Form 21P-534EZ
- Field
- date_of_death
- Rule
- Must be on or after the date of marriage
- When it fires
- When the survivor confirms extracted answers
- Effect
- Blocks submission
- Field
- cause_of_death
- Rule
- Low-confidence reads must be confirmed by a person before submission
- When it fires
- On the confirm step
- Effect
- Blocks submission
- Field
- monthly_income
- Rule
- Never extracted from a document - the survivor always enters it
- When it fires
- Always
- Effect
- Warns the filer
Downstream mapping
Where each answer lands: VBMS - Survivor claim package.
Mapped (7)
- claimant_full_nameclaimant.fullName
- claimant_dobclaimant.dateOfBirth
- veteran_full_nameveteran.fullName
- date_of_deathveteran.dateOfDeath
- cause_of_deathveteran.causeOfDeath
- marriage_daterelationship.marriedOn
- monthly_incomeincome.monthlyTotal
Not mapped (1)
- burial_expenses_paid
Captured on the intake record. Waiting for someone to choose a downstream target.
Test submissions
Synthetic payloads run against the current schema. A failed test means a rule caught something, which is usually the point.
Run a test submission
Sends a synthetic payload through validation and the downstream mapping. Nothing reaches a real system of record.
| Test case | Run on | Result | What happened |
|---|---|---|---|
| Three documents, clean scans | June 30, 2026 | Passed | 12 answers suggested, 5 flagged for review. |
| Handwritten death certificate | June 28, 2026 | Passed | Cause of death read at low confidence and held for confirmation. |
| Marriage date after date of death | June 27, 2026 | Failed | Blocked by the date ordering rule. Expected. |
Test submissions for VA Form 21P-534EZ
- Test case
- Three documents, clean scans
- Run on
- June 30, 2026
- Result
- Passed
- What happened
- 12 answers suggested, 5 flagged for review.
- Test case
- Handwritten death certificate
- Run on
- June 28, 2026
- Result
- Passed
- What happened
- Cause of death read at low confidence and held for confirmation.
- Test case
- Marriage date after date of death
- Run on
- June 27, 2026
- Result
- Failed
- What happened
- Blocked by the date ordering rule. Expected.