FMS EdgeFMS Edge — home

Guide

What has changed in Foreign Military Sales since Executive Order 14268?

Updated 2 November 2026Checked against the SAMM: 26 October 2026

No section of the manual cites 14268. The one policy memorandum that names the order, 25-97, changed no manual text. The closure requirement it announced entered the manual through 26-84, which requires Letters of Offer and Acceptance implemented in fiscal year 2017 and prior to reach final closure by September 30, 2027.

What the manual says about executive orders

13637 allocates authority and responsibility for principally to the Secretary of War and the Secretary of [SAMM ]. Directive 5105.65 delegates the Secretary of War's authority to the Deputy Secretary of War, to the Under Secretary of War for Policy (USW(P)), and finally to the Director, [SAMM ].

Closing cases implemented in fiscal year 2017 and prior

Implementing Agencies () must prioritize and carry out the final closure of cases implemented in 2017 and prior, to support an unmodified audit opinion on the Department of War (DoW) financial statements [SAMM ]. These legacy cases must reach final closure no later than September 30, 2027, because the systems used for them often lack the transactional data and documentation an audit requires [SAMM ].

For a case with pending deliveries, requisitions, actions or training, the may request an exemption, or may develop a new case with the purchaser and move the remaining scope to it by concurrent modification [SAMM ]. Apart from the programmatic exemptions and continued execution under a memorandum for record, each covered under its own heading on this page, a case without an exemption must close by September 30, 2027 [SAMM ].

Exemptions from legacy case closure

has set programmatic exemptions from the legacy closure requirement for Letters of Offer and Acceptance () implemented in 2017 and prior. The exempt categories are cases and Contingency Support Cases. These exemptions keep critical support lines active, but they do not stop an from closing a case that is no longer required, and they do not waive the manual's reconciliation requirements [SAMM ].

An may also request an individual exemption. The request must show two things: that accounting information is fully reconciled across the general ledger, the case logistics systems and the other feeder systems, and that supporting documentation for case implementation and execution is available. A general or flag officer or a member of the Senior Executive Service () must sign it. The 's closure point of contact submits the request to (/FPRE/FP) through the Case Closure Submission Tool [SAMM ]. reviews each request for compliance with policy but does not approve it, and every exempted case is subject to sampling by [SAMM ]. Once finds a request compliant, the may proceed and must record a case remark saying so in the Defense Management System () [SAMM ].

set these exemptions to support the wider case closure effort without degrading partner sustainment. Cases in both exempt categories may remain open. The manual lists the categories in Table C16.T2, and it describes I cases in C16.3.1.3 and Contingency Support Cases in C16.3.21 [SAMM ].

(/FPRE/FP) carries out the compliance review. The case remark that the shall record in states that this office found the exemption letter compliant with Policy Memo 25-97 [SAMM ]. For the exemption letter itself, the manual points to the form letter in Figure C16.F3 [SAMM ].

Continuing execution of legacy cases that cannot close

A legacy case that can neither reach final closure by the deadline nor qualify for an exemption may be eligible for reconciliation and continued execution, subject to conditions. The category covers seven kinds of case: those with pending deliveries for non-severable requirements; active or outstanding procurement requisitions that would cost the partner significantly if cancelled; open case lines on the case with a period of performance running past September 30, 2027; pending warranties; cases with partners whose practices prohibit moving requirements to a new case; an active period; and missing supporting documentation [SAMM ]. In these cases the must submit a Memorandum for Record () to through the Case Closure Tool, documenting the information required and the actions taken to reconcile and continue the case. will review each case by case and respond to the . One can cover several cases affected by the same closure challenge, and it must be approved, with conditions, at the GS-15 equivalent or higher in the 's comptroller or financial management organization. For the itself, the manual points to Figure C16.F4 [SAMM ].

Modifications and amendments to such a case are restricted to supporting its existing execution and reconciliation, and no increase in scope may be added to it at any time [SAMM ]. The must make every effort to reconcile and close the case by its estimated closure date, and it shall seek opportunities to move requirements to a new case under C16.4, for example when a contract ends [SAMM ].

will work closely with the to measure each case's progress and keep it on track for completion, through regular engagement forums such as Business Process Reviews and Financial Management Reviews [SAMM ].

