PeopleSoft G-Invoicing Business Processes

PeopleSoft provides integration that supports the G-Invoicing Requesting Agency intra-governmental Procure-to-Pay business process.

The G-Invoicing Procure-to-Pay process includes several APIs and processes in PeopleSoft as well as some manual steps as shown below.

G-Invoicing Procure-to-Pay Process

G-Invoicing Procure-to-Pay process
Stage G-Invoicing Steps PeopleSoft Steps

1. GT&Cs

GT&Cs are entered directly into G-Invoicing.

A select set of GT&C fields are pulled into PeopleSoft through GT&C API.

2. Orders

Orders are entered manually into G-Invoicing.

High level key fields are pulled into PeopleSoft through Order API.

Purchase Orders are manually entered into PeopleSoft and reference G- Invoicing GT&C and Order numbers at the header level. Purchase Order lines and schedules must reference G-Invoicing order line and schedule line numbers exactly.

3. Performance Transactions

  

Performance transactions are pulled into PeopleSoft or pushed into G-Invoicing using the Performance API.

4. 7600EZ

Select 7600EZ as Business Application on the Header Details.

All new G-Invoicing APIs will employ a push/pull model utilizing REST services.

Purchasing Receipt transactions in PeopleSoft are optional.

Purchase Orders are manually entered into PeopleSoft with reference G- Invoicing GT&C.

Order number is not applicable.

Advance payments (‘548’)

Entered into G-Invoicing by the seller.

See PeopleSoft Payables: U.S. Federal G-Invoicing Processing for more information.

Adjustments to advances (negative ‘548’)

Entered into G-Invoicing by the seller.

SeePeopleSoft Payables: U.S. Federal G-Invoicing Processing for more information.

Delivered/performed transactions (‘035’)

Entered into G-Invoicing by the seller.

Delivered/Performance transactions are loaded as Advanced Shipping Notices (ASNs) using the Pull Performance API.

ASNs can be built into Receipts by Load Receipts and are then created as vouchers by Payables.

Received/accepted transactions (‘050’)

Received from PeopleSoft using API.

Received/accepted transactions are created from Receipts by the requester and pushed back to G-Invoicing using the Push Performance API.

Adjustments to received/accepted transactions (negative ‘050’)

Received from PeopleSoft using API.

These adjustments are created from Receipts and Return to Vendor transactions by the requester and pushed back to G-Invoicing through the Push Performance API.

Adjustments to delivered/performed transactions (negative ‘035’)

Entered into G-Invoicing by the seller.

Negative delivered/performed transactions are received through Pull Performance API. These transactions must be reviewed and handled manually in PeopleSoft.

Deferred payment transactions (‘014’)

Entered into G-Invoicing by the seller to communicate the amount/percentage of work completed for work in progress transactions.

Deferred payment transactions are received through Pull Performance API. They are stored for informational purpose only.

4. Funds Settlement

G-Invoicing initiates funds transfers using IPAC.

See PeopleSoft Payables: U.S. Federal G-Invoicing Processing for more information.