Pieprasīt kavētu klienta rēķinu vispirms pieklājīgi, tad stingri

Kad izmantot

A customer has not paid an issued invoice by its due date. Not for creating or sending the invoice in the first place — use money.issue-invoice. Not for an invoice the company owes to a supplier — use money.process-incoming-invoice. If the customer turns out to be insolvent or the debt is clearly dead, this playbook hands over to money.write-off-bad-debt.

Pirms sāc

• The invoice exists in the money module with a due date and a customer contact.
• Delivery is documented: signed acceptance, delivery note, or a written "thank you / works for us" from the customer.
• The company's payment terms and any late-interest clause in the contract are known.
• Reminder templates exist in the mail module (polite / firm / final demand).

Ko izpilde pieprasa4

Ceļš9 soļi

1. S1

   Detect and list the overdue invoiceaģents

   Read the invoice-overdue event; pull the invoice from the money module: id, amount, due date, days overdue.

   Izdarīts, kad the invoice appears on the overdue list with its age in days.

2. S2

   Check the facts before any mail goes outaģents

   Confirm delivery and acceptance, the correct billing contact, and search mail and tickets for a dispute, a payment promise, or a payment already received but unreconciled.

   Izdarīts, kad a two-line note per invoice says: delivered (how known), disputed (yes/no), any promise found.

   ⛔ An invoice under a genuine dispute must not enter the reminder ladder — route it to the owner instead.

3. S3

   Draft reminder 1 — polite assumption of an oversightaģents

   Use the polite template: invoice number, amount, due date, a re-attached copy, one line asking for a payment date if there is a problem. No interest, no threats.

   Izdarīts, kad the draft sits in the mail module with the invoice attached, addressed to the billing contact.

4. S4

   Approve reminder 1īpašnieksvajag apstiprinājumu · īpašnieks

   Apstiprinājums · S4 · īpašnieks — izpilde apstājas, līdz nosaukts cilvēks ieraksta lēmumu

   The agent shows the draft and the S2 note.

   Izdarīts, kad the owner approves (or edits) the draft and names the recipient.

   ⛔ If the S2 note shows a dispute, the owner decides here whether to chase at all.

5. S5

   Send reminder 1 and log itaģents

   Send from the company's role address, record sent-date and recipient on the invoice.

   Izdarīts, kad the reminder trail on the invoice shows the first entry. If payment arrives, stop: reconcile in the money module and record the outcome in S9.

6. S6

   Send reminder 2 after the grace periodaģentsvajag apstiprinājumu · īpašnieks

   Apstiprinājums · S6 · īpašnieks — izpilde apstājas, līdz nosaukts cilvēks ieraksta lēmumu

   Default grace: 7 calendar days after reminder 1 with no payment and no promise. Firmer tone; state that statutory late-payment interest applies from the due date (⚠ jāpārbauda the rate and article for the contract's jurisdiction before naming a figure).

   Izdarīts, kad reminder 2 is sent and logged with its date.

7. S7

   Send the final demand after a further silenceaģentsvajag apstiprinājumu · īpašnieks

   Apstiprinājums · S7 · īpašnieks — izpilde apstājas, līdz nosaukts cilvēks ieraksta lēmumu

   Default: 7–10 days after reminder 2. Final-demand template: full amount, interest to date, a stated deadline (⚠ jāpārbauda a reasonable deadline — commonly 7–14 days — and any formal demand wording required before court in Latvia; check likumi.lv and the company's lawyer's standing guidance), and the statement of the next step.

   Izdarīts, kad the final demand is sent and logged.

8. S8

   Decide escalationīpašnieksvajag apstiprinājumu · īpašnieks

   Apstiprinājums · S8 · īpašnieks — izpilde apstājas, līdz nosaukts cilvēks ieraksta lēmumu

   Options: payment plan, hand to a debt-collection service, court claim, or write off. The agent prepares a one-paragraph summary: amount, trail dates, customer history, cost of each option.

   Izdarīts, kad the owner has picked one and the decision is recorded on the invoice.

   ⛔ Handing the debt to a collector or filing a claim is a third-party action by the company — only on the owner's named decision, never the agent's.

9. S9

   Record the outcomeaģents

   Update the invoice status (paid / in collection / written off); compute interest actually claimed or waived; link the write-off to money.write-off-bad-debt if chosen; add a task for any promised payment date.

   Izdarīts, kad the invoice shows a closed status and the trail is complete.

Pārbaudes — kā zinām, ka izdevās

• Read the trail back: every reminder has a date, a recipient and the approving owner's name.
• The money module shows the invoice in a terminal state — nothing left "open" silently.
• If interest was claimed, the amount matches the rate and article noted in the source check.
• The customer's ledger balance in the money module agrees with the invoice status.

Ja noiet greizi

Ko atstāj katrs solis

1. S1the invoice appears on the overdue list with its age in days.
2. S2a two-line note per invoice says: delivered (how known), disputed (yes/no), any promise found.
3. S3the draft sits in the mail module with the invoice attached, addressed to the billing contact.
4. S4the owner approves (or edits) the draft and names the recipient.
5. S5the reminder trail on the invoice shows the first entry. If payment arrives, stop: reconcile in the money module and record the outcome in S9.
6. S6reminder 2 is sent and logged with its date.
7. S7the final demand is sent and logged.
8. S8the owner has picked one and the decision is recorded on the invoice.
9. S9the invoice shows a closed status and the trail is complete.

Ko saglabāt

Invoice id and amount · every reminder's sent date, recipient and approving owner · the S2 delivery note · the final demand copy · the escalation decision (who, when, which option) · any payment plan terms.

Kā šī procedūra uzlabojas

After every 10 runs ask: how many days from due date to payment on average, and which step added the most delay? How many invoices reached S7 — is the final demand working, or should the grace periods change? Did any chase hit a dispute S2 should have caught? Did any claimed interest rate turn out to be wrong? A new version changes the step behind the delay or the miss, and says so in its change note.