KareTech Docs

Payment Application and Customer Reconnection

Critical rules for payment application, billing date rules, and reconnection procedures

Payment Application and Customer Reconnection

Version: 1.0
Created: 2026-02-11

Critical Rules

Never Do This (Unless Explicitly Stated)

  • NEVER apply payment for the current month unless the billing date has passed
  • NEVER apply payment for future months unless customer explicitly paid in advance
  • NEVER apply the "last invoice" if it is for the current or future month
  • NEVER assume customer paid for multiple months

Always Do This

  • ONLY apply payment for OVERDUE months (past billing dates)
  • Check billing date (28th of every month) before applying payment
  • Verify monthly rate from customer's service plan
  • Calculate exact overdue amount based on overdue months only
  • Require explicit confirmation for any advance payments

Billing Schedule

Billing Date: 28th of every month
Monthly Rate: Varies by customer plan (must verify)

Example Month Timeline

January 1-27:   January NOT due yet
January 28:     January billing date (January now due)
January 29-31:  January overdue

February 1-27:  February NOT due yet, January still overdue
February 28:    February billing date (February now due)

Payment Calculation Formula

Step 1: Identify Overdue Months

Overdue Month = Any month where the 28th has passed and no payment received

Example (Today = February 11, 2026):

  • December 28, 2025 — PASSED → December overdue if unpaid
  • January 28, 2026 — PASSED → January overdue if unpaid
  • February 28, 2026 — NOT PASSED → February NOT overdue

Step 2: Check Payment History

Look at last payment date in UISP. If last payment was December 2025, only January 2026 is overdue.

Step 3: Calculate Payment Amount

Payment Amount = (Number of Overdue Months) × (Monthly Rate)

Example: 1 overdue month × GYD 10,000 = GYD 10,000

Step 4: Apply Payment

Apply ONLY for calculated overdue months.

Reconnection Procedure

After applying payment:

# Unsuspend service (correct endpoint)
PATCH /crm/api/v1.0/clients/services/{serviceId}/cancel-suspend
 
# NOT /unsuspend -- that returns 404

Suspension reason IDs:

  • 1001 — Non-payment (standard)

To suspend: PATCH /clients/services/{id}/suspend with {"suspensionReasonId": 1001}

To unsuspend: PATCH /clients/services/{id}/cancel-suspend (no body needed)

Common Mistakes

MistakeConsequencePrevention
Applying current month paymentCustomer overpaysAlways check billing date vs today
Using /unsuspend endpoint404 errorUse /cancel-suspend
Applying "last invoice" amountMay include future monthsCalculate from billing dates