Fine Types
Defining charges applied when items are returned damaged, lost, or in poor condition
Two Kinds of Fines
Papyrus Cloud has two distinct fine mechanisms — do not confuse them:
| Type | When it applies | Configured in | How applied |
|---|---|---|---|
| Overdue fines | Item returned after its due date | Privileges (Fine, Days Grace, Days per Fine, Max Fine) | Calculated automatically when the item is returned. Based on days overdue. |
| Fine Types (this screen) | Item returned damaged, lost, or defective | Parameters → Publication Parameters → Fine Types | Selected manually by the Front Desk operator during the return transaction. |
A single return can attract both — an automatic overdue fine plus a manually applied damage charge if the item comes back in poor condition.
How Fine Types Work
When an item is returned damaged or lost, the operator selects the appropriate Fine Type. Papyrus Cloud then completes three actions in one step:
The amount charged is always the lesser of the Fine Type amount and the stock item's catalogued price. This prevents a member being charged more than the replacement cost of the item. If the item has no price recorded, the full Fine Type amount applies.
Fine Type: Book Lost — amount R2,000.00 · Stock item price: R350.00
The member is charged R350.00 — the item's price, because it is less than the Fine Type amount. The R2,000 is a ceiling for expensive items, not a fixed charge.
Fine Type: Not covered, needing minimal repair — amount R20.00 · Stock item price: R250.00
The member is charged R20.00 — the Fine Type amount, because it is less than the item's price. A minor repair does not warrant charging the book's full value.
The Fine Types Screen
The screen shows all defined Fine Types in a grid with three columns: Description, Amount, and Stock Status. The Add form at the top has the same three fields plus an Add button. The Stock Status drop-down lists all currently defined status codes — from the sample library's 14 statuses — plus a No status change option at the top.
Clicking Edit on a row opens it for inline editing. Delete removes the type if it has not yet been applied to any member account.
Sample Library — Five Fine Types
The sample library defines five Fine Types covering the main damage and loss scenarios. The Stock Status column shows how each fine triggers an automatic status update:
| Description | Amount | Status | What the status change does |
|---|---|---|---|
| Book Lost | R2,000.00 | 5 — Lost | Item is immediately marked Lost and blocked from future issue. The R2,000 ceiling ensures costly items are recovered at full price; cheaper items are charged at their catalogued price. |
| Donated | R10.50 | — none — | No status change. A token administrative charge when a member donates a replacement item. The original item's status doesn't need updating — only a financial record is created. |
| Not covered, needing extensive repair | R150.00 | A — Not covered | Item flagged for significant rebinding or covering work. Status A keeps it issuable while awaiting repair — the item can still circulate but staff know it needs attention. |
| Not covered, needing minimal repair | R20.00 | A — Not covered | Same status as extensive repair but a much lower charge for minor cosmetic work. Two tiers for the same condition class give staff the flexibility to match the charge to the actual damage level. |
| Water Damage | R160.00 | 4 — Binding | Item goes straight to Binding status (Allow Issue = No). Cannot be lent again until it returns from repair and staff reset the status to Normal. The fine and the workflow trigger happen simultaneously. |
Field Reference
| Field | Description |
|---|---|
| Description | The name of the Fine Type as it appears in the Front Desk drop-down list during a return. Maximum 50 characters. Make it specific enough to choose quickly: Book Lost, Water Damage, Not covered – minimal repair are better than generic labels like Damage or Fine 1. |
| Amount | The maximum fine amount. The actual charge is the lesser of this amount and the stock item's recorded price. For lost-item fines, set this high enough to cover your most expensive stock. For repair fines, set it at the typical cost of that type of repair. Accepts any positive decimal value. |
| Stock Status | The status automatically applied to the returned item when this fine is raised. Select from the full list of defined Stock Status codes, or choose No status change. Use this to trigger the appropriate item workflow — blocking (Lost, Water Damage) or flagging but remaining issuable (Not covered). Leave as No status change for administrative fines like Donated that do not represent a change in the item's condition. |
The Price Cap
The fine charged is always the lesser of the Fine Type amount and the stock item's catalogued price. This prevents overcharging for replacement and ensures members pay what it actually costs to replace or repair the item.
| Scenario | Fine Type amount | Item price | Charged |
|---|---|---|---|
| Lost — item cheaper than ceiling | R2,000.00 | R350.00 | R350.00 |
| Lost — item more expensive than ceiling | R2,000.00 | R2,500.00 | R2,000.00 |
| Lost — item has no recorded price | R2,000.00 | — | R2,000.00 |
| Repair — always less than item price | R20.00 | R250.00 | R20.00 |
The Stock Status Change — Fine Types & Stock Status Together
The Stock Status field is what makes Fine Types more than just a charge — it connects the financial record to the physical management of the item, completing both actions in a single Front Desk step rather than requiring separate updates.
| Fine Type | Status applied | Effect |
|---|---|---|
| Book Lost | 5 — Lost (blocks issue) | Item is immediately un-issuable. Appears in Lost Items reports. No separate status update needed by staff. |
| Water Damage | 4 — Binding (blocks issue) | Item routes to the bindery workflow automatically. Staff reset to Normal (0) when it returns repaired. |
| Not covered (both levels) | A — Not covered (still issuable) | Item remains in circulation but is flagged for re-covering. The covering work happens in the background. |
| Donated | — none — | No item workflow change. The fine is a purely financial/administrative record of processing a donated replacement. |
Adding and Editing Fine Types
Enter the description and amount in the Add form, choose the Stock Status change (or leave it as No status change), and click Add. The new type is immediately available at the Front Desk.
Click Edit to update an existing type. Click Delete to remove one — only possible if it has not been applied to any member account. Fine Types that have been used in transactions are preserved for historical accuracy.
Applying Fines at the Front Desk
Fine Types are applied during the return process at the Front Desk. When a member returns an item and the operator identifies damage or loss, they select the appropriate Fine Type from the drop-down list presented during the return transaction. The system applies the charge and any status change automatically.
Outstanding charges appear in the member's record alongside any overdue fines. Both types are visible and payable through Circulation → Outstanding Fines.
Planning Your Fine Types
| Guideline | Detail |
|---|---|
| Cover the main scenarios | At minimum: a Lost type, a major damage type, and a minor repair type. These cover most situations Front Desk staff will encounter day-to-day. |
| Set Lost amounts generously | The price cap means a member will never pay more than an item's recorded price. A high ceiling like R2,000 ensures costly items are recovered at full replacement cost. The amount only matters for items with no recorded price. |
| Always link Lost to a blocking status | A Book Lost fine should change the item's status to Lost (or equivalent) so it cannot be accidentally issued again. The fine and the blocking status should be applied together as a single Front Desk transaction. |
| Use two tiers for gradable damage | The sample library's R20 / R150 covering levels (both → Status A) show how the same condition can be handled at two charge levels. Extend this pattern to any damage type that comes in degrees of severity. |
| Use No status change for admin fines | Fines that record a financial transaction without changing the item's condition — like Donated — should use No status change. They should not trigger any stock management workflow. |
| Write descriptions for speed | Descriptions appear in a drop-down at the Front Desk under time pressure. Keep them short enough to scan at a glance but specific enough to choose correctly. Avoid vague labels — be explicit about the damage type and severity. |