This insight appears based on the following requirements and triggers.

Requirements:

• In order for a transaction to be considered a bill transaction, it must meet all of the following requirements:
  • It must have a status of POSTED
  • It must be a debit transaction
  • It must be associated with a merchant
  • It must be in one of the following categories:
    • Bills & Utilities
    • Internet
    • Mobile Phone
    • Utilities
• The user must have at least one historical debit transaction that is for the same merchant and in the same category as the transaction that is triggering this insight.
• The user must have at least 3 transactions in the last 4 months from the same merchant with the same category.

Trigger:

A transaction is created which meets the requirements above, or a PENDING transaction which meets the defined requirements is updated to a status of POSTED.

This insight appears based on the following requirements and triggers.

Requirements:

• A transaction must meet all of the conditions below in order for a Charge Dispute Refund insight to be generated:
  • The transaction status must be POSTED
  • The transaction must be a CREDIT
  • The system_transaction_rule_guid is set to one of the following:
    • Final dispute
    • Permanent dispute
    • Permanent credit on dispute
  • The transaction must be held in an account with type CHECKING, SAVINGS, or CREDIT_CARD.

Trigger:

A transaction is created which meets the defined requirements, or a PENDING transaction which meets the defined requirements is updated to a status of POSTED.

This insight appears based on the following requirements and triggers.

Requirements:

• A user's credit card account is considered high when all of the following are true:
  • The user has one or more credit card accounts.
  • One or more accounts has hit or passed a user configurable percentage (defaults to 75%).

Trigger:

Whenever an account which meets the specified requirements is updated.

This insight appears based on the following requirements and triggers.

Requirements:

• The user must have one or more credit cards.
• The user must have been charged some amount in interest on these credit cards in the last 90 days.
• There must be an interest charge in the last month.
• A transaction is considered an interest charge when all of the following attributes are true:
  • The transaction type must be DEBIT .
  • The transaction category must be FINANCE CHARGE .
  • The transaction must include "interest" or "finance charge" in the feed description; the case does not matter.
• This insight must not already exist for the previous month.

Trigger:

This insight is automatically generated once per month.

This insight appears based on the following requirements and triggers.

Requirements:

• A user's credit utilization is considered high when all of the following are true:
  • The user has one or more credit card accounts. We limit this insight to only using a maximum of 15 accounts.
  • A warning is generated when:
    • The user's balance is at least 20% or greater of their total credit limit.
    • The user has not had a previous warning or alert credit utilization beat for the current month.
  • An alert is generated when:
    • The user's balance is at least 30% or greater of their total credit limit.
    • The user has not had a previous alert credit utilization beat for the current month.

Trigger:

This insight is created once per week with the scheduler.

This insights appears based on the following requirements and triggers.

Requirements:

In order for a Duplicate Payment insight to be generated, at least two transactions must have either:

• The same amount and merchant guid, or
• The same amount and description but no merchant guid

In addition, the transactions must be debit transactions posted under the same account and have dates (transacted or posted dates) that are no more than 15 minutes apart. Account type should be either CHECKING or CREDIT_CARD.

Trigger:

A duplicate transaction is created in the system based upon the requirements above. It then publishes this duplicate payment information which is subscribed to and used to generate the insight. 

This insight appears based on the following requirements and triggers.

Requirements:

• Debit only transactions
• Occurs in one of the following categories:
  • Fees & Charges
  • ATM Fee
  • Bank Fee
  • Finance Charge
  • Late Fee
  • Service Fee
• Limit to five insights each week

Trigger:

A transaction is created which meets the defined requirements.

This insight appears based on the following requirements and triggers.

Requirements:

• The amount is greater than a default threshold of $500, or by a configured amount.
• Debit only transactions
• Only spend account types (Checking, Savings, Credit Card)
• Occurs in one of the following categories:
  • Auto & Transport (not auto payments or auto insurance)
  • Bills & Utilities
  • Business Services
  • Education (not student loans)
  • “Entertainment”
  • Food & Dining
  • Health & Fitness
  • Home (not mortgage or home insurance)
  • Kids
  • Personal Care
  • Pets
  • Shopping
  • Travel
  • Uncategorized
• Transaction has not been triggered in another insight already

Trigger:

A transaction is created which meets the defined requirements.

This insight appears based on the following requirements and triggers.

Requirements:

