![]() For each Procore company account, the integration is designed to support one (1) QuickBooks® file per connector. Your company will have one (1) cost code list for use with all QuickBooks®-integrated projects.Ī separate QuickBooks® company file for each project is NOT supported. Project-specific cost codes are NOT supported with the Procore + QuickBooks® integration. Procore cost codes can only be synced with QuickBooks® items designated with the type 'Service.' Sub jobs are disabled in Procore for QuickBooks®-integrated projects. The sub job feature is NOT supported with the Procore + QuickBooks® integration. For more details, see QuickBooks® and Cost Types. Because QuickBooks® does NOT have an equivalent cost type concept, all QuickBooks®-integrated projects use a single cost type of Other. They are used as a classification to identify job costs and can later be used to generate reports. For example, L=Labor, M=Materials, S=Subcontract, and so on. In Procore, a cost type (a.k.a., category) is a set of uniquely identified costs represented by an abbreviation and label. The QuickBooks® integration does NOT support the following items:.Data from these Procore tools and items do NOT sync with QuickBooks®: Toggle to any version of QuickBooks to be able to see what their clients see (Accountant, Pro, or Premier any of the industry editions: Contractor, Wholesale.Any historical projects created before your company's ERP implementation cannot sync data. The QuickBooks® integration can only sync data on new jobs/projects. Designed for use only on new construction jobs/projects:.If you have questions, please send an email to your Procore point of contact. Keep in mind that your company may have different requirements and processes, so there may be unique limitations in your environment not listed here. Before your company starts using the QuickBooks® integration with Procore, first review the Integration Map above to learn about the available features. It is also important to be aware of the limitations listed below.
0 Comments
Leave a Reply. |