Enrollment Dashboard
Enrollment Tabs
Code Additions - SUTA Registration Tab
20 min
not live π summary the code additions tab in the enrollment dashboard centralizes all cornerstone client cases where a suta state registration is required as part of an approved code addition form clients appear here when the required suta registration is not yet saved in januscrm the workflow guides users through sending the form, receiving documentation, reviewing it, and processing the applicable suta registration fee currently this feature is setup only for cornerstone clients π§ feature details when a client appears in code additions a client will populate this tab when a code addition form has been approved in underwriting for a suta required state, and the client does not have suta registration saved in their profile these entries remain until fully processed π tab columns & data displayed business name state status to complete by (carrier or client) fee amount (default $300) document (uploaded or pending) created at actions (view lead) π suta registration modal opening a record launches the suta registration modal users can designate who will complete the registration and upload or request required documents if the client already has a suta number, they must upload their suta registration confirmation form portal credentials (accounting will clarify exact upload expectations ) if not registered, the user sends the suta registration form to the client π² fee handling default fee $300 (editable pre charge) fee cannot be charged until form is completed signed documentation reviewed send form changes to charge suta registration fee once ready process as offline payment is available for externally handled payments a duplicate charge warning will appear if the client/state has already been billed π¨ client view of the registration form page 1 business info + addresses page 2 contact info + up to 3 owners page 3 payment details page 4 review & signature π status changes after submission after the client signs status updates to pending review charging becomes available βmark as reviewedβ completes the workflow documents save to the client profile cornerstone receives a copy the item disappears from the code additions tab what if the client already has a suta registration? the to complete by field defaults to carrier , but users can switch this to client when the client has already completed their own suta registration once set to client , the upload section becomes available so users can attach the documents provided by the client π€ document uploads users may upload the clientβs suta registration form proof of active suta registration any additional required supporting documents all uploaded files are saved to the clientβs document center , and the request will close once the documents are reviewed and marked as completed π recalculate suta registration (sales tab action) a new action buttonβ recalculate suta registration βhas been added to the sales tab under the actions menu of the active quote when selected, this option refreshes the clientβs profile and re evaluates their state against the list of suta client states if the clientβs state qualifies, the system will automatically generate the required suta registration task and place it in the code additions tab on the enrollment dashboard for processing if the registration or required documents have already been completed and uploaded for that client and state in janus, the system will not create a new request β when to use this button this action is intended only for existing or older clients who were not processed using the new enrollment workflow situations where suta validation was not triggered during the original onboarding or enrollment process using this button ensures that any missing suta registration requirements are correctly added to the workflow so they can be completed using the standard process π star requirement during enrollment (cornerstone only) additional workflow path this suta workflow can also occur during the enrollment process for cornerstone clients who qualify as suta client state when a qualifying client reaches enrollment, a new requirement called star appears selecting the star requirement opens the same suta registration modal used in the code additions tab users can upload registration documents or send the suta registration form directly to the client charging can also be completed from within the star requirement once finished, the requirement tile will turn green , indicating completion this provides an alternate, earlier workflow to complete suta registration before the client reaches the code additions tab β
suta client states the following states require client handled suta registration ak β alaska ar β arkansas co β colorado hi β hawaii id β idaho ky β kentucky ma β massachusetts mo β missouri ms β mississippi nd β north dakota ne β nebraska nh β new hampshire nv β nevada oh β ohio pa β pennsylvania ri β rhode island sc β south carolina sd β south dakota tn β tennessee vt β vermont π§ email notification preview after the suta registration request is completed and marked as reviewed, an automated email notification is sent to evan eisenmann\@cornerstonepeo com madison groeller\@cornerstonepeo com the enrollments department is copied on every notification to ensure full visibility across the team π alternative suta collection process for all carriers summary a new standardized workflow has been introduced to collect suta registration details from clients when the standard automated method is not available or applicable across carriers details a new front end template, βsuta registration collectionβ , has been added for manual suta information requests this template includes a pdf form designed for clients to complete and return with their star number and required suta registration details the form can be sent and received via email without system restrictions workflow requirements use the suta registration collection template when a carrier requires suta data but the automated integration cannot be used upon receiving the completed pdf from the client update the suta registration requirement field on the enrollment dashboard upload the completed document to the docs section of the lead card (for non cornerstone clients) notes & considerations ensure the pdf is fully completed before updating enrollment fields confirm the star number format is valid before marking the requirement as complete this process applies to all carriers requiring suta details next steps this concludes the enrollment section to learn about payroll processing https //kb getjanus io/payroll dashboard overview begin payroll processing https //kb getjanus io/data dashboard overview process customer requests https //kb getjanus io/leads tab overview manage customer information π quick reference need help with terminology? check our https //kb getjanus io/januscrm glossary and acronym index for definitions of all terms used in this documentation
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.