Consider what a Department-level form is for. DD Form 281A — Voucher for Emergency or Extraordinary Expense Expenditures - Memorandum — was established to Voucher for Emergency or Extraordinary Expense Expenditures - Memorandum, and it was placed in the DD sequence because the underlying transaction occurs throughout the Defense establishment in substantially the same shape. Standardizing the record was cheaper and more reliable than letting six services each design their own.
The practical effect of Department-level issue is interoperability. not stated establishes the requirement across the Defense enterprise; not stated keeps the document current for all of it. No service maintains its own variant, which means a completed record travels between components — service to agency, agency to joint command — and arrives in a format the receiving office already knows how to read.
The edition in force is not stated, carried by the publisher as not stated, and edition discipline is stricter on a Department form than most people expect, precisely because supersession happens everywhere at once. There is no interval during which one service still works from the previous layout while another has moved on.
The form is laid out top to bottom in a sequence that reflects how the record will be read, not merely how it was drawn. Identification comes first because everything below it is understood in relation to a named person, unit or transaction; substantive entries follow; certification closes the document because certification attests to what precedes it. Filling out of order tends to produce internal inconsistencies — an entry that made sense before the header was settled and does not afterward.
Check the edition date before you type anything, against not stated. Old blanks accumulate in shared drives for years, and the cost of one is not obvious until a reviewer cannot find a field. Because DD forms are revised centrally and replaced across the Department in a single action, there is no component still tolerating the old layout as a local practice.
Fill all of it, marking inapplicable items N/A. A record with gaps cannot later demonstrate whether the gap was a decision or an oversight, which is exactly the ambiguity documentation exists to remove. Dates go in the form's own format — on a document that crosses service lines, an ambiguous date is a real hazard rather than a pedantic one.
Where the form collects personal identifiers, a Privacy Act Statement accompanies it, and its placement is meaningful. The statute requires disclosure at the point of collection — authority, purpose, routine uses, and the consequence of declining — so that the person supplying the information does so knowing what becomes of it. Reading it after you have filled the fields inverts the arrangement entirely.
What the signature block asks for is an act, not a text. Ink on a printed copy performs that act; a digital signature bound to your credential performs it electronically, CAC-based in most Defense systems. Typing your name performs nothing, since anyone with the file could type the same characters. Enter the date at the same moment: the certification is a statement about a point in time and needs one recorded.
Recurring defects have a pattern to them, and it is mostly the pattern of a record that cannot be relied on: an edition that does not match, gaps that cannot be interpreted, entries that cannot be read after scanning, dates that could mean two things, and a certification nobody executed. For an ambiguous field, read the form's own instruction, then not stated, which controls.
Download the form
What you can download: PDF. The form runs unknown pages and asks for approximately unknown entries. The plurality of formats is deliberate: Defense distribution has never been able to assume one operating environment across the whole force.
Two states of the same page circulate, and the reason is worth knowing. In the fillable pdf, the boxes are real fields holding real data; in the printable pdf, the boxes are drawings. Where a record will cross components — as Department records regularly do — the typed version is the safer artifact. Each scan, each forwarding, each reproduction costs handwriting a little legibility, and the office that finally files the record is rarely the office that received it first.
If you find an xfdl file here, its presence is historical. The format belongs to IBM Lotus Forms, which the Department adopted Department-wide for electronic forms and fielded on a scale that makes wholesale removal slow. You need the matching viewer to open it; ordinary pdf software cannot read the format and will say so unhelpfully.
Nothing here is charged for. Published Defense forms are public documents and distribution carries no fee, in any format. One caution about software: fill the form in a desktop pdf application rather than a browser tab. Browser-embedded viewers implement field behaviour inconsistently, and the failure mode is silent loss of everything you entered.
The completed form goes to the office named in not stated or in local implementing procedure, and it is worth keeping a copy before it goes. On a Department form the destination is frequently outside your own chain — another service, a defense agency, a joint staff — and recovering a document that has crossed an organizational boundary is a slower business than retrieving one from a file down the hall.
Cross-referenced documents are found by series and number, with nothing further required. That the DD sequence is unified across the Department means a cited number identifies one form and no other, which is the practical payoff of centralizing the numbering in the first place.
Where a service form is cited in the same instruction, the two numbering systems should not be read across. DA numbering belongs to the Army and is administered by an Army proponent; DD numbering belongs to the Department and is administered by not stated or an equivalent Department office. The systems developed separately and were never harmonized, so identical digits in each identify two documents with nothing in common. The prefix, not the number, tells you which system you are in.
Understanding why editions change explains why checking them is not optional. Revision follows directive reissue, changes in what data is required, and amendments to mandatory notice text — decisions made at Department level and communicated through publication rather than notification. The file you saved does not update itself, so the edition date at download is what you rely on.
What you have here is the document and a description of it, which is a different thing from guidance. This page is not an organ of the Department, gives no legal or procedural advice, and makes no representation about the outcome of any filing; the offices that administer the requirement are the only ones positioned to answer that. Applicability, eligibility and procedural questions belong to not stated, to your servicing personnel office, or to the office designated in not stated.
Questions and answers
- What is DD Form 281A?
- Voucher for Emergency or Extraordinary Expense Expenditures - Memorandum
- Which edition is current?
- Not stated by the publisher
- Who is responsible for this form?
- Not stated
- In which formats can it be downloaded?