Architecture

How the engine detects recurring income and payment patterns (weekly to yearly) via a daily batch job.

Detects both income and payments that occur at a regular interval on an account. The engine detects the following recurring patterns: weekly, fortnightly, monthly, quarterly and yearly, though some slight deviation is permitted. For example, if an income series is paid on the last working day of the month, the engine will recognise this as a monthly series, despite the actual dates varying slightly. Examples of income series include salary, benefit payments and regular transfers from another account. Examples of payment series include mortgages, rent, utility bills and regular transfers to another account.

Regular series detection typically runs as a daily batch over historical transactions previously enriched by the Data Enrichment Engine. Results are delivered via the supported Kafka, API, or SFTP interfaces. The API allows you to retrieve the regular series for a particular account in a synchronous request-response call, and is intended for occasional use only.

At least 3 months of consecutive transaction history are required to make predictions, and only regular series that are still active are returned. The predicted date of the next transaction in the series must be greater than 14 days before the last date a transaction was observed on the account.

The architecture of the transaction categorisation and enrichment component of Moneyhub's Categorisation & Enrichment Engine


Did this page help you?