**Source URL:** https://clinical.veevavault.help/en/lr/71912/index.md

# Managing Studies for Site Payments

Veeva Payments allows you to track payable items for site payments within CTMS Vaults. Managing payment requests within Vault streamlines reimbursement and frees study personnel to manage other critical aspects of a trial.

Payment specialists define _Fees_ for sites based on the Clinical Trial Agreement. As _Subjects_ attend _Subject Visits_ and undergo _Procedures_ throughout the trial, Vault automatically generates _Payable Item_ records based on the defined _Fees_ and supports the manual generation of _Payable Item_ records when eligible payable events are created or updated. Payment specialists can then group _Payable Items_ under a _Payment Request_ and generate payment letters. The _Payment Request_ can be routed for approval and processing by your organization's Accounts Payable systems.


<div class="note-border alert-info">
  <div class="alert alert-info" role="alert">
    <div><i class="far fa-info-circle"></i></div>
    <div class="alert-text">
      <p><strong>Note</strong>: Some <a href="/en/lr/58930/">configuration from an Admin</a> is required before you can utilize Veeva Payment features in your Vault.</p>
    </div>
  </div>
</div>



## Study Design Configuration

### Visit Definitions & Subject Groups {#visit-and-study-arms}

_Visit Definitions_ define a set of _Subject Visits_ for that _Study_, while _Subject Groups_ define a set of groups for that study. After creating these records, [_Subject Visit_ records](/en/lr/50851/) track visits a subject completes over the course of the trial and _Subject Groups_ can be associated with a _Subject_.

### Repeating Visits

