1. Process Non-Prompt Payment Act Documents
Show Slide # 1: Process Non-Prompt Payment Act Documents
References: DFAS-IN REG 37-1, DODFMR R, VOL 5 , FM 1-06
4 hours
Facilitator Material: Each primary facilitator should possess a lesson plan, slide deck, course handouts, and practical exercise, DFAS-IN REG 37-1, DODFMR R, VOL 5, and FM All required references and technical manuals will be provided by the School House
Learner Material: Learners should possess standard classroom supplies, course handouts, practical exercises, DFAS-IN REG 37-1, DODFMR R, VOL 5, and FM 1-06FM. All required references and technical manuals will be provided by the School House.
Facilitator Actions: Classroom Setup 5 minutes, Classroom Breakdown 2 minutes
Testing Requirements/Assessment:
learners will be assessed using “Go” or “No Go” on Professional Development and Leadership during the Capstone Exercise.

2. TERMINAL LEARNING OBJECTIVE
Action: Process Non-Prompt Payment Act Documents
Conditions: FM Leaders in a classroom environment working as a member of a small group, using doctrinal and administrative publications, self-study exercises, personal experiences, practical exercises, handouts, and discussion.
Standards: With at least 80% accuracy (70% for international Learners) you must:
Analyze the miscellaneous payment process
Demonstrate How to Enter Data into Vendor Invoice (FB60)
Demonstrate How Attach Document(s) to Invoice (FB60)
Prepare a Block (Manual) Invoice (FB02)
Show Slide # 2: TLO
Action: Process Non-Prompt Payment Act Documents
Conditions: FM Leaders in a classroom environment working as a member of a small group, using doctrinal and administrative publications, self-study exercises, personal experiences, practical exercises, handouts, and discussion.
Standards: With at least 80% accuracy (70% for international Learners) you must:
Analyze the miscellaneous payment process
Navigate a Vendor Invoice (FB60)
Demonstrate How Attach Document(s) to Invoice (FB60)
Prepare a Block (Manual) Invoice (FB02)
Safety Requirement: In a training environment, leaders must perform a risk assessment in accordance with DA PAM , Risk Management. Leaders will complete a DD Form 2977 DELIBERATE RISK ASSESSMENT WORKSHEET during the planning and completion of each task and sub-task by assessing mission, enemy, terrain and weather, troops and support available-time available and civil considerations, (METT-TC). Local policies and procedures must be followed during times of increased heat category in order to avoid heat related injury. Consider the work/rest cycles and water replacement guidelines IAW TRADOC Regulation
Risk Assessment Level: Low
Environmental Consideration: Environmental protection is not just the law but the right thing to do. It is a continual process and starts with deliberate planning. Always be alert to ways to protect our environment during training and missions. In doing so, you will contribute to the sustainment of our training resources while protecting people and the environment from harmful effects. Refer to FM Environmental Considerations and GTA ENVIRONMENTAL-RELATED RISK ASSESSMENT.
Instructional Lead-In: Today, it is essential that all Soldiers (CVS Clerks assigned to specific roles) are able to log into GFEBS, research regulations and specific links to accurately input documents to receive and accept goods or services, to monitor the transactions for accuracy, and to input the documents in preparation for pay. Processing documents without error will prevent delays in accounts being settled and reconciled. This class will prepare you to successfully accomplish the tasks listed.

3. Concrete Experience http://www.youtube.com/watch?v=KeZl_LSbML8
Show Slide #3: Concrete Experience
Concrete Experience (5 minutes)
Facilitator’s Note: (Facilitator read and facilitate discussion using the slide)
The cell phone has evolved throughout the years. You have a choice now to purchase a contract, no contract,
locked, or unlocked cell phone. This clip will show one persons opinion about a particular no contract cell phone.
**Play the video and gather some of the Learners opinions, after watching the video.***
Facilitator’s Note: No contract cell phones are an example of a service not subject to the prompt payment act. Prompt Payment rules does not apply. There are no late interest penalties for payments. Early payments are not mandatory. There is not a guidance on when to make payments. Your payments are based on your(the customer needs). For example, $35 could get you 500 minutes, 500 text, 500mb of data and a $55 can get you unlimited everything.
Publish and Process (10 Minutes)
Facilitator’s Note:
What is the importance of inspecting the items that are being delivered?
Give examples of different ways goods or services can be accepted. Example: Purchasing food, gas, or shoes etc. Starting a new cell phone contract. Purchasing a car.
Have you ever ordered a package, arrived home and your package is placed on your step, porch, or by the mail box? If so, “Did you accept these goods?” What could happen if the package was stolen? Are you responsible?
Having the Learners think critically is the ultimate goal of publish and process. Force the Learners to explain their answers; meaning, how and why did they arrive at the solution to the questions.
You should also be looking for responses that will help the Learners transition from publish and process to generalize new information. During this process, remind the Learners of lesson objectives as they transition from publish and process into generalize new information.

