Compliance

Agreement coverage and compliance requirements

Compliance & Agreement Coverage

This section covers compliance requirements and agreement references for the Kasi Collections API.

Collections Result CSV Fields (Section 5.2a)

All 13 required fields are included in collection result exports:

#FieldDescription
1period_monthCollection period (YYYY-MM)
2customer_idInternal customer identifier
3external_customer_refYour customer reference
4policy_numberPolicy identifier
5product_codeProduct identifier
6collection_amount_duePremium amount due
7collection_amount_collectedAmount successfully collected
8shortfallUncollected amount
9collection_statusPAID_FULL / PAID_PARTIAL / UNPAID / CANCELLED
10first_attempt_dateDate of first collection attempt
11last_attempt_dateDate of most recent attempt
12number_of_attemptsTotal attempts made
13last_failure_reasonReason for last failure (if any)

Settlement Components (Section 6.3)

All required fee components are included in settlements:

ComponentCalculationRateAgreement Reference
Distribution Fee25% of total collections25%Section 6.1
Collections Fee3.5% of total collections3.5%Section 6.2
Total FeesDistribution + Collections--
VAT15% of total fees15%Section 6.3c
Net AmountCollections - Fees - VAT--

Service Level Agreement

RequirementDeadlineAgreement Section
Collections executionThroughout monthSection 4.2
Full collection targetBy month endSection 4.2d
Settlement generationBy 1st of following monthSection 6.4a
Invoice deliveryBy 2nd of following monthSection 6.4b
EFT payment + CSV exportBy 3rd of following monthSection 6.4c
Dispute window30 days from receiptSection 6.5

Policy Management (Section 5.1)

Policy Creation (Section 5.1a)

  • Individual Creation: POST /policies - Add policies programmatically
  • Bulk Import: POST /policies/import - Bulk onboard policies at start of month

Policy Updates (Section 5.1b)

  • Premium Changes: Update collection_amount for upgrades/downgrades
  • Status Changes: Update status for cancellations/lapses
  • Endpoint: PATCH /policies/{id}

Collections (Section 4.2 & 5.2)

Smart Collections Engine (Section 4.2)

The Smart Collections Engine:

  • Analyzes customer income patterns
  • Optimizes collection timing
  • Handles partial collections
  • Auto-retries failed collections
  • Targets full collection by month end

Collection Queries (Section 5.2b)

  • Endpoint: GET /collections/{id}
  • Use Case: Check individual collection progress
  • Returns: Complete collection status and history

Collection Reports (Section 5.2a)

  • Endpoint: GET /reports/collections
  • Use Case: End-of-month reconciliation
  • Format: CSV with 13 required fields

Settlements (Section 6.4)

Settlement Generation (Section 6.4a)

  • Endpoint: POST /settlements
  • Timeline: Generated by 1st of following month
  • Includes: All fee calculations and net amount

Invoice Delivery (Section 6.4b)

  • Timeline: Delivered by 2nd of following month
  • Format: Available via settlement details endpoint

EFT Payment & Export (Section 6.4c)

  • Timeline: Processed by 3rd of following month
  • Export: GET /settlements/{id}/export - CSV download
  • Payment: EFT to your account with payment reference

Dispute Window (Section 6.5)

Fee Structure (Schedule 1)

Fee structure is defined in Schedule 1 of the service agreement:

  • Distribution Fee: 25% of total collections
  • Collections Fee: 3.5% of total collections
  • VAT: 15% of total fees
  • Net Amount: Collections - Fees - VAT

See Fee Structure for detailed calculations.

Data Protection

POPIA Compliance

All data handling complies with the Protection of Personal Information Act (POPIA) 2013:

  • Data encrypted in transit and at rest
  • Secure API key authentication
  • Access controls and audit trails
  • Data retention policies

Data Retention

  • Minimum: 30 days (dispute window)
  • Recommended: 7 years (financial records compliance)
  • Export Access: Available throughout retention period