Procure to Pay

A table covered with papers with three people's hands pointing to various items.

APO, PO Buyers, Procurement Approvers, and Procurement Requesters : Use this page to find GA@WORK Procurement Learning Programs, review instructor-led training opportunities, access job aids, and locate support resources.

Learning Programs

APO

PO Buyer

Procurement Approver

Procurement Requester

Job Aids

Create Return to Supplier Event

Created: 6/15/2026

This job aid will show Requesters and PO Buyers the steps to create a Return to Supplier Event, an optional business…

Close Requisition

Created: 6/15/2026

This job aid will show Requesters how to Close a Requisition in the new GA@WORK requisitions system.

Find a Requisition

Created: 6/15/2026

This job aid will assist Buyers with the process of locating a Requisition in the new GA@WORK system.

To help you get started, we've highlighted a few job aids that support key procurement tasks in GA@WORK. Don't see the one you need? Use the link below to access a searchable list of all job aids.

View All Job Aids for Procure to Pay

Crosswalk and Change Impact

Key Changes

For agencies electing to opt in, auto-sourcing will be enabled for catalog requisitions only. Agencies electing to auto-source catalog requisitions will have requesters select a catalog requisition type to enable auto-sourcing. Agencies also can elect to opt out.
Submitting a requisition now creates a pre-encumbrance (commitment) against the budget, providing earlier visibility into budget impacts.
The requisition business process is standardized and automated, reducing manual ad-hoc routing and aligning with GA@WORK capabilities.
Future training for requesters will be online, making it easier for more staff to gain requester access.
Approval processes for requisitions are standardized across agencies.
Buyers have improved search capabilities and greater visibility into requisition details.
The number of PO types is reduced for simplicity and consistency.
The PO business process is more extensive and matches requisition approvals, with automatic approval if the PO matches the requisition.
Standardized change reason codes are required for change orders and returns.
Users can no longer split general ledge r(GL) accounts at the line level; instead, new lines must be created for each GL account.
Cardholders must manually select their p-card when creating requisitions; card information no longer auto-populates.
Purchase orders and requisitions will now follow a new numbering system.
All fully approved requisitions will now pre-encumber funds and reduce your available budget.

Benefits

Increased efficiency and accuracy through automation and standardization
Earlier visibility into budget impacts and commitments
Reduced manual effort for approvals and sourcing
Improved reporting and auditability with standardized codes and processes
Easier onboarding and training for new requesters
Custom validations to support compliance
User-friendly search options for easy navigation
Enhanced reporting with dashboards, visuals, and notifications

Crosswalk

Topic	Initiate/complete in legacy system by:	Initiate/complete in GA@WORK by:	Special notes:
Requisition Approval Routing	Approval routing was often manual or ad-hoc, with external requests required for over-limit or special approvals. Tracking was inconsistent.	Approval workflows are automated and standardized. Requisitions exceeding dollar limits or thresholds are routed to applicable approvers, all within the system.	Improves auditability and compliance. Eliminates need for email or paper-based approval requests. Approvers receive system notifications and can track status in real time.
Requisition Type Selection	No field for requisition type; all requests treated similarly, making reporting and automation difficult.	Requesters can select from predefined requisition types (e.g., catalog, non-catalog), enabling auto-sourcing (for agencies opting in) and better reporting.	Required for catalog requisitions to enable auto-sourcing (for agencies opting in) Supports improved data analytics and process automation. New field may require user education and validation rules.
Requisition and Purchase Order Numbering Sequences	Current numbering begins with agency code and preceding zeros and then PO number.	Requisitions and PO numbering will now begin with agency code followed by “REQ” or “POR” and then the number with no preceding zeros. For instance, 40300POR5.	Eliminates preceding zeros before requisition and PO numbers.

Instructional Videos

How to Create a Receipt

How to Create a Requisition

Procure to Pay

Learning Programs

APO

eLearning Courses:

PO Buyer

eLearning Courses:

Procurement Approver

eLearning Courses:

Procurement Requester

eLearning Courses:

Job Aids

Create Return to Supplier Event

Close Requisition

Find a Requisition

Crosswalk and Change Impact

Key Changes

Benefits

Crosswalk

Instructional Videos