4. Miscellaneous Payment Process
(Non-PPA)
FMY1
Pre-Commit
FB03
View
FMZ1
Commit
Non-PPA
Process
Show Slide #4: Miscellaneous Payment Process
1. Learning Step/Activity #1 Analyze the Miscellaneous Payment Process
Method of Instruction: DSL (large or small group discussion)
Facilitator to learner Ratio: 1:30
Time of Instruction: 30 minutes
Media: Slides, Printed Reference Materials
Facilitator's Note: Before facilitating this lesson, ask the learners which of the 21st Century Soldier Competency do they think pertain to this lesson? Facilitate a discussion on the answers given and at the end of the lesson revisit it and see if the learners still believe their choice are the same.
1. Character and accountability
2. Comprehensive fitness
3. Adaptability and initiative
4. Lifelong learner (includes digital literacy)
5. Teamwork and collaboration
6. Communication and engagement (oral, written, and negotiation)
7. Critical thinking and problem solving
8. Cultural and joint, interagency, intergovernmental, and multinational competence
9. Tactical and technical competence (full spectrum capable)
Facilitator’s Note: Facilitate discussion using the slide on the Miscellaneous Payment Process
Facilitator’s Note: Remind the Learners that the FMY1 (Pre-commitment) and the FMZ1 (Commitment) was done in the previous lesson.
During this learning activity we will start with the FB60 (Enter Vendor Invoice) and end with the FB03 (View Invoice) process for the non-PPA.
FB02
Attach File
/Block
FB60
Post
Invoice
FB03
View

5. Miscellaneous Payment Process (Non-PPA) Cont.
A miscellaneous payment invoice is an invoice that does not reference a purchase order or contract. These obligations of the government are generated by a variety of obligating documents or agreements. Some miscellaneous payments are subject to the Prompt Payment Act (PPA); but the majority of miscellaneous payments fall in the (non-PPA) group. Those that are not subject to PPA can be processed through the Enter Vendor Invoice (FB60) transaction with reference to a Funds Commitment Document (FMZ1).
Show Slide #5: Miscellaneous Payment Process (Non-PPA) Cont.
Facilitator’s Note: (Facilitator read and facilitate discussion using the slide)
There is no government form or contract for many of the utility bills the government is obligated to pay. For other obligations, such as training; a government form generates an obligation for the government to reimburse the vendor who delivers the training. Additional examples include tuition reimbursements, legal claims, attorney fees, etc.

6. User Role: Site Invoice Processor
The Site Invoice Processor responsibilities include the following:
Receiving and entering miscellaneous payment invoices that have to be processed manually.
Entering credit memos.
Posting vendor down payments;
Releasing invoices that are blocked for payment in GFEBS.
Show Slide #6: User Role: Site Invoice Processor
Facilitator’s Note: (Facilitator read and facilitate discussion using the slide)
Facilitator’s Note: Inform the Learners that they will see the five key areas when they log into the training environment and walkthrough the transaction with the instructor. 6

