SAP Reltio's velocity pack for Banking brings together systems and most of these systems duplicate customer information. Match rules define the criteria Reltio uses to determine whether two records are duplicates.

SAP Reltio's velocity pack for Banking comes with predefined match rules specific to the industry. Take a look at the match rules types defined for a specific entity in Console > Data Modeler > Entity Types > <entity> > Match rules.

For general information on match rules, see Reltio match and merge. For information on working with match rules, see Configure match rules overview. For descriptions of the match rules that come with SAP Reltio's velocity pack for Banking, see the following sections.

Individual entity type match rules

This table identifies the SAP Reltio's velocity pack for Banking match rules used to master data for the Individual entity type. Use these match rules to create a record for a person master for retail banking customers, applicants, beneficial owners, and authorized signers. Carries KYC and AML due-diligence attributes: tax identifiers (SSN/TIN), government-issued ID documents, citizenship and tax residency for FATCA/CRS reporting, PEP and sanctions flags, screening status, risk rating, and credit score from the primary bureau. Use Organization for legal entities.

(
    Exact on
        Suspect Match On Name
)

(
    Exact on
        Match On Tax ID
)

(
    Exact on
        Match On Government ID
)

(
    Exact on
        Suspect Match On Name And Date Of Birth
)

Organization entity type match rules

This table identifies the SAP Reltio's velocity pack for Banking match rules used to master data for the Organization entity type. Use these match rules to create a record for a legal-entity master for commercial banking customers and their corporate families. Carries banking identifiers (LEI, Tax ID, DUNS), industry classification, legal entity type, registration jurisdiction, and due-diligence attributes (PEP flag, sanctions flag, screening status, risk rating, FATCA status, verification lifecycle) for regulatory compliance. Parent and subsidiary structure is modeled by the OrganizationHierarchy relation, not by a separate entity.

(
    Exact on
        Auto-merge On LEI
)

(
    Exact on
        Auto-merge On Tax ID
)

(
    Exact on
        Auto-merge On DUNS Number
)

(
    Exact on
        Suspect Match On Name And Jurisdiction
)

Household entity type match rules

This table identifies the SAP Reltio's velocity pack for Banking match rules used to master data for the Household entity type. Use these match rules to create a record for a family and economic grouping of individuals, aggregating the customer relationship across its members: internal identifier, primary member reference, total assets, relationship tier, and aggregated risk rating for cross-sell and compliance.

(
    Exact on
        Auto-merge On Household ID
)

FinancialAccount entity type match rules

This table identifies the SAP Reltio's velocity pack for Banking match rules used to master data for the FinancialAccount entity type. Use these match rules to create a record for a polymorphic account master covering deposits, cards, loans, and mortgages, with the terms specific to each subtype held in their own nested groups — overdraft terms, card terms, loan terms, mortgage terms. Balances are multi-valued and typed, so ledger, available, and pending amounts coexist on one record. Consolidates a customer's full relationship across every line of business into a single best-version profile.

(
    Exact on
        Account Number At The Same Institution
)

(
    Exact on
        Internal Account ID
)

Product entity type match rules

This table identifies the SAP Reltio's velocity pack for Banking match rules used to master data for the Product entity type. Use these match rules to create a record for a banking product catalog master for deposits, cards, lending, and mortgage offerings. Carries features, pricing (interest rates, fees), eligibility rules, and productType discriminator. Applications and accounts link to Product for product-definition reference.

(
    Exact on
        Product Code
)

Banker entity type match rules

This table identifies the SAP Reltio's velocity pack for Banking match rules used to master data for the Banker entity type. Use these match rules to create a record for a bank employee (relationship manager, loan officer, branch staff) with book-of-business assignments to customers and accounts. Posted to a branch via BankerToHomeBranch, which groups staff by branch for reporting and service routing. Job function is carried by `role` and business line by `department`; the pack models no reporting lines between bankers.

(
    Exact on
        Employee ID
)

(
    Fuzzy on
        Name And Role
)

