<?xml version="1.0" encoding="UTF-8"?><oembed><type>video</type><version>1.0</version><html>&lt;iframe src=&quot;https://www.loom.com/embed/5f0b74207c8b4410afaf43bc658df9e8&quot; frameborder=&quot;0&quot; width=&quot;1972&quot; height=&quot;1479&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>1479</height><width>1972</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>1479</thumbnail_height><thumbnail_width>1972</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/5f0b74207c8b4410afaf43bc658df9e8-2400ac35d1385ee3.gif</thumbnail_url><duration>68.409</duration><title>Addressing Billing Code Issues in SalesBuilder and Autotask</title><description>In this video, I’m addressing an issue with the billing code field in SalesBuilder, which is required but not in Autotask. This discrepancy is causing problems for a company that doesn&apos;t use the billing code, forcing them to constantly switch to Autotask and disrupting their workflow. I wanted to highlight this to ensure we understand the impact on their internal processes. Please take a look and consider how we can address this issue moving forward.</description></oembed>