a. Protocol Parameters

TABLE OF CONTENTS

1. Hover over Financials Menu > Financials Console
2. Enter protocol number into Select Protocol Field
   1. This is a filter as you type field so options will narrow the more characters you include
3. Scroll to the bottom of the page and click "Update"

Budget Related Parameters

1. Navigate to the first block in the financials console's main page to enter the Budget Related Parameters
2. Select a Rate Base from the first drop down menu - this is an OnCore required field
   1. Options for WashU's rate bases are:
      1. FED-Federal
      2. FOUNDATION-Foundation
      3. IND-Industry
3. Select the Default Sponsor from the second drop down menu and select the main financial sponsor for that protocol
4. In the Sponsor Settings section, there is a spot to enter a Withholding % if the sponsor will withhold any payment until a later date.

WARNING: If you use withholding in OnCore, when the invoice is integrated with Workday, the invoice amount will NOT include the amount withheld.  For example, if you withheld 10% of the invoice cost in OnCore, the Workday invoice amount will only be 90% of the total OnCore invoice amount.  This makes reconciliation very difficult.  For this reason, we DO NOT recommend using Withholding in OnCore.

1. Indirect Rate % - Enter the indirect rate here.
2. Enter No. of Cycles for Budget Calculations, if applicable. This is only applicable and required for protocol calendars created with open-ended segments

• • When a number is entered in this field for a given calendar version, the following areas are impacted:
    • Any possible milestone visits and/or pass through items will be created only up to the cycle number indicated
    • The Budget Summary and Budget Calendar reports will be calculated only up to the cycle number indicated
  • The Extending Visit notification
    • This notification is used to let the financial coordinator know that a subject has had a visit logged on this last cycle entered in the No. of Cycles for Budget Calculations field and that this number of cycles should be increased to allow additional milestones to be recorded. 
    • An email is sent to the Financial Coordinator listed on the protocol the morning after this visit was logged (overnight process).  
    • If you would like this notification to go to someone other than the Financial Coordinator listed on the protocol, this can be configured on a protocol by protocol basis. See Notifications Descriptions & Adding Custom Notifications for instructions.
  • When this number needs to be extended, the Financial Coordinator will create a New Unlocked Budget Version, extend the number in the Parameters No. of Cycles for Budget Calculations field, and add any additional Milestone and Pass Through items for these cycles.  Once the budget is released, these cycles will be available for invoicing on future subject visits for that calendar version.

7. Enter Comments, as applicable

Invoice Related Parameters

1. Based on the CTA, enter Screening Failures to Invoice Ratio (Not Eligible: Enrolled), if applicable. 

   1. A screen failure occurs when a subject is marked as ineligible in the Subject Console. 

   2. Screen failures will appear in the Invoiceable Items tab if Screen Failed is set up as a milestone.

   3. The ratio x:y (Not Eligible:Eligible) indicates the sponsor can be billed for x number of subjects deemed ineligible, for every y number of eligible subjects. 

      1. Not Eligible: indicates the number of screen failures.

      2. Enrolled: indicates the number of subjects that must be considered "enrolled" in order for you to bill the sponsor for the number of screen failures indicated in the "Not Eligible" field.

      3. For example, a ratio of 1:4 means that you can invoice 1 screen failure after 4 subjects have been enrolled. 

   4. This ratio applies only after the value set in the Initial Invoiceable Screening Failures field is reached, and up until the Maximum Screening Failures is met.

2. Based on the CTA enter Initial Invoiceable Screening Failures if applicable
   1. Indicates the number of screening failures that must occur before the Screening Failures Invoice Ratio applies. 
   2. When this field is left blank or set to 0, the Screening Failures Invoice Ratio applies immediately.
3. Based on the CTA enter the Maximum Screening Failures if applicable
   1. Indicates the number of screen failures that will be available for invoicing. 
   2. In order for screening failures to display on the Invoiceable Items tab, you must have a value (other than 0) entered into Maximum Screening Failures. 
   3. Note that this setting can also be used on its own without the other values (Screening Failures Invoice Ratio, Enrollment Status, and Initial Invoiceable Screening Failures) being set.
4. Enter First Invoiceable SAE
   
   1. Indicates the first serious adverse event (SAE) on the protocol for which the sponsor will receive an invoice.. 
   2. The Invoiceable Items tab automatically begins listing the SAEs once the number meets and exceeds the limits indicated here, if SAEs are selected as milestones in the Milestones tab. 
   3. Enter 0 if you want the first SAE that occurs to be invoiced. 
   4. When this field is left blank, no SAEs are created as invoiceable items.
5. Enter First Invoiceable OSR
   

   1. Indicates the first Outside Safety Report/external SAE on the protocol for which the sponsor will receive an invoice. 

   2. The Invoiceable Items tab automatically begins listing the OSRs once the number meets and exceeds the limits indicated here, if OSRs are selected as milestones in the Milestones tab. 
      1. For example, when you enter 5 in this field, the fifth OSR is the first one added to the Invoiceable Items tab. 
   3. Enter 0 if you want the first OSR that occurs to be invoiced. 

   4. When this field is left blank, no OSRs are created as invoiceable items.

6. Enter Milestone Invoiceable Visit Prerequisite to indicate when subject milestones can be invoiced
   1. These correspond to the date fields of the same name on the Subject Visit Update page within the Subject Console
   2. The Occurred Field corresponds to the visit status of "Occurred" within the Subject Visit Update page of the Subject Console
   3. If Occurred is chosen for this field, visits for this study can be invoiced as soon as they have occurred
      
      

Remit To/Bill To

1. Click the Add Remit To Address, enter the below and click Create. The Send to Address on the invoice template will have the below address, regardless of what value is entered here.

   Washington University
   P.O. Box 505505
   St. Louis, MO 63150-5505

   
   

2. Click Add Bill To Address, enter the address(es) per below, and click Create for each.

   1. A Bill To sponsor is required to facilitate sponsor invoicing and payment reconciliation.
   2. This address should match the contract 
   3. These can be marked Active or Inactive after creation by clicking the Edit button to the right.

Invoicing Reminder

1. If you want OnCore to email a regular invoicing reminders, use the following fields:
   1. Notification Frequency (Months): Enter 3 here. WashU has a set notification frequency of every 3 months (Jan 1, Apr 1, June 1, Oct 1).  OnCore will ignore all other values.
   2. Number of Invoice reminders to send after study closure: Number of reminders sent once protocol has a completed status (Abandoned, Terminated, or IRB Study Closure).
   3. Notification Start Date: The date on which notifications are activated.  If you enter 4/15/2020 in here, for example, your first notification will occur on 6/1/2020.
   4. Notification Comments: Any other information you wish to add regarding the notifications.
2. The invoicing reminder notification is an email that will go to the Financial Billing Contact and the Financial Coordinator listed on the protocol. There should only be one financial billing contact listed.
   1.  If you wish to modify who this notification goes to and what it says, see the Adding Notifications page.
   2. Here is the standard template for the Invoicing Reminder, which will be populated with the corresponding fields in OnCore: