IPPS-A Walkthrough: Absence, PARs, Records, and Approval Queues
IPPS-A is the Army HR system that now sits between soldiers and a lot of basic life admin: absence requests, personnel action requests, records, orders-adjacent workflows, pay-impacting data, and leader approvals. The trick is knowing whether you can fix the issue, your S-1 can fix it, or the transaction is stuck behind a role/permission problem.
Educational guide based on public IPPS-A and Army sources. IPPS-A workflows change often; use your unit S-1, HR professional, or Talent Readiness Administrator for account-specific actions. Last verified: July 7, 2026.
How to handle IPPS-A
Log in through the right door
Self-service users should use the soldier-facing IPPS-A login. Elevated users and HR professionals use the HR production site. If you are a civilian or sister-service user supporting an Army organization, you may need a TRA to add you as a person of interest and assign roles.
Start with the public job aid for the exact action
The official Training Aids page breaks tasks into self-service, leader, HR professional, and quick-sheet resources. Use the specific job aid for absence, BAH certification, personnel records review, records update, DD214, or monitor approvals before guessing through menus.
Capture the transaction before you ask for help
Write down the action type, transaction ID if shown, current status, current approver, date submitted, and any error text. Take screenshots that do not expose unnecessary PII. This turns a vague complaint into something S-1 can route or research.
For absence, verify the routing path before resubmitting
If leave or pass is not moving, check whether it is saved as draft, submitted, returned, or sitting with a specific approver. A duplicate absence request can create more cleanup work than the original delay.
For record problems, separate IPPS-A from iPERMS
IPPS-A displays and routes personnel data, but documents may still live in iPERMS or need HR validation. If a board file or record brief is wrong, ask whether the source document is missing, the source document is present but not reflected, or the IPPS-A field itself is wrong.
For BAH or pay-impacting data, escalate earlier
BAH certification, dependency changes, duty status, and pay-affecting personnel data are not harmless UI problems. Give S-1 the official document set, transaction proof, and date the pay impact started.
The problems people actually search for
My absence request is stuck and nobody can see it.
Usually means: It is a draft, it routed to the wrong approver, the approver position is not mapped correctly, or a leader has visibility without the approval role.
Move: Open the request and capture status, submitted date, approver name/position, absence dates, and transaction ID. Send that to your first-line leader and S-1. Ask for routing repair, not a policy explanation.
My supervisor changed, but IPPS-A still sends actions to the old person.
Usually means: The real chain of command and the IPPS-A position/role structure are out of sync. This is common after PCS, task org changes, detachments, and command transitions.
Move: Give S-1 the soldier name, UIC, current supervisor, old approver, and screenshot of the approval path. The fix is position/role mapping, not another absence request.
My record review will not validate or my board file is wrong.
Usually means: The source document may be missing from iPERMS, the data field may be wrong in IPPS-A, or the record is waiting on HR validation.
Move: Split the issue into document missing, document present but not reflected, or field value wrong. Attach the source document and say exactly which section/field needs correction.
BAH recertification or dependency data is wrong.
Usually means: IPPS-A, DEERS, finance, and source documents may not agree. Pay-impacting data needs cleaner evidence than a normal admin ticket.
Move: Build a packet with DA/branch-required forms, marriage/birth/divorce documents as applicable, lease/address proof if required, DEERS status, IPPS-A screenshot, and LES showing the pay impact.
A PAR was returned with a vague comment.
Usually means: The reviewer saw a missing document, wrong action type, wrong effective date, or local SOP issue but did not write a usable correction note.
Move: Reply with the returned comment, your intended action, the supporting document, and a direct question: "What exact field or attachment must change before I resubmit?"
The mobile app or self-service screen shows less than the HR person sees.
Usually means: Self-service, leader, and HR professional views are different. Some actions are role-gated or only visible in elevated access.
Move: Do not argue from screenshots alone. Ask the role holder what status they see in elevated view and get the next required action in writing.
Where people usually get stuck
The action exists on your screen but never entered the workflow.
The request routed to an old supervisor, empty position, or person without the right approval role.
A leader or clerk can see a soldier but cannot take the action.
A document exists somewhere, but the visible IPPS-A record still looks wrong.
Build the proof packet before you escalate
- Screenshot of the IPPS-A action showing status, action type, current approver, and submitted date.
- Transaction ID or request number if IPPS-A displays one.
- Exact effective date, requested start/end dates, or record field that is wrong.
- Source document: orders, DA form, marriage certificate, birth certificate, divorce decree, certificate, award, school document, or signed memo.
- For pay-impacting issues: the LES month where the error appears, expected entitlement, and date the entitlement should have started or stopped.
- For routing issues: old approver, correct approver, UIC, position title, and whether the soldier recently PCS-ed, changed platoons, or changed duty status.
Things that make the problem worse
Who can actually fix it
Immediate supervisor
For absence and routine PAR visibility, first ask whether the action is visible in the leader approval queue.
Unit S-1 / HR professional
For stuck routing, returned actions, record corrections, dependency/pay-impacting data, and role questions.
Talent Readiness Administrator or unit IPPS-A access manager
For role, permission, and access problems where the user can log in but cannot perform the required action.
IPPS-A help desk / official support path
For confirmed system errors, known-issue behavior, or account access failures your local role holders cannot fix.
Copy/paste messages that get cleaner answers
Stuck absence request
Subject: IPPS-A absence request stuck - routing check needed Requesting help with an IPPS-A absence request that appears stuck. Soldier: [rank/name] UIC/unit: [UIC/unit] Absence dates: [dates] Submitted: [date/time] Current IPPS-A status: [status] Current approver shown: [name/position] Correct approver should be: [name/position] Screenshot attached: yes Can S-1 verify whether this is a draft/submission issue, an approver mapping issue, or a role/routing issue?
Record correction / board file issue
Subject: IPPS-A record correction request - source document attached I need help correcting the following record item before [board/deadline/event]. Incorrect field/section: [field] Current value shown: [value] Correct value: [value] Source document attached: [document name] Document is/is not in iPERMS: [status] IPPS-A screenshot attached: yes Please advise whether this requires an IPPS-A update, iPERMS upload, HRC action, or another PAR type.
Fast answers
Is IPPS-A the same as iPERMS?
No. IPPS-A is the Army HR transaction and personnel data system. iPERMS is the official military personnel records document repository. Many record problems involve both.
Why can my leader not approve my request?
Usually routing, role assignment, or position mapping. The leader may be correct in the real chain of command but not correctly mapped in IPPS-A.
Should I delete and resubmit a stuck action?
Only after S-1 or the responsible HR professional tells you to. Duplicates can create conflicting requests or pay-affecting cleanup.
What should I send S-1?
Action type, date submitted, current status, current approver, transaction ID if available, screenshots, and the official document that supports the request.