{"id":75582,"date":"2022-06-23T09:00:19","date_gmt":"2022-06-23T08:00:19","guid":{"rendered":"https:\/\/www.bullhorn.com\/uk\/?post_type=customer_blog&p=75582"},"modified":"2022-06-22T21:54:36","modified_gmt":"2022-06-22T20:54:36","slug":"automation-in-practice-catch-billing-mistakes-before-they-happen","status":"publish","type":"customer_blog","link":"https:\/\/www.bullhorn.com\/uk\/customer-blog\/automation-in-practice-catch-billing-mistakes-before-they-happen\/","title":{"rendered":"Automation in Practice: Catch Billing Mistakes Before They Happen"},"content":{"rendered":"

Payroll or back-office problems require significant time to fix. Plus, they can provide a poor experience to your placed candidates. What if you could ensure you caught mistakes before they became a problem \u2014 better yet, with no additional time required for anyone? That\u2019s what this Automation in Practice is all about. Let\u2019s jump in.<\/span><\/p>\n

Here\u2019s the problem:<\/b><\/h3>\n

Mistakes were mostly discovered after they had become a problem and made their way to payroll. Then, the back-office team would have to urgently fix the problem. Missing or delayed paychecks would provide a poor experience for anyone affected. Then, <\/span>Bullhorn Automation<\/span><\/a> came along.<\/span><\/p>\n

Here\u2019s how the client fixed it:<\/b><\/h3>\n

The client created an automation to check all placements for anything abnormal and send a notification to the back-office team if anything came up: for example, end dates from the past, missing pay rates, missing margin or burden, margin or burden that was too low, or incorrect overtime rates. Once the notification was sent, this allowed the appropriate team to quickly rectify the issue.<\/span><\/p>\n

The result: this client had six mistakes fixed in near real-time in the first two weeks of this automation going live. These mistakes were corrected before they reached payroll processing. The client saved time by not having to deal with these problems later \u2014 after they had become problems \u2014 and provided a better experience not only for their placed candidates, but also for their internal employees.<\/span><\/p>\n

Here\u2019s how you can do this yourself:<\/b><\/h3>\n

To make this use case happen, we\u2019re going to create a placement-based automation.<\/span><\/p>\n

    \n
  1. In the top right corner of your Automations page, select <\/span>Add Automation<\/b>.<\/span><\/li>\n
  2. Select <\/span>Blank Automation<\/b>.<\/span><\/li>\n
  3. Select <\/span>Placement-based<\/b>.<\/span><\/li>\n
  4. Under <\/span>Choose the type of automation<\/b>, leave the type as <\/span>Standard<\/b>. This can be candidate or contact-based. Name your automation and hit <\/span>Save<\/b>.<\/span><\/li>\n
  5. Any of these triggers will be list criteria; that\u2019s the main mechanism operating behind this automation. We\u2019ll come back to this later.<\/span><\/li>\n
  6. What we\u2019ll do is send a notification, so select <\/span>Add New Step<\/b>, then <\/span>Send Notification<\/b>. That will send an internal email, so you can route that to whoever the notification needs to go to, whether that\u2019s a team, your back-office, payroll, etc. That notification will go out if anything matches your criteria.<\/span><\/li>\n
  7. Going back up to <\/span>Automation Enrollment<\/b>, we\u2019ll now set the list criteria. Select <\/span>Create New List<\/b>.<\/span><\/li>\n
  8. Under <\/span>Choose the type of list<\/b>, select <\/span>Always Updated<\/b>.<\/span><\/li>\n
  9. Usually, you\u2019ll want to use a placement status, so under <\/span>List Summary<\/b>, type and select <\/span>Placement Status<\/b> Is<\/b> Approved, Pending, Submitted, <\/b>or whichever naming convention you use throughout your process, just to show that you have something new that\u2019s happening. Here, we\u2019ll select <\/span>Approved<\/b>.<\/span><\/li>\n<\/ol>\n

    Now, just to walk through a few potential options, you could find placements that have end dates in the past. Under the <\/span>And<\/b> section, you would select <\/span>Placement End Date More than 0 Days Ago. <\/b>You could even add a <\/span>Placement Date Added<\/b> criteria \u2014 say, <\/span>Less Than 7 Days Ago<\/b>. This would capture placements created in the past seven days that have an end date in the past. This, obviously, is a mistake. Oftentimes, this can happen if you\u2019re copying an old job record or an old placement. If this mistake happens, the automation will then send a notification.<\/span><\/p>\n

    If you do multiple types of placements, you might want to segment by the different employment types. If so, you can add another criterion: <\/span>And Placement Employment Type Is Contract, Temporary,<\/b> or whichever placement type on which you\u2019d like to focus.<\/span><\/p>\n

    Other criteria you can focus on is pay rates or overtime rates. If either of those categories is missing, or less than they should be, you can flag that as well. You would just add another criterion: <\/span>And Placement Pay Rate Less Than <\/b>and add whichever number you deem appropriate.\u00a0<\/span><\/p>\n

    Similarly, you can find anything that\u2019s missing a burden percentage by adding the criterion <\/span>And Placement Burden % Is<\/b> or <\/span>Less Than<\/b> whichever percentage you like. If you have margin in custom fields in your placement record, you can take the same action there.\u00a0<\/span><\/p>\n

    The whole idea is to find those anomalies \u2014 those things that are incorrect \u2014 notify the appropriate people, and fix them before they become a problem in your payroll processing.<\/span><\/p>\n

    See this Automation in Practice:<\/b><\/h3>\n

    Watch the video below<\/a> to see Billy Davis put this automation into practice:<\/span><\/p>\n