Skip to content

Claims Management Module

An employee pays for something out of their own pocket and wants the money back. This module is the paperwork between those two events: the claim they submit, the supervisor who approves it, the entitlement balance it draws on, the monthly cycle in which finance reviews it, and the reports somebody takes to the bank portal or to payroll. It is for whoever sets claims up and whoever pays them. Start with Core concepts: six ideas that explain almost everything surprising here.

Claims posts no journal, moves no stock and creates no payment voucher. Money leaves through the Bank Report, the PV Details Report or the salary-payment export, each a hand-off to a person (Core concepts §7).

Applets in this module

Membership is an editorial judgement — the product has no module↔applet relationship in its data.

AppletWhat it is for
Claim AppletWriting and approving claims, and nearly all the module’s master data: claim items, claim accounts and entitlements, approval settings, cut-off logic. It stops at supervisor approval.
Claim Cycle AppletThe finance side: one cycle per company per month, level-by-level review, sampling, and the payment reports.

Where to go next

The entitlement balance is enforced by a checkbox called “Display”

A claim account’s entitlement is checked at submission (CLAIM_DOC_LINES_INSUFFICIENT_BALANCE) and spent at approval only when Display Entitlement Balance is ticked on the account. With it off, employees can claim past their entitlement with no error. The full rule is in Core concepts §4.