MazerikMazerik
Documentation home

Capabilities

Recurrence

Detect recurring transaction patterns and cadence trends.

Last updated: 2026-03-24

Why recurrence matters

Recurring behavior helps teams estimate obligations, detect anomalies, and predict cashflow pressure.

Example response

{
  "recurrence": {
    "status": "recurring",
    "cadence": "monthly",
    "expected_next_at": "2026-04-18",
    "confidence": 0.89
  }
}

Operational recommendations

  • Treat low-confidence recurrence as advisory.
  • Validate recurrence windows against posting delays.
  • Recompute cadence after major account behavior changes.

Previous

Categorization

Open previous page

Next

Endpoint Reference

Open next page

Need help?

Talk with our team about architecture and rollout decisions.