A Rate is a single calculation rule that produces one line item on a statement. Example: "$0.55 per loaded mile."

A Rate Policy is a named bucket that groups one or more rates that should always fire together, with optional Rules that gate when the policy applies. Example: a policy called "California Hourly" containing a Per Hour rate and a Daily Per Diem rate, with a rule "Trip Subsidiary = California."

A Driver can have multiple policies. They are evaluated independently, and every policy whose rules match contributes line items to the statement.

Rate: dollar amount per trip. Single flat number (e.g. $150 per trip) or a tiered set of (mileage threshold, rate) pairs.

Mileage Type (only used with tiers): Loaded, Empty, or Total. Determines which mileage value picks the tier.

Tiers (optional): a set of mileage bands each mapping to a flat trip dollar amount.

Use Highest Tier checkbox: off = stepped (rare for Per Trip), on (typical) = the trip pays the flat dollar amount of the band it falls in.

Owner operator paid a flat $400 per trip regardless of miles.

Local shuttle driver paid $75 per short-haul trip, $125 if the trip crosses a mileage threshold (tiered with Use Highest Tier on).

Per Trip applies once per trip leg, not once per load. A 2-leg load generates 2 line items.

The Mileage Type only matters when tiers are configured; the field is ignored on a single flat rate.

Stepped mode (Use Highest Tier off) makes little sense for Per Trip since it would pay across bands; in practice you almost always want Use Highest Tier on.

Rate: flat dollar amount per load.

"We pay drivers a $50 loading bonus per load." Use Per Load $50 instead of trying to identify "the first stop."

OO paid a flat $500 per completed load on a dedicated lane.

If a load is split between two drivers, only the driver doing the last leg of that load gets the Per Load amount. To split it, use a percentage rate instead.

The Per Load line item appears on the leg where the load is fully delivered, not on the first pickup.

Rate: per-mile amount. Single flat number, or a tiered set of (mileage threshold, rate) pairs.

Tiers (optional): add multiple bands like "up to 100 mi: $1.50 / up to 300 mi: $1.20 / 300+ mi: $1.00". Thresholds must be unique.

Use Highest Tier checkbox: when off (default), tiers are stepped like a tax bracket; when on, the system picks the single tier matching the trip's total mileage and applies that flat rate to all loaded miles. See the Mileage tiers section for worked math.

Tenant who wants drivers to see loaded vs empty separately on every statement.

OO paid a higher rate on loaded miles ($0.85) and a lower rate on empty miles ($0.55), so the driver can see what each contributed.

Mileage progression where long hauls pay more per loaded mile (stepped tiers) or short hauls fall into a different flat rate band (Use Highest Tier on).

Loaded Miles + Empty Miles in the same policy is the standard way to split. They generate two line items per trip.

If you want a "no empty pay" structure, configure Loaded Miles only. Empty miles will not pay.

The mileage value comes from the trip's calculated miles, not a manual field. Miles are locked once the trip is on a processed statement.

Rate: per-mile amount, flat or tiered.

Tiers (optional): same shape as Loaded Miles.

Use Highest Tier checkbox: off = stepped tiers, on = flat rate for the band the trip's mileage falls in.

"We pay $0.30 for deadhead." Use Empty Miles $0.30 alongside Loaded Miles $0.55.

Compensating drivers for repositioning trips where empty miles dominate.

Different deadhead pay below vs above a mileage threshold (use tiers).

If you do not include an Empty Miles rate, the driver is not paid for empty mileage at all (unless the policy is using Total Miles).

Rate: per-mile amount, flat or tiered.

Tiers (optional): same shape as Loaded / Empty Miles.

Use Highest Tier checkbox: off = stepped tiers, on = flat rate for the matched band.

Simple per-mile contract that does not distinguish loaded from empty.

Mileage progression where the driver earns more per total mile on longer runs (stepped tiers).

Short-haul vs long-haul flat rates by mileage band (Use Highest Tier on).

