Collection FAQ

What triggers the creation of a collection ticket?

A collection ticket is automatically generated in Mobiloan whenever there is an indication that a repayment obligation has not been properly executed. This can occur under the following conditions:

1. Adverse Bank Response on Promissory Notes

   • If the bank returns an adverse response on a promissory note, the system automatically raises a collection ticket.

2. Unposted Manual Repayment Instalment

   • If a manual repayment instalment has been scheduled but was not successfully posted to the loan account, a collection ticket is generated.

---

Situations Where Collection Tickets Should Not Be Created

• Non-Mobiloan Clients

  • Do not create tickets for clients that are not registered or managed within Mobiloan.

• Successful Settlement or Tracking

  • No ticket should be created where the transaction has a successful response (207) or is in tracking status (211).

• Unpaid or Non-Disbursed Loans

  • If the loan has not yet been paid out, a collection ticket will not be generated.

• Loans Fully Settled or Overpaid

  • Tickets are not created if the loan is already fully receipted or has been overpaid.

---

Excluded Response Codes

The following transaction response codes are specifically excluded from triggering collection ticket creation, regardless of their outcome:

POS Transactions

• 240 – POS Balance Enquiry Settlement (any response)

• 241 – POS Credit Card Purchase Settlement (any response)

• 242 – POS Debit Card Purchase Settlement (any response)

• 250 – POS Reversal Settlement (any response)

• 251 – POS Refund Settlement (any response)

Instalments & Recall

• 410 – Instalment Recall (any response)

AEDO Transactions

• 503 – AEDO Presentment Result (responses 207, 211)

• 504 – AEDO Tracking (any response)

NAEDO Transactions

• 508 – NAEDO Presentment Result (any response)

• 509 – NAEDO Tracking (any response)

• 510 – NAEDO Presentment Dispute (no responses)

• 511 – NAEDO Presentment Dispute After 40 Days (no responses)

EFT Transactions

• 533 – EFT Dated Presentment Result (responses 207, 211)

• 534 – EFT Same Day Presentment Result (responses 207, 211)

• 536 – EFT Presentment Dispute (no responses)

• 540 – Grindrod EFT Presentment Result (responses 207, 211)

• 541 – Grindrod EFT Presentment Dispute (no responses)

• 544 – Social Grant EFT Presentment Result (responses 207, 211)

• 545 – Social Grant EFT Presentment Dispute (no responses)

ACOL Transactions

• 546 – ACOL Presentment Result (responses 207, 211)

• 547 – ACOL Tracking (any response)

• 548 – ACOL Presentment Dispute (no responses)

• 549 – ACOL Mandate Suspension (no responses)

• 550 – ACOL Bank Error (no responses)

• 555 – ACOL Creation Authentication (any response)

• 556 – ACOL Edit Authentication (any response)

• 557 – ACOL Cancellation Authentication (any response)

RMAN Transactions

• 570 – RMAN Presentment Result (responses 207, 211)

• 571 – RMAN Tracking (any response)

• 572 – RMAN Presentment Dispute (no responses)

• 573 – RMAN Mandate Suspension (no responses)

• 574 – RMAN Bank Error (no responses)

• 575 – RMAN Creation Registration (any response)

• 576 – RMAN Edit Registration (any response)

• 577 – RMAN Cancellation Registration (any response)