Location entity type match rules

This table identifies the SAP Reltio's velocity pack for Banking match rules used to master data for the Location entity type. Use these match rules to create a record for an address master covering both customer addresses and bank branches. Carries branch-specific attributes (branchCode, branchManager, hoursOfOperation, locationType) for physical and virtual service locations in retail and commercial banking.

(
    Exact on
        Auto-merge On Address Line And Postal Code
)

(
    Exact on
        Auto-merge On Branch Code
)

Application entity type match rules

This table identifies the SAP Reltio's velocity pack for Banking match rules used to master data for the Application entity type. Use these match rules to create a record for an account or loan application, from submission through underwriting decision to the account it opens. Carries the product requested, the decision and its reason, and the underwriting inputs (credit score, income, collateral, ratios). A first-class entity rather than an Interaction subtype, so an application persists as a record in its own right with its own identity and match rules. The applicant resolves to an Individual or Organization profile, and it is that entity's match groups, not this one's, that determine whether the applicant is someone already on the books.

(
    Exact on
        Application ID
)

(
    Exact on
        Internal Application ID
)

(
    Exact on
        Submission Date
        and
        Type
        and
        Amount
)

BeneficialOwner entity type match rules

This table identifies the SAP Reltio's velocity pack for Banking match rules used to master data for the BeneficialOwner entity type. Use these match rules to create a record for a beneficial ownership relationship between Individual and Organization with ownership percentage and control type for UBO traversal. Relationship-as-entity with independent lifecycle tracking effective dates, verification status, and regulatory reporting requirements. Supports AML/KYC compliance and ultimate beneficial owner (UBO) identification per FATF recommendations.

(
    Exact on
        Ownership ID
)

(
    Exact on
        Internal Ownership ID
)

ControllingParty entity type match rules

This table identifies the SAP Reltio's velocity pack for Banking match rules used to master data for the ControllingParty entity type. Use these match rules to create a record for a relationship-as-entity recording who controls a company and on what basis, with the mechanism, percentage, chain depth, dates, and evidence needed for regulatory reporting. The controlling party is an Individual or an Organization, never both on one record. Distinct from BeneficialOwner, which carries stakes: use this entity where an equity stake alone does not explain the control, and see the ControlMechanism lookup for the full range, which runs well past voting rights and board seats to contractual arrangements, trusts, proxies, and veto rights. Feeds the OrganizationOwnershipHierarchy graph and FinCEN customer due diligence reporting.

(
    Exact on
        Ownership ID
)

(
    Exact on
        Internal Ownership ID
)

AccountHolder entity type match rules

This table identifies the SAP Reltio's velocity pack for Banking match rules used to master data for the AccountHolder entity type. Use these match rules to create a record for a relationship-as-entity linking an Individual or Organization to a FinancialAccount. The capacity in which the account is held is carried by `role`, and for jointly held accounts each holder's share by `ownershipPercentage`. Independent lifecycle attributes — effective and expiration dates, authorization status — let a holding be opened, closed, and reopened without losing what went before, which is what account authorization and tax reporting need.

(
    Exact on
        Authorization ID
)

(
    Exact on
        Holder
        and
        Account
        and
        Effective Date
)

(
    Exact on
        Account Number
)
and
    Fuzzy on
        Holder Name

(
    Exact on
        Internal Authorization ID
)

AuthorizedSigner entity type match rules

This table identifies the SAP Reltio's velocity pack for Banking match rules used to master data for the AuthorizedSigner entity type. Use these match rules to create a record for a relationship-as-entity linking an Individual to a FinancialAccount they may act on without owning it. Carries what they may do in `permissionLevel`, the legal instrument conferring it in `authorizationType`, monetary ceilings in `transactionLimit` and `dailyLimit`, and the dates and evidence that the authority was granted and remains valid. Distinct from AccountHolder, which records ownership rather than delegated authority.

(
    Exact on
        Authorization ID
)

(
    Exact on
        Internal Authorization ID
)