Summary

Entities are resources for which payments are made. An entity can be either an individual or a business and can have one or multiple users assigned to it.

Entity States

Accepted: Initial entity data has been staged on the Routefusion system
Finalized: The entity details have been finalized and committed to Routefusion
Pending: The entity onboarding process is underway
Request For Information: A request for information is open for the entity
In Review: The request for information has been completed by the customer and is being reviewed
Rejected: The entity has been rejected from onboarding to Routefusion
Verified: The entity has passed onboarding and can begin interacting with Routefusion

Compliance Requirements

Entities may need to undergo a compliance check depending on your approved model. This process ensures that the entity meets regulatory and legal standards, including:

Identity Verification: Confirming the identity of the entity.
Risk Assessment: Evaluating the potential risk associated with the entity.
Regulatory Adherence: Ensuring compliance with anti-money laundering (AML) and Know Your Customer (KYC) regulations.

Uniqueness Constraints

Each organization must maintain uniqueness for entity identifiers to prevent duplicate records:

Business Entities
- business_name must be unique within the organization.
- tax_number must be unique within the organization.
Personal Entities
- email must be unique within the organization.
- tax_number must be unique within the organization.

Note

Requirements for creating an entity may change if you are not currently onboarded with Routefusion. Compliance requirements may also vary based on the nature of the entity and the jurisdiction in which it operates.

Permission Requirements: Admin

For the countries available for onboarding businesses and freelancers view here

Compliance Onboarding