Restriction Codes and Attribute Controls

Chinese source: 账户管控码与属性控制
Locale: en-US
Audience: Internal learning

Key Terms

Chinese	English	Usage Note
管控码	Restriction Code / Account Control Code	Use restriction code by default in learning pages.
属性控制	Attribute Control	Control attributes attached to account objects.
客户层	Customer Level	Applies to the customer entity.
客户账户层	Customer Account Level	Applies to the account container.
子户层	Sub-account Level	Applies to a specific deposit account.

Concept

A restriction code is a control label that expresses whether a customer, customer account, or sub-account is under certain rules. It is not necessarily an accounting transaction, but it can affect whether later transactions are allowed, restricted, or require additional verification or authorization.

Restriction code = control label on an account object.
Restriction status = the visible result of one or more controls or business states.

When you see an account is restricted, ask what caused the restriction, at which level, what transaction types it affects, who set it, and whether it can be released.

Three Control Levels

Level	Common Field	Business Meaning	Impact Scope
Customer level	Customer restriction code	Applies to the customer entity.	May affect multiple accounts or businesses.
Customer account level	Customer account restriction code	Applies to the account container.	Affects capabilities under the customer account.
Sub-account level	Sub-account restriction code	Applies to a specific sub-account.	Affects a specific product, currency, or deposit account.

Relationship to Special Operations

Restriction codes are not the same as freeze, stop-pay, or legal debit, but they often relate.

Object	Relationship
Restriction code	Label or attribute expressing control state.
Freeze / stop-pay / legal debit	Business action or source that may create a control state.
Restriction status	Inquiry-page result that may come from codes, special operations, product rules, or risk rules.
Special operation record	Source record used to trace control setup, release, and history.

Maintenance Principles

• Identify the level before maintaining the code.
• Do not expand to customer level if sub-account level is enough.
• Setting a code affects customer rights; releasing a code restores transaction capability.
• Keep operator, authorization, before/after values, timestamp, and business reason.
• Do not release controls based only on verbal customer explanation.