The driver cannot see the loaded vs empty breakdown on a Total Miles statement. If you need that visibility, use Loaded Miles + Empty Miles instead.

Rate: per-mile deduction amount. Flat or tiered.

Mileage Type: Loaded, Empty, or Total. Determines which mileage value gets multiplied.

Tiers (optional): for graduated charge-backs (e.g. lower fee per mile on long hauls).

Use Highest Tier checkbox: off = stepped tiers, on = flat rate for the band the trip's mileage falls in.

OO equipment lease charged at $0.10/mile. Configure Per Mile Deduction $0.10, Mileage Type = Loaded.

Insurance pass-through charged at $0.05/mile across all miles (Mileage Type = Total).

Graduated lease where the per-mile charge drops on long hauls (use tiers).

Per Mile Deduction is a true negative line item, separate from accessorial-based deductions. It applies inside the rate engine, not via the statement's deduction section.

If the OO's per-mile earnings are $0.55 and you add a $0.10 Per Mile Deduction, net effect is $0.45/mile. Both line items appear on the statement (positive $0.55 and negative $0.10).

Threshold: number of stops that are NOT paid (typically 1, to exclude the pickup or delivery).

Rate: dollar amount per stop beyond the threshold.

Flat Bonus: optional flat amount added on top once the threshold is crossed.

"Pay $25 per extra stop after the first." Set Threshold = 1, Rate = $25.

"Pay $30 per stop plus a $50 multi-stop bonus when there are more than 2 stops." Set Threshold = 2, Rate = $30, Flat Bonus = $50.

The threshold is per trip leg, not per load. A two-leg load with two stops each fires Per Trip Stop separately on each leg.

If the same driver covers multiple legs of a load and you want a per-load count instead, use Per Customer Stop.

Threshold: number of customer stops not paid (e.g. 1 to exclude the first customer).

Rate: dollar amount per customer stop beyond the threshold.

Flat Bonus: optional flat amount layered on top.

"Pay $25 per extra customer stop on a multi-stop load." Threshold = 1, Rate = $25.

OOs paid for multi-drop runs where the load may span multiple legs but the customer stops are what matters.

Customer stops only. Yard moves, fuel stops, and relay stops are not counted.

If a load has two drivers, only the driver running the last leg gets the Per Customer Stop pay. To split, configure each driver's policy differently or use Per Trip Stop on each leg.

Percentage: 0 to 100.

Components: customer Line Haul + customer Fuel Surcharge. Nothing else.

NOT included: detention, lumper, layover, TONU, and every other customer accessorial.

Proration: Trip Value = (Line Haul + Fuel Surcharge) x (this trip's total miles / load's total miles). Proration uses total miles (loaded + empty), not loaded miles. A single-trip load = the full (line haul + FSC).

Override: users can manually override a trip's value on the load. If overridden, the system uses the override and stops auto-proration for that trip.

Trip value for A = ($1,800 + $200) x (600 / 1,000) = $1,200

Trip value for B = ($1,800 + $200) x (400 / 1,000) = $800

The $150 detention is excluded entirely. To pay the driver for detention, configure it through accessorial settings or add a manual line item to the statement.

Owner operator paid a single percentage that covers both line haul and fuel surcharge in one line item.

Tenants who do not want to expose two separate "% of Line Haul" and "% of FSC" lines on the driver statement.

Proration is by total miles, not loaded miles. % of Line Haul and % of Fuel Surcharge both prorate by loaded miles. Same load can therefore yield slightly different splits depending on which rate type you use, when loaded and empty miles are unevenly distributed across trips.

Tenants who want different percentages on line haul vs fuel surcharge (e.g. 75% of line haul, 100% of FSC) should use % of Line Haul + % of Fuel Surcharge as two separate rates. % of Trip Value bundles the two and applies a single percentage.

