Add Billing Company Fee

Custodian; value comes from the clear_custodian_broker_no_all dynamic enum, not fixed.

Call GET /v1/datasets/refs/clearing_agents_all to retrieve the current data dictionary, and use the returned entry's key as this field's value.

The billing item ID, selected via the billing item selector.

The billing-item object, containing fields such as id/name_loc, submitted together with the selected billing scenario.

The measurement type; values come from the billing_fee_metric_type dynamic enum, such as 1 = filled quantity, 2 = filled amount, 9/10/11 = option-related, etc.; filtered by the selected billing item.

Allowed values:

• 1 - Transaction Quantity(Fractional support)
• 2 - Transaction Amount
• 3 - Single Billing By Corresponding granularity
• 4 - Options Quantity
• 5 - Upstream
• 6 - Number Of Billing Contracts
• 7 - Number Of Orders
• 8 - Number Of Transactions
• 9 - Value Of Positions
• 10 - Calculation Based On Existing Scenarios
• 11 - Market Value Of Securities Lending
• 13 - Transaction Quantity Of Board Lot (Transfer Warehouse)
• 14 - Market Value (Transfer Warehouse)
• 15 - Number of Ems Orders

Call GET /v1/datasets/refs/billing_fee_metric_type to retrieve the current data dictionary, and use the returned entry's key as this field's value.

The measurement threshold; required when metric_type is not "charge by number of contracts". A numeric string with at most 10 decimal places.

Rate type. Values come from the dynamic billing_package_fee_type_ref enumeration; see the options below.

Agent billing does not support monthly-tiered type 3.

Allowed values:

• 1 - Flat Rate
• 2 - Tiered Rate Per Txn
• 3 - Monthly Tiered Rate
• 4 - Float Rate
• 5 - Float Rate (Per Txn)

The calculation method, derived from fee_rate_type: floating types (2, 7) are "2", and all others are "1".

Used for fixed rates. Each item has the form { fee_rate }; the value must be non-negative and may have up to 10 decimal places.

The final rate structure submitted, generated from fixed_rates/single_rates/float_rates/month_rates according to fee_rate_type; each element contains fields such as gt/lte/fee_rate.

Currency; values come from the global_currency_filter_by_account_channel dynamic enum, such as USD/HKD/CNH.

Call GET /v1/datasets/refs/tenant_currencies_by_channel to retrieve the current data dictionary, and use the returned entry's key as this field's value.

Specifies Minimum Fee. This field is required.

A numeric string, default 999999999.

Maximum-ratio limit object { max_metric_type, max_metric_rate }, shown only under specific measurement-type / business-type combinations.

Specifies Max Metric Type.

Allowed values:

• 0 - Disabled
• 1 - Enabled

The rate value when the maximum ratio limit is enabled; multiplied by 100 for display and divided by 100 to restore it upon submission.

Billing granularity; value comes from the billing_fee_granularity dynamic enum, shown only in scenarios such as filled quantity / filled amount.

Allowed values:

• 1 - Contract
• 2 - Order
• 3 - Trade_done
• 4 - Ems_order

Call GET /v1/datasets/refs/billing_fee_granularity to retrieve the current data dictionary, and use the returned entry's key as this field's value.

The minimum ratio limit object { min_metric_type, min_metric_rate }.

Expanded from min_metric.min_metric_type.

Expanded from min_metric.min_metric_rate.

Rounding method; value comes from the billing_fee_cutoff_method dynamic enum.

Allowed values:

• 1 - Round
• 2 - Round Up
• 3 - Round Down

Call GET /v1/datasets/refs/billing_fee_cutoff_method to retrieve the current data dictionary, and use the returned entry's key as this field's value.

The number of rounding digits; the values come from the billing_cutoff_digit dynamic enum. Disabled when the rounding method is "Follow Scenario".

Allowed values: 0, 1, 2, 3

Measurement-period type. Use 4 for monthly tiers and 0 otherwise. Broker billing always uses 0.

An array of differentiated rate conditions, filtered by business type (in the agent scenario, conditions whose business type includes 11 are filtered out).

A frontend form snapshot attached upon submission for backend audit tracing; in the add scenario it is fixed as an add operation.