1 Terminal Learning Objective Action Process paying agent for FOO CERP OMA ARP amp Rewards Conditions FM Leaders in a classroom environment using doctrinal and administrative publications practical exercises personal experience handouts discussion and access to GFEBS ID: 724573
Download Presentation The PPT/PDF document "Describe the Pay Agent Process in GFEBS" is the property of its rightful owner. Permission is granted to download and print the materials on this web site for personal, non-commercial use only, and to display it on your personal computer provided you do not modify the materials and that you retain all copyright notices contained in the materials. By downloading content from our website, you accept the terms of this agreement.
Slide1
Describe the Pay Agent Process in GFEBS
1Slide2
Terminal Learning ObjectiveAction: Process paying agent for FOO, CERP, OMA, ARP & RewardsConditions: FM Leaders in a classroom environment using doctrinal and administrative publications, practical exercises, personal experience, handouts, discussion and access to GFEBS.
Standard
: Analysis includes:
- Create a vendor (employee) via transaction code XK01
- Create a MISC Pay PR&C via transaction code ME51N
- Verify availability of funds via transaction code ME53N
2Slide3
AgendaCreate a vendor (employee) via transaction code XK01Create a MISC Pay PR&C via transaction code ME51N Verify availability of funds via transaction code ME53N 3Slide4
Battle Drill 5:
Process (P2P) Paying Agent (PA) for Field Ordering Officer (FOO) (CERP), OMA,
&
Rewards Programs)
4Slide5
Legend
GFEBS
Operation
Create MISC Pay PR
ME51N
Verify availability of
funds
ME53N
XK01
Create a vendor
(employee)
5Slide6
Pay Agent (PA)PA is an extension of the DO at the unit levelPA is an individual who is trained by the DDO/DA to account for government funds and make payments in relatively small amountsPAs are individuals whose regular duties do not involve disbursing functionsPA is paired with an Project Purchasing Officer (PPO) and cannot be appointed as an PPOThe PA will not make payments without the express authorization from the PPOThe PA interacts with the DDO/DA on a routine basisIs usually a USG employee, however defense policies may allow for multinational members6Slide7
Commanders Emergency Response Program (CERP)Provide an immediate and measurable benefit to the local populationBe completed quicklyPromote local national employmentBe highly visible to the local populaceIncorporate host nation entities throughout the life of the project, from inception to turnoverBe sustained by the host nation after turnoverAccepted as beneficial by the local indigenous population7Slide8
Field Ordering Officer (FOO)Every FOO is paired with a Pay AgentAll purchases must be made as a teamFOO makes the purchase decisionA third party must receives the itemsThe FOO has the responsibility to fill out the SF 44FOO funds can be used for emergency purchasesCannot make purchases that are foreseeable or reoccurring8Slide9
Creating a Vendor Master Data Record LSA-19Slide10
XK01- Create Vendor (Employee)
XK01
1A2B4
2
Enter the appropriate “Vendor Account “Group if known or select the appropriate code
Note:
the most commonly utilized codes are “Z001” and “Z004”
1
Enter the Vendor CAGE to be processed
3
Select the most appropriate Account Group
Z005
4
Click “Enter” to start the Vendor Creation
10Slide11
9
Click “Next Screen”
XK01-
Create Vendor (Employee)
(Cont’d)
6
Name of Company
7
Search terms (able to search for this vendor by these terms). (Vendor CAGE code is recommended)
US Army
SFC Michael Wilson Employee 1
1A2B4
Vendor 1
8
Enter Company address information. Ensure the Country information is correct.
123
Mohamet
Street
Kabul
15
12345
5
Title will be “Company” unless it is an individual
“Address” Screen
AF
11Slide12
9
Click “Next Screen”
TIN (Taxpayer Identification Number) and Tax information is required for U.S. Vendors. If it is an individual, instead of company, the Social Security Number will be entered in these fields.
“Control” Screen
XK01-
Create Vendor (Employee)
(Cont’d)
12Slide13
AF
AFIBAFKA*
Enter the desired search string with wildcards “*” if needed to locate the Bank in the system (must be pre-loaded)
12
Once entered, click the checkmark to populate the “Bank Key” field
11
Select the appropriate “Bank Key” (SWIFT Code or ABA)
AFIBAFKA
13
Enter the correct bank account number
12345
10
Enter the appropriate “Country Code” for the Bank Location
Mukhar
Al
Saleem
“Payment Transactions” Screen (Bank Data)
XK01-
Create Vendor (Employee)
(Cont’d)
15
If provided, enter the type of account:
01- Checking
02- Savings
01
14
Enter the name of the bank Account “Beneficiary”. Must be based on the name the bank account is under (cannot me misspelled)
13Slide14
17
Click “Next Screen”
16
General ledger account to which transactions in the subsidiary ledgers (such as in the customer, vendor, or assets areas) are automatically updated. “2110.0100” is the most commonly utilized for CVS Vendors
2110.0100
“Accounting Information” Screen
XK01-
Create Vendor (Employee)
(Cont’d)
14Slide15
21
Click “Next Screen”
Z030
18
Enter the payment terms applicable to this vendor
19
Select the appropriate “Payment Method”. (GFEBS does not support Cash payments). EFT is the preferred method of payment in theater and GFEBS.
Note:
The Deployable Disbursing System (DDS) utilizes“ CTX (Corporate Trade Exchange) Format ACH” .
20
Click after selection is made
T
20
Place a checkmark here to ensure all invoices are checked for duplicates during entry
“Payment Transactions Accounting” Screen
XK01-
Create Vendor (Employee)
(Cont’d)
15Slide16
23
Click “Next Screen”
No Input necessary for a foreign vendor
No Input necessary for a foreign vendor
22
Enter the Currency the vendor is likely to be paid with
USD
“Correspondence Accounting, Withholding Tax Accounting, Purchasing Data” Screens
XK01-
Create Vendor (Employee)
(Cont’d)
16Slide17
24
The “Partner Functions” is the last data field. Click “Save” to record the vendor entry.
No Input necessary
19
The Vendor is now added to the GFEBS database and is ready to be utilized.
Note:
Vendor Master Data may be changed as needed. T-Code “
XK02
” will allow an authorized user to make adjustments to the record when applicable and when needed.
“Partner Functions” Screen and saving the Vendor data
XK01-
Create Vendor (Employee)
(Cont’d)
17Slide18
Create a Vendor (employee)LSA - 218Slide19
Battle Drill 5:
Process (P2P) Paying Agent (PA) for Field Ordering Officer (FOO) (CERP), OMA,
&
Rewards Programs)
19Slide20
XK01 – Create VendorSimulationThe instructor demonstrates this activity while you follow along Hands on ExerciseThe instructor will lead you step by step through the activity using the training materials provided20Slide21
Create a Miscellaneous Pay Purchase Requisition (PPA)LSA - 321Slide22
Battle Drill 5:
Process (P2P) Paying Agent (PA) for Field Ordering Officer (FOO) (CERP), OMA,
&
Rewards Programs)
22Slide23
ME51N – Create Purchase RequisitionSimulationThe instructor demonstrates this activity while you follow along Hands on ExerciseThe instructor will lead you step by step through the activity using the training materials provided23Slide24
Display a Miscellaneous Pay Purchase Requisition (PPA)LSA - 424Slide25
Battle Drill 5:
Process (P2P) Paying Agent (PA) for Field Ordering Officer (FOO) (CERP),
OMA,&
Rewards Programs)
25Slide26
ME53N – Display Purchase RequisitionSimulationThe instructor demonstrates this activity while you follow along Hands on ExerciseThe instructor will lead you step by step through the activity using the training materials provided26Slide27
Check on Learning
What
t-code is used to create a vendor(employee)?
2.
Which account group are employees and individuals assigned to?
How
do you verify that funds has been added to conduct the PA mission?
27Slide28
Questions?27