Export Prime Contracts to ERP
While we are now able to import prime contracts from Sage to Procore, we would love the ability to export prime contracts from Procore to Sage as without that capability I may be forced to take 10 steps backwards and relearn sage. Any way you could escalate this would be extremely helpful- I personally am a huge fan of the software and would love to see this company continue to move forward in launching various tools until we are 100% bought in.
Thanks for the feedback! Our team has reviewed your suggestion and we will update this ticket if we proceed.
Ralph Crumpton commented
We are on the verge of disabling the ERP integration of Prime Contracts because of the constraints placed on the Procore SOV. I intend to make a separate post requesting that details for a Prime Contract (SOVs, etc) are managed in Procore and only a single line item, or lump sum amount is sent over to Sage.
We prefer to use Procore as our all-in-one PM software, while Sage is our accounting software. All Sage needs to know in our case is the total amount of our Prime Contract or PCCO; the details should be recorded and maintained inside Procore.
Laura McLean commented
All of our financial workflows start with construction/Procore, then flow TO accounting through ERP. We want our Prime contracts to sync in the same way, rather than bringing in Primes FROM Sage.
Laura McLean commented
Export Prime Contract to Sage 300 CRE
Josh Mays commented
I would like to see the Microsoft App be supported like the Apple app. On the apple app, you can have access to all the tools, but the Microsoft app is never updated. Its basically useless.
Tiffanie Artigas commented
We really need to be able to enter the SOV from the Procore side. This is the PM's responsibility.PMs do not have access to Sage.
Joe Burgess commented
We disabled this ERP integration today. We found potential change orders (PCO) were required to be linked to the schedule of values line items after the Sage ERP integration. If these PCO's were linked to new line items on the schedule of values, the pay application automatically displayed the new line items with the potential change order in complete detail (with a $0 value), even though it wasn't even approved or rolled up into owner change orders yet. This could be edited off but our project management team felt there were too many work arounds at this time. For example, a 1 page schedule of values, might grow to 4-5 pages after including all the PCO detail. Also, when we approved a PCO and incorporated it into a prime contract change order, the pay application listed the PCO twice=once on the original line item (with a $0 value) and secondly in the PCCO (with the actual $$$ value). Please let us know when this problem is fixed.
Matt McMenamin commented
In total agreement with Lee and his comments dated 2/15/19. We are unable to take advantage of this workflow until Lee's comments noted are implemented.
Lee Marbach commented
We were excited about the potential to streamline the prime contract workflow, however with how this is currently set up our team will not be utilization it. For this feature to help with the workflow we would need a few things to work better.
1) SOV in the prime contract needs to remain editable in Procore during the life of the project to allow for the project team to do pay apps effectively.
2) Requirmeing the SOV to be entered in on the SAGE side at the beginning of the project can be problematic. We would prefer to keep this is in Procore and sync back to SAGE.
Emily Ellis commented
Agree with this one. When we went to Procore, we stopped entering Prime Contracts in Sage because of the double entry. Our Prime Contracts are only entered in Procore and totals are entered in Sage JC via Misc Worksheet entries each month. I don't necessarily need the CN module updated. I'd really like to see the JC module updated so that WIP is calculated correctly with Prime Contracts, Change Orders, and Revised Contracts.