Collect Grant/Project Expenditures is the process that takes place in the Project Costing module. Actual expense might need to be tracked and billed depending on the terms in conditions identified in the contract.  

**Important Tip** In order to show the true business process please share the Project ID number(s) and Activity ID(s) to your colleagues who are testing the Purchasing and Travel modules; so they can create transactions that you can later invoice.

To use this UAT guide first review the business process flow diagram below, which outlines the various steps to complete the test activities. Note that the business process flow diagram has distinct places where one can start testing this process, noted by a green 'Start' circle. Use the diagram, following the arrows to each step that must be executed. Use the Quick Reference Guide (QRGs) links, also below, to find the instructions on how to execute each step. The Quick Reference Guides are numbered to match each box on the flow diagram to assistant testers with following the flow of the business process.  Once testing is complete for each box on the flow diagram, click the link in the Next Step (Tier 2) in the High Level UAT Framework section to access the next UAT Guide.

Printable View of Ff.002.3 Collect Grant/Project Expenditures

• FF.002.3.1  Cost Collection Process:
  • Process to be run by State Board
• FF.002.3.2 Create an Interface ID:
  • Create an Interface ID (Reimbursable)
  • Create an Interface ID (Fixed Price)

• Process As Incurred Billing
  • Process Billing for "As Incurred" or Reimbursable Contracts
• Process Other Billing (Fixed Price Contract)
  • Process Billing for "Other" or Fixed Price Contracts

• Process As Incurred Billing:
  • Error Condition: If the date of the invoice has no billable lines then a worksheet will not be produced.
    • Expected Behavior: No invoice will be produced.
  • Error Condition: If all of the billable lines in the designated parameter are already on an invoice, no invoice will be produces as not to bill twice.
    • Expected Behavior: Interface ID will produce an error
  • Error Condition: If a billable line is on an Interface ID then you can not create another Interface ID with the same billable lines.
    • Expected Behavior: An Interface ID will not be created, you will receive a warning message.
• Process Billing for "Other" or Fixed Price Contracts:
  • Error Conditions: If the event date is not designated in the Contract then an invoice will not be produced  
    • Expected Behavior:  A warning message will occur, with no results produced.                                                                                                                                                                                                                          

UAT- FF.002 Grant/Non-Grant Billing to GL (Cost Collection) Part 2