A Department of Defense Activity Address Code (DoDAAC) is a six-character identifier used to identify organizations, activities, and authorized locations within the Department of Defense (DoD) logistics and supply system. It helps government systems determine which activity is requesting supplies, where shipments should be directed, and which organization is responsible for particular supply transactions. DoDAACs are essential to military requisitioning, transportation, inventory management, and financial accountability because they connect transactions to established organizational records.
A DoDAAC does not function like a conventional street address. Instead, it identifies an activity whose associated record contains information used for logistics and administrative purposes, including relevant address and organizational details. Depending on the transaction, a DoDAAC may identify a requisitioning activity, a ship-to destination, or another organization participating in the supply process. The same organization may perform several functions, but the identifiers used for those functions are not necessarily identical.
The DoDAAC is part of the broader Department of Defense Activity Address Directory (DoDAAD), which maintains activity identification and address information for authorized organizations. The directory provides a standardized reference that supports transactions across different military departments, defense agencies, and logistics systems. Without this shared identification framework, supply organizations would have greater difficulty distinguishing similarly named units, maintaining consistent records, and directing shipments to the correct recipients.
DoDAACs are also relevant to government supply channels outside traditional military operations. GSA Global Supply uses activity address information to identify eligible government customers and support the processing of supply orders. Civilian federal agencies may use corresponding Activity Address Codes (AACs), which serve comparable identification purposes within the government supply environment. The terminology and administration differ by organization, but both types of codes help connect orders to recognized government activities.
For federal contractors, DoDAACs are most important when fulfilling orders for defense customers or interpreting government logistics and contract documents. A contractor may encounter one code identifying the organization placing an order and another identifying the activity receiving the goods. Understanding these distinctions helps prevent shipping errors, incorrect transaction records, and delays in government acceptance or payment.
How DoDAACs Are Assigned and Maintained
A DoDAAC consists of six alphanumeric characters and is assigned through authorized Department of Defense activity address management procedures. The code identifies an activity within the applicable government directory, while its associated record provides information needed to support logistics and administrative transactions. A DoDAAC should not be interpreted as a universally readable abbreviation of an organization’s name, installation, or geographic location.
The assignment and maintenance of DoDAACs are governed by DoD activity address management policies, including DoD Manual 4000.25, Volume 6, which addresses DoDAAD administration. Authorized Central Service Points and other designated management organizations perform responsibilities associated with establishing, updating, and maintaining activity records. Individual contractors and ordinary system users cannot simply create their own valid DoDAACs for government transactions.
An activity may require a DoDAAC because it performs an authorized logistics function, such as requisitioning supplies, receiving shipments, maintaining inventory, or participating in other supply operations. The need for a code depends on the organization’s responsibilities and the applicable assignment rules. Not every physical location or administrative office automatically requires a separate identifier.
A DoDAAD record may contain several types of information used by government systems. The exact fields and authorized uses depend on the activity and the relevant directory requirements.
| Record element | Purpose | Operational significance |
|---|---|---|
| DoDAAC | Identifies the activity | Connects transactions to an established organizational record |
| Activity name | Identifies the organization or unit | Helps users recognize the responsible activity |
| Physical or mailing address | Provides applicable location information | Supports correspondence and administrative identification |
| Shipping address information | Identifies an authorized delivery destination | Supports routing and delivery of supplies |
| Organizational association | Connects the activity to its responsible organization | Supports accountability and directory administration |
| Authority and status information | Indicates applicable record attributes | Helps systems determine whether a code is appropriate for a transaction |
These elements illustrate the types of information associated with activity identification rather than a complete list of every DoDAAD data field. Some records may contain additional attributes needed for particular logistics processes, and access to certain information may be restricted.
A critical distinction exists between the six-character code and the information associated with it. A DoDAAC may remain the same while authorized directory personnel update an activity’s address or other record information. Conversely, organizational changes may require the assignment of a new code or changes to the status of an existing one.
For example, a military organization may relocate to another installation while retaining its organizational identity. Whether its existing DoDAAC remains appropriate depends on the applicable directory management rules and the nature of the organizational change. The code itself should not be used to infer that the activity is still located at a previously known address.
Directory maintenance is particularly important because outdated records can affect actual supply operations. If an activity’s shipping information is no longer accurate, a requisition may contain a valid DoDAAC but still result in delivery problems.
Organizations responsible for DoDAAC records therefore need procedures for reviewing and updating activity information when operational circumstances change. Relevant events may include:
- Establishment of a new authorized military or defense activity.
- Relocation of an existing organization or receiving location.
- Changes in organizational responsibility or administrative control.
- Consolidation or restructuring of military units.
- Changes in an activity’s authorized logistics functions.
- Deactivation or closure of an organization.
- Correction of inaccurate directory information.
The status of a code matters as much as its format. A six-character value that resembles a DoDAAC is not necessarily a valid or currently usable activity identifier. Systems and personnel must rely on authoritative directory information to determine whether a code is assigned and appropriate for the intended transaction.
DoDAAC Functions in Military Requisitioning and Supply Transactions
The principal value of a DoDAAC is its ability to connect supply transactions to specific government activities. In military logistics, a single requisition may involve several organizations performing different responsibilities, including requesting supplies, providing funding information, managing inventory, and receiving the shipment. Standardized activity identifiers allow these responsibilities to be represented consistently across systems.
The distinction between requisitioning and receiving activities is particularly important. The organization requesting an item may not be the same organization that physically receives it, especially when supplies are delivered to centralized warehouses, distribution facilities, or operational locations.
For example, a military maintenance unit may request replacement parts for equipment undergoing repair. The parts could be delivered to a separate installation supply facility rather than directly to the maintenance unit’s administrative office. The requisition and associated logistics records must distinguish the organization requesting the material from the location designated to receive it.
A DoDAAC may therefore appear in several functional contexts, depending on the transaction structure and the applicable logistics procedures.
- Requisitioning activity. Identifies the organization requesting supplies through the government supply system.
- Ship-to activity. Identifies the activity associated with the designated delivery destination.
- Supplementary address information. Provides additional activity identification where required by the transaction.
- Supply accountability. Connects requisitions and related records to responsible organizations.
- Transportation processing. Supports the identification of government activities involved in routing and delivery.
- Financial and administrative processing. Helps associate transactions with relevant organizational records and responsibilities.
These functions should not be interpreted as meaning that every DoDAAC automatically carries authority to perform all of them. The activity’s authorized roles, associated directory information, and applicable transaction requirements determine how the identifier may be used.
In defense logistics, DoDAACs are commonly associated with transactions conducted under Defense Logistics Management Standards (DLMS). These standards support structured exchanges of supply and logistics information between government systems. Activity identifiers help those systems interpret the organizations participating in a transaction without relying exclusively on free-text names and addresses.
A requisition may contain an activity identifier together with item identification, requested quantity, priority information, and other required transaction data. The DoDAAC identifies the relevant activity, but it does not independently identify the item being ordered or establish the quantity required.
This distinction prevents confusion between organizational and product identifiers. A National Stock Number (NSN), for example, identifies an item of supply, while a DoDAAC identifies an activity participating in the transaction. Both may appear in the same requisition, but they answer different operational questions.
Consider a simplified example involving replacement equipment:
| Transaction element | Illustrative value | What it identifies |
|---|---|---|
| Requisitioning activity | Assigned DoDAAC A | Organization requesting the equipment |
| Item identification | Valid NSN | Specific item of supply requested |
| Requested quantity | 20 | Number of units requested |
| Ship-to activity | Assigned DoDAAC B | Activity associated with the delivery destination |
| Transaction reference | Requisition document identifier | Individual requisition record |
The illustrative labels are not actual assigned DoDAACs. The example demonstrates how different identifiers work together in a supply transaction.
The distinction between an activity identifier and a requisition document identifier is also important. A DoDAAC identifies an organization or activity, while a requisition document number identifies a particular transaction. The same activity may submit many requisitions over time, and those transactions require separate references for tracking and reconciliation.
An incorrect DoDAAC can disrupt this process even when the requested item and quantity are correct. The transaction may be associated with the wrong organization, directed to an inappropriate destination, or rejected because the activity information does not satisfy the applicable system requirements.
DoDAAC and Activity Address Codes in GSA Global Supply
GSA Global Supply provides a government supply channel through which eligible federal customers can obtain a variety of products. Activity Address Codes are important in this environment because they help identify government organizations participating in supply transactions. The codes support customer identification, order processing, and the association of orders with authorized government activities.
DoD customers generally use DoDAACs, while civilian federal agencies may use corresponding AACs. These identifiers perform comparable organizational identification functions, although their assignment authorities and administrative procedures are not identical. In both cases, the purpose is to provide a recognized activity reference rather than rely solely on an organization’s name or mailing address.
An activity address code is not the same as a commercial customer account number. It is part of a government identification framework used to represent authorized activities in relevant supply and logistics processes. Its use may be necessary for particular GSA Global Supply ordering methods, but the presence of a code alone does not establish that every person associated with the activity is authorized to place orders.
Eligibility to purchase through a government supply program depends on the applicable program rules and purchasing authority. A valid AAC or DoDAAC supports organizational identification, but it does not replace the requirements governing who may order, what may be purchased, or how the transaction must be funded.
For example, a civilian agency office may have an assigned AAC that identifies it within the relevant supply system. When an authorized employee places a GSA Global Supply order, the code may be used to associate the order with the agency activity and its applicable account or logistics information.
A military organization may use its DoDAAC for a comparable purpose. However, the government systems involved may require additional information, including delivery instructions, payment details, or other transaction-specific data.
The distinction between DoDAAC and civilian AAC can be summarized as follows.
| Characteristic | DoDAAC | Civilian AAC |
|---|---|---|
| Primary organizational context | Department of Defense activities | Civilian federal agency activities |
| Identifier format | Six alphanumeric characters | Six-character activity address identifier |
| Principal purpose | Identifies activities in defense logistics and related transactions | Identifies civilian activities in applicable government supply processes |
| Administrative responsibility | Authorized DoD directory management organizations | Applicable civilian agency and government address code management authorities |
| GSA Global Supply relevance | Supports identification of DoD customers | Supports identification of civilian agency customers |
| Purchasing authority | Not established by the code alone | Not established by the code alone |
Although the identifiers are closely related in purpose, users should not assume that every DoDAAC or AAC can be used interchangeably across all government systems. The applicable ordering platform, customer eligibility rules, and directory records determine how the code is processed.
For government buyers, the most practical requirement is to use the correct activity identifier for the organization and transaction. A code copied from an old purchase order may no longer reflect the appropriate ordering or receiving activity if the organization has been restructured or its logistics arrangements have changed.
For contractors, the relevant concern is usually the accuracy of the activity information provided in the order. A supplier fulfilling a GSA Global Supply-related requirement or another federal supply transaction should distinguish the ordering organization from the actual delivery destination and follow the instructions contained in the applicable transaction documents.
DoDAACs in Federal Contracts, Shipping, and Payment Processing
Federal contractors may encounter DoDAACs in solicitations, purchase orders, delivery instructions, electronic transaction records, and contract administration documents. Their significance depends on the role assigned to the activity in the particular acquisition. A code identifying a government customer should not automatically be treated as the correct shipping destination or payment office.
Defense contracts frequently involve multiple government organizations with separate responsibilities. One office may administer the contract, another may inspect or accept delivered supplies, and another may perform payment-related functions. Activity identifiers help systems distinguish these organizations and direct information to the appropriate participants.
In some DoD contract documents, DoDAACs appear in designated fields identifying activities such as the issuing office, administration office, inspection or acceptance location, and payment office. The specific use of each code depends on the document format and applicable contract instructions. Contractors must interpret the code in its assigned context rather than assume that all listed activities are involved in receiving physical goods.
For example, a contractor may receive a purchase order identifying a military installation as the delivery destination while listing a separate government payment office. Shipping the products to the payment office would be an obvious operational error, even if the payment office’s DoDAAC is valid.
The same principle applies to electronic invoicing and acceptance systems. The correct activity identifiers may be necessary to route transaction information to the appropriate government organizations. An incorrect value can create processing delays, but it does not automatically mean that the underlying goods or services were unacceptable.
Contractors should distinguish several types of information commonly found in federal transactions:
- Issuing office information identifies the organization responsible for issuing the contract or order.
- Contract administration information identifies the office responsible for assigned administrative functions.
- Ship-to information specifies the destination for physical delivery.
- Inspection and acceptance information identifies the applicable government responsibilities for evaluating and accepting performance.
- Payment office information identifies the organization responsible for designated payment processing functions.
- Requisitioning activity information identifies the organization associated with the supply request.
These functions may be performed by different organizations or combined within a single activity, depending on the acquisition. Contractors should not infer the correct activity identifier from a government office’s name when the contract or order provides a specific code.
An additional distinction exists between DoDAACs and CAGE codes. A Commercial and Government Entity (CAGE) code identifies an entity for government business purposes, while a DoDAAC identifies an activity within the government logistics and administrative framework. The two identifiers may appear in the same acquisition records but are not substitutes for one another.
For example, a contractor’s CAGE code may identify the company supplying equipment, while a DoDAAC identifies the government activity receiving the shipment. Both contribute to accurate transaction records, but they refer to different participants and serve different identification functions.
DoDAACs should also not be confused with GSA contract numbers. A MAS contract number identifies an awarded contract, while a DoDAAC identifies a government activity. A contractor may receive orders from several government activities under the same contract, each with its own applicable organizational identifier.
This distinction is relevant to contractors serving multiple military installations or defense organizations. Even when the same product is supplied under similar contractual terms, each order may contain different activity identifiers and delivery instructions.
Common DoDAAC Errors and How to Prevent Them
Most DoDAAC-related problems arise from incorrect activity identification, outdated directory information, or confusion between the roles of different government organizations. Because the code contains only six characters, it may appear simple to enter or copy. However, its operational significance depends on the accuracy of the associated activity record and the context in which the code is used.
One common problem is selecting a valid DoDAAC that belongs to the wrong activity. Automated systems may recognize the code as properly formatted, but the transaction may still be routed incorrectly. This type of error is particularly difficult to detect when the contractor or ordering personnel rely on a previous transaction rather than the current order instructions.
Another problem involves organizational changes. Military units may relocate, consolidate, or change administrative responsibilities, and their activity records must be maintained accordingly. A contractor that continues using outdated shipping information may experience delivery problems even though the original code was legitimate.
The following practices help reduce the risk of activity identification errors:
- Verify the complete code. Confirm that all six characters match the identifier specified in the current transaction documents.
- Identify the code’s function. Determine whether it refers to the requisitioning, shipping, administration, inspection, acceptance, or payment activity.
- Use current authoritative information. Avoid relying exclusively on codes copied from old orders or internal customer records.
- Confirm delivery instructions. Ensure the physical shipping destination matches the applicable order requirements.
- Distinguish organizational identifiers. Do not substitute CAGE codes, contract numbers, or other references for DoDAACs.
- Review electronic transaction requirements. Confirm that activity identifiers are entered into the correct fields in applicable ordering, invoicing, or acceptance systems.
- Escalate discrepancies. Request clarification from the responsible government contact when activity codes and written instructions appear inconsistent.
These controls are especially important when contractors automate order processing. An enterprise resource planning system may store government customer identifiers and automatically populate shipping or invoicing records. If the stored activity information is incorrect, the same error may affect multiple transactions before it is discovered.
For example, a distributor supplying maintenance materials to several defense installations may maintain separate customer records for each activity. If two installations have similar names but different DoDAACs, selecting the wrong customer record can result in a shipment being directed to the wrong receiving organization.
The contractor should therefore validate the activity code against the actual order rather than rely solely on a text match between organization names. This is particularly important when a centralized purchasing office places orders for multiple receiving locations.
Another issue arises when a government activity’s code is valid but not appropriate for the requested transaction. The existence of a directory record does not necessarily establish requisitioning authority, purchasing eligibility, or permission to use a particular ordering channel. Contractors and government personnel must follow the applicable transaction rules and activity authorizations.
When a discrepancy occurs, the appropriate correction depends on its source. A typographical error in an order may require clarification or correction by the issuing organization, while an outdated DoDAAD record generally requires action through authorized directory management procedures. Contractors should not attempt to resolve government directory problems by inventing replacement codes or independently changing official activity information.
For organizations using GSA Global Supply, accurate AAC or DoDAAC information supports reliable customer identification and order processing. For contractors performing defense-related orders, the same identifiers help distinguish the government activities responsible for ordering, receiving, administering, and paying for supplies.
The essential principle is that a DoDAAC identifies an activity, not a complete transaction or a physical address by itself. Correct use requires understanding the activity’s role, verifying current information, and applying the identifier in the appropriate field. When these elements are handled consistently, DoDAACs support accurate requisitioning, dependable deliveries, and clearer accountability throughout federal supply operations.
