Reports

The Claims module has fourteen reports and no report builder. They are fixed screens, split between the two applets by audience: the Claim Applet’s are for claimants and supervisors and show lines; the Claim Cycle Applet’s are for finance and show a cycle.

Two of these are not really reports — they are the payment instruction. The Bank Report and the salary-payment CSV are what somebody takes to the bank portal or to payroll. Nothing is paid automatically, so if nobody generates and acts on them, nobody gets reimbursed. See Core concepts §7.

For claimants and supervisors — Claim Applet

Report	Who it is for	What it shows
My Claim	Claimant	Your own claims, with status summary cards and a dashboard window
Line Reports	Claimant	Every one of your claim lines, one row per expense, with its approval sequence and history
Engagement Report	Claimant	Your chargeable lines grouped by the client engagement they belong to
Pending Approvals	Supervisor	The lines waiting for you, with approve and reject, a duplicate-receipt view and related lines
Staff Reports	Supervisor	Claims of the people who report to you
Non-Reimbursable Report	Supervisor	Lines the company already paid — auto-approved, never routed
Professional Study Scheme Report	Supervisor	Professional-study claims with their validity dates and any forfeiture

The claimant screens and the supervisor screens are separated by which endpoint they call, not by a permission toggle: a claimant’s screens can only ever return their own lines. Whether someone sees the Supervisor group at all is a matter of feature visibility and the permission sets they hold.

For finance — Claim Cycle Applet

Five of these are tabs inside a cycle; four are cross-cycle screens on the sidebar.

Report	Where	What it answers
Bank Report	Cycle tab	Who do we pay, how much, and to which account? One row per employee, with bank code, bank name and account number pulled from their payment method, and the cycle’s crediting date
PV Details Report	Cycle tab + sidebar	What do we code the payment to? One row per claim line with company, branch, claim item, GL code, tax and amount. This is the working paper for a manual Payment Voucher
Cross-Billing Report	Cycle tab	Which claims belong to a different company or branch than the one that paid? Lines whose billing branch differs from their expense branch
Pivot Report	Cycle tab + sidebar	Where is the spend going? Company, branch, employee, claim item, amount
Professional Subscription Report	Cycle tab	Professional-body subscription claims
Payroll Payment Report	Sidebar	The `SALARY_PAYMENT` lines to hand to payroll. A CSV export sits behind it
Sampling Analysis Report	Cycle tab + sidebar	The results of the audit samples drawn from this cycle or across cycles, with summary tiles

Claim Cycle History shows closed cycles read-only, with the same tabs, so last month’s Bank Report is still there after the cycle is closed.

Two things that will confuse you the first time

Two finance users can see different totals for the same cycle, and both are right. The filter that decides whether a cycle’s queues and finance reports count finance-payment lines, salary-payment lines or both is a personal setting, not a company one. (The Payroll Payment Report and the cycle’s Payroll Payment tab ignore it and always show salary-payment lines.) It defaults to finance payment only. If your colleague’s cycle total does not match yours, compare that setting before you compare anything else.

The Bank Report refuses to generate rather than showing an empty table. There is no claim data. means no approved lines match your payment-processing filter and the Reviewed By Level filter you have set — not that the cycle is empty. Check both filters before concluding anything.

Which report answers which question

Question	Report
Where is my claim?	My Claim, or Line Reports for the line detail
What is waiting for me to approve?	Pending Approvals
What has my team claimed this year?	Staff Reports
What did we spend on this client job?	Engagement Report, then Cross-Billing Report for the finance view
Who do we pay this month, and to which bank account?	Bank Report
What GL codes does the payment voucher need?	PV Details Report
Which claims should payroll include?	Payroll Payment Report, and its CSV export
Where is the spend concentrated?	Pivot Report
Did the sample we checked pass?	Sampling Analysis Report
Which lines look suspicious?	The flagged filter on sampling — receipts reused across claims, or amounts and dates edited away from what OCR read

What has no report

These four reports are worth ruling out before you go looking for them, because none of them exists:

No entitlement balance ledger. Balances are visible on the employee link under the claim account and on the claim line when Display Entitlement Balance is on. There is no report that lists every employee’s remaining allowance.
No departmental budget or variance report. Claims has no budget concept, and the Budgetary applet will not count claim spend either: only finalised purchase and sales invoices that carry budget details consume a budget register, never a claim or the payment voucher that pays it. Compare spend by expense account in your financial reports, or by claim item in the cycle’s Pivot Report, against the budget you hold.
No policy-violation report. Violations are refused at submission rather than recorded, so there is nothing to report on. The nearest thing is the flagged-claims filter in sampling.
No tax-deductibility summary. Claims holds no deductibility data at all. That analysis happens in Financial Accounting, on the vouchers the claims reports produced.