FAQ Section
DebiCheck

How Do DebiCheck Collections, Tracking and Retries Work?

 

How DebiCheck collections are submitted and processed, how tracking re-presents a collection when funds become available, and the rules for retries.

Once a DebiCheck mandate is authenticated, the real work begins: submitting collections each cycle and getting them paid. DebiCheck gives collectors two structural advantages here — priority processing in the early morning window, and the ability to track an account for funds — which together materially improve collection rates compared with ordinary debit orders.

This page covers how a collection moves through the system, how tracking works, and what your options are when a collection fails.

How is a DebiCheck collection processed?

  1. The service provider submits the collection instruction (via API or host-to-host file, directly or through a payments provider like Kwik).
  2. The consumer's bank verifies the collection against the stored mandate — account, amount within the approved limits, frequency and timing.
  3. Matching collections are queued for processing; non-matching collections are rejected without touching the account.
  4. DebiCheck collections process as first priority in the early morning processing window, after credits. This means the collection hits the account just after salaries and other credits land, and before later debit order streams — a significant advantage when an account holds limited funds.
  5. The outcome — successful or unpaid with a reason code — is returned to the service provider.

What is DebiCheck tracking?

Tracking instructs the bank to monitor the payer's account for available funds for a specified period of up to ten days. If the account has insufficient funds when the collection is first presented, the bank keeps watching; as soon as sufficient funds become available, the account is debited.

Key points about tracking:

  • It turns a single collection attempt into a continuous window of opportunity, catching irregular salary dates and mid-month deposits.
  • The tracking period is specified per collection, up to the ten-day maximum.
  • Where tracking is used, the mandate should disclose it to the payer — see minimum mandate requirements.
  • Registered Mandate (RMS) collections support tracking in the same way — see RMS collections, tracking and settlement.

How do retries work when a collection fails?

If a collection is unpaid and its tracking window closes without funds becoming available, the collection has failed for that cycle. Options then include:

  • Re-presenting the collection on a later date within the current cycle, still within the mandate's terms.
  • Adjusting the collection date going forward (for example to the payer's actual salary date) via a mandate amendment where needed.
  • Engaging the payer to settle the arrears by another method.

Two constraints matter:

  • Every retry is still verified against the mandate, so retries must stay within the authenticated amount, frequency and timing terms.
  • Retrying a collection that failed for a structural reason — account closed, mandate suspended — will fail again. Check the reason code first; see statuses and reason codes.

DebiCheck collections vs ordinary EFT collections

AspectDebiCheckEFT debit order
Pre-processing checkVerified against the bank's mandate registerNo mandate verification
Processing priorityFirst priority, early morning after creditsLater in the processing cycle
TrackingUp to ten days per collectionNot available in the same form
Failed collectionsReason-coded; retry within mandate termsReason-coded; resubmission rules apply
Dispute exposureMatching collections cannot be unfairly disputedEasier for payers to dispute

For the EFT side of this comparison, see unpaids, returns and resubmissions.

How does this look in practice with Kwik?

Kwik submits DebiCheck collections with the tracking window you choose, monitors outcomes across banks, normalises reason codes, and gives you a single view of successful, tracking and unpaid collections so your team can act on genuine exceptions rather than raw bank files.

Copyright © 2026 Kwik Payments