Transaction Types

Transaction types categorise every charge and credit that runs through the platform. They decide how transactions are grouped on invoices, what accounting code they carry, and which carrier they default to. Good transaction types make invoices clearer for customers and keep your financial reporting tidy.

Overview

Every transaction the platform creates, whether a one-off charge, a recurring charge, a call charge or a manual adjustment, is tagged with a transaction type. Common examples are “Monthly Subscription”, “Usage Charges”, “Setup Fees” and “Account Credit”.

You can add as many transaction types as you need. Once created, a type is available to pick anywhere transactions are added, set as a default on feature types, and used as a filter when building Fixed Fee Tariff rates.

Where Transaction Types Are Used

  • Feature types set a default one-off and a default recurring transaction type. Features inherit these defaults, so charges added automatically when a feature is created, or during daily processing, pick up the correct type without any manual selection. See Feature Types.
  • Invoices group lines by transaction type and sort them by the positions you set.
  • Fixed fee tariff rates can be filtered by transaction type, so a rate only applies to specific kinds of charges.
  • Reporting and accounting exports use the default transaction code so charges land under the right ledger in your accounts package.

Key Fields

Transaction Type Details

This section defines the basic properties of the transaction type, including its name, display characteristics, default codes, and product associations. These settings determine how the transaction type appears and behaves throughout the system.

FieldDescription
Transaction TypeName of the transaction type as it appears in the system
Transaction Type AvailabilityAvailability of this transaction type (Headline, Standard, or Historic)
Transaction Type Display ClassCSS class used for display formatting of this transaction type
Transaction Type Display PositionNumeric position for ordering this transaction type in displays
Default Transaction CodeDefault transaction code used for transactions of this type, typically used for accounting packages
Customer ProductsCustomer products that can use this transaction type
Is SeatWhether this transaction type represents a seat-based service

Carrier Transaction Details

Configuration for how this transaction type interacts with carrier transaction processing, including settings for discount plan allowances and carrier-specific handling.

FieldDescription
Default Transaction CarrierDefault carrier for transactions of this type when no carrier is set on the feature/standard feature (or when the transaction has no feature)
Add Discount Plan AllowancesWhether to add discount plan allowances for transactions of this type

Transaction Type Invoice Details

Settings that control how this transaction type appears on customer invoices, including display names, grouping, and positioning within invoice sections.

FieldDescription
Transaction Invoice NameName displayed for this transaction type on customer invoices
Transaction Type Group NameGroup name for organising related transaction types on invoices
Transaction Type Group PositionPosition within the transaction type group for invoice ordering

Transaction Type Platform Commission Details

Commission rate settings for platform-level commission calculations on transactions of this type.

FieldDescription
Transaction Type Platform Commission

System Information

FieldDescription
Last ModifiedTimestamp of the most recent modification to this transaction type
CreatedTimestamp when this transaction type was created

A few fields deserve extra notes:

  • Transaction Type must be unique. The platform blocks duplicates, case-insensitive.
  • Availability values are Headline, Standard and Historic. Historic types are only visible to users at the Standard expert level or above, so you can retire a type without deleting it.
  • Transaction Type Group Name and Group Position control how related types cluster on invoices. Types sharing a group name appear under the same heading in the charge breakdown.
  • Default Transaction Code is the code exported to your accounting package (for example, a nominal or Xero account code).

Managing Transaction Types

Listing Transaction Types

Go to Main Menu > Settings tab > Transaction Types. The list shows active types sorted by availability, display position and name. The page title shows a count of how many transactions use each type.

Adding a New Transaction Type

  1. Open the Transaction Types list.
  2. Click “Add Transaction Type”.
  3. Fill in the system name, display name, group and position.
  4. Set the default transaction code if you need it in your accounting export.
  5. Choose the availability. New types normally start as Standard.
  6. Save.

The new type is immediately available on feature types and fixed fee tariff rates.

Editing a Transaction Type

Open the transaction type from the list and change the fields you need. Changes to display name, group or position only affect invoices produced after the change, so existing invoices keep their original layout.

Retiring a Transaction Type

Once a transaction type has been used, the platform won’t let you delete it. The linked transactions still need it on their audit trail. To retire one in that case:

  1. Set its availability to Historic.
  2. Remove it from any feature type defaults and tariff rate filters.

Existing transactions keep pointing at the historic type so your audit trail stays intact.

Deleting an Unused Transaction Type

If a transaction type has never been used, you can delete it outright:

  1. Open the transaction type from the list.
  2. Click Actions menu > Delete Transaction Type.
  3. Confirm the deletion.

If any transaction still references the type, the action is blocked and you’ll see a message explaining why. Retire it with the Historic availability instead.

Access

  • Permission: Users need the Transaction Types permission to view or edit them. Assign it through the usual user or user group permissions.
  • Historic types: Only visible to users at the Standard expert level or above.
  • Feature Types — set defaults that flow down to features.
  • Fixed Fee Tariffs — use transaction types as rate filters.
  • Transactions — see how transaction type and code appear on individual transactions.
  • Features — how features inherit the one-off and recurring defaults.

Need flexible billing categories that match your accounting system? see how SAFE Billing Platform handles transaction types and coding

Still Didn’t Find Your Answer?

For assistance, please contact us below.

Submit a ticket