AF Form 406: Miscellaneous Obligation/Reimbursement Document

AF Form 406: Miscellaneous Obligation/Reimbursement Document  – The AF Form 406, officially titled the Miscellaneous Obligation/Reimbursement Document (commonly abbreviated as MORD), is a key financial management tool used by the U.S. Air Force (and Department of the Air Force) to record miscellaneous obligations and process reimbursements.

This form helps document financial transactions that do not fit standard procurement or contract processes, ensuring proper obligation of funds, compliance with fiscal laws, and accurate reimbursement for authorized expenses. It replaced the older AF Form 113 and dates back to the July 1984 edition, which remains the current version available from official Air Force e-Publishing sources.

What Is AF Form 406 Used For?

AF Form 406 serves as a temporary obligating document (or, in some cases, a direct funding mechanism) for miscellaneous payments and reimbursements. It records a legal obligation of government funds while facilitating reimbursement to individuals, contractors, or other entities for authorized costs.

Common uses include:

  • Reimbursing travel expenses, training costs, or other miscellaneous personal or unit expenses.
  • Funding vendor pay (miscellaneous payments not tied to a formal contract).
  • Recording obligations for ancillary services, such as aviation fuel charges, non-fuel purchases, or support services.
  • Handling Government Furnished Material (GFM) for contracts, including Depot Purchased Equipment Maintenance (DPEM) or certain working capital fund transactions.
  • Year-end adjustments, such as closing out Government Purchase Card (GPC) residual balances or covering unbilled charges.
  • Inter-unit or inter-agency reimbursements, vehicle accident damage recovery, or other one-time miscellaneous obligations.

It is frequently referenced alongside other forms like DD Form 448 (Military Interdepartmental Purchase Request/MIPR), AF Form 616 (Fund Cite Authorization), or SF 1034 (Public Voucher for Purchases and Services Other Than Personal) for payment processing through the Defense Finance and Accounting Service (DFAS).

The form ensures compliance with the Antideficiency Act (ADA), DoD Financial Management Regulation (FMR) Volume 3 Chapter 8 (on obligations and miscellaneous payments), and Air Force financial management instructions such as DAFI 65-601 and related MAJCOM or installation guidance. Proper use prevents violations of purpose, time, and amount rules for appropriated funds.

Key Features of AF Form 406

  • Structure: The form includes fields for document number, description of the obligation, lines of accounting, amounts (in USD and sometimes foreign currency with exchange rates), contractor/debtor information, and certification/approval blocks.
  • Flexibility: It supports both obligation recording and reimbursement processing. Some MORDs are “Vendor Pay MORDs” or “Vendor Pay Funding MORDs,” which require specific notations in the description block (e.g., “VENDOR PAY MORD” or “VENDOR PAY FUNDING MORD”).
  • Accounting Integration: MORDs often feed into systems like IAPS (Integrated Accounts Payable System), BQ, or other Air Force accounting platforms. They may be processed manually or electronically depending on the context.
  • Replaces: AF Form 113 (May 1981 edition).

Download the official AF Form 406 PDF directly from the U.S. Air Force e-Publishing site:
https://static.e-publishing.af.mil/production/1/saf_fm/form/af406/af406.pdf

Always use the official version for official business to ensure compliance.

How to Fill Out and Process AF Form 406? (Step-by-Step Guidance)

While the exact block instructions appear on the form itself and in supporting financial management guides, here is a high-level overview based on standard Air Force practices:

  1. Header Information — Enter the miscellaneous obligation document number, date, and preparing organization/unit.
  2. Description Block — Provide a clear, complete explanation of the purpose. For vendor pay actions, explicitly include required phrases like “VENDOR PAY MORD.” Attach supporting documentation (receipts, authorizations, invoices, etc.).
  3. Line of Accounting — Enter the correct appropriation, budget activity, and other accounting classification data. Most MORDs use only one line of accounting.
  4. Amounts — Record the obligated amount. Include exchange rates if foreign currency is involved.
  5. Payee/Contractor Information — Include name and details as required (some funding MORDs may defer detailed payee info to the payment voucher).
  6. Certifications — The Resource Advisor (RA), Financial Management Analyst (FMA), or Certifying Officer reviews for validity, accuracy, funds availability, and compliance. Funds must be certified before obligation.
  7. Routing and Processing:
    • Submit to the local Comptroller Squadron or Financial Management Office (FMA) for review and certification.
    • For certain vendor pay MORDs, forward copies with documentation to DFAS within specified timelines (e.g., three days in some older guidance).
    • Track in accounting systems; de-obligate residual funds after all transactions clear to avoid improper retention of obligations.
    • Amendments may be needed if actual costs differ from the initial obligation.

Important Notes:

  • FMA personnel certify funds availability and ensure no ADA violations.
  • For year-end or GPC closeouts, automated processes may generate MORDs.
  • Residual balances after fiscal year-end must typically be de-obligated once transactions are complete.
  • Always coordinate with your local Financial Management office, as procedures can vary slightly by MAJCOM, base, or specific scenario (e.g., contingency operations, working capital funds, or contract field teams).

Who Uses AF Form 406?

  • Resource Advisors (RAs) and Resource Cost Managers (RCMs) — Initiate requests.
  • Financial Management Analysis (FMA) offices — Review, certify, and process.
  • Contracting OfficersCorps of Engineers Representatives (CORs), and unit commanders — In support of contracts or reimbursements.
  • DFAS — Handles final payment processing for many MORDs.

It applies across Regular Air Force, Air Force Reserve, Air National Guard, and Department of the Air Force civilian activities where appropriated funds are involved.

Best Practices and Compliance Tips

  • Accuracy is Critical — Incomplete or inaccurate MORDs are often rejected and returned for correction.
  • Supporting Documentation — Always attach receipts, authorizations, invoices, or memorandums justifying the obligation.
  • Timeliness — Process promptly, especially for vendor payments or year-end actions.
  • De-obligation — Actively monitor and de-obligate unused funds to maintain clean accounting records.
  • Training — Consult your base Financial Management office or the Air Force Financial Management & Comptroller community of practice for the latest guidance, as it supplements higher-level instructions like DoD FMR and DAFI 65-601 series.

Related Resources:

  • Official form: Air Force e-Publishing (search for AF Form 406).
  • DoD Miscellaneous Payments Guidebook.
  • Local supplements from your MAJCOM or installation Comptroller Squadron.
  • Broader policy: DAFI 65-601 Volume 1 (Budget Guidance and Procedures) and Volume 2.

Why Proper Use of AF Form 406 Matters?

Accurate use of the MORD supports fiscal accountability, ensures Airmen and units receive timely reimbursements, maintains audit readiness, and helps prevent Antideficiency Act violations that can carry serious consequences.

For official instructions tailored to your unit or command, contact your local Comptroller Squadron (CPTS/FMA) or Financial Management office. Procedures evolve, and installation-specific guidance often provides the most current step-by-step processes.

Download AF Form 406 hereOfficial PDF

This article is for informational purposes and is based on publicly available Air Force publications and financial management references as of 2026. Always verify with official sources and your servicing financial management office before use, as policies and systems may update.