A new federal payment rule turns a routine Perkins V draw into a short compliance exercise. Beginning November 1, 2026, the U.S. Department of Education says its G5 payment system will require a written justification for every Department of Education grant payment request. The justification must fit within 255 characters and include the grant program, expense categories and amounts, the earliest and latest expense dates, and no personally identifiable information.
That applies to Pennsylvania career and technical education administrators who request Perkins V funds. The deadline is close enough that a district finance office should test the handoff now, before a coordinator discovers that a useful explanation cannot fit the required field.
What changed in the federal payment workflow?
The Department of Education’s September 28, 2026 memo, titled “Mandatory Written Justifications for Payment Requests to Implement Executive Order 14222,” describes the new G5 requirement. The memo names Perkins V as an example of a grant program that must appear in the justification. It does not describe a new Perkins allocation formula. It changes the information required when a grantee asks for payment.
The required entry has four practical parts:
- The name of the grant program, such as Perkins V.
- The expense categories and dollar amounts that add up to the payment request.
- The earliest and latest dates covered by those expenses.
- No personally identifiable information, or PII, in the 255-character field.
The character limit is the operational problem. A finance reviewer may understand a long explanation, but G5 will not accept one if the required entry exceeds the limit. A district can have complete backup documentation and still fail to meet the memo’s submission standard if the short justification is incomplete or exceeds the limit.
The memo is a federal administrative requirement, not a recommendation. Its effective date is November 1. As of October 18, 2026, administrators have a limited testing window to identify who drafts the justification, who verifies the numbers, and who submits the request.
Why Pennsylvania programs should treat this as a local workflow issue
Pennsylvania is not waiting for a new investment before it manages its Perkins process. The Pennsylvania Department of Education’s Perkins page lists tentative 2026–27 secondary allocations totaling $34,046,448. It lists $6,237,599 for Philadelphia City School District.
Those figures matter because they show the scale of the workflow. Perkins funds support programs across districts and career and technical centers, but the federal payment request still moves through a specific finance process. A short field in G5 now has to connect a local expense record to a federal grant request without exposing student or employee information.
PhillyCTE’s read: the new rule makes the Perkins-to-finance handoff part of program operations, not a final clerical step. A CTE director may own the spending plan, a Perkins coordinator may know the program purpose, and a fiscal agent may submit the draw. If those three roles use different labels or date ranges, the request can become difficult to explain in 255 characters.
The same issue applies outside Philadelphia. A Pennsylvania district, intermediate unit, or career and technical center should not assume that a finance office will infer the program connection from a purchase order. The justification needs a repeatable format that the people approving the expense and the people submitting the request can both recognize.
What the new rule does not answer
The Department of Education memo identifies the required payment-request justification. It does not, by itself, decide whether a particular purchase is an allowable Perkins expense. Administrators still need to use the applicable Perkins rules, Pennsylvania guidance, local application, procurement controls, and district review process when they decide whether to charge an expense to the grant.
That distinction matters for budgeting. The memo creates a documentation test, not a blanket approval for equipment, supplies, contracted services, or other costs. A clean 255-character sentence cannot make an otherwise unallowable expense allowable. It only explains a request that has already passed the program and fiscal checks.
It also does not authorize staff to put student names, identification numbers, medical information, or other personal details into the field. The memo’s no-PII instruction should be treated as a design constraint. If a reviewer needs more detail, the district should use its approved supporting records and secure process rather than placing personal information in the payment justification.
What this means for your program
Pennsylvania CTE administrators can take four steps before the November 1 effective date:
- Map the handoff. Write down who identifies the Perkins expense, who confirms the category and amount, who checks the expense dates, who removes PII, and who submits the G5 request. If one person holds every role, document that too.
- Create a 255-character template. Use a neutral structure such as: “Perkins V | [category]: $[amount] | [earliest date]–[latest date] | [second category]: $[amount].” Treat it as a drafting aid, not a replacement for required records.
- Run a dry run outside G5. Use a recent, already-approved expense and check whether the category labels, totals, and dates match the finance system. Count characters before the first live request. Do not use student or employee names in the test text.
- Add the check to the local calendar. The Perkins coordinator and fiscal agent should review the process before the first affected draw. Keep a record of the test and any correction. If the district is unsure how the memo interacts with Pennsylvania guidance, ask PDE or district counsel rather than guessing.
These actions require coordination more than new spending. They also avoid a common failure: making the CTE office responsible for facts it cannot see, or making finance staff responsible for program labels they were never given.
The good, the bad, what’s best?
The good news is that the rule is specific. Administrators know the effective date, the character limit, the required content, and the PII restriction. That gives districts a concrete workflow to test.
The bad news is that the limit leaves little room for vague prose. A request that says only “Perkins supplies” may not identify the expense categories, amounts, or date range the memo requires. A request that includes too much detail may expose PII or exceed 255 characters.
What is best is a short, shared template backed by the district’s existing records. Do not treat the field as the entire audit file. Treat it as a precise index into the approved documentation already held by the program and finance teams.
Test the Perkins-to-finance handoff before November 1
The first useful action is not rewriting every local application. It is running one approved Pennsylvania Perkins expense through the complete workflow: program review, fiscal review, character count, PII check, and G5 preparation. That test will show whether the people, labels, dates, and records line up before the new federal payment requirement is active.
Sources
- U.S. Department of Education, “Mandatory Written Justifications for Payment Requests to Implement Executive Order 14222,” September 28, 2026. Accessed October 18, 2026. https://careertech.org/wp-content/uploads/2026/10/Defend_the_Spend_September_28_2026_Memo.pdf
- Pennsylvania Department of Education, “Perkins.” Accessed October 18, 2026. https://www.pa.gov/agencies/education/programs-and-services/instruction/career-and-technical-education/perkins
Last verified: October 18, 2026.