Trip value can be manually overridden on a load via Edit Trip. Once overridden, automatic proration is bypassed for that trip.

Trip Value visibility on driver statements is configurable at the driver or tenant level.

Percentage: 0 to 100.

Management or admin fee charged as a flat percentage of the customer rate per trip.

Factoring fee structured as a percentage of trip value rather than line haul alone.

Negative percentage charge-backs where the deduction should scale with both line haul and fuel surcharge together.

Mirrors % of Trip Value's quirks: prorated by total miles (loaded + empty), not loaded miles. Same as the earnings counterpart.

If you want to deduct against line haul only (not fuel surcharge), use % of Line Haul Deduction instead.

Trip Value can be manually overridden on a load; the deduction will calculate against the overridden value if one is set.

Percentage: 0 to 100.

OO paid 75% of line haul.

Team driver split: each driver gets 50% of line haul, automatic via proration.

Line haul is the customer-billed line haul number on the load, not the driver's calculated revenue.

Proration is by loaded miles. A driver who covered 60% of the loaded miles gets 60% of the line haul share.

Combine with % of Fuel Surcharge if you also want to pass through fuel.

Percentage: 0 to 100.

OO charged a 3% factoring fee on every load.

Equipment lease structured as a percentage of revenue.

Functionally similar to a Service Fee but tied specifically to line haul, not the driver's running subtotal.

Percentage: 0 to 100.

OO paid 100% of fuel surcharge as a fuel pass-through.

Company driver paid 50% of fuel surcharge as a partial pass-through.

If the customer rate confirmation has $0 fuel surcharge, this rate pays $0. It does not invent a value.

Combine with % of Line Haul for the classic OO structure.

