Records Management
UD/MIPS Key Supporting Document Storage (MARADMIN 601/24)
MARADMIN 601/24 directs upload of certified unit diary files and MILPAY key supporting documents into UD/MIPS within 5 working days of certification.
T&R Event Details
- Event Code
- 0111-PERA-2008
- Source Policy
- MARADMIN 601/24
- MOS Performing
- 0111, 0170
- Grades
- PVT, PFC, LCPL, CPL, SGT, SSGT
- Sustainment Interval
- 12 months
- Evaluation-Coded
- No
- Readiness-Coded
- No
Performance Steps (T&R)
- Certify the unit diary
- Gather every KSD substantiating the reported transactions
- Save each file in an un-editable, legible format
- Upload to the applicable unit diary in UD/MIPS under its source document tab
- Complete the upload within 5 working days of certification
- Verify the EDFR for the related MCTFS transactions
What MARADMIN 601/24 Directs
MARADMIN 601/24MARADMIN 601/24 directs IPACs and all unit diary reporting activities to upload certified unit diary files into UD/MIPS with all associated supporting documentation not resident or required in a Marine's OMPF. The message standardizes UD/MIPS as the central document repository (CDR) for MILPAY Key Supporting Documents (KSDs).
- Upload target is the applicable unit diary in UD/MIPS, under its respective source document tab.
- Files save in an un-editable format and remain legible enough to substantiate the reported transaction.
- Uploads complete within 5 working days after diary certification.
- The OMPF stays the record home for documents required in a Marine's official file. UD/MIPS holds the MILPAY KSDs the OMPF does not accept or require.
Why This Directive Exists
Audit findings drove the change. The FY18 and FY19 Notices of Finding and Recommendations identified internal control gaps for MILPAY KSDs. The Independent Public Accountant found the Marine Corps unable to demonstrate existence and completeness of KSDs supporting MILPAY transactions. Before this message, IPACs held those documents in local files under command-generated, non-standardized filing procedures. MARADMIN 015/20MARADMIN 015/20 established the OMPF field folder as the CDR for selected MILPAY KSDs as a compensating control. OMPF upload restrictions limited its reach, so 601/24 extends the CDR to UD/MIPS for everything else.
Active and Reserve Component MILPAY payments exceed seventeen billion dollars annually, more than half of the Commandant's annual financial outlays. Clean financial audits depend on a KSD backing every MILPAY transaction.
Performance Steps
Step 1 - Certify the Unit Diary
The upload requirement triggers at certification. Confirm the diary is certified before staging documents.
Step 2 - Gather the KSDs
Pull every document substantiating the transactions on the certified diary. Route documents required in the OMPF through the OMPF field folder per MARADMIN 015/20MARADMIN 015/20. Everything else supporting the diary goes to UD/MIPS.
Step 3 - Prepare the Files
- Save in an un-editable format.
- Confirm legibility. An unreadable KSD fails to substantiate the transaction and reads as missing during audit.
Step 4 - Upload to the Source Document Tab
Attach each KSD to the applicable unit diary in UD/MIPS under its respective source document tab. Attaching to the wrong diary breaks the transaction-to-document link auditors trace.
Step 5 - Meet the 5-Day Window
Uploads complete within 5 working days after certification. Track open uploads against the certification date.
Step 6 - Verify the EDFR
Pull the Electronic Diary Feedback Report and confirm the reported transactions processed per MCTFSPRIUMMCTFSPRIUM. The document upload and the MCTFS transaction are linked but separate. Both must succeed.
Common Errors
- KSD attached to the wrong unit diary. The document exists but auditors tracing the transaction find nothing. Re-attach to the certified diary reporting the transaction.
- Editable file format. Save as an un-editable format before upload.
- Illegible scan. Rescan until the document substantiates the transaction on its face.
- Upload past the 5 working day window. Track certification dates and close uploads inside the window.
- Document required in the OMPF uploaded only to UD/MIPS. OMPF-required documents follow the OMPF submission path. UD/MIPS holds the remainder.
Inspection Posture
Use of UD/MIPS to store MILPAY KSDs is an inspectable item for the Marine Corps Administrative Analysis Team (MCAAT), including MCAAT inspections conducted alongside Inspector General of the Marine Corps inspections. Manpower Strategy Branch (M&RA MX) and MCAAT are available for assistance with MILPAY and MILPERS audit readiness standards.
Command Accountability
Commanders at all levels retain accountability as the Commandant's direct representative for the accuracy of their Marines' personnel and pay records. Financially relevant updates must be timely, accurate, and complete.
Related Roles
- Marines confirm their pay-affecting documents reached their records through MOL.
- Leaders at S-1 stage supporting documents with the diary submission and confirm upload completion.
- Commanders own the accuracy of personnel and pay records and answer for KSD availability during audits.
Same topic, other roles
References
- MARADMIN 601/24 Directed Usage of UD/MIPS for Storage of Key Supporting Documents
- MARADMIN 015/20 OMPF Field Folder as the Central Document Repository
- MCO P1070.12 Marine Corps Individual Records Administration Manual (IRAM)
- MCTFSPRIUM Marine Corps Total Force System Personnel Reporting Instructions Users Manual
- DoDFMR Vol 1 General Financial Management Information, Systems and Requirements
Related Pages
- Admin
UD/MIPS Transactions Overview
same topic - same function - 3 shared references
- Admin
EDFR Processing and Failure Resolution
same topic - same function - 2 shared references
- Admin
Electronic Service Record (ESR) Management
same topic - same function - 2 shared references
- Admin
IRAM (MCO P1070.12) Overview
same topic - 2 shared references
- Admin
Records Disposition and Retention Schedules
same topic - 2 shared references