Export Prime Contracts to ERP as a Single Line Lump Sump
When syncing Prime Contracts to (Sage) ERP, too many constraints are placed on a user's flexibility with the SOV. Procore's default SOV options are awesome, but all the awesomeness is lost by virtue of syncing the Prime Contract; when synced, the SOVs become controlled and managed by Sage, which has a boatload of constraints.
A better option would be to allow the syncing of the lump sum contract amount only, rather than the entire SOVs. The same would apply for PCCOs. Sage needs to know the value of the contract and the value of changes. Procore should manage the details of ech.
Thanks for the feedback! Our team will review your suggestion and I will update this ticket if we proceed.
4 comments

Rob Sloyer commented
For whatever it's worth, we've disabled the Prime Contract synching on our projects because it's so broken. We went back to entering manually into Sage and having that push to Procore. "not prioritized for development" does not give me much confidence that this is even being looked at.

Ralph Crumpton commented
Highly recommend a revisit. Currently, unless you want Sage to control every single line item in a Prime Contract SOV (hint: you do NOT), Prime Contracts, and change orders thereto, cannot sync from Procore to Sage.

Kevin Hicks commented
This would be how the current Prime Contract ERP integration with Sage can be improved. Let me know if I need to post this anywhere or explain any part further.
1. At the project level add option to for Prime Contract integration:
a. What controls Contract Items / SOVs? Sage or Procore (we’d select Procore)
2. If Sage is selected, then essentially leave the current functionality the same except for how pay apps work. Need to have an option to automatically rollup PCCO changes inside of related SOV items.
3. If Procore is selected, then you follow the following steps.
a. Create contract in Sage CN and add only one contract item with the contract value.
b. If Prime contract does not yet exist in Procore, then import from Sage.
i. This would create a new prime contract in Prime contract in Procore linked to Sage.
ii. PM would create the owner SOV items and while doing this Procore will verify that the SOV items total does not exceed the value from Sage.
c. If Prime contract already exists in Procore, then user can easily link the existing Sage contract.
i. This process would verify the Procore Prime Contract does not exceed what is currently shown in Sage.
d. PM can then create Pay Apps and now regain complete control over the order, description and any other functionality they had prior to the Sage Prime Contract ERP v1 integration.
e. PM can create PCCO’s inside Procore and then have them exported to Sage. Since in this scenario Sage does not care about the Procore SOV’s the only information that will be sent to Sage CN is the revised contract amount rolled up from the PCCO and directly applied to the single contract item in Sage and any associated JC budget revisions.Validation Notes:
• In order to back check the SOV items to Sage, I’d assume that a user could not create a new pay app until the SOV items matched the Sage Contract total or revised total at that point in time.
• If user created a new pay app and was in draft state and then needed to split out items for whatever reason, then they’d just need to modify their SOV’s and either delete and recreate the draft pay app to pull in the SOV updates or have option in draft only pay app to sync the SOV’s items. 
Ralph Crumpton commented
It seems like there are two general types of ERP customers: (1) those who produce owner invoices out of Procore, and (2) those who produce Owner invoices out of Sage.
For those in the 1st category, the single line import makes more sense. When Procore gets around to integrating Prime Contract invoices from Procore to Sage, the same concept will apply: Sage only needs to know how much was invoiced and how much was retained, not the linebyline detail.