Closure adjustments for cases that cannot be reconciled

An that cannot fully reconcile a case for closure through the established procedures, after all other options are exhausted, must submit an requesting a closure adjustment before it can submit a case closure certificate. The should coordinate the in advance with the Country Finance Director (), and then routes it for review and approval. Once the Defense Finance and Accounting Service () has processed an approved adjustment, the completes the case closure certificate [SAMM ].

The adjustment is for a case the cannot reconcile despite its best efforts, for example because of irreconcilable discrepancies between systems. The must be signed at GS-15 level or above [SAMM ]. The sends the request to the case closure team through the Case Closure Tool. For the itself, the manual points to Figure C16.F2. 's Financial Analysis and Compliance Division (/FPRE/FAC) will pass the to the offices that review and approve it. If it is approved, /FPRE/FAC will sign it, return it to the and forward the approved Closure Adjustment Package to Indianapolis () for processing in the . If it is not, /FPRE/FAC will return it to the for revision. The completes the Case Closure Certificate in line with C16.3.8 [SAMM ].

Moving cases from interim to final closure

If invoices have not come in within four years of the Supply/Services Complete () date, whatever the amount, the must move the case to final closure status; an invoice can still be paid by reopening the case [SAMM ]. Excess funds stay in the to cover delayed but valid claims; once nine years have passed since the original date, will return what remains to the purchaser's [SAMM ].

The Defense Finance and Accounting Service, Indianapolis () must tell the purchaser in writing that a valid invoice or claim submitted after the return will be billed for immediate payment [SAMM ]. A case line qualifies for final closure only when its date is at least four years past and the line and its contracts are not subject to active litigation, an investigation or a pending U.S. Government claim [SAMM ].

The manual points to AP7.C4.6 for the move to final closure and to AP7.C4.13.3 for paying an invoice by reopening the case [SAMM ].

To collect amounts due on out-of-cycle bills, may follow AP7.C4.10.2 [SAMM ].

Government property clauses on contracts with case funding

Contracts that carry funding must include the clause 52.245-1, Government Property, and the Defense Supplement () clause 252.245-7005, Management and Reporting of Government Property, each as its regulation prescribes [SAMM ].

Inventory in the Security Assistance Accounts financial statements

Accounts (SAA) inventory covers the defense articles, spare parts and support equipment that the DoW holds for sale to a partner, including items stored at contractor facilities until title transfers [SAMM ]. inventory shall be valued at historical cost: the original purchase price plus every cost of bringing the inventory to its current location and condition [SAMM ]. Software held for sale is accounted for as inventory [SAMM ]. Detailed accounting guidance is in Statement of Federal Financial Accounting Standards 3 and the Financial Management Regulation (), Volume 4, Chapter 4 [SAMM ].

The method for determining historical cost depends on how the inventory is tracked [SAMM ]. For more detailed accounting guidance on software held for sale, the manual points to Financial Accounting Standards Board (FASB) Accounting Standards Codification (ASC) 985-20 [SAMM ].

Enhanced End Use Monitoring designation

Enhanced () is a designation that gives the U.S. Government greater oversight of a partner's compliance with the transfer conditions of an or another government-to-government agreement [SAMM ]. -designated articles require enhanced accountability, including physical security assessments of partner storage sites and inventories by serial number [SAMM ].

An -designated article sold through must be sold on a defined order line under an -coded designator, with physical security and accountability notes [SAMM ]. A or other that recommends designating an article for must submit the request to signed at the general officer, flag officer or level [SAMM ].

Defense articles are designated for against the criteria in C8.4.4. The articles designated for for all -eligible countries are listed in Table C8.T4, which the manual keeps on its restricted site. Other defense articles may require Case Unique , additional U.S. control measures (such as U.S. custody or electronic monitoring), or both, decided case by case in the transfer approval process [SAMM ]. 's Division (/GEX/) holds the list of articles designated for Case Unique [SAMM ].

Because commits U.S. Government and partner resources, oversees and administers the U.S.-provided defense articles designated for it [SAMM ].

Foreign Military Training Report responsibilities