7. GFEBS Miscellaneous Pay Process
A Miscellaneous Payment Invoice transaction should not be processed in GFEBS unless correct and complete supporting documentation is received. In general, the existing paper-based process relies on expenses being claimed via the following:
The Site Invoice Processor records the obligation and enters the invoice into GFEBS.
The Site Invoice Processor provides DFAS with the signed, certified, misc. payment document Public Voucher for Purchases and Services Other Than Personal (SF1034) via fax.
Payments are placed on a pay proposal by the DFAS Payment Processor
DFAS Certifier ensures that the Army Site Invoice Processor has properly transcribed the data from the document into GFEBS and selected the proper payment path (non-PPA vs. PPA)
DFAS Certifier validates the SF1034 against the DD577 on file with the Disbursing Office (via electronic Document Access)
Show Slide #7: GFEBS Miscellaneous Pay Process
Facilitator’s Note: (Facilitator read and facilitate discussion using the slide)
This is the complete process of entering and certifying the invoice. Inform the Learners that a Miscellaneous Payment Invoice. Transaction should not be processed in GFEBS unless correct and complete supporting documentation is received.
A Miscellaneous Payment Invoice transaction should not be processed in GFEBS unless correct and complete supporting documentation is received. In general, the existing paper-based process relies on expenses being claimed via the following:
The Site Invoice Processor records the obligation and enters the invoice into GFEBS.
The Site Invoice Processor provides DFAS with the signed, certified, misc. payment document Public Voucher for Purchases and Services Other Than Personal (SF1034) via fax.
Payments are placed on a pay proposal by the DFAS Payment Processor
DFAS Certifier ensures that the Army Site Invoice Processor has properly transcribed the data from the document into GFEBS and selected the proper payment path (non-PPA vs. PPA)
DFAS Certifier validates the SF1034 against the DD577 on file with the Disbursing Office (via electronic Document Access)

8. LSA #1 Check on Learning Show Slide #8: LSA #1 Check on Learning
Facilitator’s Note: Ask the following Question; (Facilitate discussion on answers given)
Q1. Explain what is a miscellaneous payment invoice?
A1. A miscellaneous payment invoice is an invoice that does not reference a purchase order or contract

9. LSA #1 Summary Show slide #9: LSA #1 Summary
Facilitator’s Note: In this lesson, we Analyzed the Miscellaneous Payment Process.

10. Enter Vendor Invoice (FB60)
Purpose
Use this procedure to manually enter a Misc. Pay not subject to PPA invoice
(e.g. utility bill).
Trigger
Perform this procedure when you need to manually enter a Misc. Pay not
subject to PPA invoice. Examples include, but not limited to: Utility payments,
clothing, tuition reimbursement, training requests, and legal claims and fees.
Prerequisites
A funds commitment document referenced by the invoice. (FMZ1)
Show Slide #10: Enter Vendor Invoice (FB60)
2. Learning Step/Activity #2 Navigate a Vendor Invoice (FB60)
Method of Instruction: DSL (large or small group discussion)
Facilitator to learner Ratio: 1:30
Time of Instruction: 45 minutes
Media: Slides, Printed Reference Materials
Facilitator’s Note: Before you move to the next slide inform the Learners that you will now cover inputting the FB60. This is instructor-led, while walking through the process, the Learners will follow along in the Training Environment. At this time have the Learners log into the training environment for GFEBS.
Facilitator’s Note: (Facilitator read and facilitate discussion using the slide)
For Misc. Pay not subject to PPA invoices, refer to the Online Help Procedure: Enter Vendor Invoice (FB60). This same transaction may be used to manually enter a credit memo against a Contractual invoice. If the Soldier is assigned to a CVS Battle Team their position will be a Commercial Vendor Service (CVS) Technician with an assigned role as a Site Invoice Processor.

