Payroll Dashboard
Service Tier & Processing Program Logic
11 min
π§© overview januscrm uses service tiers to define automation level, communication rules, and available payroll features for each client each tier maps directly to a processing program , determining how the clientβs payrolls are handled after binding service tiers are established during the pre bind payroll settings step and remain central to all system logic once the client is live βοΈ configuring the service tier pre bind setup the service tier is selected by the broker inside pre bind β payroll settings all new leads default to the express service tier the tier can only be changed prior to binding within this section the selection determines which processing program activates at bind, and which services & features become available post bind behavior once a client is bound ( gets createdd on binding status ), januscrm automatically creates a payroll customer record on the payroll tab of the lead card after this point, the service tier cannot be edited directly any change to the tier must occur through an update to the clientβs processing program on the payroll customer example moving a client from advisor express (express tier) to whiteglove program automatically changes the associated service tier π§± services & features availability the services & features section of the pre bind payroll settings dynamically limits what can be enabled based on the selected tier feature express tier whiteglove tier enterprise tier safety program β
available β
available β
available deductions / garnishments β
available β
available β
available health insurance π« requires whiteglove or enterprise β
available β
available life insurance π« requires whiteglove or enterprise β
available β
available 401(k) π« requires whiteglove or enterprise β
available β
available certified payroll π« requires whiteglove or enterprise β
available β
available time & attendance π« requires whiteglove or enterprise β
available β
available pto tracking π« requires whiteglove or enterprise β
available β
available note express clients may only toggle safety program and deductions / garnishments all other options display a locked message βrequires whiteglove or enterprise tier β π·οΈ service tiers and processing programs service tier processing program(s) automation level ownership express yeo express / advisor express π full automation system / payroll advisor whiteglove whiteglove βοΈ partial automation payroll advisor enterprise enterprise π§ controlled manual payroll advisor π automation logic by tier express tier all system notifications and automated updates enabled decline, cancellation, inactivity, reporting, and risk triggers includes automatic pending cancellation, program minimum, credit hold, and bounced logic designed for fully automated client handling whiteglove tier sends reporting reminders, decline emails, payroll finalization skips late reporting and inactivity workflows allows manual status changes by advisor delays credit hold / bounce processing by 7 business days sends pending approval emails (optional per client) enterprise tier suppresses all notifications except credit card decline emails disables automatic status changes, inactivity, and late reporting all actions performed manually by management or billing teams π§ ownership & permissions role authorized actions notes payroll advisors β’ move between standard β escalations β’ trigger manual whiteglove status changes cannot place clients in credit hold or collections billing team β’ manage credit hold / collections β’ resolve declined or bounced payments can restore clients to active programs after resolution management / admin β’ override tier restrictions β’ approve reinstatements β’ control enterprise workflows full system access across all tiers π§ system behavior matrix scenario express whiteglove enterprise 3rd payment decline auto pending cancellation + email manual review before pending cancellation decline email only late reporting auto reminder + program minumum flag reminder only none bounced payment auto escalation β escalations program delay 7 business days β manual escalation manual review credit hold auto hold + notification manual hold after 7 days manual hold by billing/management π§© additional notes once a client is bound , service tier changes occur only through processing program updates on the payroll customer feature availability and automation settings remain locked to the selected tier until the program is updated system dashboards and filters automatically reflect tier based automation visibility to prevent false workflow triggers
π€
Have a question?
Our knowledgeable support team and an awesome community will get you an answer in a flash.
To ask a question or participate in discussions, you'll need to authenticate first.