Consider what a Department-level form is for. DD Form 2658 — DD Form 2658, Returned and Undeliverable Check/Bond Record, August 1993. — was established to Returned and Undeliverable Check/Bond Record, 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.
Work down the page in the printed order, and understand why the order exists. The identifying block establishes whose record this is and under what circumstances it arises. The body of the form then answers questions that are only meaningful once that context is fixed. The signature block comes last because a certification signed before the entries are complete certifies nothing.
Before the first entry, compare the date printed on the form face with not stated. This is not bureaucratic fussiness. Editions change field numbering, and a receiving office working from the current layout may look for information where your copy does not put it. On a Department form the exposure is wider than usual: your record may be reviewed by an office in another service entirely, one with no reason to remember what the previous edition looked like.
For an ambiguous field, read the form's own instruction, then not stated, which controls.
Download the form
The set published here is PDF, covering 1 pages with roughly 161 fields.
All of it downloads without charge. Where care is needed is in the reader you choose. A fillable pdf depends on field properties that desktop applications honour and browser previews frequently ignore, so work locally rather than inside a browser window.
What the form asks for
- 1. Date returned, line 1.
- 2. Check or bond number.
- 3. Check or bond date.
- 4. Amount.
- 5. Payee.
- 6. Voucher number.
- 7. Disposition.
- 8. Date of disposition.
- 1. Date returned, line 10.
- 2. Check or bond number.
- 3. Check or bond date.
- 4. Amount.
- 5. Payee.
- 6. Voucher number.
- 7. Disposition.
- 8. Date of disposition.
- 1. Date returned, line 11.
- 2. Check or bond number.
- 3. Check or bond date.
- 4. Amount.
- 5. Payee.
- 6. Voucher number.
- 7. Disposition.
- 8. Date of disposition.
Submission follows not stated and whatever local instruction supplements it. Make a copy before the original leaves. Department forms travel across organizational lines by design, and the administrative distance that makes them useful is the same distance that makes tracing a lost one difficult.
Forms referenced inside this one are located by number alone, and that simplicity is a direct product of Department-level numbering. Because the DD sequence is maintained centrally and not duplicated by service, a number is a complete address: one number, one document, throughout the Defense establishment.
Procedures that touch both Department and service processes will cite forms from both sequences, and the coincidence of numbers between them is exactly that — coincidence. An Army proponent maintains the DA series for the Army; not stated or another Department office maintains the DD series for the whole Department. Two independent registries, two independent numbering runs, no correspondence at any value.
A form is downstream of the policy that requires it, and revision usually starts there: a directive is reissued, a collection requirement is altered, notice language is updated by statute. The form is republished as a consequence. Since none of that reaches individual users, an archived copy quietly becomes wrong, and verifying not stated each time you download is the whole remedy.
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 2658?
- DD Form 2658, Returned and Undeliverable Check/Bond Record, August 1993.
- Which edition is current?
- Not stated by the publisher
- Who is responsible for this form?
- Not stated
- In which formats can it be downloaded?