Guide from the checks

Recurring series can signal a liability to review

Repeated debit descriptions and cadence can make a debt pattern easier to review. This guide explains the signal, its limits, and why a flag is not a verdict.

Repetition adds context

A single debit description can be ambiguous. The same keyword appearing in a series of debits on a regular cadence gives a broker more context to review. Broker Lens groups transactions that share a normalised description, direction, cadence, and similar timing.

The recurring-series detector needs at least three transactions. It recognises weekly, fortnightly, and monthly patterns with the tolerances defined in the deterministic checker. Amounts can vary: a variable-amount buy-now-pay-later series can still be a recurring series.

How the debt signal is produced

The debt-signal check looks for terms from its maintained keyword library in debit descriptions. A keyword hit inside a recurring debit series is a primary signal. A one-off keyword hit is a secondary notice. Both are review prompts, and neither is a conclusion about the applicant.

For a recurring match, the result links the matching transaction rows and records the cadence and representative amount. That makes the question concrete: review the descriptions, the dates, and the application before deciding what the pattern means.

What it does not establish

The detector does not identify a liability from a merchant name alone. Descriptions can be incomplete, and an ordinary purchase can resemble a keyword. A series can also be genuine without being relevant to the application. The check therefore asks for a review rather than labelling a transaction as undeclared or fraudulent.

The boundary matters most when a description is close to a keyword but not an exact word-boundary match. Precision is preferred to creating repeated false alarms. If the source description is unclear, inspect the original statement and record the explanation outside the automated result.

A practical review sequence

  1. Open all rows linked to the signal, not just the first match.
  2. Confirm the cadence and whether the descriptions refer to the same service.
  3. Compare the pattern with the applicant's explanation and supporting documents.
  4. Record the outcome in the broker's normal review process.

The detector makes a repeated pattern visible. The broker supplies the context and the decision.

A flag is a prompt for human review, not a verdict. Keep the source document beside the extracted evidence when you decide what to do next.