PPC Logo

USCG Pay & Personnel Center             

KNOWN ISSUE in mLINQS

There is currently a known issue in mLINQS FSC is working on.  The error is being caused when an amendment is done in mLINQ that removes the expense lines that had a payment processed against it for an advance and another amendment is processed to add the expenses back in. This action creates duplicate lines in FSMS and produces a “fetch error” as FSMS does not know how to process against the multiple lines due to a payment being tied to one. There is currently a SNOW ticket open at FSC Tier 3/FSMS.

ATTENTION - E2 USERS

Single sign on (CAC) for E2 is currently causing profiles issues. Please refrain from using and/or creating CAC E2 profiles until further notice. Using the user name and password (historical E2 log on process) should be used at this time, at E2 User ID and password

ETS ERROR

ETS is currently producing an error when creating new accounts or updating user IDs/EMPLIDs to current accounts, please submit a PPC ticket for these members so that the issues can be fixed individually. A system wide fix is still trying to be worked. If a member who does not have an ETS account is needing to book upcoming travel with a departure date within the next 3-5 days, they will need to call the TMC/SATO to make any reservations and insist that the booking be made without a profile.

With the ongoing issue in E2 that prevents new user accounts from being created, if any of the impacted members have had to call the TMC to make reservations without a TMC profile, please submit a PPC Customer Care Ticket including the following information below. PPC is working with E2 programmers/contractors to track this issue as well as reduce the TMC fees for those impacted due to the systematic issue.

Member Name, Rank, and EMPLID:

Reservation Confirmation Code:

Travel Dates:

Duplicate Relocations Found in mLINQS from Unauthorized Manual Entries

There have been several duplicate PCS relocations found in mLINQS causing a plethora of issues.

AO’s and/or proxies should NOT be entering relocations manually in mLINQS without contacting PPC first (customer care ticket) as relocations should be processed from DA to mLINQS. Below are the steps to take if a relocation has not processed from DA to mLINQS.

If the PCS relocation has been put in a “ready” status in DA and is not found in mLINQS :

  1. Contact PPC customer care via trouble ticket subject “re-submit to mLINQS” and PPC will manually re-submit this relocation over to mLINQS.
  2. If PPC cannot process this relocation over to mLINQS due to a systems error, we will work with the AO on manual entry.
  3. Relocations input using the legacy process should still submit a ticket to finish those claims using the legacy process calculator method. Only if they have already started using the legacy process.
  4. Any manual input relocations into mLINQS outside of this process will require an AO/proxy re-training and possible revocation of elevated permissions.

RETIRED PAY 

PPC is addressing a processing delay due to systematic issues and a shortage of personnel. This is causing a delay in response efforts for VA offsets, AEWs, CRDP, and CRSC disability. You remain our primary concern. We want to assure you that we are fully committed to resolving these issues promptly and handling your cases with utmost care and accuracy. 

PPC Page Menu
Redirecting...
Contact Us

 

PPC Customer Service Feedback

 

PPC Mailing Address:

Commanding Officer (RAS)
U.S. Coast Guard 
Pay & Personnel Center
444 S. E. Quincy St.
Topeka, KS 66683-3591


Customer Support Telephone: 

PPC Customer Service

Personnel/Administrative Issues (not related to DA technical issues).

(866) 772-8724
7:30AM - 4:00PM (Central time) M-F

C5I Service Center Product Support Service Desk

Assistance with Password Resets, Logon Assistance, or Other DA Technical Issues. 

(800) 821-7081
6:30AM - 6:30PM (Eastern time) M-F


E-Mail:

PPC Customer Service: PPC-DG-CustomerCare@uscg.mil 

C5I Service Center: SMB-USCG-KerWV-ProductSupportSD@uscg.mil 


PPC Web Content Manager 

Feedback button

ALCGFINANCE 028/25 SUBJ: GUIDANCE FOR TEMPORARY DUTY TRAVEL ORDERS CROSSING FISCAL YEARS

PRINT  |  E-MAIL

