DTS Voucher Stuck in Review Longer Than Expected — Here’s What Actually Moves It

DTS vouchers have gotten complicated with all the conflicting advice flying around about what to do when yours stops moving. As someone who submitted a voucher after TDY last year and watched it sit completely untouched for two weeks, I learned everything there is to know about getting these things unstuck. Today, I will share it all with you.

Here’s how it went for me. I came back from a temporary duty assignment, submitted what I was convinced was a spotless voucher — receipts attached, dates lined up with my authorization, per diem calculated down to the dollar. Fourteen days passed. The status screen said “In Review.” No rejection. No comment. No flag. My AO hadn’t touched it. The system had just… absorbed it. I checked the status page probably thirty times over those two weeks, which accomplished exactly nothing.

What I eventually figured out is that “stuck in review” almost always has one fixable cause behind it. The trick is knowing which cause it is before you fire off a vague email to your AO that generates zero results. So, without further ado, let’s dive in.

Why DTS Vouchers Stall in Review

Three things stop vouchers cold. Understanding which one applies to your situation changes everything about how you approach fixing it.

The first is plain workload backlog. Your approving official might be genuinely buried. I’ve talked to finance NCOs juggling 40 open vouchers simultaneously with no extra staffing and no relief coming. Your voucher isn’t lost — it’s queued. It just hasn’t surfaced yet. This one stings because nothing is actually wrong with your submission. You’re waiting your turn.

The second is a line item mismatch or receipt problem. This is the one that got me. Your lodging per diem doesn’t match the authorization. You uploaded a credit card charge instead of an itemized hotel folio. A meal receipt came out blurry and the amount is unreadable. A file hit the 2 MB upload limit and got corrupted. The system flagged it — but nobody told you. Sometimes that flag sits idle for days before an AO even opens the voucher.

The third is a system-level hold. Your voucher got pulled for audit review. A routing error bounced it sideways into a finance office queue instead of staying with your AO. Some backend glitch froze it entirely. These are rare, honestly. But they happen — and when they do, your AO can’t unstick you alone. That’s worth knowing before you spend three days pestering the wrong person.

Most soldiers assume category three immediately. They’re usually wrong.

First Check These Things in DTS Before Contacting Anyone

Probably should have opened with this section, honestly. Open your DTS account right now. Pull up the voucher. Look at the status screen before sending a single email or making a single call. The answers are often already sitting there, visible, waiting for you to scroll down far enough to find them.

1. Check for error flags or comments. Scroll past the basic header information. Look for red text, yellow warning indicators, or any notes left by your AO. DTS will sometimes display “Missing Receipt” or “Lodging Amount Exceeds Authorization” right on that screen — plain as day. Read it carefully. That comment is the actual problem. Not a mystery. Not a glitch. Just a flagged line item waiting for you to address it.
2. Verify all receipts are attached and readable. Navigate to your attachments section and open every single file you uploaded. Check that nothing is blurry. Confirm the dollar amount is visible and legible. Check file sizes — DTS gets finicky about anything over 2 MB and will sometimes accept the upload without actually processing it correctly. If a receipt looks bad, delete it and re-upload a clean version. This step alone fixes more stuck vouchers than anything else I’ve seen.
3. Confirm your lodging and meal totals match your authorization. Pull up the original TDY authorization document. Write down the approved per diem rate for lodging and meals at each location. Now compare those numbers against your voucher line by line. If you were authorized $160 per night for lodging in Fayetteville and you claimed $185 because that’s what the hotel charged, that $25 gap will hold the voucher. You’ll need to attach documentation explaining the difference — or adjust the claim.
4. Make sure location data matches exactly. Your authorization says Fort Benning. Your voucher says Fort Moore. That kind of discrepancy — even a name-change discrepancy for the same physical location — creates holds. Check every city, state, installation name, and date range on every line item against what your authorization letter actually says.

Find a problem? Fix it right there. Delete the bad receipt, re-upload the clean one. Correct the dollar amount. Save. The system bumps it back into the review queue immediately. Sometimes that’s the entire solution.

Find nothing wrong? Move to the next step.

How to Follow Up With Your AO the Right Way

Your message matters more than you think. A generic “What’s the status of my voucher?” lands in a pile of fifty identical messages — and gets treated accordingly. Be specific instead. Make the AO’s job easier, not harder.

Write something like this:

“SGT [Your Name] — I submitted voucher [number] on [date]. It’s still showing ‘In Review’ in DTS. I’ve already checked all receipts and line items against my authorization and everything looks correct on my end. Is there anything blocking approval that I can address? If not, do you have a rough timeline for when it might process? Thank you.”

That message signals that you’ve done basic troubleshooting already. You’re not asking your AO to solve a problem you could have solved yourself. You’re asking a direct question with a voucher number, a submission date, and a clear request. AOs respond to this faster — at least the ones I’ve worked with do.

Wait five business days before sending this. Not five calendar days. Business days. If it’s been longer than that, send it. If your AO doesn’t respond within three business days after that, escalate. Copy the finance office or your organization’s ODTA. Keep it professional: “SGT [Name] hasn’t responded to my status inquiry from [date]. I’m reaching out to make sure the voucher hasn’t fallen through the cracks.”

Don’t make my mistake — I waited almost the full two weeks before contacting anyone, assuming the system would sort itself out. It did not sort itself out.

When Finance or the ODTA Needs to Step In

Some holds are simply outside your AO’s authority to release. You’ll usually know because your AO will say so directly — something like “this one’s flagged for audit” or “finance put a routing hold on it.” Those are the moments to escalate deliberately rather than keep circling back to the same person who can’t actually help you.

Contact your finance office directly. Bring or reference the following:

• Your voucher number
• The original submission date
• A screenshot of the status screen showing “In Review”
• The specific hold type or flag your AO mentioned, if they told you

Say: “My voucher [number], submitted on [date], appears to have a system-level hold. Can you identify the hold type and give me a timeline for resolution?”

That question gets answered. A vague complaint about your voucher being stuck does not — at least not quickly.

If the finance office hits a wall, go to your ODTA. They handle vouchers that get wedged between departments. They have backend system access your AO doesn’t have. They can see audit queues, routing errors, and technical flags that are completely invisible at the unit level.

How to Prevent Your Next Voucher From Getting Stuck

That’s what makes a clean submission endearing to us — the fact that it just moves through the system without drama. Here’s how to keep it that way.

• Submit within five days of returning. The sooner it goes in, the sooner it moves. Older dates create more opportunities for something in the system to shift and break your claim before it’s approved.
• Attach receipts in the right format. JPG or PDF, under 2 MB per file. For lodging, use the itemized hotel folio — not the credit card charge summary from your bank app. For meals, make sure the receipt shows the amount, the date, and what was actually purchased. Blurry photos are the single most common cause of unnecessary holds.
• Spend 90 seconds comparing your authorization to every line item. Location names matter. Installation naming conventions matter. Dates matter. Per diem rates matter. I’m apparently detail-blind when I’m tired from travel, and a careful line-by-line comparison works for me while a quick skim never catches anything.
• Confirm your AO received the submission. Send a quick message the day after you submit: “Just confirming you received voucher [number]. Let me know if you need anything else from me.” Takes thirty seconds. Eliminates one entire category of mystery.

A stuck DTS voucher feels like a broken system — and sometimes it genuinely is one. But most of the time, it’s a blurry receipt or a $25 lodging discrepancy that takes five minutes to fix once you know where to look.