<?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/724446370a48409db9d8360a482a5a64&quot; frameborder=&quot;0&quot; width=&quot;1920&quot; height=&quot;1440&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>1440</height><width>1920</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>1440</thumbnail_height><thumbnail_width>1920</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/724446370a48409db9d8360a482a5a64-321fe7039aef51d6.gif</thumbnail_url><duration>363.212</duration><title>Syncing Change Orders from Procore to Sage 100C</title><description>In this video, I walk you through how Agave syncs change orders from Procore into Sage 100 Contractor, starting with a change event that generates both prime and sub changes. I highlight the differences in how Procore and Sage handle budget increases, where Procore increases the budget with the prime change, allowing the sub-change to consume that budget. After syncing the change orders, I demonstrate how the details appear in Sage, including the approved profit and the increased budget amounts. I also show how to create a commitment change from the same event, which further impacts our budget view in Procore. Please ensure you follow the steps outlined to keep our systems aligned.</description></oembed>