Troubleshooting | Duplicate Account Records Returned from Member Aggregation

Last updated: July 1, 2026

In some cases, a member connection may return duplicate account records — where the same physical account appears multiple times in the payload from GET /users/{user_guid}/members/{member_guid}/accounts. This can happen when an aggregation job encounters an error that prevents stale records from being properly closed out, causing duplicate entries to persist alongside updated records.

Common Signs of Duplicate Accounts

  • Multiple account records sharing the same product name and account number

  • Accounts with the same created_at and imported_at timestamps

  • Account numbers appearing in slightly different formats (e.g., 1000 and 81000, 1004 and 31004) with matching product names

  • A stale account's balance matching a newer account's feed_minimum_payment value

  • An unusually high number of open accounts returned for a single member

Why This Happens

Duplicate records are typically caused by a failed or interrupted aggregation job that prevents old account records from being marked as closed. When a subsequent aggregation runs, both the stale and updated records may be returned together. In some cases, the original sync interruption may fall outside the active logging retention window, making it impossible to identify the exact root cause for older duplicates.

How to Resolve Duplicate Account Records

To clear duplicate account data and ensure the user sees accurate account information, follow these steps:

  1. Contact MX Support to trigger a fresh aggregation job for the affected member connection. A successful re-aggregation will pull only the correct, deduplicated accounts.

  2. Once the fresh job has completed, ask the user to remove their existing connection and re-add a new connection. This ensures that any cached duplicate data is fully cleared and the user sees the correct account details in your app.

Deduplication and Stable Identifiers

If you need to deduplicate or match member accounts in your own system, contact MX Support with the relevant member_guid and, optionally, the user_guid. This allows the MX team to review the specific data behavior for your setup and provide a definitive recommendation on which fields to rely on for stable identification and deduplication.

Still Seeing Duplicates After Reconnecting?

If duplicate records persist after the user has removed and re-added their connection, please reach out to MX Support with the affected member_guid and user_guid so the issue can be investigated further.