Administrative documents are written for readers who were not present, and DA Form 7381 is no exception. Titled BOSS GENERAL LEDGER SUMMARY, it is used to boss general ledger summary — a transaction that means little in conversation and a great deal in a file. The published edition here carries the date September 2006 and the status not stated. Its 2 page(s) and roughly 200 fields are sized to what the record must prove years later, which is always more than the moment appears to need.
Behind any Army form sit two separate decisions. What the document asks is settled by ACSIM, which maintains and revises it. Whether you raise it, and where it goes once signed, is settled by CIR 608-06-1. That division is the reason a form can outlive several changes in the process it serves.
Retrieval governs the order of entry. The head of the form takes name, identification number, unit and date, and those values become the handles by which the record is found later — the substantive blocks are never searched on. This is why the spelling must match official records exactly rather than approximately.
The rules of entry all trace back to the page being fixed in advance. Tabbing follows the order built into the form, which usually matches how the page reads and misses less than clicking. An exclusive group discards the earlier selection because contradictory entries would make the record unusable. One-line fields have no wrap because print positions are predetermined, so an overlong entry displays fully and prints truncated. Longer text goes to the remarks area or a continuation, both provided for exactly that. Where nothing applies, the nil mark is entered — a blank leaves the reader unable to tell a considered answer from a skipped one.
Signing is the act that makes the document evidence, and until it happens the entries are only a proposal. Additional signatures — reviewer, approver, witness — each stand for a separate judgement, dated when applied so the record shows who accepted what and in what order. The common faults all damage that record in the same way: a blank mandatory field breaks the chain of required answers, swapped digits in an identification number detach the document from its subject, an inverted day and month misplaces it in time, and stale data from a reused copy states things nobody meant to state.
Behind the Privacy Act statement is a requirement that anyone asked for personal data be told, in advance, under what authority it is sought, for what purpose, who else routinely sees it, and whether refusal is possible. Reading it after completing the fields defeats its function. And the completed form is itself a personal record from that point on, subject to the handling rules such records carry.
Download the form
The published formats — PDF, XFDL — reflect the range of places a form gets filled in. Where there is a computer, the fillable pdf supplies live fields that keep entries positioned and readable. Where there is not, the printable pdf gives the identical page as flat artwork for pen entry. The distinction is one of setting rather than of authority; the page is the same document in both.
The choice of application decides whether your work survives. Browsers render pdfs as documents to be read; where a viewer shows fields without a mechanism to store them, typed text disappears when the tab closes, and nothing announces the loss. A full reader treats the file as a form and preserves entries on save. The xfdl format comes from IBM Lotus Forms, used across Army systems because of the routing and signature functions built into it, and it opens in the Lotus Forms Viewer alone.
There is no charge and no sign-up. Published documents are distributed as published, without modification.
What the form asks for
- ContentArea1
- Descrip
- DescripA
- DescripA_1
- DescripA_10
- DescripA_11
- DescripA_12
- DescripA_13
- DescripA_14
- DescripA_15
- DescripA_16
- DescripA_17
- DescripA_18
- DescripA_19
- DescripA_2
- DescripA_20
- DescripA_21
- DescripA_22
- DescripA_23
- DescripA_24
- DescripA_25
- DescripA_26
- DescripA_27
- DescripA_28
The routing in CIR 608-06-1 decides where the document goes — a named office, the administrative channel, or the individual's file — and the records schedule for the series decides how long it stays. Neither is a local judgement, because a record system loses its meaning if each office keeps things for its own preferred interval. Copy the form before submitting it.
Series and number are how the DA series signals which documents belong together, and the grouping follows real process boundaries: a shared proponent or directive usually means a shared purpose. A form cited on the face of another is part of that same transaction, and continuation sheets, covers and transmittals complete it.
An edition marks the form at a point in a process that keeps moving, and the date printed on the page is what distinguishes one from another. Since a saved file never announces its own obsolescence, compare its date against the current edition before using it again. Prior executions remain valid: the change applies forward, and a record is read against the edition it was written under.
One boundary should be stated clearly. What is distributed here are copies of published Department of the Army forms; the site is independent, issues nothing of its own, and holds no position in the system it describes. Proponency, prescribing directives and retention schedules operate without reference to it. Consequently nothing here is legal advice and no assurance about acceptance is possible. Questions about a particular entry, a requirement or eligibility belong with ACSIM or your servicing administrative office.
Questions and answers
- What is DA Form 7381?
- BOSS GENERAL LEDGER SUMMARY
- Which edition is current?
- September 2006
- Who is responsible for this form?
- ACSIM
- In which formats can it be downloaded?
- PDF, XFDL