purpose code declaring why funds are moving. Lumx uses the purpose for AML monitoring, regulatory reporting, and to match the transaction against the correct destination holder relationship.
Accepted values
| Code | When to use |
|---|---|
PERSONAL_ACCOUNT | Customer moving funds to or from an external account they own. Only valid with destinations whose holder.relationship is SELF. |
INVESTMENT | Capital allocated to securities, funds, or other investment vehicles. |
REAL_ESTATE | Purchase, sale, or rental payments related to real property. |
TRADE_TRANSACTIONS | Cross-border payments for goods or services: supplier invoices, import/export settlement. |
TAX | Tax remittance to a domestic or foreign tax authority. |
LOAN | Loan disbursement, repayment, or inter-company capital injection. |
BILLS | Routine bill payment: utilities, subscriptions, recurring services. |
EXPENSES_REIMBURSEMENT | Reimbursing employees or contractors for business expenses. |
PROFESSIONAL_SERVICES | Payments for consulting, legal, accounting, or other professional services. |
Choosing the right code
Pick based on the economic substance of the transaction, not the rail or destination type. Two heuristics:- If the customer and destination holder are the same legal entity, use
PERSONAL_ACCOUNT. - Otherwise, pick the code that best describes the underlying commercial activity. When more than one applies, go with the more specific one:
TAXoverBILLS,EXPENSES_REIMBURSEMENToverPROFESSIONAL_SERVICES.
Related resources
Transactions
Full transaction lifecycle and request schemas.
Destinations
Holder relationships that pair with each purpose code.
Treasury management
Worked example of purpose codes across an inter-company flow.
Request for Information
What happens when purpose doesn’t match the underlying activity.