Every reportable training activity must be shared with and collected by it, and prepares the Foreign Military Training Report (FMTR) from the data [SAMM ]. must regularly review and update the training data held in [SAMM ]. The Combatant Commands () should coordinate Military Group () completion of training data in the Security Cooperation-Training Management System () database of the Web (SANWeb) [SAMM ].

At the end of the fiscal year, issues the FMTR data call. must conduct a training data compliance review in , and the Military Departments must support them in verifying the data on time [SAMM ].

Training data should be uploaded in real time and finalized in once a training event is complete. and should make sure the data is reviewed and validated continuously throughout the year, for both the and the Team training tracks [SAMM ].

The data call is a tasking message that sets out the reporting procedures and administrative guidance for the report. On receiving it, the and Military Departments will make sure the message reaches every and reporting Country Program Manager, so that those offices can complete their remaining training data in and . In the compliance review, the correct any errors and supply any missing information [SAMM ].

Redirecting or disposing of Building Partner Capacity articles

() and the geographic coordinate to identify defense articles from a Building Partner Capacity () program that may warrant redirection to another benefitting partner [SAMM ]. Any redirection must be consistent with, and further, an established Significant Initiative () for the new partner, and the geographic is responsible for explaining how the redirection furthers U.S. security interests [SAMM ].

The Department of War organization holding the articles works with the that sourced them to assess whether their condition suits a transfer, since they are likely to ship "as is", and their location matters because it decides whether shipping them to the new partner is feasible and what it costs. Moving articles that sit in one geographic 's area of operations to another area may be cost ineffective and administratively cumbersome. The geographic for each potential new partner must assess that partner's capacity to absorb the articles [SAMM ]. The preference of the geographic for the cancelled program will always be considered, but it does not prevent the USW(P) from directing the articles to another partner [SAMM ].

For articles found unserviceable, or that fail inspection before shipping for safety reasons (ammunition, for example), () carries out the disposal in coordination with the Defense Logistics Agency (), the Joint Munitions Command (JMC), OUSW(P) (SPF) and the Under Secretary of War for Acquisition and Sustainment's office (OUSW(A&S)). The disposal is shown on the case in the line description note [SAMM ].

Congressional notification thresholds

By law, an that meets or exceeds one of the thresholds in Table C5.T19 requires a Congressional Notification () under Section 36(b)(1) of the , and the thresholds vary by purchaser [SAMM , ] []. A is also required when an amendment or modification would raise the value or the to a threshold and Congress has not been notified of the sale before [SAMM ].

For North Atlantic Treaty Organization () countries, Australia, Israel, Japan, the Republic of Korea and New Zealand, the thresholds are $25M of , $100M of and $300M of design and construction services. For all other countries, for organizations and for all other international organizations, they are $14M, $50M and $200M [SAMM ]. For an Amendment or Modification to a case Congress has already been notified of, the manual points to C5.7.3.2. Table C5.T20 sets out the information a 36(b)(1) must contain and names the three documents that carry it in full (the Transmittal, the Policy Justification and the Sensitivity of Technology) [SAMM ].

Foreign Military Sales metrics

26-75 (E-Change 845) added the metrics to the manual. A is actionable once it meets the mandatory criteria in Table C5.T4A, and the “ Actionable” milestone must be entered in before case development begins on a Category A, B or C document, because the case development clock starts there [SAMM ]. Table C5.T9 sets the standard, counted from Actionable to Offer, as 85% of documents within 30 days for Category A, 90 days for Category B and 130 days for Category C [SAMM ]. The Assessment comes before that clock and is counted from Receipt. The 's first finding that the is actionable or insufficient has a of 10 days for Category A, 10 days for Category B and 45 days for Category C [SAMM , ]. The same case development standards apply to amendments [SAMM ].

25-103 first set the case development standards of Table C5.T9 and moved the start of the Category A and B clock from Receipt to Actionable. For those two categories, how the new standard compares with the old therefore depends on how long a request takes to become actionable. Category C was already counted from Actionable.

When a Category A, B or C document misses its standard, at least one reason code from Table C5.T10 must be entered in for it, whatever its category. A reason code should state the concrete reason the standard was not met, whereas Case Development Extenuating Factors, which rest largely on anticipated issues, decide which cases are assigned to Category C [SAMM ].