Percentage: 0 to 100 (the % of the driver's gross to deduct).

Flat Fee: optional flat amount added on top of the percentage.

"We charge OOs 5% of their gross plus a $10 admin fee per trip." Percentage = 5, Flat Fee = $10.

Carriers that pass internal dispatch costs to OOs as a percentage of pay.

Service Fee is the only rate that is computed against output of other rates, not against load or trip fields. This is why it must run last.

If you add Service Fee twice, both fees stack and the second one is computed against the subtotal that already had the first one applied. Avoid this unless intentional.

This is NOT the same as a % of Line Haul Deduction. Service Fee uses the driver's running subtotal (which may include per-mile pay, stop pay, etc.); % of Line Haul Deduction uses the load's line haul directly.

Hourly Pay (documented above): pays per Hours Worked on each trip.

Overtime Threshold and OT Rate (documented above): extends Hourly Pay with a threshold and OT rate.

Mileage Per Diem (documented above): per-mile per diem on each trip.

Daily Pay and Daily Per Diem (below): fire per calendar day selected via Manage Calendar.

Rate: dollar amount per day.

Salary-style drivers paid a daily rate. "$200/day, 5 days/week."

OTR drivers on a "guaranteed daily pay" structure during long runs.

Days must be selected manually via Manage Calendar in Driver Settlements. There is no auto-generation.

If you forget to mark days, Daily Pay does not fire.

If you select 7 days but the driver only worked 5, you pay for 7. Pay attention to the calendar.

Rate: dollar amount per per-diem day.

OTR driver paid a $50/day per diem for every day on the road.

Layover day pay structured as per diem for tax handling.

Marking a day as per diem versus regular is done on Manage Calendar at selection time.

As with Daily Pay, the user must manually select days. Per Diem does not auto-trigger from trip events.

Base Rate: dollar amount per hour.

Local / hourly drivers who do not have a per-mile structure.

Drivers on a yard or shuttle assignment paid hourly regardless of mileage.

Hours Worked is a per-trip field on the trip itself, accessed via Open the trip > Edit Trip > Hours Worked. It accepts hours and minutes (e.g. "5 hours 25 minutes").

If Hours Worked is empty, the line item is $0. The trip will be hidden from the Open list unless Allow $0 line items on driver statements is on at the company level.

Hourly Pay does NOT integrate with HOS / ELD data. The dispatcher (or driver via the app) enters hours manually.

Base Rate: dollar amount per hour (the standard Hourly Pay rate).

Overtime Threshold: the hour count at which OT kicks in. Common values: 40 hrs/week, 8 hrs/day, 10 hrs/day, 12 hrs/day.

Overtime Rate: dollar amount per OT hour. Common configurations: 1.5 x Base Rate, 2 x Base Rate.

Threshold Basis: per-trip, per-day, or per-statement.

California hourly driver: $22/hr base, then 1.5x to $33 after 8 hrs/day, then 2x to $44 beyond 12 hrs/day.

Federal FLSA: 40 hrs/week at base, then 1.5x beyond.

Local drivers paid hourly with daily OT premiums for long shifts.

For multi-tier OT (1.5x then 2x at a second threshold), configure two separate OT rules.

Threshold Basis determines when OT triggers. Picking the wrong basis (e.g. per-statement when state law requires per-day) results in underpayment.

Hours Worked must be entered on the trip for OT to compute. See the Hourly Pay section for the Hours Worked field.

Rate: per-mile per diem amount. Flat or tiered.

Mileage Type: Loaded, Empty, or Total.

Tiers (optional): per-mileage-band per diem amounts.

Use Highest Tier checkbox: off = stepped tiers, on = flat by band.

"Pay drivers $0.12/loaded mile as a non-taxable per diem on top of their loaded-mile pay."

Tax-advantaged structures where part of the driver's pay is structured as a per-mile per diem.

Higher per diem on long hauls (tiered with Use Highest Tier on).

Mileage Per Diem reads trip mileage directly; it does NOT require Manage Calendar selections like Daily Pay and Daily Per Diem do.

Tax treatment of per diem is your accountant's call, not the system's. The system labels it as per diem and the accounting integration handles the rest.

Minimum Amount: dollar floor for the statement.

Basis: selector with two options.

Flat: "Guarantee every driver $1,200 per pay period." Minimum Pay $1,200.

Flat: New-hire training period with a guaranteed weekly minimum.

Prorated: Driver started midweek (e.g. Wednesday on a Sun-Sat pay period); a flat $1,200 guarantee would overpay for a partial week. Prorated minimum scales the floor to 5/7 of $1,200 = $857.14.

Prorated: Driver took 2 unpaid days. The minimum scales down so they are not paid the full floor for a partial week.

Prorated basis is only valid for 7-day pay periods. If the driver's pay period is biweekly, monthly, or any other length, the Basis selector is disabled with the helper text "Only choose if your pay period is every 7 days."

Minimum Pay does NOT cap pay. It only adds a shortfall line; high earners are unaffected.

If the driver has deductions that push their net below the minimum, the shortfall is added BEFORE deductions are applied, so the floor is on gross pay, not net pay.

Once a statement is processed, the shortfall amount is locked. Changing the Minimum Amount on the rate does NOT retroactively recalculate processed statements.

Flat is the default. Switch to Prorated explicitly when you want partial-week scaling.

Amount: flat dollar bonus.

"Pay drivers an extra $50 per week as a retention bonus." Statement Bonus $50.

Holiday or sign-on weekly bonus tied to a date range (combine with a rule to scope to weeks).

Statement Bonus is unconditional unless gated by a Statement Total Amount rule. If you want "bonus only when the driver clears $2,000," add a rule like Statement Total Amount >= 2000.

For one-time bonuses, use a manual New Transaction on the statement, not a recurring Statement Bonus rate.

Statement Bonus is taxable income. If you need a non-taxable per-statement payment, use Statement Per Diem instead.

Amount: flat dollar per diem.

Weekly per diem allowance paid every pay period regardless of trips run (e.g. $100/week per diem for OTR drivers).

Per diem tied to a specific pay period via a Statement Total Amount rule, e.g. only pay the per diem when the driver actually earned something on the statement (Statement Total Amount > 0).

Tax treatment is your accountant's call, not the system's. The system labels the line item as per diem and the accounting integration handles it from there.

For per-day or per-mile per diems (rather than a flat per-statement amount), use Daily Per Diem or Mileage Per Diem instead.

Statement Per Diem fires unconditionally per statement by default. Gate with a Statement Total Amount rule if you only want it to apply on statements above a threshold.

The trip is created with a driver assigned.

The driver is reassigned on the trip.

The trip's miles, stops, equipment type, or any rule input changes.

A rate policy on the driver is added, edited, or removed.

A trip is reopened from a draft or reverted from a processed statement (the rate is re-evaluated against current rules and rate config).

What it inspects: the customer on the load (the company who tendered the freight, Load.CustomerId resolved to the customer name).

Null/empty behavior: if the load has no customer (rare; most loads do), = never matches; not equals matches against every selected value.

Use case: "Pay drivers an extra $0.05 per loaded mile when running for Walmart." Customer = Walmart + a Loaded Miles rate at the bonus amount.

Common pitfalls: the rule reads the customer on the LOAD, not the customer the driver was last dispatched to. Reassigning a load to a different customer re-fires evaluation and may flip which policies match. Also: the dropdown shows the customer's current name, not the name at the time the load was created. Customer renames propagate automatically.

What it inspects: the fleet the load was assigned to (the load-level Fleet field), NOT the driver's home fleet.

Null/empty behavior: if the load has no fleet, an = rule never matches.

Use case: "Drivers running our Dedicated Northeast fleet get a different per-mile rate." Fleet = Dedicated Northeast.

Common pitfalls: confusing this with the driver's fleet. To gate on the driver's fleet instead, use the Driver Rate Plans driver segment (see below). The trip-level Fleet rule is for load-bound dispatch decisions, not driver characteristics.

What it inspects: the lane contract on the load (the Load.LaneContractId). Only relevant if your tenant uses lane contracts.

Null/empty behavior: loads with no contract never match an = rule.

Use case: "Loads on the Acme Beverage contract pay 80% of line haul to the OO; everything else pays 75%." Gate the 80% policy on Contract = Acme Beverage. The 75% policy needs to also be gated on Contract not equals Acme Beverage, otherwise it stacks on top of the 80% policy (additive).

Common pitfalls: policies stack additively, so the "everything else" companion policy needs an explicit not equals rule. Forgetting this is the #1 source of double-paying tenants who configured an exception policy and a default policy without making them mutually exclusive.

What it inspects: the value of a tenant-defined custom reference on the load. Custom references you have configured on loads (text, date, select, checkbox, multi-select) show up in the rule's dropdown.

Null/empty behavior: loads without a value set never match an = rule; they match a not equals rule.

Use case: Tenant has a "Customer Tier" custom reference on loads with values Gold / Silver / Bronze. Pay a percentage bonus on Gold tier loads.

Common pitfalls: changing the custom reference value on a load re-fires evaluation of any rules that reference it. Plan ahead if you back-fill custom references on historical loads — only open and draft payables recompute; processed statements stay locked.

What it inspects: which subsidiary tendered the trip (Trip.TenderAsSubsidiaryId). Set per trip leg, since different legs of the same load can bill under different LLCs.

Null/empty behavior: trips without a Tender As never match an = rule. Almost every active trip in production has Tender As set.

Use case: "Our California subsidiary pays $24/hr; the Texas subsidiary pays $20/hr." Two policies, each gated on Tender As.

Common pitfalls: Tender As is per trip leg, not per load. A two-leg load can tender as different subsidiaries on each leg. If your driver is paid the same regardless of who tenders, do not add this rule — it adds maintenance overhead without changing pay.

What it inspects: the equipment type configured on the trip (Reefer, Dry Van, Flatbed, Tanker, etc.), from the trip's Equipment Type field.

Null/empty behavior: trips without an equipment type fall through.

Use case: "$0.60/mile when running reefer, $0.50/mile on dry van." Two policies, each gated on Equipment Type.

Common pitfalls: the system does NOT know whether a reefer unit was actually running vs. idle. You can pay "reefer rate" for a trip where the reefer was off if the trip's equipment type is set to Reefer. If you need finer control ("reefer on vs off"), today the workaround is to change the trip's equipment type at assignment time or pay the higher rate and adjust manually.

What it inspects: the count of drivers assigned to the trip: 1 (solo) or 2 (team). Only = is supported.

Null/empty behavior: trips without an assigned driver are not evaluated for any rate at all (they have no payable yet).

Use case: "Team drivers each get $0.30/mile instead of the solo $0.55." Solo policy gated on Number of Drivers = 1; team policy gated on Number of Drivers = 2.

Common pitfalls: the team driver each gets the full rate value (it does not auto-split). If you want a true split, configure the team rate at half the solo amount.

What it inspects: the truck (Trip.TruckId) assigned to the trip.

Null/empty behavior: trips without a truck do not match. Rare in production.

Use case: a tenant who pays a different rate when a specific premium truck is used (e.g. a tanker truck with bonus pay). Truck = the specific truck IDs.

Common pitfalls: truck-level rules are brittle. Adding a new premium truck means updating every policy that references the truck list. Most tenants are better off using Equipment Type or a Driver Rate Plan segment based on Fleet or Truck Type instead.

What it inspects: properties on the driver record. The three checkable values are:

Null/empty behavior: unset boolean defaults to false. An = rule selecting "Is Owner Operator = true" never matches company drivers (who have IsOwnerOperator = false or unset).

Use case 1: "Owner operators get % of line haul; company drivers get per mile." OO policy gated on Driver Attributes = Is Owner Operator.

Use case 2: "If the OO is using their own trailer, they get an extra 5% of line haul." Stack a second OO policy with Driver Attributes = OO Using Own Trailer on top of the base OO policy. Both policies will fire and contribute additive line items.

Common pitfalls: Driver Attributes is the only driver-side rule on policies (vs all the others which look at the trip/load). For more driver-side filtering options (Fleet, Subsidiary, Tenure, Type, custom references), use Driver Rate Plans with a Driver Segment (see the Driver Rate Plans section below).

What it inspects: the value of a tenant-defined custom reference on the trip. Whatever custom references you have set up on trips (text, date, select, checkbox, multi-select) show up in the rule's dropdown.

Null/empty behavior: trips that do not have the custom reference set never match an = rule against a specific value; they match a not equals rule (the value isn't in the selected set).

Use case: Tenant uses a "Service Level" custom reference on trips with values like Premium / Standard / Economy. Pay drivers a bonus rate when Service Level = Premium.

Common pitfalls: the rule reads the trip's current value of the custom reference. Editing the value after the trip has delivered triggers re-evaluation (open and draft items recompute; processed statements are locked).

Note: trip custom references are distinct from driver custom references (which power Driver Rate Plan segments). Both can be defined per tenant; they apply to different entities.

What it inspects: at least one stop on the trip has a state matching one of the selected states. "Any stop" includes pickup, delivery, intermediate, fuel, and yard stops.

Null/empty behavior: trips with no stops match no = rule and match every not equals rule.

Use case: "Pay $50 extra anytime the trip touches NY or NJ." Per Trip $50 rate gated on Stop State = NY, NJ.

Common pitfalls: the rule fires if ANY stop is in the state, not just customer stops. A fuel stop in NY would also trigger it. Use First Customer Stop State or Last Customer Stop State if you want to scope to origin/destination only.

What it inspects: at least one stop on the trip has a zip code matching one of the selected zips. Same scope as Stop State (all stop types).

Null/empty behavior: stops without zips do not match. Some EDI-tendered loads may have zip-less stops.

Use case: "Pay $100 extra for stops in NYC five-boroughs zip codes" with a zip list.

Common pitfalls: zips are matched exactly. "10001" and "10001-0001" are different strings; if your zips include +4 extensions you need to enumerate or use a different mechanism.

What it inspects: the value of a tenant-defined custom reference on any stop of the trip. Like the standard Stop State / Stop Zip rules, the match fires if ANY stop on the trip has a matching value.

Null/empty behavior: stops without the custom reference set are skipped during evaluation. Trips with no matching stop do not satisfy an = rule.

Use case: Tenant tags stops with a "Stop Type" custom reference (Drop Trailer / Live Unload / Hook & Drop). Pay an extra per-stop bonus when at least one stop is Live Unload.

Common pitfalls: Stop Custom Reference behaves like Stop State — it scans every stop on the trip, including yard moves and fuel stops, not just customer stops. If you only care about customer stops, today there is no first/last-customer-stop variant of this rule. Set the custom reference on the right stop types at dispatch time.

What they inspect: the very first customer stop on the load (origin pickup). Customer stops are stops typed as a customer pickup/delivery, not yard moves or fuel stops.

Scope: load-level, not trip-level. On a multi-trip load, the same first-stop value applies to every trip.

Null/empty behavior: loads with no customer stops do not match.

Use case: "Loads originating in California get a different rate" to cover higher idle / fuel cost. First Customer Stop State = CA.

Common pitfalls: if a load is restructured (stops reordered, a new first customer stop added), the rule re-evaluates. Avoid baking last-mile detail into rules that may change post-dispatch.

What they inspect: the very last customer stop on the load (final delivery).

Scope: load-level. Same value across all trips of the load.

Null/empty behavior: loads with no customer stops do not match.

Use case: "Loads delivering into the Northeast get a $200 layover bonus." Last Customer Stop State = NY, NJ, PA, CT, MA, RI.

Common pitfalls: confusing this with Stop State (any stop). Stop State fires on intermediate stops too; First/Last Customer is locked to origin and destination of the whole load.

What it inspects: the running statement subtotal in dollars, after Trip and Time-based pay rates have computed but before this Statement-category rate fires. This is the only rule whose input is derived from other rate output, not from the trip/load.

Operators: all six (=, not equals, >, >=, <, <=). The only rule that supports the full numeric comparison set.

Null/empty behavior: an empty statement has a subtotal of 0; rules like < 1000 will match.

Use case 1: "Give a $200 weekly bonus if the driver clears $2,000 in a week." Statement-category policy with Statement Total Amount >= 2000 and a Bonus rate of $200.

Use case 2: Conditional minimum pay: "Pay a flat $50 supplement only if the statement is under $800." Statement Total Amount < 800 with a $50 Bonus. Note: the Minimum Pay rate type is usually a cleaner choice for floor logic.

Common pitfalls:

Profile policies: rate policies set directly on a single driver profile. Best for one-off customizations.

Rate plans: workspace-level templates that apply to many drivers via a driver segment. Best for shared pay structures (e.g. "all owner operators in the Northeast," "all company drivers past 90 days of tenure").

Plan A (matched by Type = Owner Operator): % of Line Haul 75%.

Plan B (matched by Fleet = Northeast): Per Trip Stop $25.

Plan C (matched by Tenure (days) >= 365): Bonus $50 per statement.

Editing a plan does not change historical payouts.

A driver gaining a plan via segment match does not generate back pay for prior trips.

A driver losing a plan (e.g. via fleet change) does not claw back already-processed pay.

The plan name and brief description.

The reason it applies (which segment rule matched).

A deep link to the plan settings page (permission-gated).

Partner Admin, Admin, Biller: can view, create, edit, archive plans, and edit a driver's assigned plan settings.

All other roles: read-only or hidden, depending on the View Driver Rate / Edit Driver Rate permissions.