{"article":{"id":63519611535897,"url":"https://roubler.zendesk.com/api/v2/help_center/en-us/articles/63519611535897.json","html_url":"https://support.roubler.com/hc/en-us/articles/63519611535897-Release-Notes-23-October-2026-Roubler-v26-4-1","author_id":5308062942361,"comments_disabled":true,"draft":false,"promoted":false,"position":0,"vote_sum":0,"vote_count":0,"upvote_count":0,"downvote_count":0,"section_id":360004158073,"created_at":"2026-10-22T21:56:20Z","updated_at":"2026-10-23T03:21:42Z","name":"Release Notes: 23 October 2026 | Roubler v26.4.1","title":"Release Notes: 23 October 2026 | Roubler v26.4.1","source_locale":"en-us","locale":"en-us","outdated":false,"outdated_locales":[],"edited_at":"2026-10-23T03:21:42Z","user_segment_id":null,"permission_group_id":1035394,"content_tag_ids":[],"label_names":[],"body":"<p>Roubler 2026.4.1 improves how Employment Hero Payroll sync errors are shown in Roubler, and resolves an issue with onboarding flows.</p><h3 id=\"h_01M5JSQY6AK29G004MCY8F8ND8\">Clearer Employment Hero Payroll (KeyPay) sync errors</h3><p>When an employee fails to sync to Employment Hero Payroll (KeyPay) via employee update or bulk sync, the <strong>Sync Issue</strong> on the employee profile and sync report now shows the specific validation error from Employment Hero (for example, that an external ID is already in use) instead of only “Bad Request”.</p><div data-testid=\"renderer-heading-wrapper\" data-level=\"3\"><h3 id=\"RB-13048-—-Complete-Onboarding-After-Final-Declaration-Is-Signed\" tabindex=\"-1\" data-local-id=\"0d6bfbc4a9f2\" data-renderer-start-pos=\"309\">Complete onboarding after the final declaration is signed</h3></div><p><span role=\"presentation\"></span></p><p data-renderer-start-pos=\"375\" data-local-id=\"0a407c2a9035\">When the final declaration has already been signed, but the initial <strong>Sign &amp; Complete</strong> activation did not succeed, employees can still finish onboarding by using a <strong>Complete </strong>button on the <strong>Final Declaration</strong> step.</p>","user_segment_ids":[]}}