One Person, One Allowance: Catching Duplicate Customer Records Before They Double a Limit

A sending limit is only as strong as your idea of who the customer is. When the same person signs up twice, with a new email, a second phone number or a name spelled a little differently, every limit, document tier and risk check you built is applied to half of them at a time. Their allowance doubles, their history splits in two, and nobody sees the whole picture.

This guide is for compliance heads, MLROs and operations leads who want limits that follow the person rather than the account. The approach applies on any platform; where RemitSo handles a step, we say so.

Most remittance platforms measure limits per customer record. That is reasonable until one person holds more than one record. Then three things go wrong at once.

• Limits double. A customer at the 90-day limit on one record starts again from zero on the other. A policy that asks for source of funds above a threshold never sees the combined total.
• Document tiers reset. The second record asks for the basic documents again and nothing more, so the customer meets the easy tiers twice instead of the harder tier once.
• History splits. A block, a watch-list entry or a sanctions ruling sits on one record. The other record sends as if none of it had happened.

Not every duplicate is deliberate. People forget they already have an account, change phones, or sign up again after a failed verification. That is why the answer is not to refuse every second sign-up, but to find the records, decide what they are, and then count the person.

Duplicate records leave traces. The strongest are data that should be unique to one person:

Run the check at sign-up and again whenever a customer adds a document or a payment method, because the link often appears later. A customer who signed up with an email address may only reveal their passport number at the first document tier.

A matching signal is a question, not an answer. Every possible pair needs one of three outcomes, made by a person and recorded:

1. The same person. Link the records, so everything that follows reads them as one.
2. Not a real pair. Dismiss it: the match was coincidence, for example a common name with a different date of birth on closer inspection.
3. Different people with a genuine connection. Record that they are different people, such as a parent paying for an adult child from the same account. This stops the pair coming back every week.

The third outcome matters more than it looks. Without it, investigators clear the same family pair again and again, and the queue fills with decisions already made.

Hold, or count while you decide

While a pair waits for a decision, you have a choice. You can let both records keep sending and count them together, or you can hold records with strong evidence from quoting or sending until someone decides. Holding is safer but costs good customers time. Counting keeps them moving while still applying the combined limit. Many operators start by counting and switch the hold on once the queue is under control and support knows what to tell customers.

Linking two records only helps if your controls then use the link. Check each one:

• Sending limits add up what every linked record has sent in each window.
• Document tiers use the combined total, so the person meets the tier their real activity has reached.
• A sending block on one record stops the person, not just that account.
• The watch list applies to every linked record.
• Sanctions screening and its rulings follow the person.
• The compliance dashboard shows the person once, so risk counts are not inflated by duplicates.

Raised limits

Decide how a raised limit works for a linked person. A sensible design: a raise granted on one record applies to that record, and every linked record's sends count toward it. That way a raise cannot be multiplied by opening another account, and it is clear which record the decision was made on.

The figures are illustrative. The operator's 90-day limit is 9,000, with source of funds required above 6,000.

Record B was opened with a new email after the customer forgot their password. Both records hold the same passport number. The pair appears for review; an investigator confirms it is one person and links the records. The next quote reads the combined total: the customer is over the limit and is asked for source of funds. Support explains, the customer uploads payslips, and an officer decides on a raise with the full picture in front of them.

Without the link, the customer would have kept sending on two records at 5,000 to 5,500 each, under every document tier, with nobody aware of a 10,500 total.

• How pairs are found: which signals you use and why.
• Each decision: who decided, when, which outcome, and the reason.
• What linking changed: limits and tiers that applied after the link, for a sample of linked customers.
• The queue: how many pairs are waiting and how long they wait.

Since release 2026.11.2, RemitSo treats records that belong to one person as one. Your team still decides on every pair and on when to switch the hold on.

• Records found and linked: customer records that share an identity document, a name and date of birth, or a payment account are found and linked, so a second registration is not a second allowance.
• Controls read the person: sending limits, document tiers, the sending block, the watch list, sanctions screening and the Compliance Dashboard all read the linked person.
• A Possible Duplicate Customers desk: pairs that need an investigator wait in one place. Open a pair to compare the two records, then link them as one person, dismiss the pair, or record that they are different people.
• A hold you switch on when ready: records with strong evidence can be held from quoting or sending until someone decides. The hold is off until your installation switches it on; until then they are counted together.
• Raised limits that cannot be multiplied: a raise covers one customer record, and every linked record's sends still count toward it.
• A risk indicator for possible duplicates among the 47 ready-made indicators, for use in your own risk rules, and an AI Assistant (optional add-on) that explains risk triggers and linked records when a team member asks why a customer cannot send.

The upgrade to 2026.11.2 needs preparing for: a review of risk rules built on the retired indicator, new permissions to grant, alerts to subscribe and a backfill run afterwards. Read the release notes, see the admin features, or book a demo.