• This insight is account specific.
• The account balance threshold is tied to the corresponding Notification Profile from MoneyMap associated with the account.
• This insight does not depend on the top-level Low Account Balance Notification Profile being enabled, it only checks for Notification Profiles being enabled for specific accounts.
• The account did not trigger a previous Low Account Balance beat within 15 days.

Trigger:

This insight is triggered when the specified requirements are met.

This insight appears based on the following requirements and triggers.

Requirements:

• In order for the Micro-Deposits insight to be generated, two transactions must:
  • Have the is_micro_deposit classifier
  • Have the same merchant_guid
  • Have the same description
  • Be in a deposit account
  • Transactions must be credit transactions posted under the same account and must have occurred within 24 hours of each other. Account type should be either CHECKING or SAVINGS.

Trigger:

Two micro-deposits are created in the system based upon the requirements above.

This insight appears based on the following requirements and triggers.

Requirements:

• This insight must not already exist for the previous month.
• The user must have at least 1 Checkings or Savings account.
• The user must have at least 2 months in the previous 4 months with transactions in Checkings or Savings account(s).
• The user must have transactions for the previous month in Checkings or Savings account(s).

Trigger:

This insight is created once per month with the scheduler.

This insight appears based on the following requirements and triggers.

Requirements:

• A subscription is considered a new subscription when all of the following are true:
  • The transaction status must be POSTED.
  • The transaction is associated with a scheduled payment.
  • The transaction is a debit.
  • The transaction is associated with a merchant.
  • The scheduled payment has scheduled_payment_type set to 1.
  • We are unable to find a previously created transaction for the same Scheduled Payment. We look as far as 13 months ago for a matching transaction.

Trigger:

This insight triggers when a transaction is created which meets the defined requirements, or a PENDING transaction which meets the defined requirements is updated to a status of POSTED.

This insight appears based on the following requirements and triggers.

Requirements:

• Two transactions are required in order for a Subscription Price Increase beat to be generated:
  • The first transaction is the transaction that is being created.
  • The second transaction is the previous transaction associated with the subscription. The search range for this transaction starts one second before the date time of the first transaction and goes back 13 months.
• Both of these transactions must be:
  • Assigned to the same merchant (merchant_guid).
  • Assigned to the same scheduled payment (scheduled_payment_guid)
• The difference in the amount of the two transactions must be over 50 cents ($0.50).
• The type of the assigned scheduled payment must be 'SUBSCRIPTION'.

Trigger:

This insight triggers when a transaction is created which meets the defined requirements, or a PENDING transaction which meets the defined requirements is updated to a status of POSTED.

This insight appears based on the following requirements and triggers.

Requirements:

• A user must have at least one checking account.
• Account balance information must be available for the account in question for the current date and each day for one month prior.
• An Overdraft Prediction must exist with a prediction value of true.
• The user can't already have a transparent overdraft warning beat for a given account that was active within the last 7 days.

Trigger:

This insight triggers when the requirements mentioned above are met.

This insight appears based on the following requirements and triggers.

Requirements:

• This insight must not already exist for the ScheduledPayment.
• ScheduledPayment occurs_on date must be in the future.
• ScheduledPayment must be for a bill.
• ScheduledPayment must not be from the same merchant, on the same day, and for the same amount.

Trigger:

This insight is triggered when a user's ScheduledPayment(s) is created/updated.

This insight appears based on the following requirements and triggers.

Requirements:

• Total of small purchase amounts from the previous week must be at least as high as the Small Purchases Total Threshold set on the client's insight profile (default value is $30).
• A transaction is considered a small purchase when:
  • the amount is less than the Small Purchase Ceiling Amount configured by the client (default value is $10).
  • it is a Debit transaction.
  • it comes from a Savings, Checking or Credit Card account.
  • the top level category is one of the following:
    • Auto & Transport
    • Bills & Utilities
    • Business Services
    • Education
    • Entertainment
    • Fees & Charges
    • Financial
    • Food & Dining
    • Gifts & Donations
    • Health & Fitness
    • Home
    • Kids
    • Personal Care
    • Pets
    • Shopping
    • Travel
    • Uncategorized
  • the category is not one of the following:
    • Auto Insurance
    • Auto Payment
    • Babysitter & Daycare
    • Baby Supplies
    • Child Support
    • Doctor
    • Groceries
    • Health Insurance
    • Mortgage & Rent
    • Utilities

Trigger:

This insight is triggered once per week.