11. (FB60) Cont. Enter Vendor Invoice 1 2 3
Enter the Invoice receipt date and Invoice date (Today’s Date) Note: Use Dropdown.
Enter or locate the appropriate “Vendor” code
Utilize the Invoice Number as the “Reference”
(this is your initials and birth date (JF1226) 1 2 3
3DS82
07/10/2014
07/10/2014
JF1226
Show Slide #11: Enter Vendor Invoice (FB60) Cont.
Facilitator’s Note:(Facilitator navigate the learners through the steps and facilitate discussion):
Use the “"page down"” key to navigate through the steps. You will need to do this for all the transaction code demonstrations.
The process will start by typing FB60 in the field next to ”Menu” key. As you go through the slides read the appropriate notes and remind the Learners
to follow along with you in the Training Environment.

12. (FB60) Enter Vendor Invoice 4
Click on the “Document Type” option. This code will establish if the transaction will be processed and approved manually (will not need to be approved by a second party in GFEBS - Misc. Pay Approver) or if it will initiate the GFEBS Workflow for the Miscellaneous Pay Approver to certify the transaction prior to payment. The main two types utilized for this type of transaction (FB60- Miscellaneous Pay Non-PPA) are:
MP-Doc Type: this option will trigger the workflow process by automatically blocking the invoice (M-Block) until it is certified by the Miscellaneous Pay Approver and ultimately paid.
KR-Doc Type: this option will allow the transaction to be paid without certification in GFBES but a manually certified SF 1034 will have to be submitted to the paying office prior to payment.
FB60
3DS82
07/10/2014
07/10/2014
JJF1226 4
Show Slide #12: Enter Vendor Invoice (FB60) Cont.
Facilitator’s Note:(Facilitator navigate the learners through the steps and facilitate discussion):
Use the “"page down"” key to navigate through the steps. You will need to do this for all the transaction code demonstrations. Continue the process with Step 4.

13. (FB60) Enter Vendor Invoice
In the event that “Document Type” does not show (below the posting date), execute the following steps:
Menu – Settings – Editing Options – Doc Type Hidden – Entry with short name.
FB60
3DS82
07/10/2014
07/10/2014
JJF1226
Show Slide #13 :Enter Vendor Invoice (FB60) Cont.
Facilitator’s Note:(Facilitator navigate the learners through the steps and facilitate discussion):
Use the “"page down"” key to navigate through the steps. You will need to do this for all the transaction code demonstrations. This slide is to inform you what you will need to do if the “Document Type” does not show.

14. Enter Vendor Invoice (FB60) 5 6 Click on the “Payment” tab
3DS82
JJF1226
Ensure the correct “Payment Method Supplement” is reflected. This code is “Location Based” and is utilized for reporting purposes
Examples: AF- Bagram
AG- Kandahar
KQ-Kuwait
Show Slide #14 :Enter Vendor Invoice (FB60) Cont.
Facilitator’s Note:(Facilitator navigate the learners through the steps and facilitate discussion):
Use the “"page down"” key to navigate through the steps. You will need to do this for all the transaction code demonstrations. As you go through the slides read the appropriate notes.
Select the appropriate Payment method. EFT (“T”) or Check (“C”) are the preferred methods
Select the appropriate payment terms. Consult the DoD Miscellaneous Payment Guide for the correct terms 5 6 T

15. Enter Vendor Invoice (FB60) 7 9 8 10
Enter the FMZ1 (Commitment/ Obligation) document number and press “Enter”. Will auto-populate the applicable accounting data
FB60 10
Enter the “invoiced amount”
3DS82 7
JF1226
Enter the Commitment Item utilized in the Commitment/ Obligation (FMZ1).
It should be part of the line of accounting used on the payment document
Show Slide #15:Enter Vendor Invoice (FB60) Cont.
Facilitator’s Note:(Facilitator navigate the learners through the steps and facilitate discussion):
Use the "page down" key to navigate through the steps. You will need to do this for all the transaction code demonstrations. As you go through the slides read the appropriate notes.
18750
Scroll to the right to and locate the “Earmarked Funds” column
Enter the Payment Document dollar amount 9 8 B
18750

16. Enter Vendor Invoice (FB60) 11
Click “Simulate” to verify all input data.
Although not a requirement (the user may Click “Post” and bypass this option) it is a function that allows the user to view the effects and accuracy of the input
Click “Post” to ensure the transaction is saved and that it is posted against the Obligation. 11
FB60 10
3DS82
JJF1226
Show Slide #16:Enter Vendor Invoice (FB60) Cont.
Facilitator’s Note:(Facilitator navigate the learners through the steps and facilitate discussion):
Use the "page down" key to navigate through the steps. You will need to do this for all the transaction code demonstrations. As you go through the slides read the appropriate notes. B
18,500.00

17. LSA #2 Check on Learning Show Slide #17: LSA #2 Check on Learning
Facilitator’s Note: There is no Check on Learning for this LSA.

18. LSA #2 Summary Show slide #18: LSA #2 Summary
Facilitator’s Note: In this lesson, we navigated through a Vendor Invoice (FB60)

19. Attach Document(s) to Invoice (FB02)
Show Slide #19: Attach Document(s) to Invoice (FB02) 3. Learning Step/Activity #3 Demonstrate How to Attach Document(s) to Invoice (FB60)
Method of Instruction: DSL (large or small group discussion)
Facilitator to learner Ratio: 1:30
Time of Instruction: 45 minutes
Media: Slides, Printed Reference Materials
Facilitator’s Note: Inform the Learners that we will be covering the Change Document User Procedure (FB02). Any changes to a manual invoice will be done using the FB02. For this FB02, we will be attaching supporting documents.
Facilitator’s Note: Have the student(s) create a generic word document on their desktop. This will be used to attach for the FB02

20. Attach Document(s) to Invoice (FB02)
The Site Invoice Processor can change miscellaneous payment
invoices that have been posted (using the FB60 transaction) by
using the Change Document (FB02) transaction. GFEBS prevents
the data in certain fields of a posted document from being
changed.
This includes: Posting Amount, Account, Posting Key,
Fiscal Year, and Tax Amount. These fields cannot be changed,
because they have updated certain account balances during
posting.
Show Slide #20: Attach Document(s) to Invoice (FB02) Cont.
Facilitator’s Note: (Facilitator read and facilitate discussion using the slide)
Inform the Learners that if changes are made the Site Invoice Processor must satisfy certain conditions imposed by GFEBS. This is necessary to prevent any changes to documents that could result in the undesired manipulation of data, which would then make reconciliation impossible.
If you need to explain reconciliation, explain that reconciliation refers to the process of ensuring that two sets of records (usually the balances of two accounts) are in agreement. Reconciliation is used to ensure that the money leaving an account matches the actual money spent, this is done by making sure the balances match at the end of a particular accounting period.

21. Attach Document(s) to Invoice (FB02)
Use this procedure where policy dictates the need to attach the physical documentation to the Invoice transaction (either MIRO, FB60 or FB65). Only the “Site Invoice Processor” should execute this action. Attaching the document creates an outstanding audit trail for future reference and for the researching of similar payments against a particular contract.
Show Slide #21: Attach Document(s) to Invoice (FB02) Cont.
Facilitator’s Note: (Facilitator read and facilitate discussion using the slide)
Inform the Learners that in GFEBS Production (live system) this process must be accomplished within 15 minutes of posting the invoice transaction. Failure to do so may result in unnecessary delays and work. Use this procedure where policy dictates the need to attach the physical documentation to the Invoice transaction (either MIRO, FB60 or FB65).

22. Attach Document(s) to Invoice FB02
Purpose
Use this procedure to attach supporting documents to the invoice. Supporting
documents are an essential part of the certifying process.
Trigger
Perform this procedure when you want to attach supporting documents, change only
Certain accessible information, such as the document header text, the reference
number, or the reason code for such things as discounts not taken or lost on an
invoice that has been posted using the FB60 transaction.
Prerequisites
Processed Invoice using the FB60 transaction.
Role Requirement
Must be assigned the role of Site Invoice Processor
Show Slide#22: Attach Document(s) to Invoice (FB02) Cont.
Facilitator’s Note: (Facilitator read and facilitate discussion using the slide)
Read the purpose, trigger, and prerequisites. Inform the Learners that when researching this transaction in the PSW, the FB02 will be listed as Chang Document User Procedure. Before you move to the next slide inform the Learners that you will now cover the FB02. This is instructor-led. While the instructor is walking through the process, the Learners will follow along in the Training Environment. At this time have the Learners log into the training environment for GFEBS.

23. Attach Document(s) to Invoice FB02
Click the “Services for Object” button
FB02
Enter the “FB60” invoice document number
2014
Enter the Fiscal Year (FY)
Show Slide#23: Attach Document(s) to Invoice (FB02) Cont.
Facilitator’s Note:(Facilitator navigate the learners through the steps and facilitate discussion)
Use the "page down" key to navigate through the steps. You will need to do this for all the transaction code demonstrations. As you go through the slides read the appropriate notes, If there are not any notes inform the Learners to select the highlighted (numbered) information.
Hover over the “Create…” option then click on the “Create Attachment” option

24. Attach Document(s) to Invoice FB02
Select the location of the file to be attached
From the location of the file, either double-click or single-click the file to be uploaded and click “Open”
Show Slide#24: Attach Document(s) to Invoice (FB02) Cont.
Facilitator’s Note:(Facilitator navigate the learners through the steps and facilitate discussion)
Use the "page down" key to navigate through the steps. You will need to do this for all the transaction code demonstrations. As you go through the slides read the appropriate notes, If there are not any notes inform the Learners to select the highlighted (numbered) information.

25. LSA #3 Check on Learning Show Slide #25: LSA #3 Check on Learning
Facilitator’s Note: Ask the following Questions; (Facilitate discussion on answers given)
T-Code FB60 is used to ______ a vendor invoice?
Display
Delete
Enter
Exit
True or False: As per the payment method, the EFT (“T”) or
Check (“C”) are the preferred methods.
True
False
By clicking the “Simulate” button on the menu bar, this action:
Checks the document for completeness and accuracy
Generates a new document number
Checks the Validity of the EDI user

26. LSA #3 Summary Show slide #26: LSA #3 Summary
Facilitator’s Note: In this lesson we navigated through to attach document(s) to invoice (fb02).

27. Block (Manual) Invoice (FB02)
Show Slide 27: Block (Manual) Invoice (FB02)
4. Learning Step/Activity #4: Prepare a Block (Manual) Invoice (FB02)
Method of Instruction: DSL (large or small group discussion)
Facilitator to learner Ratio: 1:30
Time of Instruction: 30 Minutes
Media: Slides, Printed Reference Materials
Facilitator’s Note: The block invoice (FB02) is used for invoices that were input manually by the Site Invoice Processor. We have covered the block for the contractual invoices in the previous lesson utilizing the MIRO. Make sure the Learners know the difference in the FB02 and the MIRO (block).

28. Block (Manual) Invoice (FB02)
An Invoice is Blocked (Changing an Invoice Document) in GFEBS for the purposes of precluding the system from retrieving the transaction from being part of a Payment Run. Blocked invoices must be monitored closely to ensure they do not incur interest when the contract is subject to the Prompt Payment Act (PPA) and to avoid unnecessary delays in the payment process for those that are not.
An Invoice may be manually blocked or GFEBS may block it automatically due to imbalances through established system variables. Once an Invoice is Blocked, it must be Released either automatically or manually.
Show Slide 28: Block (Manual) Invoice (FB02) Cont.
Facilitator’s Note: (Facilitator read and facilitate discussion using the slide)
The FB02 is titled “Change Document”. One of the changes that can be done using the FB02 is to Block a invoice.

29. Block (Manual) Invoice (FB02)
The following personnel will have the ability to execute the transactions covered in this block of instructions based on their assigned position and GFEBS Roles:
CVS Technician
CVS Analyst
Show Slide 29: Block (Manual) Invoice (FB02) Cont.
Facilitator’s Note: (Facilitator read and facilitate discussion using the slide)
Although the CVS Technician and the CBS Analyst have the ability to Block an Invoice from payment, the transaction may be “viewed” by all the CVS Battle Team members.

30. Block (Manual) Invoice (FB02)
Click the “Save” button
FB02
The “executable areas” went from gray to white. Processor can change;
Click the “Change Display/Change Mode” in order to execute blocking procedures.
Double-click “Line item1 on the below screen “Posting Key” code 31
Payment terms from 30 days
Payment method (cash, check, etc.)
Show Slide #30: Block (Manual) Invoice (FB02) Cont.
Facilitator’s Note:(Facilitator navigate the learners through the steps and facilitate discussion)
Use the "page down" key to navigate through the steps. You will need to do this for all the transaction code demonstrations.
As you go through the slides read the appropriate notes.
Click in the “Pmnt Block box to initiate dropdown B
Select (click) the block reason.

31. View Invoice Status ( block/attachment) FB03
Notice the processor is now in “Display” mode.
FB03
Click the “Services for Object” button
Double Click the desired file or Click the “Display” button (glasses) to view the document
Once again, enter the invoice number and fiscal year (FY). If unknown, do a search. Click “Enter”
Click the “Attachment List” button
Double click “Line Item 1” to view the Block status.
2014
Processor views all information for accuracy, and ensures the “Pmnt Block” status reads “B” for Block.
Show Slide #31: Block (Manual) Invoice (FB02) Cont.
Facilitator’s Note: When transactions are put into GFEBS, they can be viewed for accuracy or for general information about the Invoice.
To utilize this function input the View Invoice Status (FB03).
Facilitator’s Note:(Facilitator navigate the learners through the steps and facilitate discussion)
Use the "page down" key to navigate through the steps. You will need to do this for all the transaction code demonstrations. As you go through the slides read the appropriate notes, If there are not any notes inform the Learners to select the highlighted (numbered) information.

32. Reverse Document (FB08)
If the Site Invoice Processor has entered an incorrect miscellaneous payment invoice,
he/she can reverse it, thereby also clearing the open items. The Site Invoice Processor
uses the Reverse Document (FB08) transaction to reverse a miscellaneous payment
invoice. A miscellaneous payment invoice can only be reversed if: 
It contains no cleared items
It contains only vendor and G/L account items
All entered values are still valid
Note: A contractual invoice (MIRO) cannot be reversed using the FB08 transaction,
but with the MR8M transaction.
Show Slide #32: Reverse Document (FB08)
Facilitator’s Note: We will not be doing a transaction for the FB08. The Training Environment will not allow this t-code it can only be done in
Production (live system). A contractual invoice (MIRO) cannot be reversed using the FB08 transaction. The FB08 is for manual invoices. In the previous lesson we used the MR8M to reverse the contractual invoice. ** Make sure the Learners understand the difference in the FB08 and the MR8M. **

33. LSA #4 Check on Learning Show Slide #33: LSA #4 Check on Learning
Facilitator’s Note: Ask the following Questions; (Facilitate discussion on answers given)
Instructor Note: The questions below are only examples. As the instructor you are free to ask varied questions. However, ensure the questions are open-ended and serve to ensure the Learners see the relevance of the generalized new information presented and future usage.
This phase is student-centered and instructor facilitated. Allow the Learners to decide how they will use the information. The definitive goal is for the Learners to think critically and creatively about how to use the information garnered from the lesson plan in the future. As the instructor you can direct the Learners to brainstorm in small groups or you can ask open ended questions such as:
Name and identify the difference in a manual invoice and a contractual invoice. Give one example for each type of invoice.
If a service has been performed and you fail to inspect, “What are some issues that could occur?”

34. TERMINAL LEARNING OBJECTIVE
Action: Process Non-Prompt Payment Act Documents
Conditions: FM Leaders in a classroom environment working as a member of a small group, using doctrinal and administrative publications, self-study exercises, personal experiences, practical exercises, handouts, and discussion.
Standards: With at least 80% accuracy (70% for international Learners) you must:
Analyze the miscellaneous payment process
Demonstrate How to Enter Data into Vendor Invoice (FB60)
Demonstrate How Attach Document(s) to Invoice (FB60)
Prepare a Block (Manual) Invoice (FB02)
Show Slide #34: TLO Summary
Facilitator’s Note: Read TLO
Action: Process Non-Prompt Payment Act Documents
Conditions: FM Leaders in a classroom environment working as a member of a small group, using doctrinal and administrative publications, self-study exercises, personal experiences, practical exercises, handouts, and discussion.
Standards: With at least 80% accuracy (70% for international Learners) you must:
Analyze the miscellaneous payment process
Navigate a Vendor Invoice (FB60)
Demonstrate How Attach Document(s) to Invoice (FB60)
Prepare a Block (Manual) Invoice (FB02)
“Or”
Facilitator’s Note: During and throughout the lesson we have covered how to analyze the miscellaneous payment process, how to enter data into vendor invoice (FB60), how to attach documents to invoice (FB60), and how to prepare a block (manual) invoice (FB02) which we can put that in action through the assessment at the conclusion of this lesson with the PE scenario with review and input form the class and facilitators.
Facilitator's at this time, have one learner from each group to explain the most important take away to them from this lesson. Facilitate a discussion on each answer.

35. Non-PPA Practical Exercise FB60
Show slide #35: Non-PPA Practical Exercise FB60
Facilitator’s Note: In this activity, the Learners will input the FB60. The Learners should log into the GFEBS Portal and Training Environment.
Use the data sheet included in the course packet to complete the activity. If questions arise that do not pertain to the scenario, address them after
the hands-on training. Explain to participants the resources they have available to complete the activity. 15