In Vault EDC, users can create Visit Groups to manage a Visit or set of Visits.  For studies where the same Visit Group is making repeat visits, you can create _Visit Group Definition_ records to define groups. You can create these records in Business Admin, where you must also select the relevant _Study_ from a picklist, or via the **Visit Definitions** [section](/en/lr/26387/#add-edit-move-sections) of a _Study_ record. Creating _Visit Group Definitions_ and related records allows for defining more specific Fees.

In addition to a _Name_, you must specify the _Expected Repeats_ value. The _Max Repeats_ field is optional; Vault uses this field for EDC connections and isn't used otherwise.

<div class="note-border alert-info">
  <div class="alert alert-info" role="alert">
    <div><i class="far fa-info-circle"></i></div>
    <div class="alert-text">
      <p><strong>Note</strong>: Vault does not support the following characters in Visit Definition Names: <code class="language-plaintext highlighter-rouge">&lt; &gt; : ; " / | \? *</code></p>
    </div>
  </div>
</div>



If your Vault receives [repeating visit information from EDC Vaults](/en/lr/60672/#repeating-visits), it generates _Payable Items_ based on the shared _Visit Definition_, _Visit Group_, and _Repeat Instance Sequence_ for each _Subject Visit_



<div class="note-border alert-important">
  <div class="alert alert-important" role="alert">
    <div><i class="far fa-exclamation-circle"></i></div>
    <div class="alert-text">
      <p><strong>Important</strong>: For Vaults with a CDMS &amp; Clinical Operations Vault Connection, Visit Group Definitions and Repeat Instance Identifiers are created automatically using matched Event Groups Labels and Repeating Event Override Labels values from EDC.</p>

<p>Veeva suggests creating the connection before creating Visit Group Definitions. If you did create these records before the connection, you must ensure the names match exactly in both Vaults.</p>
    </div>
  </div>
</div>



For each _Visit Group Definition_, you can define _Repeat Instance Identifiers_. Specify a _Name_ and _Instance Sequence_ for each.

Once _Visit Groups_ and Repeat _Instance Sequences_ are created, you can define _Fees_ for each recurrence.

### Procedure Definitions {#procedure}

_Procedure Definitions_ outline a standard set of _Procedures_ that subjects will undergo over the course of the trial, for example, biopsies or CT scans. Click **Create** in the _Procedure Definitions_ section on a _Study_ record details page to create a **Procedure Definition.** 

You can create a base _Procedure Definition_ or a _Global Procedure Definition_. Base _Procedure Definitions_ link to a specific _Study_, while _Global Procedure Definitions_ create a reference library for tracking _Procedure Definitions_ across studies. An Admin must configure the _Global Procedure Definitions_ object type for the _Procedure Definition_ object before you can use it in your Vault.

On _Study_ records, you can use the _Populate Procedure Definition_ user action to create _Procedure Definition_ records for a _Study_ based on _Procedure Definitions_ defined for specific sources: _Procedure Templates_ or _Studies_. The user action references the _Procedure Definitions_ in the source to create copies of the _Procedure Definition_ records that exist in the source that do not exist in the _Study_. You can select multiple _Procedure Templates_ or _Studies_ to copy _Procedure Definitions_ from. To use the _Populate Procedure Definition_ user action, an Admin must configure the action on the _Study_ object.

### Procedure Template  

_Procedure Templates_ reference _Global Procedure Definitions_ to create a set of records that any _Study_ can use. _Procedure Templates_ allow you to easily reuse a consistent set of _Procedure Definitions_ across _Studies_. 

To create a _Procedure Template_, navigate to **Business Admin \> Objects \> Procedure Templates** and click **Create**. In the _Procedure Definition_ section, click **Add** to include **Global Procedure Definitions**. _Procedure Definition Templates_ track the use of _Procedure Definitions_ in _Procedure Templates_.

### Creating Procedures {#procedures}

After creating _Subject Visits_, you can create _Procedure_ records related to a _Subject_ _Visit_. For example, you could create a _Procedure_ record for a CT scan performed on a subject during a _Subject Visit_. Create _Procedures_ from the _Procedures_ section of a _Subject Visit_ record's details page.

If configured, your Vault may receive new _Procedure_ records and updates to existing _Procedure_ records from a [connected CDMS EDC Vault](/en/lr/60661/).

### Site Fee Definitions {#site-fees}

_Site Fee Definitions_ outline the items eligible for reimbursement that are not related to a subject. For example, you could define _Site Fees_ for a Start-Up Fee and Initial IRB Approval. Create _Site Fee Definition_ records from the _Site Fee Definitions_ section on a _Study_ record's details page.

## Payee Setup {#payee-configuration}

_Payee_ records represent the recipients of reimbursements. _Payees_ are available from the _Study Organizations_ associated with the site. When defining _Payees_ for a site, you can select the **Organization**, **Location**, and whether the organization will serve as the primary payee. For example, you could identify that the clinical site organization and a separate local laboratory will be reimbursed for some subject-related payments.

When Vault generates _Payable Items_, it checks these records in this order:

1. Any [_Payee Overrides_][6] defined.
2. The primary payee of the _Fee Schedule_. 
3. The primary payee of the _Site_.

Vault assigns any _Payees_ it finds going through the list, creating one _Payable Item_ record for each payee defined by an override or set as a primary payee. Should none be defined, the _Payee_ field remains blank.

### Payee Override {#payee-override}

In some cases, there may be multiple payees defined for a given fee, or the desired payee may be different than the primary. You can address these scenarios using _Payee Overrides_.

To enter _Payee Overrides_ for a fee:

  1.  Navigate to a _Fee_ record and select **Yes** on the **Payee Override** field. Vault will display a _Payee Override_ section.
  2.  From the **Payee Override** section, click **Create**.
  3.  Select the **Payee** and enter the amount of the override.

<div class="note-border alert-info">
  <div class="alert alert-info" role="alert">
    <div><i class="far fa-info-circle"></i></div>
    <div class="alert-text">
      <p><strong>Note</strong>: When approving a <em>Fee Schedule</em>, Vault validates that the sum of <em>Payee Overrides</em> is equal to the <em>Fee Amount</em>.</p>
    </div>
  </div>
</div>



## Fee-Related Objects Setup {#fee-related-objects-configuration}

### Fee Schedules {#fee-schedule}

_Fee Schedules_ are a collection of fees negotiated with a site. You can set the _Study Organization_ for a _Fee Schedule_ to divide fees between various organizations at a site when there are separate contracts for main hospitals, labs, or pharmacies, for example. This allows you to manage entire _Fee Schedules_ for multiple _Payees_ at the same site, each with their own effective dates. You can use [_Payee Override_ functionality][6] for further flexibility.

Create _Fee Schedule_ records from the _Fee Schedules_ section on a _Site_ record's details page. You can create _Fee Schedules_ from an existing _Fee Schedule_ or approved _Fee Schedule Template_. The _Create Fee Schedule_ action allows users to pick an existing _Fee Schedule Template_ to copy or to create an entirely new _Fee Schedule_.

When you copy an existing _Fee Schedule_ using the _Copy Record with Related Fees_ action
, Vault copies all related fees from the _Fee Schedule_. All the records Vault creates in copying the _Fee Schedule_ are in _Initial_ state. By default, the list only includes _Fee Schedules_ at the _Site_. You can, however, choose to include _Fee Schedules_ from other _Sites_ in the _Study_.

You can also update an existing _Fee Schedule_ with _Fees_ from an approved _Fee Template_ by using the _Copy Fees from Template_ action. When you run this action, Vault creates the _Fees_ from the selected _Fee Schedule Template_ and associates them with your _Fee Schedule_.

A fee schedule must be approved to generate _Payable Items_. You can create and approve multiple _Fee Schedules_ with the same _Study Organization_ for a _Study Site_,  with the following limitations:

  * The end date of one *Fee Schedule* cannot overlap with the start date of another approved *Fee Schedule*. For example, an approved *Fee Schedule* cannot have a start date of `Dec 25 2020` if an approved *Fee Schedule* exists with a start date of `Dec 01 2020` and an end date of `Dec 31 2020`.
  * No gaps can exist between _Fee Schedule_ start and end dates. For example, you can only approve a second _Fee Schedule_ with a start date of `Dec 25 2020` when a _Fee Schedule_ exists with an end date of `Dec 24 2020`.
  * Only one _Fee Schedule_ can have a blank start date and only one _Fee Schedule_ can have a blank end date.

<div class="note-border alert-info">
  <div class="alert alert-info" role="alert">
    <div><i class="far fa-info-circle"></i></div>
    <div class="alert-text">
      <p><strong>Note</strong>: For some <em>Payable Item</em> object types, Vault includes VQL criteria configurations for the <em>Fee Schedule</em> field. This criteria limits the object to only using <em>Fee Schedules</em> in the <em>Approved</em> lifecycle state. We recommend you remove the VQL criteria from the <em>Fee Schedule</em> field for <em>Payable Item</em> object types. To remove the VQL criteria, navigate to <strong>Admin &gt; Configuration &gt; Objects &gt; Payable Item &gt; Object Types</strong>, click the <strong>Fee Schedule</strong> check box in the object type column, and delete the logic in the <strong>Criteria VQL</strong> field.</p>
    </div>
  </div>
</div>



The *Approve and Update Related Fee Schedules* user action allows you to review and approve proposed updates to related *Fee Schedules* as part of approving a new *Fee Schedule*. For updates to only one existing *Fee Schedule*, the action prompts users to review proposed changes before Vault processes the changes and the new *Fee Schedule*.

Vault proposes the following updates:

* For a new *Fee Schedule* with a *Start Date* later than the *Start Date* of the existing *Fee Schedule*, Vault applies an *End Date* to the existing *Fee Schedule* for the day before the *Start Date* of the new *Fee Schedule*.   
* For a new earlier *Fee Schedule* with an *End Date*, Vault applies a *Start Date* to the existing *Fee Schedule* for the day after the *End Date* of the *Fee Schedule.*   
* When the *Start Date* and/or *End Date* negates or replaces the date range of an existing *Fee Schedule*, Vault sets the existing *Fee Schedule* to the *Superseded* lifecycle state. 

The *Approve and Update Related Fee Schedule* user action is a system-managed action. After you confirm the updates to the *Fee Schedules,* the *Approve and Update Related Fee Schedule* user action updates the *Fee Schedules* regardless of entry criteria or validation rules. The user action also does not trigger entry actions. 

Admins can add the *Approve and Update Related Fee Schedules* user action to *Fee Schedule* lifecycle states and workflows or enable it as a bulk action to update multiple *Fee Schedules* simultaneously.

<div class="note-border alert-info">
  <div class="alert alert-info" role="alert">
    <div><i class="far fa-info-circle"></i></div>
    <div class="alert-text">
      <p><strong>Note</strong>: To use existing <em>Fee Schedules</em> set to the <em>Superseded</em> lifecycle state, the lifecycle state must be set to <em>Active</em>. To set the <em>Superseded</em> lifecycle state to an <em>Active</em> state, go to <strong>Admin &gt; Configuration &gt; Object Lifecycles &gt; Fee Schedule Lifecycle &gt; Superseded</strong> and deselect the <strong>Records in this state become inactive</strong> checkbox.</p>
    </div>
  </div>
</div>



### Fee Schedule Templates {#fee-schedule-templates}

You can use a _Fee Schedule Template_ to define a set of _Fees_ at the *Study* or _Study Country_ level that Vault can use to default _Fees_ for a given site. Once Vault defaults _Fees_ from a template, you can update them to align with any site-specific negotiations.

Create _Fee Schedule Template_ records from the _Fee Schedule Template_ section on a _Study_ record's details page.

You can also create a new _Fee Schedule Template_ by copying an existing _Fee Schedule Template_ on the _Study_ record. This option is not available if no _Fee Schedule Templates_ exist for a _Study_.

## Fees {#fees}

You define _Fees_ as part of a site's _Fee Schedule_. Fee information is generally captured within the Clinical Trial Agreement and outlines the various amounts a site will be reimbursed for different activities. _Fee Schedules_ include three _Fee_ types:

  * **Visit Fees**: Fees related to a given _Subject Visit_, for example, a baseline visit.
  * **Procedure Fees**: Fees related to a given _Procedure_, for example, a blood draw.
  * **Site Fees**: Fees not related to subject activities, for example, IRB Approval.

To create _Fee_ records:

  1.  Navigate to the **Fees** section within your _Fee Schedule_ record's details page.
  2.  Select a **Fee Type**.
  3.  Select a **Visit**, **Procedure**, or **Site**, depending on the _Fee Type_ you chose. The **Visit** or **Procedure** you chose must already be defined.
  4.  In the Payment Rules section, select all [statuses][4] for which a _Payable Item_ should be created.
  5.  Optional: Enter [payment rules][3] for the fee.
  6.  Optional: Select a **Budget Category** to track this _Fee_ against the [study budget](/en/lr/71874/).
  7.  Optional: Set **Include Overhead** to **Yes** and enter an **Overhead Percentage** to designate a portion of the fee as overhead.
  8.  Optional: Set **Include Holdback** to **Yes** and enter an **Holdback Percentage** to hold back that portion of the payment until it is marked for payment.
  9.  Optional: Set **SDV Required** to **Yes** if Site Data Verification is required for a _Site Visit_.
  10. Optional: Set the **Exclude from Payment Threshold** field to **Yes** to have the system include the corresponding _Payable Items_ in the generated _Payment Requests_ when the _Payment Request_ falls below the _Study Organization_'s _Threshold_, also enabling payments while a Site Advance is outstanding.
  11.  Enter the **Amount** the site will be reimbursed for this fee type.
  12.  Click **Save** or **Save + Create** to create more _Fee_ records.


<div class="note-border alert-info">
  <div class="alert alert-info" role="alert">
    <div><i class="far fa-info-circle"></i></div>
    <div class="alert-text">
      <p><strong>Note</strong>:  If <a href="/en/lr/58930/#config-overview">configured</a>, the system uses the value set for the <a href="/en/lr/71912/#payment-rules"><em>Exclude from Payment Threshold</em></a> field on the <em>Fee Schedule</em> record to populate the corresponding field on the <em>Fee</em> record. The system also copies the <em>Exclude from Payment Threshold</em> value from the <em>Fee</em> record to the generated <em>Payable Item</em>.</p>
    </div>
  </div>
</div>




### Fee Criteria {#fee-criteria}

#### Status {#status}

_Subject Visits_, _Procedures_, or _Site Fees_ can be in different statuses throughout clinical trial conduct, such as _Planned_, _Submitted_, and _Completed_.

The **Status** you select when creating a _Fee_ defines when Vault creates payable items during clinical trial conduct. For example, if you selected a _Submitted_ status for a _Fee_ of type _Visit_, when the _Subject Visit_ record _Visit Status_ field value is _Submitted_, Vault automatically creates _Payable Item_ records for the _Fee_.

You can select multiple statuses if necessary. Vault will create _Payable Items_ when the visit, _Site Fee_, or procedure reaches any of the selected statuses. Vault will only create one set of _Payable Items_ for each _Fee_.

<div class="note-border alert-info">
  <div class="alert alert-info" role="alert">
    <div><i class="far fa-info-circle"></i></div>
    <div class="alert-text">
      <p><strong>Note</strong>: If Automated Adjustments are enabled, Vault does not automatically adjust <em>Payable Items</em> for <em>Visits</em> that move from <em>Submitted</em> to <em>In Progress</em>. Instead, Vault sets the <em>Reverted to In Progress</em> field value to <em>Yes</em> on the <em>Visit</em>. Vault updates the field to <em>No</em> when the <em>Visit Status</em> changes to another value. Depending on the new value, Vault may generate payment adjustments.</p>
    </div>
  </div>
</div>



#### Subject and SDV Status

You can also set criteria for Fees based on Subject or SDV Status:

* **Subject Status**: When set for a _Visit_ or _Procedure Fee_, this option generates a _Payable Item_ when the _Subject Status_ on a _Subject Visit_ matches the _Status_ chosen.
* **SDV Complete**: Set this to **Yes** to generate a _Payable Item_ once the _SDV Complete_ field on a _Site Visit_ record is also **Yes**.
* **SDV Complete Only when SDV Required**: Set this to **Yes** to generate a _Payable Item_ when both _SDV Required_ is **True** and _SDV Complete_ is **True** on the _Visit_ record. If _SDV Required_ is **False** on the _Visit_, the _Payable Item_ will generate.

#### Payment Options and Rules {#payment-rules}

Some studies have additional requirements. For example, it may be negotiated that a site will not be reimbursed for more than a certain number of screen failures, or you may need to provide an advance payment to the site. Use these options on your _Fee_ records to accommodate these requirements:

  * **Include Holdback** indicates that when a payable event meets the _Fee_ criteria, two _Payable Items_ will be generated.
  * **Include Overhead** indicates that the _Base Amount_ field will be entered and the _Total Amount_ field will update based on the _Fee's Overhead Percentage_.
  * A **Maximum Count** allows you to limit the total number of _Payable Items_ that Vault will generate for a _Site_.
  * A **Rate** is a [payment limit](/en/lr/58941/#payment-limits) that limits the number of _Payable Items_ Vault will generate based on the number of _Subjects_ in a particular _Rate Metric_ at the _Study Site_. For example, if you create a **Rate** of three for the _Total Enrolled_ on a "Screen Failure" fee, Vault only generates a _Payable Item_ when there are three subjects for the _Total Enrolled_ metric. A _Rate_ references the _Rate Metric_ for the associated _Study_. You can also select a **Rate Subject Group** to have the _Rate_ reference the _Rate Metric_ for a [_Subject Group_](/en/lr/80113/) associated with the _Study_. 
  * You can elect to pay a site in advance by setting **Site Advance** to **Yes**. Doing so automatically creates debit and credit Payable Items for the amount, and as the site does incremental work it will accrue Payable Items to offset the Site Advance and then initiate ongoing Payments.
  * The **Exclude from Payment Threshold** field indicates if the _Generate Payment Request_ action will only include _Payable Items_ if the _Payment Request_ falls below the _Threshold_ field value defined on the [_Study Organization_](/en/lr/4345/#study-org).

##### Recurring Visit Fees

In some cases, sites may have negotiated different amounts for visit activities depending on a subject's assigned _Visit Group_ and the _Repeat Instance Sequence_. For example, a Week 1 Visit may be reimbursed $300 per subject for Cycle 1 and $400 per subject for Cycle 2.

Based on the _Visit Group_ and _Repeat Instance Sequence_ of a fee, Vault will generate payable items in the amount of $300 if the subject is in Cycle 1 and $400 if the subject is in Cycle 2.

##### Fees with Subject Groups

In some cases, sites may have negotiated different amounts for visit activities depending on a subject's assigned _Subject Group_. For example, a _Week 1 Visit_ may be reimbursed in the amount of $300 for a subject on _Subject Group_ A, and $400 for a subject on _Subject Group_ B.

Based on the _Subject Group_ selected for a fee, Vault will generate payable items in the amount of $300 if the subject is on _Subject Group_ A and $400 if the subject is on _Subject Group_ B.

## Additional Fees for Study Expenses {#study-expenses}

Build a library of _Additional Fees_ in your Vault, which you can use to create _Payable Items_ at the study, study country, and study site levels. You can then use these fees to track ad hoc and vendor payments that fall outside of pre-defined fee schedules. For example, you can utilize _Additional Fees_ to reimburse IRBs for a study-level ethics review, CROs for managing study conduct in a country, and sites for equipment maintenance expenses.

### Creating Additional Fees

Navigate to **Admin > Business Admin > Fees** or a custom tab to **Create** _Additional Fee_ types of _Fee_ records. You can define one or more _Payment Levels_ for each fee.

### Setting Up Vendors for Payments

#### Adding Vendors to Global Directory

Vendors must be active in the Global Directory for you to be able to associate them with study-specific _Payable Items_ for _Additional Fees_. To add a new _Organization_:

  1.  Navigate to **Global Directory > Organizations**
  2.  Click on **Create** to create a new _Organization_ record
  3.  Select an **Organization Type** and click **Continue**.
  4.  Enter the details and click **Save**.

#### Adding Vendors to a Study

Add active _Organizations_ to the _Study Organization_ section of a _Study_ record to track vendor participation in a study and make them eligible to receive payments. Add the vendor with the appropriate level of detail

### Adding Additional Fees to a Study or Site

Add _Additional Fees_ in the _Payable Items_ section of _Study_, _Study Country_, or _Study Site_ records.

## Budget Tracking Setup

You can also setup your Vault to track budget categories for study budgets. See [Configuring for Study Budget Tracking](/en/lr/71877/#budget-categories) for more details.

## Related Permissions {#configuring-the-generate-payable-items-action}

The following permissions control your ability to setup studies and payment components for Veeva Payments:

<table class="wbord" style="width: 827px;">
    <tr>
        <td style="width: 108px;">
            <p> <strong>Type</strong> </p>
        </td>
        <td style="width: 318px;">
            <p> <strong>Permission Label</strong> </p>
        </td>
        <td style="width: 401px;">
            <p> <strong>Controls</strong> </p>
        </td>
    </tr>
    <tr>
        <td style="width: 108px;">
            <p> Security Profile </p>
        </td>
        <td style="width: 318px;">
            <p> Objects: Visit Definitions: Create, Edit </p>
        </td>
        <td style="width: 401px;">
            <p> Ability to create and edit <em>Visit Definition </em>records. </p>
        </td>
    </tr>
    <tr>
        <td style="width: 108px;">
            <p> Security Profile </p>
        </td>
        <td style="width: 318px;">
            <p> Objects: Subject Visit: Create, Edit </p>
        </td>
        <td style="width: 401px;">
            <p> Ability to create and edit <em>Subject Visit </em>records. </p>
        </td>
    </tr>
    <tr>
        <td style="width: 108px;">
            <p> Security Profile </p>
        </td>
        <td style="width: 318px;">
            <p> Objects: Study Group: Create, Edit </p>
        </td>
        <td style="width: 401px;">
            <p> Ability to create and edit <em>Study Group </em>records. </p>
        </td>
    </tr>
    <tr>
        <td style="width: 108px;">
            <p> Security Profile </p>
        </td>
        <td style="width: 318px;">
            <p> Objects: Procedure: Create, Edit </p>
        </td>
        <td style="width: 401px;">
            <p> Ability to create and edit <em>Procedure</em> records. </p>
        </td>
    </tr>
    <tr>
        <td style="width: 108px;">
            <p> Security Profile </p>
        </td>
        <td style="width: 318px;">
            <p> Objects: Procedure Template: Create, Edit </p>
        </td>
        <td style="width: 401px;">
            <p> Ability to create and edit <em>Procedure Template</em> records. </p>
        </td>
    </tr>
    <tr>
        <td style="width: 108px;">
            <p> Security Profile </p>
        </td>
        <td style="width: 318px;">
            <p> Objects: Procedure Definition: Create, Edit </p>
        </td>
        <td style="width: 401px;">
            <p> Ability to create and edit <em>Procedure Definition</em> records. </p>
        </td>
    </tr>
    <tr>
        <td style="width: 108px;">
            <p> Security Profile </p>
        </td>
        <td style="width: 318px;">
            <p> Objects: Procedure Definition Template: Create, Edit </p>
        </td>
        <td style="width: 401px;">
            <p> Ability to create and edit <em>Procedure Definition Template</em> records. </p>
        </td>
    </tr>
    <tr>
        <td style="width: 108px;">
            <p> Security Profile </p>
        </td>
        <td style="width: 318px;">
            <p> Objects: Site Fee: Create, Eidt </p>
        </td>
        <td style="width: 401px;">
            <p> Ability to create and edit <em>Site Fee </em>records. </p>
        </td>
    </tr>
    <tr>
        <td style="width: 108px;">
            <p> Security Profile </p>
        </td>
        <td style="width: 318px;">
            <p> Objects: Fee Schedule: Create, Edit </p>
        </td>
        <td style="width: 401px;">
            <p> Ability to create and edit <em>Fee Schedule </em>records. </p>
        </td>
    </tr>
    <tr>
        <td style="width: 108px;">
            <p> Security Profile </p>
        </td>
        <td style="width: 318px;">
            <p> Objects: Fee: Create, Edit </p>
        </td>
        <td style="width: 401px;">
            <p> Ability to create and edit <em>Fee </em>records. </p>
        </td>
    </tr>
    <tr>
        <td style="width: 108px;">
            <p> Security Profile </p>
        </td>
        <td style="width: 318px;">
            <p> Objects: Fee Schedule Template: Create, Edit </p>
        </td>
        <td style="width: 401px;">
            <p> Ability to create and edit <em>Fee Schedule Template </em>records. </p>
        </td>
    </tr>
    <tr>
        <td style="width: 108px;">
            <p> Security Profile </p>
        </td>
        <td style="width: 318px;">
            <p> Objects: Budget Categories: Create, Edit </p>
        </td>
        <td style="width: 401px;">
            <p> Ability to create and edit <em>Budget Category </em>records. </p>
        </td>
    </tr>
</table>

 [3]: #payment-options-and-rules
 [4]: #status
 [5]: #payment-rules
 [6]: #payee-override