procore erp integrations

Re-Imagining the Accounting Experience

Creating a vision for Procore's ERP Integrations tool: a scalable information architecture, clearer error handling, and a faster review workflow for accountants.

Re-Imagining the Accounting Experience

the problem

An outdated ERP Integrations tool

The ERP Integrations tool hadn't been updated in years. The frontend code and user experience didn't match Procore's design system, and the backend architecture was outdated.

At the time, the tool had over 15 ERP integrations, 10 integration endpoints, and more in the pipeline. This complexity made it challenging and time-consuming for customers to use.

Old ERP Integrations tool screens
A sampling of old ERP Integrations tool screens

background

Enhancing ERP and Procore integration

While construction project managers prefer Procore, accountants use their ERP (Enterprise Resource Planning) software for project finances. Information must be shared seamlessly between Procore and ERP systems to ensure accurate financial reporting.

Procore's ERP Integrations tool allows financial data to be imported and exported between Procore and the customer's ERP software.

Current state of the integration workflow

my role

Lead designer

Vision

Create a vision for the ERP Integrations tool's future.

Collaboration

Collaborate with product and engineering teams to work towards that vision.

Design brief

discovery

Identifying opportunities for improvement

I began by researching our product internally to understand it quickly and identify key opportunities. I consulted colleagues from integration, support, and sales teams and combined this information with customer feedback and analytics.

Scale & efficiency

The manual process was dependent on multiple roles and time-consuming.

Communication

Accountants were not promptly notified of items needing review and struggled to locate them in the tool.

Pain point one
Pain point two

initial designs

Streamlining the user experience

The current UI had a tab for each item type, which was not scalable. My first design change was organizing the top-level navigation by item status (Ready to Export and Ready to Import). This allowed users to see all item types in one list and review items more quickly.

Initial design updates
Initial design updates

validation

Gathering feedback on new designs

I validated the new direction with customers and internal SMEs, gathering feedback to ensure the designs met their needs.

Need more information

Customers requested additional data points, including the Item ID.

Mixed response to new IA

The change from tabs for item type to tabs for item status received mixed reviews. Customers found it hard to differentiate item types in one list.

iterations

Refining the user interface

Sometimes, the slightest change makes the most significant difference. I added color-coded tags to differentiate item types, improving customer response from skeptical to enthusiastic.

I created a new pattern for bulk reviewing items, an improved framework for error handling, and simplified settings content. I collaborated with the systems team to design, validate, and contribute new components to our design system.

Tag component spec
Bulk review and error handling designs
Design iteration 1
Design iteration 2
Design iteration 3
Design iteration 4
Design iteration 5
Design iteration 6

usability testing

Ensuring practicality and effectiveness

The final test involved usability testing with customers. Participants completed each task and provided positive feedback.

Task completion

All participants successfully completed tasks.

Information architecture

Thanks to the tags and improved filter experience, participants appreciated having everything on one page.

Import success screen

team onsite

Collaborating for successful implementation

With validated designs and positive feedback, we needed cross-division stakeholder approval. We organized a team onsite in our Portland office involving product management, customer support, implementation, and custom solutions teams. I led sessions to review designs, discuss roadmaps, and share customer feedback.

The team onsite in Portland
Team photo

outcomes

Positive customer and stakeholder feedback

This is exactly what I was going to ask for! If this screen were up I'd be able to take a glance and see what I need to do.

Customer feedback

Following design validation and positive customer feedback, the project received approval to move into the implementation phase. I worked with product and engineering leadership on sequencing and creating a roadmap draft before transitioning the project to the implementation team.

The re-imagined Procore ERP Integrations tool enhances the user experience for construction project managers and accountants. We created a more efficient, scalable, and user-friendly tool by addressing critical pain points and involving customers in the design process.

Final ERP integrations designs

because you can't afford mediocrity

Today's market demands that you ship amazing, world-changing products faster, with fewer people, and smaller budgets.

Outshine your competition

Ship higher quality products

Increase team productivity

Transform ideas
into impact