G00 BASICS
How often is it recommended that FMB work the G00?
At least weekly.
What system/reporting tool do we use to review the Travel ODL?
Travel ODL Stats.
Who should you contact to determine whether the travel actually occurred?
The RA and/or traveler.
TRUE OR FALSE: Writing “Emailed traveler” is enough documentation by itself.
FALSE. The annotation should document the action/follow-up and relevant date.
The G00 shows an old travel obligation. What's the FIRST basic question you need answered?
Did the travel actually occur?
What is the main purpose of reviewing the G00/Travel ODL?
To identify and research outstanding travel obligations and determine whether they are still valid or require action.
Where does FMB pull the G00 report used to work outstanding travel documents?
AFAFO / Power BI using the applicable G00 travel report.
Who should be involved in G00 cleanup besides FMB?
Unit RAs and unit leadership.
What's one important date that should be documented when contacting a traveler?
The date the traveler was contacted.
The traveler says, “Yes, I went TDY.” What should you check next?
Research whether the final voucher was filed/processed using Power BI, DTS, and/or FM Workflow/RTS.
According to DoD FMR Vol 3, Ch 8, who is responsible for reviewing obligations?
The Funds Holder.
What does the Travel ODL Stats page default to?
AMC OAC 65.
According to the training, who may receive ODLs greater than 60 days from the Comptroller Commander?
Unit Commanders.
The traveler isn't responding. Give ONE acceptable follow-up action that could be documented.
Contact the supervisor, First Sergeant, Commander, or other appropriate unit leadership.
The travel DID occur, but you're researching a manually created obligation. What important information should you compare?
Make sure the TANUM/order number in DTS/RTS matches what is in DEAMS.
What are the three main places listed in the training that you can research to determine whether a final voucher was filed?
Power BI, DTS, and FM Workflow/RTS.
What DTS information has been incorporated into Power BI so you can identify statuses such as CTO Cancelled, Created, and Rejected?
DTS Routing Status Report data.
A manual travel order was cancelled. What must FMB obtain before deobligating the funds?
A cancellation amendment.
You submitted a DEAMS, DTS, or DFAS-LI ticket. What TWO things should your annotation capture?
The ticket/case number AND date submitted.
The travel DID NOT occur and it's a DTS document. What's your first course of action?
Exhaust the available DTS options to complete the trip cancellation process.
At the end of the review, who signs the report and who certifies it?
The technician signs it and the supervisor certifies it.
Power BI identifies a trip where the DTS trip dates don't match the accounting information. Why might that happen?
The trip may have been extended, and DEAMS does not systematically update from the DTS trip-date data.
You cannot deobligate a valid cancellation locally. Who may FMB need to submit an inquiry/request to?
DFAS-LI.
Spot the Better Annotation
Which is better?
A: “Waiting on traveler.”
B: “25 Aug – Contacted traveler; voucher not submitted. Follow-up sent to RA. Awaiting action.”
B.
Why? It tells the next analyst when, who, what happened, and what you're waiting on.
You find an aged manual travel obligation. The traveler confirms:
“Nope. TDY was cancelled.”
What's the basic process?
Verify the cancellation → ensure the cancellation amendment was completed → obtain the amendment → deobligate the funds from DEAMS/GAFS-BQ → if it cannot be deobligated locally, submit the appropriate DFAS-LI inquiry/request → document the action on the listing.