R 141233Z AUG 25 MID180001944614U 
FM COMDT COGARD WASHINGTON DC 
TO ALCGFINANCE 
BT 
UNCLAS 
ALCGFINANCE 028/25 
SUBJ: GUIDANCE FOR TEMPORARY DUTY TRAVEL ORDERS CROSSING FISCAL YEARS 
REF: (A) FY25 FINANCIAL MANAGEMENT AND REPORTING CLOSEOUT GUIDANCE, 
ALCGFINANCE 027/25 
1. This guidance shall be used for temporary duty travel chargeable to single 
year appropriations that crosses fiscal years (FY). Specifically, this applies 
to cases where advanced preparation in FY25 is required to effectively
facilitate travel in FY26. FY25 travel is any that occurs on or before 
30 September 2025. FY26 travel is any that will occur from 
01 October 2025 through 30 September 2026. 
2. For travel attributable to a single-year appropriation that begins in FY25 
and crosses into FY26: 
a. Do NOT obligate anticipated FY26 enacted funds in FY25. 
CG-83 will distribute FY26 funding to projects and tasks (POETs) 
only after a Continuing Resolution is enacted, at which time FY26 
obligations can be made. 
b. Airfare and Rental Cars fully reserved and paid to SATO: FY25 
funds may pay for the entire reservation, to include round-trip 
flights, even if the return flight or rental car return occurs in 
FY26. One-way fares are charged to the FY in which the 
travel occurs, with exception to travel occurring in the first 
week(s) of FY26, per paragraphs 4 and 5. 
c. Per Diem/Lodging/Incidentals: The FY25 portion of these travel 
expenses must be charged to the FY25 POET, while the portion of 
these travel expenses occurring in FY26 must be charged to the FY26 
POET. 
d. Enter the following in the travel order remarks: "Full 
transportation expenses are authorized on the FY25 POET. All other 
related expenses from the date of travel through 30 September 2025 
are authorized to be charged to the FY25 POET. All travel expenses 
from 01 October 2025 through the end of travel will be charged to 
the FY26 POET subject to an approved appropriation and budget 
authority." 
e. In ETS: No later than 30 September 2025, all FY26 travel portions 
must be set to "no entitlements" to ensure FY25 funds are not 
charged for FY26 entitlements. After 30 September, amend the 
original travel authorization with the FY26 POET and fund the FY26 
entitlements. 
3. For multi-year appropriations with periods of availability extending 
into Budget Fund Year (BFY) 26, travel obligations are permitted 
throughout the appropriation's period of availability. 
4. Paragraph 10.a. of reference (A) is amended as follows, pertaining to 
CONUS travel attributable to single year, expiring appropriations, with 
travel commencing 01 through 07 October (inclusive) 2025: 
a. Due to airfares being charged at the time of ticket issuance, full 
roundtrip airfare may be charged to the FY25 POET to ensure a timely 
reservation and availability. 
b. All other travel entitlements, including rental cars, shall be 
charged to the FY26 POET and funded accordingly upon receipt of 
budget authority. 
5. Paragraph 10.a. of reference (A) is amended as follows, pertaining to 
OCONUS travel attributable to single year, expiring appropriations, 
with travel commencing 01 through 21 October (inclusive) 2025: 
a. Due to airfare being charged at the time of ticket issuance, 
and the significant lead time necessary to reserve international 
airfare, full round-trip airfare may be charged to the FY25 POET 
to ensure a timely reservation and availability. 
b. All other travel entitlements, including rental cars, shall be 
charged to the FY26 POET and funded accordingly upon 
receipt of budget authority. 
6. Direction during a Lapse in Appropriations: 
a. In the event of a lapse in appropriations, members will cancel 
their travel unless it meets one of the excepted/exempted missions 
outlined in the Consolidated Lapse in Appropriations Guidance, 
located at: 
https://uscg.sharepoint-mil.us/sites/CGCC/Appropriations_Lapse. 
Upon cancellation, the SATO airfare fee will still be paid using 
funding from the FY in which the travel obligation was created. 
b. Travelers in a travel status will await further instruction as 
whether to return to unit or remain in place. 
7. Only obligate the required FY25 portion of all TDY travel. Do not 
charge FY26 expenses to FY25 when entering travel in ETS. 
8. Except in emergent cases, all FY25 obligations must be 
entered into ETS. No unobligated or unfunded Direct Access open 
authorizations or group authorizations are authorized in ETS after 
25 September 2025. 
9. For deferred travel or travel which starts in FY25, travelers 
should submit a travel voucher for FY25 expenses incurred as 
soon as is practicable. Per reference (A), all travel actions, 
including approval of travel vouchers and funding for travel 
authorizations (TAs) must be completed by 25 September 2025 
to be processed in FY25. Upward adjustment voucher payments 
submitted after this date will not be paid out until approximately 
30 days after the financial system is restored. No increases in FY25 
authorizations/obligations can be transmitted prior to 15 October 
2025. Vouchers that are more than the authorization must be 
adjusted before 25 September 2025 to ensure funds are 
obligated and the voucher is paid while the system is online. 
10. For travel authorizations utilizing FY26 POETs of organizations 
that have recently been renamed (i.e. DCS, District Oceania): 
a. Members shall utilize the new Organization Codes populated in 
ETS, where applicable. 
b. Legacy Organization Codes that are not authorized for use 
in FY26 will be labeled with 'DNU' at the beginning of the 
Organization name. 
c. All travel authorizations previously submitted for FY26 travel 
must be re-submitted in a new authorization using the new 
Organization Code. Do not attempt to edit previously approved 
FY26 authorizations to change the Organization Code, 
a new authorization is required. 
11. During FSMS shutdown period (01 October - 05 October), 
hold all travel authorizations in ETS at the AO level. This will 
prevent errors and incorrect payments. When FSMS comes back online, 
AOs can then approve authorizations for payment in FSMS. 
12. For more information regarding ETS, please visit: 
https://www.dcms.uscg.mil/ppc/travel/ets2/ or email the Travel 
Management Office at
HQS-SMB-CG-1332-TravelManagementOƯice@uscg.mil
13. POC: For more information regarding TDY travel preparations, 
contact LCDR Kellen Browne, Acting CG-833 or 
Mr. Edward Soriano, CG-PSC-BOPS-R. 
14. CAPT P. J. Granati, Office of Resource Management (CG-83), sends. 
15. Internet release is authorized. 
BT 
#0001 
NNNN