Posting Classes

Posting class records are used throughout Catch-e to classify financial and operational activity. They act as a central mapping layer that links costs, events, and contract rules across multiple parts of the system.

Posting classes are used in the following areas:

Where posting classes are used

Contract Types

Posting classes define the allowable budgets and expenses for each contract type. This controls what cost categories can be applied to a contract.

Contracts / Events

Posting classes are used to classify event record types within a contract. They can also be configured to drive event behaviour, including email triggers.

Contracts / Maintenance

Posting classes classify maintenance payments and expense items. They also apply business rules such as recharge flags defined in Contract Types.

New posting classes can be created within the system and optionally configured to appear as contract events.

To view the full list of posting classes, navigate to:

Setup → Export Table Data → glpostingclasses

Field Descriptions

Class Code

A short text code used to identify the posting class.
Example: S for Service

Name

A descriptive name for the posting class.

Changing the Name field has system-wide impacts:

  • If linked to Quote Profile Tables, updates will cascade to all related quote references

  • The SDR posting class also affects screen naming on the Quotes / Finance tab

  • Changes to other posting class behaviours may require assistance from your Account Manager

Group

A drop-down field used to group posting classes for reporting purposes. Values are stored in the glpostingclassgroups table.

Standard groups include:
Accidents, Maintenance, Registration, Tyres, Transport, Fuel, Other

Additional groups can be created via data upload or by contacting Catch-e support.

The special group Exclude removes costs from:

  • FBT Operating reports

  • Novated Driver reports (Statutory and Operating methods)

Event

When enabled, the posting class can be used as an event type in Contracts / Events.

It can also be configured to trigger system emails.

Event Completed

If selected, new events created using this class will default the “Completed” flag to ON, including events generated from accepted quotes.

System Event

Indicates that the event is system-generated, typically via scheduler jobs such as mailQuery or eventQuery.

System events:

  • can be viewed and filtered in Contracts / Events

  • cannot be manually created by users

  • may not allow email triggering via the standard UI

If used incorrectly (especially with reimbursement events such as RN), this setting can cause data issues.

1link Export / AutoGuru Export

When enabled, matching maintenance or budget records are exported to external platforms such as 1link or AutoGuru.

Event View Flag

Controls whether external users can view events of this posting class in:

  • Contracts / Events

  • Events reports

If unchecked, external users will not see these events.

Event Create Flag

Allows external roles such as group managers or fleet managers to create and edit events of this class.

Event Follow Up Flag

Allows authorised roles to manage event workflow fields:

  • Action

  • Due Date

  • Completed

This feature only works when:

  • Event View Flag is enabled

  • Event Create Flag is enabled

  • Event Follow Up Flag is enabled

If used for drivers, access is limited to specific event types (e.g. ECM and Non-Use Days) and only when enabled in Client Contract Defaults.

Disclose Transactions

Controls whether transactions for this posting class are visible to external users in Contracts / Maintenance.

This works in combination with other system settings. Refer to Disclose Running Costs for full configuration rules.

This field may be renamed or role-restricted depending on system setup.

FBT Operating Method

When enabled, maintenance transactions linked to this posting class are included in FBT Operating report calculations.

Termination Cost

Indicates that this posting class contributes to Sale Management “Net Charges” during vehicle termination processes.

Quote Profile Table Relationships

Posting classes can be linked to quote calculations via the Quote Profile Table.

This relationship ensures that costs are correctly mapped between posting classes and quote components.

Class Code

Name

Quote Profile Table

AMFEE

Accident Management Fee

qtquoteaccidentmanagementfee

CEO

Carbon Emissions Offset

qtquotecarbonemissionsoffset

CSD

CSD

qtquotes

EW

Extended Warranty

qtquoteextendedwarranty

F

Fuel

qtquotefuel

FIN

Finance

qtquotes

INS

Comprehensive Insurance

qtquoteinsurance

LTI

Loan Termination Insurance

qtquotelti

MAINT

Maintenance and Servicing

qtquotemaintenanceservice

RSA

Roadside Assistance

qtquoteroadsideassistance

REG

Registration

qtquoteregctp

RVEH

Relief Vehicle

qtquotereliefvehicle

SDR

Small Damage Repairs

qtquotesmalldamagerepairs

T

Tyres

qtquotetyres

WALKAWAY

Walkaway

qtquoteralkaway

VMP

Maintenance Program

qtquotevehiclemaintenance_program

Important Warning

Changing a Class Code has wide-ranging impacts across the system.

If the Class Code is modified:

  • existing quote relationships may be broken

  • quoting logic may no longer match historical contracts

  • quote forms and driver reports may be affected

  • screen naming may revert to system defaults (notably for SDR)

Additionally:

  • itemised quote forms must be updated manually

  • changes do not automatically update printed or external templates

Payment

When enabled, this posting class becomes available in:
Contract Types → Payments tab

Payment setup must be completed following the standard Payments configuration process.

Supplier

Allows a supplier code to be assigned as a default for sundry payment schedules linked to new contracts.

This supports automated payment setup within Contract → Payments workflows.