This is a reactive field buy.
Sit with the chief for a minute before you crack the book. Nobody is routing a decision down to you here. The relay is a short walk away, the chief is waiting, and the system that would normally write this order is dark. Your job is to name the buy, then move.
The SF 44 belongs in moments like this one: small, immediate, local, and easier to handle over the counter than to push through a system that needs a working connection. Don't over-engineer it into a miniature solicitation. The only question is whether the form fits the facts in front of you.
Field Buy
The pressure is real, but the rhythm is still simple: recognize the situation, fit-check the instrument, execute cleanly, and bring back evidence.
If the relay can change hands right now, the amount is inside your warrant, funds are sitting there, one delivery and one payment close the loop, and your office allows the form, the SF 44 is probably the cleanest move you've got.
Carry that rhythm through the whole buy. It keeps the call anchored to the facts in front of you instead of turning the moment into a form-filling drill.
Recognize
Small, immediate, local need. Vendor is in front of you. The system route or the card route isn't the better answer right now.
Fit-check
Authority, threshold, funds, local permission, immediate availability, one delivery, one payment, and price support all line up.
Execute
Write a clear order, name the seller, capture item and price, get a receiving signature, and keep the copy trail intact.
Bring back evidence
Come back with the form, vendor receipt or invoice, fund support, receiving proof, your price note, and whatever your office needs to close it out.
Authority comes first.
Start where you already are. You're appointed, and if you deployed as a contingency contracting officer (CCO) you probably carry a simplified acquisition threshold (SAT) warrant. So the dollar limit usually isn't what stops an SF 44 buy. The real questions are how far the SF 44 itself reaches under the rules you operate under, whether funds and a payment path exist, and what your local procedure controls.
Whether the micro-purchase floor or the SAT is your ceiling decides whether the SF 44 can carry the buy. Here is that latitude in concrete terms.
How much latitude you actually have. The SF 44 isn't locked to micro-purchase. Under the DoD RFO class deviation (DFARS 212.403(b)(2)(i)), the micro-purchase limit applies to all purchases except that purchases up to the SAT may be made for the deviation's listed cases. The one that lifts this buy is (B) overseas transactions by a contracting officer supporting a contingency operation (10 U.S.C. 101(a)(13)) or a humanitarian or peacekeeping operation (10 U.S.C. 3015(2)). A relay bought at a bare-base airfield supporting a contingency operation is squarely that case, so when the deviation path applies, the SAT is your ceiling for it. Know the neighbor on the list too: (A) fuel and oil, which also reaches the SAT, though Government fuel cards (not the SF 44) are used for fuel, oil, and authorized refueling-related items (PGI 212.403(b)(2)(i)(1)). At a fueling operation you'll work next to both.
That's a real tool in your pocket, and you may be standing in exactly the situation it was written for. Plenty of places never get a Government Purchase Card. Others take months to stand up payment in WAWF so a vendor can get paid through the normal system. Iraq and Afghanistan ran that way for years. When the deviation applies and both the card lane and the system lane are closed, an SF 44 up to the SAT can be how the mission still gets its part. It isn't always the smartest move. More dollars means more cash crossing a table and more exposure. But the latitude is there, and knowing you have it keeps you from freezing on a buy you're cleared to make.
Source note: RFO FAR 12.403(b) is the current primary source for this lesson for agencies on the FAR Overhaul or a deviation path. The latitude language above is from the DoD RFO class deviation, FAR Part 12 / DFARS Part 212 (DARS Tracking Number 2026-O0028, effective February 1, 2026). The deviation also lists transactions in support of intelligence and other specialized activities under Part 2.7 of Executive Order 12333. Confirm component adoption, local procedure, and current statutory cross-references against your command's posted version. Legacy FAR 13.306 is still useful transition background, but it isn't the lead authority anymore.
Use the SF 44 when the facts are tight enough.
Skip the flowchart. A fast fit-check is what helps at the counter, because the real question is whether this specific buy can be closed as one clean field transaction.
The SF 44 is your whole contract file.
Say the fit-check held. This really is an SF 44 buy. The instrument does three jobs at once, and the name says so: Purchase Order – Invoice – Voucher. One sheet is your proof of the purchase, your proof of receipt, and your proof of payment. That's why it works as a pocket contract file: order, invoice, voucher, fund cite, receiving evidence, payment support, and file evidence all compressed into one form. The teaching mockup below is labeled so you can see where each piece sits.
U.S. Government Purchase Order - Invoice - Voucher
This is a learning mockup. Use the official controlled form for real buys.
Route 4 Service Yard
Local vendor POC and phone
Delivered at vendor counter / handed to maintenance chief
| 5 Supplies or services | 6 Quantity | 7 Unit price | 8 Amount |
|---|---|---|---|
| Starter relay, generator fuel pump support | 1 each | Local currency / USD equiv. | Amount paid or invoiced |
| Brief description enough to identify what was bought |
Make the paper tell the whole story.
You've seen where every piece sits on the sheet. The work now is making each one carry weight: the vendor should understand what the Government is ordering, the receiver should sign for what they actually took, and the contracting office should be able to reconstruct the transaction without calling you at midnight.
This signed SF 44 is the contract. There is no separate award document behind it, so write the order like the binding instrument it is: what the Government is buying, who ordered it, when it happened, and which order number or serial control applies. If the description is too vague for a file reviewer to identify the item, fix it before leaving.
Capture the seller, item, quantity, unit price, total, and any vendor invoice or receipt. If the vendor uses its own receipt, attach it and make the SF 44 crosswalk obvious.
Put the accounting data where finance can use it. A field buy still needs an obligation and a way to pay cleanly when the paperwork gets home.
The receiving signature is the Government's evidence that the thing was received or the service was performed at the point of need. Get it from the person who actually took delivery.
Payment office and voucher blocks close the loop. If your local process routes those blocks after return, leave the copy trail complete enough for that office to finish without guessing.
Bring back the SF 44 copy, vendor receipt or invoice, quick price note, funding support, receiving evidence, and any MFR needed to explain why the field method fit.
Two things the walkthrough doesn't put in a block, but every field buyer has to plan for: the cash, and where the buy actually happens.
The cash is the real risk.
What makes an SF 44 feel heavy isn't the form. It's the stack of cash you may be carrying to pay the vendor. You control that cash with people, not with paperwork. You rarely do this alone: a paying agent handles and disburses the funds, you write and sign the order, and the acceptor (the user, or whoever requested the buy) confirms the Government got what it paid for. Three sets of eyes on the same transaction keep it on the up and up. Depending on how much you're carrying and where, security rides along too. Arrange the cash pickup and the escort before you leave, not at the vendor's table.
There may not be an actual counter.
Don't get stuck on the picture of a literal store counter. Sometimes there isn't one. The vendor delivers to your facility and comes back to get paid once the load is there. That's still an SF 44 buy: one delivery, one payment, closed cleanly. Other times you really do walk into a shop and pay across the counter. Either way works. Plan for the field reality though: an SF 44 means nothing to a local merchant, and the form will confuse a vendor who's never seen one. If you can, bring a translator so the vendor knows what they're signing and what they're being paid for.
A note on "payment was never made."
SF 44 is meant for over-the-counter buys. The vendor walks away paid that day. If a vendor shows up at the office a week later saying payment was never made, that's a hard "no" from me. The whole reason you use this form is that payment and delivery happen in the same exchange. Treat after-the-fact payment requests on an SF 44 as a flag, not a normal accounting fix. Run them up the chain and let your legal and finance shops sort out whether they're a real claim or someone trying their luck.
When this stops being an SF 44 buy.
Here are the signals that the SF 44 doesn't fit anymore and the buy needs a different method. Spot them early and switch lanes. That's your call as the executor.
Threshold or authority isn't clean
If the amount is over your limit, the threshold path is murky, or local authorization is missing, the SF 44 isn't your instrument. Use a method that fits the dollar value and your authority.
Delivery or payment isn't one-and-done
Recurring needs, split deliveries, future labor, installments, or partial payments usually mean the transaction has outgrown the pocket form.
The requirement is fuzzy
If nobody can describe the item or service well enough for the vendor, the receiver, and the file to agree on what was bought, slow down and define it.
The price doesn't track
If the quote looks high, the vendor can't explain it, or another source is plainly available without hurting the mission, build a better price note or switch methods.
Payment controls are messy
Cash, foreign currency, taxes, unusual receipt practices, or unclear finance routing can all be made to work, but they need local procedure nailed down before the buy.
The buy keeps repeating
A second or third similar SF 44 is a signal. Bring it back as market intelligence for a BPA, purchase order, GPC, or other planned method.
My take on the form, the cash, and the "controlled" debate.
This is the part where I drop the textbook voice. The DoD has been pushing the 3-in-1 tool for years to digitize what the SF 44 does on paper, and there's training for it through JCCS that's worth scanning if you've never seen the tool. It's old, but it's still the standing reference.
3-in-1 training (CAC required): jccs.gov/3in1ng. Old material, but it walks through the digital 3-in-1 workflow the way DoD wants it done.
That said, I'm an old man stuck in his ways. I still like paper SF 44s. They're easier to track, easier to keep on me, and I don't need a connection to use one. They've also gotten me out of jams in places where the digital tool wasn't a real option. Take that for what it's worth.
I've also deployed places where I didn't have a book of SF 44s on me, and that's where it got creative. What I did, more than once, was make an Excel version of the form. The blocks line up, you can fill it on a laptop, print it for the vendor and the receiver, and bring it back as your file copy. It's not the controlled form, so there's a debate to be had about whether you should be doing that at all.
The "controlled" form debate.
SF 44s used to be treated like controlled items: serial numbers tracked, books issued and returned, the whole nine. The reasoning was that the form is a bearer instrument for Government obligation, so loose books are a risk. I'll be honest, the control framing never fully tracked for me. An SF 44 with no line of accounting (LOA), no CCO signature, and no vendor or receiver signatures is a piece of paper. It can't obligate anything, and it can't be paid against. If a vendor ever walked up to me waving an unsigned SF 44 demanding payment, I'd send them back out the door. The form is meant for over-the-counter purchases. Payment happens at delivery. That's the entire point of it.
That doesn't mean throw the control aside. Follow your local procedure on books, serial numbers, and turn-in. It does mean don't lose sleep over the form itself: every line that matters has to be filled in and signed by a warranted person before it can hurt anybody.
Simplest advice I can give.
If you're heading somewhere you'll be paying cash, bring SF 44s with you. Pull a book before you fly. They take no space, they don't need a connection, and they'll be there when the system is down and the vendor is in front of you. Everything else is a workaround.
SF 44 pocket field card.
Use this as your quick reference before you leave the office, at the counter, and when you bring the evidence back.
SF 44 Pocket Field Card
For appointed CCOs/COs using an official controlled SF 44 under local procedure.
Before you move
- Confirm appointment and the ceiling that applies (micro-purchase, or SAT under the deviation's listed cases).
- Confirm SF 44 is authorized by agency/local procedure.
- Confirm funds, accounting data, and payment office.
- Arrange the cash pickup, paying agent, and security escort if cash is involved.
- Know what evidence must return with you.
At the counter
- Describe the item or nonpersonal service plainly.
- Capture seller, date, quantity, unit price, total, and currency.
- Keep the paying agent and acceptor present; use a translator for local vendors.
- Get receiving evidence from the right person.
- Attach or cross-reference the vendor invoice or receipt.
Back at the office
- Route the copy package for payment and certification.
- Write a short price and method note if the form does not tell enough.
- Log the buy under local control procedures.
- Flag repeats for a planned buying method.
Where this lesson's authority comes from.
You didn't need any of this to make the call at the counter. It's here so the contracting office, or you when the file comes back, can check the authority behind every claim above.
Current FAR/RFO anchor
For agencies operating under the FAR Overhaul or an implementing deviation, Acquisition.gov RFO FAR Part 12 section 12.403 identifies the SF 44 as the pocket-size purchase order-invoice-voucher for limited on-the-spot, over-the-counter purchases when all listed conditions are met.
DoD deviation and the SAT latitude
For DoD readers, the FAR Part 12 / DFARS Part 212 class deviation (DARS Tracking Number 2026-O0028) is effective February 1, 2026 and runs until rescinded or incorporated. DFARS 212.403(b)(2)(i) is the provision that lets an SF 44 run up to the SAT for its listed cases: fuel and oil; overseas contingency, humanitarian, or peacekeeping transactions; and intelligence or other specialized activities addressed by Executive Order 12333. Fuel-card procedures are at PGI 212.403(b)(2)(i)(1), and the contingency and humanitarian definitions are at 10 U.S.C. 101(a)(13) and 10 U.S.C. 3015(2). Confirm the current text and your component's adoption against your command's posted deviation.
Form pedigree
GSA identifies SF 44 as "U.S. Government Purchase Order - Invoice - Voucher," current revision 10/1983. The mockup block labels were cross-checked against official DoD SF 44 data requirements and example structure.
Caveats for field use
Thresholds, agency adoption, class deviations, appointment language, local fiscal controls, cash handling, and payment routing can change. This page is a training aid, not legal advice or a substitute for your agency policy, deployed CCO guide, or contracting office direction.
RFO transition note: some official pages and older training still point to legacy FAR 13.306 or FAR 53.213 for SF 44. This draft uses the RFO Part 12 source path as the current primary framing and treats legacy citations as transition/background.