COL · Collection

When a driver's balance is overdue, collection calls him and may issue a debt letter (surat hutang) that bundles his open charges. A charge can appear again on a later letter. Code COL.

Not yet a rule

These questions are open in #87. Each gets a rule with a new ID once it is answered.

COL open 1 · Writes

Rules

R-COL-01 · A debt letter number is unique within the organization

Status: planned
Example: given a debt letter with a number, when a second letter with the same number is saved in the organization, then it is refused.
Refusal: none: unique_violation (23505).
Who: every writer.
Source: [Ref] Data model V13: debt_letters.

R-COL-02 · A charge is listed at most once on the same debt letter

Status: planned
Example: given a letter listing a damage charge, when the same charge is added to that letter again, then it is refused; it may appear on a later letter.
Refusal: none: unique_violation (23505).
Who: every writer.
Source: [Ref] Data model V13: debt_letter_items.

R-COL-03 · A collection call with a promise records the promised date

Status: planned
Example: given a call where the driver promises to pay, when it is saved with outcome promised and no promised_on, then it is refused.
Refusal: none: check_violation (23514).
Who: every writer.
Source: [Ref] Data model V13: collection_calls.

R-COL-04 · Reading debt letters and collection calls needs payment:read or debt_letter:read at the driver's pool

Status: planned
Example: given a satpam at PML, when he reads debt_letters, then nothing comes back; a checker at PML, who holds debt_letter:read, sees them.
Refusal: none: hidden.
Who: super_admin, admin, admin_fleet, finance, asuransi, checker and viewer hold one of these.
Source: [Ref] Roles, policy matrix.