Chapter 6 adds two acquisition metrics for and . Required Award Date Variance () measures whether contracts are awarded on time, and Contractual Delivery Date Variance () measures whether contractors deliver by the contractual dates. The military departments and DoW components are required to meet both metrics' performance standards on the cases they execute that include such equipment [SAMM ]. All DoW components must adopt the and standards and monitor and report performance data each month through to OUSW(A&S), in unless another tracking system is coordinated with [SAMM ].

Cases implemented on or after October 1, 2017 ( 2018) are also measured against case closure performance standards, to be met at the 85 percent level [SAMM ]. The first closure metric runs from 's posting of the Supply/Services Complete CLOSHOLD milestone to the 's submission of the case closure certificate to , and the second from that certificate to 's final closure of the case [SAMM , ]. When a case exceeds a closure standard, must enter reason codes in for the metric it missed [SAMM ].

Three active policy memoranda set performance standards without changing manual text. 25-103 covers case development and 26-01 covers case closure; 26-75 has since written both sets of standards into Table C5.T9 and C16.1.7. 26-89 covers the Department of War steps of a , which are the 's preparation of the package and 's review of it before it goes to the Department of State.

Sister cases and concurrent modifications for legacy cases

26-55 (E-Change 830) lets an create a Sister case in to receive the ongoing partner requirements of a Legacy case [SAMM ]. A Concurrent Modification transfers , aligns the with the Legacy case and makes the allowable changes listed in Table C6.T7. For a change outside that table the may request an ; without an approved ETP, must make any pending scope change by Amendment to the Sister case once the Concurrent Modification is implemented [SAMM ].

For a Legacy case in the Case Closure Initiative population, the Sister case must meet the prerequisites in Table C16.T3, which cover changes to the legacy case, case structure, the , documentation, and the surcharge and accessorial rates [SAMM ]. Because the Sister case carries the remaining scope and funds with no change to overall scope, no partner signature is needed, and the will accept and implement it unilaterally [SAMM , ]. The must then give the partner a copy of the Sister case and a notification of the change [SAMM ].

Once its scope and funds have moved, the Legacy case must be taken toward closure under Appendix 7 [SAMM ]. A partner may also ask for two or more Legacy cases to be consolidated onto one new Sister case, and must first carry out the compliance procedures the manual lists for that [SAMM , ].

Offering an LOA after congressional notification

26-118 (E-Change 882) changed when an may reach the purchaser after a notification. For a Section 36(b)(1) or 36(b)(5)(C) notification, the cannot give the purchaser a draft until the Department of State confirms that the has been formally transmitted to Congress, unless the Assistant Director for International Operations consents in writing. A final cannot be offered before the statutory review period ends. For a Section 36(b)(5)(A) report the may be offered on formal notification, because no statutory review period applies, but the partner may not take or transfer of the reported articles until 45 days have passed since formal notification [SAMM ].

Where an sets a not-to-exceed () threshold, a significant rise in will require an updated , or an official email from the or the partner at or above the level of whoever signed the original . That email attests that the partner verbally approved the revised case amount [SAMM ].

Unmanned aerial systems under the Missile Technology Control Regime

26-124 (E-Change 886) rewrote the manual's Missile Technology Control Regime () screening. The is an informal, voluntary political understanding among states that seek to limit the spread of missiles and missile technology, including unmanned aerial systems () [SAMM ].

When an actionable covers an Category I , the program office, program manager or equivalent will send an LOR-Advisory to the Office of Regional Security and in the Department of State's Bureau of Political-Military Affairs (PM/RSAT). The advisory carries the , the end user, the system name and the quantity. PM/RSAT asks the Missile Technology Export Control (MTEC) working group to make a nonproliferation pre-assessment of the while DoW review and case development continue [SAMM ]. The 's point of contact should go ahead with case development during the MTEC review and assume the working group's approval unless the Department of State contacts the after the , but MTEC approval is required before the is offered [SAMM ].

Investment Letters of Offer and Acceptance

26-128 (E-Change 891) created the Investment , through which a partner invests in research and developmental evaluation of capabilities that are not a U.S. . The memorandum's procedure is not yet in the manual; its note on C5.1.4.2, below, names the case structure use for an Investment .

