You can make topic area wider by clicking the X over the contents.
This section shows pay entitlements automatically stopped or started, upon approving and saving the Permanent Change Of Station departing transaction or reporting transaction. A program will update stop dates in the Entitlement row(s) in Direct-Access.
The SPO must not put a stop date in or modify the Entitlement row(s) for these items.
When you press 'Save' on the Departing or Reporting endorsement, stop dates are inserted in the appropriate entitlement. If you wipe that date out and then reenter a stop date you will be creating a stop transaction (P625). If you use the link to the entitlements summary from the PCS process and do not see the stop dates, you may need to exit the member's entitlement page and reenter (deferred processing). Due to deferred processing there is a delay before the system-generated stop entries will appear in the entitlements section.
Many times an SPO will approve a departing or reporting PCS endorsement, save it, then look at the member’s entitlement rows in Direct Access and it will look like the stop dates were not inserted when the endorsement was approved. This sometimes causes the SPO to attempt to insert the dates manually. If the dates do not show up in entitlements, click ‘Return to Search’ and then get back into the member’s entitlements summary. The dates will be inserted.
When an SPO inserts the date manually it is causing several problems.
When the auto stop function is allowed to work it does not create an audit record. Therefore no transaction is sent to JUMPS. If it is manually entered an audit record is created and will kick out on the exception report because the JUMPS auto stop program already closed the segments on the correct date.
There have been numerous occasions where the SPO entered an incorrect date when manually entering the dates, most frequently, when entering ENLBAS.
It is important to remember that the JUMPS auto stop program is shutting down the proper segments when the departing or reporting endorsement is transmitted to JUMPS.
The Direct Access auto stop function is inserting the dates to reflect what JUMPS is doing. No transaction is sent to JUMPS when these dates are inserted. Due to deferred processing there is a delay before the system-generated stop entries will appear in the entitlements section.
Please see the BAH During PCS topic on page 5 of the BAH Entitlement Guide and JFTR, U10416 (Chapter 10). Table U10E-12 for more information on BAH entitlements for members departing or reporting PCS.
The SPO does not need to manually adjust PPC Auto Stops of entitlements if the member's departure or report date is changed after the endorsement is approved and saved.
There are times when a departing and reporting endorsement have been approved and the SPO has to change the departure date later. For instance, after the member reports it is discovered that the member left at a later date, but the previous SPO was unaware of the change. When the departure date is changed, the entitlements rows do not always reflect the new date. Sometimes the stop date will reopen but nothing is inserted to reflect the new date. The resync program will take care of inserting the date after the update cycle runs. If an SPO tries to manually adjust these dates, audit records are created, which is confusing when they hit the exception report.
Remember, when the departing or reporting endorsement processes, it causes the segments to adjust the member’s PCS entitlements. The only time an SPO should change the stop date inserted by the Direct Access auto stop function is if the member’s entitlement actually changed on a different date. For instance, once the departing endorsement is completed, an SPO may receive notification the member checked out of government quarters prior to the departure date. The stop date should be changed so a new row can be inserted for the new BAH entitlement.
The following pay entitlements will automatically be stopped in JUMPS upon successful processing of a PCS departing transaction. Direct-Access entitlement rows will by updated by the system after the PCS departing transaction is approved and saved.
The SPO must not put a stop date in or modify the Entitlement row(s) for these items.
If you use the link to the entitlements summary from the PCS process and do not see the stop dates, you may need to exit the member's entitlement page and reenter in order to see the changes. Due to deferred processing there is a delay before the system-generated stop entries will appear in the entitlements section.
Entitlement |
Entitlement Stops |
BAH Without Dependents Note: See the BAH During PCS topic on page 5 of the BAH Entitlement Guide and JFTR, U10416 (Chapter 10). Table U10E-12 |
Effective 1 January 2006, BAH for members without dependents auto-stops effective the date of PCS departure. These members are entitled to BAH W/O while in transit and the system (JUMPS) will credit any BAH due when the reporting endorsement on orders transaction processes.
Previously, BAH W/O continued at the rate for the old permanent duty station (PDS) until the reporting endorsement on orders transaction processed. This logic was causing overpayments; particularly in cases were members were transferring to units where they were required to occupy government quarters or transferring from a high-cost/BAH area to a lower-cost/BAH area.
Recouping the overpayments, which were often a significant dollar amount because of the delay between the actual reporting date and the payroll processing cycle the reporting PCS transaction processed, adversely impacted members. |
Career Sea Pay (CSEAPAY) & Career Sea Pay Premium |
Effective the date of PCS departure. |
Special Duty Assignment Pay (SDAP) |
Effective the day prior to PCS departure. |
Diving Duty Pay |
Effective the date of PCS departure. |
Hardship Duty Pay Location (HDP-L) |
Effective the date of PCS departure. |
Imminent Danger Pay/Hostile Fire Pay Combat Tax Exclusion/Combat SGLI Allowance |
Effective the last day of the month of PCS departure. |
Responsibility Pay |
Effective the day prior to PCS departure. |
Aviation Crew / Non-Crew Pay (HDIP) |
Effective the date of PCS departure. |
Family Separation Allowance (FSA – S) |
Effective the date of PCS departure. |
Aviation Career Incentive Pay (ACIP) |
ACIP will stop on date of departure if the Continue ACIP checkbox is not selected on the Departing Endorsement Transaction |
Discount Meal Rate (BASDMR) |
Effective the day prior to PCS departure.
Note for BASDMR earn type: the stop date in the row is the day prior to depart. Even though that date is inserted, ENLBAS will remain open until report date in JUMPS. Direct Access isn't effecting the stops on PCS, the JUMPS auto stop program is still shutting down the entitlements just as it was in the past. |
When a member departs a BASDMR unit, the departing PCS transaction: (a) Stops the BASDMR row in Direct Access the day prior to departure PCS. (b) Shuts down segment 27 the day prior to departure PCS. (c) Inserts an ENLBAS row to start the day of departure PCS. (d) Keeps segment 24 running (because the member is entitled to ENLBAS while en route PCS). |
|
Family Separation Housing |
Effective the date of PCS departure. |
Overseas Housing Allowance (OHA) Note: See the BAH During PCS topic on page 5 of the BAH Entitlement Guide and JFTR, U10416 (Chapter 10). Table U10E-12 for more information.
Note: Elimination of 60-day Continuance Provision for OUTCONUS COLA and OHA
The JFTR has been modified to eliminate the 60-day continuance provision. Instead, the JFTR no provides that O’COLA and OHA shall terminate on the day prior to PCS departure (this includes departure on “terminal leave” ICW separation). The member may apply to COMDT (CG-1222) to have O’COLA and OHA paid/re-restarted at the dependents location if exigent circumstances require the member and dependent(s) to maintain separate households. SCP 35033 has been created to address the JFTR change in DA & JUMPS |
Effective the day prior to PCS departure
Note: DO NOT mark the ‘Continue OHA’ checkbox. See note on Elimination of 60-day Continuance Provision for OUTCONUS COLA and OHA. CG-1222 will forward approved requests for continuation of OHA/COLA to PPC (mas) for payment.
When members PCS from OUTCONUS and OHA stops, the SPO needs to start BAH TR for the effective the day of PCS departure. |
OUTCONUS COLA
Note: Elimination of 60-day Continuance Provision for OUTCONUS COLA and OHA
The JFTR has been modified to eliminate the 60-day continuance provision. Instead, the JFTR no provides that O’COLA and OHA shall terminate on the day prior to PCS departure (this includes departure on “terminal leave” ICW separation). The member may apply to COMDT (CG-1222) to have O’COLA and OHA paid/re-restarted at the dependents location if exigent circumstances require the member and dependent(s) to maintain separate households. SCP 35033 has been created to address the JFTR change in DA & JUMPS |
Effective the day prior to PCS departure.
Note: DO NOT mark the ‘Continue OHA’ checkbox. See note on Elimination of 60-day Continuance Provision for OUTCONUS COLA and OHA. CG-1222 will forward approved requests for continuation of OHA/COLA to PPC (mas) for payment.
|
The system inserts a BAH without dependents (segment 35) row to start the day of PCS departure for members without dependents assigned INCONUS who were receiving Partial BAH or no BAH at the old PDS
State Income Tax Withholding (SITW) auto starts on date of PCS reporting if member assigned to state that taxes military pay while member is stationed with the state. See State Tax Withholding Data Entry Procedures for more information.
The following pay entitlements will automatically be stopped in JUMPS upon successful processing of a PCS reporting transaction. Direct-Access entitlement rows will by updated by the system after the PCS reporting transaction is approved and saved.
The SPO must not put a stop date in or modify the Entitlement row(s) for these items.
If you use the link to the entitlements summary from the PCS process and do not see the stop dates, you may need to exit the member's entitlement page and reenter in order to see the changes. Due to deferred processing there is a delay before the system-generated stop entries will appear in the entitlements section.
Entitlement |
Entitlement Stops |
BAH With Dependents Note: See the BAH During PCS topic on page 5 of the BAH Entitlement Guide and JFTR, U10416 (Chapter 10). Table U10E-12 for more information. |
DA will insert a stop date effective the day prior to PCS reporting. However, JUMPS will continue to pay BAH-With until a new transaction is submitted reflecting the member's BAH entitlement at the new unit. |
BAH w/o Dependents Note: See the BAH During PCS topic on page 5 of the BAH Entitlement Guide and JFTR, U10416 (Chapter 10). Table U10E-12 for more information.
|
Effective 1 January 2006, BAH for members without dependents auto-stops effective the date of PCS departure. These members are entitled to BAH W/O while in transit and the system (JUMPS) will credit any BAH due when the reporting endorsement on orders transaction processes.
Previously, BAH W/O continued at the rate for the old permanent duty station (PDS) until the reporting endorsement on orders transaction processed. This logic was causing overpayments; particularly in cases were members were transferring to units where they were required to occupy government quarters or transferring from a high-cost/BAH area to a lower-cost/BAH area.
Recouping the overpayments, which were often a significant dollar amount because of the delay between the actual reporting date and the payroll processing cycle the reporting PCS transaction processed, adversely impacted members. Effective the day prior to PCS reporting
|
Partial BAH Note: See the BAH During PCS topic on page 5 of the BAH Entitlement Guide and JFTR, U10416 (Chapter 10). Table U10E-12 for more information. |
These members are entitled to BAH W/O while in transit and the system (JUMPS) will credit any BAH due when the reporting endorsement on orders transaction processes. |
ENLBAS |
Effective the day of PCS reporting. |
The table below describes how a Permanent Change Of Station can affect Overseas Housing Allowance (OHA), and Cost Of Living Allowance (COLA), and describes SPO action needed in conjunction with PCS.
Entitlement |
Automatic PMIS/JUMPS Action |
SPO Action Needed In Conjunction With PCS Departing |
SPO Action Needed In Conjunction With PCS Reporting |
Overseas Housing Allowance (OHA) |
The PCS Departing will automatically shutdown Overseas Housing Allowance effective the day prior to PCS departure.
Note: Elimination of 60-day Continuance Provision for OUTCONUS COLA and OHA
The JFTR has been modified to eliminate the 60-day continuance provision. Instead, the JFTR no provides that O’COLA and OHA shall terminate on the day prior to PCS departure (this includes departure on “terminal leave” ICW separation). The member may apply to COMDT (CG-1222) to have O’COLA and OHA paid/re-restarted at the dependents location if exigent circumstances require the member and dependent(s) to maintain separate households. SCP 35033 has been created to address the JFTR change in DA & JUMPS. CG-1222 will forward approved requests for continuation of OHA/COLA to PPC (mas) for payment. |
For members w/dependents, the SPO for the unit the member is departing from needs to start BAH TR (BAH Transit rate, formally BAH Type II) effective the day of PCS departure. The BAH TR will auto-stop effective the day prior to PCS reporting. The reporting SPO should start BAH TR, effective the day of PCS departure, and stop BAH TR, effective the day prior to reporting, for members without dependents |
If the member is entitled to OHA at the new duty station, a Start OHA (P609) transaction must be submitted. A lease agreement or mortgage is required before starting OHA.
For members administratively transferred within the same OHA-locale, select “Continue OHA” on the Reporting PCS. |
INCONUS COLA |
Members receiving INCONUS COLA at the old duty station will continue to receive it enroute. The PCS Reporting will automatically shutdown CONUS COLA the day prior to reporting, and also automatically reduces CONUS COLA for the number of days the member is in a travel status. |
|
A Start INCONUS COLA (P607) transaction must be submitted, effective the date of reporting PCS, to reflect the zip code of the member’s new duty locale. |
OUTCONUS COLA |
The Departing PCS will automatically shutdown COLA effective the day prior to PCS departure.
Note:
Elimination of 60-day Continuance Provision for OUTCONUS COLA and OHA
The JFTR has been modified to eliminate the 60-day continuance provision. Instead, the JFTR no provides that O’COLA and OHA shall terminate on the day prior to PCS departure (this includes departure on “terminal leave” ICW separation). The member may apply to COMDT (CG-1222) to have O’COLA and OHA paid/re-restarted at the dependents location if exigent circumstances require the member and dependent(s) to maintain separate households. SCP 35033 has been created to address the JFTR change in DA & JUMPS. CG-1222 will forward approved requests for continuation of OHA/COLA to PPC (mas) for payment. |
|
If the member is entitled to OUTCONUS COLA at the new duty station, a Start COLA (P607) transaction must be submitted. For members administratively transferred within the same OUTCONUS COLA-locale, select “Continue COLA” on the Reporting PCS. |