AF Form 406, Miscellaneous Obligation/Reimbursement Document: Filing, Signatures, Reversal

AF Form 406, the Miscellaneous Obligation/Reimbursement Document (MORD), is a temporary Department of the Air Force accounting placeholder used to record an obligation or reimbursement when the permanent supporting paperwork has not yet posted. You download it from the Department of the Air Force E-Publishing site at e-publishing.af.mil, complete the identification and accounting fields, describe the transaction, obtain preparer and approving-official signatures, route it to your local Financial Management office, and reverse it once the actual obligating document is recorded in the system.

What the MORD Is For

The form fills a narrow gap. When a unit knows an obligation or reimbursement exists but the formal funding document is stuck in coordination or will not post before a fiscal deadline, the MORD stands in so the accounting records reflect reality. The amount entered can be an estimate and gets revised once the actual figure is confirmed.¹

One hard rule sits behind everything else on this form: a MORD cannot be used to reserve funds before an actual obligation exists. It is not an earmarking tool. The transaction has to be a real, known financial event that simply lacks its final paperwork at the moment.¹

When to Use AF Form 406, and When Not To

The most common trigger is a fiscal deadline arriving before the underlying document does. End-of-year and end-of-month closeouts are the classic case: the finance office needs the books to balance by a hard date, and the contract modification or delivery order that would carry the obligation has not posted. Filing a MORD bridges the gap.¹

In logistics, the MORD funds the Government Furnished Material Unit Repair Cost tied to a contract delivery order. When contractor expenses are on track to exceed the awarded amount, the MORD covers the gap to prevent an Anti-Deficiency Act violation or a work stoppage. Any MORD amendment in that context has to be completed before the customer’s funding expires.¹ NATO Support Services, shipping transactions, and supply efforts that must post before the actual funding document is available also rely on MORDs.

Some situations call for a different form. Inter-service procurement, where one military department buys goods or services from another, runs on a DD Form 448, Military Interdepartmental Purchase Request, not a MORD.² Local purchase requirements for base-level operational support typically go through an AF Form 9, Request for Purchase, or a Government Purchase Card.¹

Where to Get the Current Form

Download AF Form 406 from the Department of the Air Force E-Publishing site at e-publishing.af.mil. Go to the forms product index and search by form number. Confirm the edition is current before you start filling it in. Outdated editions cause processing delays or outright rejection at the finance office.

Filling Out the Form

The form has an identification block at the top, a main transaction block, and a continuation section for additional line items. Financial management offices reject entries with incomplete or mismatched data, so precision on each field matters more than speed.

Identification and Accounting Fields

Enter the document number, the date of preparation, and the name of the preparing unit. The accounting classification is the critical data point: it identifies the fund cite that will be charged or credited. Enter the Fund Summary Record (FSR), Program Summary Record (PSR), and Disbursement Summary Record (DSR) codes that correspond to your unit’s appropriation.³ For a foreign-currency transaction, enter the currency code and exchange rate in the designated fields; leave those blank for U.S.-dollar transactions.

Transaction Description and Amount

Write a specific description of the obligation or reimbursement. Vague entries like “supplies” or “services rendered” invite questions from the finance office. Specify what was provided, to whom, and under what authority. Enter the amount in U.S. dollars. Because the MORD accepts estimated amounts, flag the figure as an estimate so reviewers know a revision will follow.¹

Complete the contractor or debtor name field and the document number field that references the underlying contract, purchase request, purchase order, or work order. Both give the finance office a trail back to the real transaction the MORD is standing in for.³

Continuation Lines

Use the Transaction Record Continued section for multiple line items. Each line gets its own document number, date, description, and dollar amount. If the front runs out of space, continue on the reverse. Every line item should tie back to a single identifiable financial event. Do not lump unrelated obligations onto one MORD.³

Signatures and Approving Authority

AF Form 406 requires two signatures. The preparer, who assembled the data and completed the fields, signs first. The approving official then certifies that the obligation is legitimate and funds are available. In practice, that is usually the unit’s Resource Advisor or a financial management officer with delegated certifying authority. Before routing the form, confirm the approving official’s delegation of authority covers the dollar amount and the transaction type. A signature outside delegated authority creates its own problems.

Submitting and Tracking

Once signed, route the form to the local Financial Management office. Most units submit through secure digital portals; physical delivery remains an option where electronic access is limited. Finance reviews the MORD to verify the accounting classification is valid, funds are available, and the description supports the recorded amount.

Track status through the Air Force’s integrated financial systems or by asking your Resource Advisor for a system-generated acknowledgment. If the form is rejected, the notice will identify the field or data element to fix. Correct the error and resubmit as a new entry rather than trying to amend the rejected version.

Reversing the MORD

The MORD is temporary by design, and this is the step people most often skip. Once the actual obligating document (the contract, delivery order, or other permanent funding instrument) posts to the accounting system, reverse the MORD.¹ Leaving it in place creates a duplicate obligation in the books, distorts the unit’s available budget, and can trigger audit findings.

Build reversals into routine closeout procedures. A running log of open MORDs, with the expected arrival date of each permanent document, keeps this manageable. Where a MORD was filed with an estimated amount and the actual obligation turns out to be different, the reversal corrects that discrepancy at the same time.

Record Retention

The Department of Defense Financial Management Regulation requires obligation document records, including records tied to contract pay, vendor pay, and intragovernmental transactions, to be retained for a minimum of ten years after the final invoice or similar closing documentation.⁴ Keep the completed MORD, any amendments, the reversal documentation, and the permanent obligating document that replaced it together in one file. A complete audit trail protects the unit during Inspector General reviews and lets transactions be reconstructed years later.

How the MORD Fits Air Force Budget Rules

AF Form 406 operates inside the broader Air Force budget framework. Department of the Air Force Instruction 65-601, Volume 1 sets the overarching budget policy and procedures for appropriated fund management across the Air Force and Space Force.⁵ DAFMAN 65-605, Volume 1 adds technical procedures. One rule directly affects MORD usage: reimbursable obligation authority is created only when a valid order is received and accepted, and units cannot obligate against anticipated reimbursements before that order arrives.⁶

The MORD lives inside that rule. It can record an obligation that already exists but lacks its paperwork. It cannot create an obligation where none has occurred. Keeping that distinction in mind is what separates a routine bridge document from Anti-Deficiency Act exposure.

1
Air Force E-Publishing. AFMC Instruction 20-102 – Logistics Requirements Definition and Purchase Instrument Development
2
Acquisition.GOV. PGI 253.208-1 DD Form 448, Military Interdepartmental Purchase Request
3
FormsPal. AF Form 406 – Miscellaneous Obligation/Reimbursement Document
4
Department of Defense. DoD Financial Management Regulation Volume 1, Chapter 9 – Financial Records Retention
5
Department of the Air Force. Department of the Air Force Instruction 65-601, Volume 1 – Budget Guidance and Procedures
6
Department of the Air Force. DAFMAN 65-605V1 – Budget Guidance and Technical Procedures