Clarifications in DSCA 26-127

26-127 (E-Change 889) made clarifying updates. Letters of Request for space capabilities, technologies, systems or spacecraft go to the Air Force's SAF/IAPG (Space Division) for action [SAMM ]. The details of 36(b)(1) notifications are published on the Major Arms Sales page of the Department of State website [SAMM ]. A Support Partnership case may be an Agent Sale by exception, through 's process [SAMM ]. In Chapter 10 the Naval Small Craft Instruction and Technical Training School now appears under its new name, the Special Boat Training Command [SAMM ].

Month by month: the change log, from October 2026

References

SAMM

Public authorities

  • SecWar memo, 7 Nov 2025: Secretary of War memorandum, 7 November 2025, "Unifying the Department's Arms Transfer and Security Cooperation Enterprise to Improve Efficiency and Enable Burden-Sharing"
  • DoW release, 10 Feb 2026: Department of War release, 10 February 2026, "Department of War Finalizes Realignment of the Defense Security Cooperation Agency and the Defense Technology Security Administration"
  • AECA §36(b): Arms Export Control Act of 1976, as amended, §36(b) (22 U.S.C. §2776(b))
  • EO 14268: Executive Order 14268, Reforming Foreign Defense Sales To Improve Speed and Accountability (April 9, 2025)

Facts referenced

DSCA policy memoranda

  • DSCA 25-97: Prioritization of Case Closure Activities for Letters of Offer and Acceptance Implemented in Fiscal Years 2017 and Prior
  • DSCA 26-84: Updating Security Assistance Management Manual for Legacy Case Closure [SAMM E-Change 854]
  • DSCA 26-85: Title 22 Foreign Military Sales Closure Adjustment [SAMM E-Change 855]
  • DSCA 26-10: Requirements to Resolve Problem Disbursements [SAMM E-Change 807]
  • DSCA 26-95: Interim to Final Closure [SAMM E-Change 863]
  • DSCA 26-96: Reconciliation and Continued Execution of Certain Foreign Military Sales Cases Implemented in Fiscal Year 2017 and Prior [SAMM E-Change 864]
  • DSCA 26-63: Return and Closure Procedures on Direct Commercial Contracts Approved in Fiscal Year 2017 and Prior
  • DSCA 26-20: Recognition of Inventory and Related Property in the Security Assistance Accounts Financial Statements [SAMM E-Change 775]
  • DSCA 26-79: Enhanced End Use Monitoring Criteria SAMM Chapter 8 Update [SAMM E-Change 849]
  • DSCA 26-72: Chapter 8 End Use Monitoring Administrative and Clarification Updates [SAMM E-Change 842]
  • DSCA 26-73: Updates to Chapter 10 Foreign Military Training Report Requirements and Responsibilities [SAMM E-Change 843]
  • DSCA 26-43: Building Partner Capacity Updates for Redirection, Treatment as Department of War Stock, or Disposal of Defense Articles Originally Intended for a Benefitting Partner [SAMM E-Change 759]
  • DSCA 24-29: 36(b) Congressional Notification Update [SAMM E-Change 483]
  • DSCA 26-75: Foreign Military Sales Metrics Security Assistance Management Manual Update [SAMM E-Change 845]
  • DSCA 25-103: Performance Standards for Case Development from Letter of Request Actionable to Letter of Offer and Acceptance Offer
  • DSCA 26-01: Performance Standards for Foreign Military Sales Case Closure
  • DSCA 26-89: Performance Standards for Department of War-specific Foreign Military Sales Congressional Notification
  • DSCA 26-55: Concurrent Modification Process for Legacy Case Closure [SAMM E-Change 830]
  • DSCA 26-118: Administrative and Compliance Updates to the Congressional Notification Process [SAMM E-Change 882]
  • DSCA 26-124: Updates to Missile Technology Control Regime Guidance [SAMM E-Change 886]
  • DSCA 26-128: Procedural Guidance for Investment Letter of Offer and Acceptance [SAMM E-Change 891]
  • DSCA 26-127: Clarification Updates [SAMM E-Change 889]

Related