Every function needs at least one fee before registrants can buy a ticket, because the fee sets the price. When a function has more than one fee, such as “Member” and “Non-Member,” registrants choose the correct fee on the registration form.
Prerequisites
You need access to the event in the Events Console and permission to set up function fees. To delete a fee, you need the separate delete permission; without that permission, the delete option is not available.
Where to Find It
Open the function’s record page from the Functions Overview by selecting the function name, then open the Fees tab. The tab shows every fee on the function, including its price and member price.
- Create Fee opens a blank fee form for this function.
- Open a fee from the list to edit it.
- Use the delete icon on a fee to remove it after nothing still uses it.
The Settings
| Setting | Options | Default | Effect |
|---|---|---|---|
| Name (Abbreviated) | Any text | <function name> Fee | Required. Appears in dropdowns on the registration form and elsewhere in the Console |
| Full name | Built automatically | <event>/<function>/<abbreviated name> | Appears on product reports and rebuilds whenever the abbreviated name changes |
| ID: | Suggested in upper case | <function's identifier>-FEE-<suggestion> | Required. Permanent after you save |
| Business unit | Fixed | The event's business unit | Determines which business unit’s currencies and accounting the fee uses; you cannot edit it here |
| Status | Active, inactive | Active | Controls whether the fee is offered |
| Revenue | A bank account or a specific revenue allocation account | Empty | Required. Either option works; your organization decides which one to use for accounting |
| Price and member price | An amount per currency | Empty | Sets the base price when no deadline price applies |
| Deadline Pricing rows | An amount and a member amount per registration deadline | Empty | Appears only when the event’s registration settings use deadlines. A blank row falls back to the base price |
A fee’s ID starts with the function’s identifier, so shortening only the fee’s abbreviated name will not shorten the generated ID much. The function and event identifiers at the beginning stay the same length. Keep the full generated fee ID under 128 characters. A longer ID can prevent you from adding that fee to an unpaid proforma invoice later, and after registrants have bought tickets at a fee, recreating the function or fee to shorten the ID is not practical.
The registration form builds the label for a function’s questions and choices from both the function name and the fee name. If those names use similar wording, the combined label can look repetitive even when neither name is duplicated on its own. Rename the fee to remove the overlap and clean up the display.
Tip
If everyone who buys access to a specific function should pay the same fixed amount, put that amount on the function fee instead of a registration package. A package used only to show the option to registrants can have a price of zero, because the actual charge comes from the function ticket.
Purchasing Eligibility and Restrictions
A function fee’s Advanced Rules & Logic can limit purchasing eligibility so that only people who meet a condition can buy it. These rules evaluate contact or organization data, such as a contact custom field or contact role, rather than a membership custom field. You can use the same eligibility criteria for special pricing, so a specific group, such as members of one section, can receive a different rate than general attendees.
Warning
Purchasing eligibility rules can check a registrant’s existing saved data, such as a contact custom field, but they cannot evaluate a choice the registrant made earlier on the same in-progress registration form. If eligibility needs to depend on something the registrant picks during registration, capture it first as a contact custom field on the registration’s update form so it exists as saved contact data when the fee’s eligibility rule runs.
You cannot restrict a specific fee so that only guest or spouse registrations can purchase it.
Dependencies and Precedence
- A function fee appears only where its function appears, so hiding a function from the Portal or schedule also hides its fees.
- Deadline pricing rows come from the event’s registration settings. If the event turns deadline-based pricing off, those rows no longer appear on this form, but any prices you already entered stay stored and still apply.
- When Rhythm prices a ticket, it checks the registration deadlines that have already passed and uses the price tier for the most recent one. If no deadline has passed, or if that tier has no price entered, Rhythm uses the fee’s base price and member price. A deadline row with a date outside this event’s own deadlines is never used, because Rhythm reads deadlines only for the fee’s event.
- A function’s registration questions apply to the whole function, not to one fee. You cannot show a question only when a registrant selects a specific fee.
- If you need to stop new sales of one fee within a function without capping the whole function, set that fee’s status to inactive to remove it from the registration form. There is no separate capacity limit for an individual fee type.
Tip
Give every fee a base price in addition to any deadline prices. A deadline tier with no price falls back to the base price, and a ticket priced outside any tier uses only the base price and member price.
Credit Card Processing Fees
A credit card processing fee is separate from the fee prices on this screen. You configure it in the event’s registration settings and in the registration process settings, and it must be enabled in both places before it applies to a purchase. If a registration process has Override Commerce Settings turned on, it can suppress credit card fees even when they are enabled everywhere else. Turn that override off if fees are not being assessed as expected.
If you sell registrations through a store, a registration package’s processing fee can apply broadly across every event and registration type the package includes. Outside a store, you must enable the processing fee individually for each event.
Cancellation Fees
A cancellation fee has two separate parts: the cancellation fee product in registration settings and the cancellation fee amount. Rhythm adds the cancellation fee product to the invoice when it charges the fee, while you set the cancellation fee amount on the registration package or the function ticket. To control which general ledger accounts a cancellation fee posts to, first create a miscellaneous product with its GL accounts configured in Financial & Billing setup, then associate that product with the registration package in the event’s settings.
Change Impact and How to Revert
Changing a fee’s price affects only tickets bought after the change; tickets already sold keep the price they were charged. Renaming a fee is safe because tickets refer to the fee by its identifier, not its name.
Warning
You can’t delete a function fee while any ticket, active or cancelled, still names it. If Rhythm refuses the delete, check the function’s ticket tabs, including Cancellations, for tickets still pointing to that fee.
You don’t need to delete a function’s fees one at a time before deleting the function itself. Deleting a function that nothing blocks, as described in Functions, removes its fees in the same action. If you only want to remove one fee and keep the function, delete that fee after no active or cancelled ticket still names it.
Permissions
Creating and editing a fee requires the permission your administrator grants for function fee setup. Deleting a fee requires a separate delete permission; without it, the delete icon is not available on the fee.
Validation and Errors
- Rhythm refuses to save a fee without a name, an identifier, or a business unit.
- Rhythm refuses a deadline price with more than two decimal places.
- Rhythm refuses to delete a fee that a ticket still uses and shows a message that the fee can’t be deleted.
- If a registration invoice shows the wrong number of included function tickets, check the fee’s bundled product configuration for a duplicated or misassigned included item. Correcting that configuration fixes the invoice display.