Case Changes and Reviews · 1 of 3
A signed case is not fixed. Quantities move, prices move, delivery dates move, and the paperwork has to keep up. There are two instruments for that, and picking between them is not a matter of size or convenience. "The scope of an FMS case is the key factor in determining whether to prepare an Amendment, Modification, or new LOA to accomplish a particular LOA change" (SAMM C6.7.1.1).
Scope is the purpose the case was written to serve. Where a change would alter that purpose, neither instrument is correct. The manual gives two blunt illustrations: "When the change would alter the purpose of the LOA (e.g. adding UH-60s to a F-35 case, or adding a frigate to a blanket order training case), the existing LOA should not be amended or modified" (SAMM C6.7.1.1). A fresh case is written instead.
Because scope carries this weight, the implementing agency has to say out loud why a change is within it. The purpose of the change goes in the case description, and for a modification the agency "must write a clear explanation why there are no changes in scope" (SAMM C6.7.1.2).
An amendment is the instrument for anything the partner has to agree to. "An FMS case must be amended when there is a change in scope to a case line or note. Such changes require the FMS purchaser's acceptance" (SAMM C6.7.2.1). An amendment can also carry changes that would not have needed one, since all changes on a case can be accomplished this way.
One category is settled in advance rather than argued case by case. Adding follow-on support is always a scope change: "As the additional follow-on support services is a change in scope, a Modification cannot be initiated" (SAMM C6.7.2.2). To prevent support lapsing, the agency may start that amendment without waiting for a formal letter of request, and the partner's agreement arrives with acceptance.
There is a small accounting rule with visible consequences. "The DSCA database records Amendments reflecting net increases of more than $50,000 in the fiscal year the Amendment is accepted. Amendments that reflect net increases of $50,000 or less are recorded in the year of the basic LOA" (SAMM C6.7.2.3.1). Large amendments therefore appear as current year sales, while small ones vanish into the original year.
Money moves with the document as well. Where the existing schedule will not cover costs through to the next billing cycle, payments are added to the amendment, and an under-collected case picks up current financial requirements including termination liability (SAMM C6.7.2.3.2).
A modification does the opposite job. "An FMS case Modification is used on an FMS case to make administrative changes that do not alter the scope of a case, case line, or case note. These changes may be accomplished unilaterally by the USG and do not require the FMS purchaser's acceptance" (SAMM C6.7.3.1).
The list of permitted changes is published rather than inferred, and the everyday examples are financial. Funding on a defined order line can be raised or lowered to match actual or projected billing, and a line can be reconciled as a case moves toward closure (SAMM Table C6.T7).
Timing carries a duty. A price increase modification has to reach the partner before the accrued costs reported to it exceed the case estimate, unless the case is already closing (SAMM C6.7.3.1.2). A partner that learns of an overrun from a statement rather than from a modification is seeing a process failure.
Implementation is correspondingly light. "Modifications do not require purchaser signature and are implemented upon countersignature" (SAMM C6.7.3.4). The partner is asked only to acknowledge receipt, which is not a condition of anything.
There is a hybrid for one specific problem. "DoD may utilize Concurrent Modifications to transfer funding between two or more FMS cases" (SAMM C6.7.3.2). The documents are linked in the case system so that all of them implement together.
Several conditions apply at once. The official requesting the shift must hold authority to accept cases, and the letter of request stating the shift is attached to each modification. The arithmetic is capped: "Total amount(s) increased are no more than the total amount(s) decreased" (SAMM C6.7.3.2.3). Cases being reduced must keep enough funds for their remaining obligations, and every case in the package must already be implemented.
Existing grant financing can travel this route between cases. New terms of sale and new types of grant assistance generally cannot (SAMM C6.7.3.2.2). Where an increase would trigger an initial deposit, an amendment is required instead.
An offered amendment that needs reworking can be restated rather than withdrawn. That is available while the document sits in offered status, the partner has not yet signed, the offer expiration date "has not been expired for more than six months, and all changes are consistent with FMS policies and procedures" (SAMM C6.7.2.4). The amendment number survives, and the restated version supersedes the earlier one.
Extending the deadline alone is simpler, and bounded. "The OED may be extended, without a requirement for case restatement, only if requested no later than 6 months after the current valid OED" (SAMM C6.7.2.7.1). Minor corrections can be made by hand while the document remains unsigned. Significant ones, such as revised quantities or prices, need a new or restated amendment.
Signing a document and correcting it at the same time does not work. "When an Amendment is signed by the purchaser and returned to the IA with unauthorized pen and ink changes, it is processed as a counteroffer" (SAMM C6.7.2.7.4). The document has to be restated and reoffered, or cancelled and replaced.
On the other instrument the rule admits no exception at all: "Pen and ink changes to Modifications are NOT authorized" (SAMM C6.7.3.3). A further change means a further document.
Where the manual has no answer, an exception to policy can be requested through the agency's tracker, with a justification and a written endorsement from the implementing agency policy office. Replies are promised within ten business days for routine requests and fifteen for special ones, and appeals must be lodged within fifteen business days of a denial (SAMM C6.7.5).
An approval is not open-ended. "Approved ETPs will expire six months from date of approval unless otherwise requested and approved" (SAMM C6.7.5). Approvals are carried in the case package rather than kept on file elsewhere.
One route is closed off entirely. Neither instrument may be used to reduce an unused case to zero or to any other figure, and that includes stripping out every line. The closure process is the way to return value on an unused case (SAMM C6.7.6). How that runs is set out in how a case is reconciled and closed.
| Scope | The purpose a case was written to serve, and the test that selects the right instrument. SAMM C6.7.1.1. |
|---|---|
| Amendment | A change in scope, requiring the partner's signature. |
| Modification | An administrative change within scope, made unilaterally. |
| Concurrent modification | Linked modifications moving funding between implemented cases. |
| OED | Offer expiration date, after which an offer is no longer valid. |
| ETP | Exception to policy, approved for six months unless stated otherwise. |
Every statement above links to the document behind it. The full source list for this piece is on the sources page.
This page describes public United States government programs for general information. It is not legal, regulatory or procurement advice, and it does not address the facts of any particular case.
Changes to a case reach the ground long after they are signed. Sentfore provides secure transport, protective security, facilities and life support around defense programs in difficult environments, and its principals have worked on overseas defense and security programs. Requirements can be sent through the contact page.