Frequently Asked Questions

One inBuild customer had two full-time employees dedicated to managing invoicing before implementing the platform. With inBuild, those employees now spend only about 20% of their time on invoicing, freeing the majority of their time for other work.

inBuild adds a centralized workflow layer for invoice intake, AI-assisted data extraction and coding, document review, approvals, duplicate detection, mappings, collaboration, and synchronization. Rather than replacing Procore or QuickBooks, it helps connect the work that happens between receiving an invoice and having the final transaction recorded correctly in those systems.

Yes. inBuild supports multiple QuickBooks Online integrations and allows projects to be mapped to the appropriate accounting connection. This is useful for construction companies operating across multiple legal entities or accounting files.

Yes. inBuild is designed to act as a workflow and synchronization layer between Procore and supported accounting systems such as QuickBooks Online and QuickBooks Desktop. It maintains mappings between projects, vendors, accounts, items, cost codes, tax codes, and other relevant records.

Yes. inBuild supports configurable approval rules with ordered tiers, named reviewers, Procore project-role reviewers, and conditional routing. This allows different invoices to follow different approval paths based on the company's configured rules.

Yes. inBuild supports workflows for direct costs and accounting-only bills in addition to subcontractor or commitment-based invoices. The appropriate processing path depends on how the company has configured its Procore and accounting workflows.

Yes. inBuild supports configurable commitment change-order workflows. Users can upload or create a change-order document, associate it with the appropriate commitment, review the line items, and submit it through the configured workflow.

Yes. When commitment processing is enabled, users can upload or create commitment documents, review the extracted schedule of values, select the appropriate project and vendor, and submit the resulting commitment through the configured Procore workflow.

Yes. inBuild is designed for construction companies with project-based accounting and invoice workflows, including general contractors, specialty contractors, and owner-developers. The best fit is typically an organization processing a meaningful volume of invoices across projects, commitments, cost codes, and approval workflows.

Yes. inBuild can use AI-assisted recommendations to help map invoice information to vendors, projects, accounts, items, commitments, WBS values, and cost codes. Users can review and correct those recommendations before the invoice is approved or synchronized.

One inBuild customer previously had two employees spending 100% of their time managing invoicing. After implementing inBuild, those same employees spend only about 20% of their time on invoicing. Results vary by company and workflow, but inBuild is designed to dramatically reduce the manual work involved in invoice entry, coding, review, approvals, and synchronization.

Yes. Integrations with Acumatica and CMiC are underway as part of inBuild's accounting-platform expansion. Prospective customers should speak with the inBuild team about timing, supported document flows, and participation in design-partner or early-access programs.

Sage integration work is underway. Today, customers should confirm the supported Sage product, workflow scope, and availability with the inBuild team before planning an implementation, because roadmap functionality should not be treated as generally available until released.

Yes. A company can enable and govern invoice, commitment, change-order, Procore approval, and accounting-only approval workflows independently. This lets teams route each document according to its destination and business process instead of forcing every financial document through one universal path.

An administrator can build an ordered accounting approval chain with one or more tiers. Each tier can require any selected reviewer or all selected reviewers, and later tiers begin after the preceding requirement is satisfied. The configured accounting workflow applies to eligible standalone QuickBooks bills.

Yes. Procore invoice approvals and accounting-document approvals are configured separately. This allows a company to preserve its project-side approval process for Procore invoices while applying a different approval chain to bills that go straight to QuickBooks Online or QuickBooks Desktop.

Yes. inBuild can require approval before standalone QuickBooks Online or QuickBooks Desktop bills are submitted. Accounting approval tiers are evaluated inside inBuild, giving teams a controlled review step even when the document is intended to go directly to the accounting system rather than through Procore.

Invoice creation and editing follow the user's invoicing role. Commitment and commitment change-order creation follow the user's commitments role. Admins and managers can edit within an allowed domain, viewers receive read-only access, and a role of none hides that domain. Company-wide administrators retain full access.

Yes. inBuild separates the invoicing and commitments permission domains. A company administrator can give a user admin, manager, viewer, or no access independently for each domain, allowing someone to process invoices without creating commitments—or manage commitments without receiving invoice-editing access.

Yes. Commitment change-order creation is available as a separately configurable workflow. Authorized users can create or upload a change-order document, associate it with its parent commitment, review line items, and submit it when change-order processing is enabled.

Yes. When commitment processing is enabled, authorized users can upload or manually create commitment documents, review the extracted schedule of values, select the project and vendor, and submit the resulting commitment through the configured Procore workflow.

inBuild uses company-scoped memberships, roles, and permissions. Administrative controls govern integrations, company settings, approval rules, mappings, and member management. Procore sign-in and company activation can also require that a user be marked as an employee in the Procore company directory.

Yes. The web application includes responsive mobile layouts for inbox navigation, invoice review, line-item editing, filters, and account navigation. The codebase also includes native-app bridge and push-notification support for configured mobile deployments.

Yes. inBuild supports accounts payable CSV exports, project-level CSV exports, and bulk stamped-PDF export workflows. Export availability depends on the user's permissions and enabled company features.

inBuild includes accounts payable reporting, payables-by-project reporting, processing analytics, and operational monitoring views. Users can filter invoice and project data and inspect processing, assignment, approval, and synchronization status.

inBuild checks QuickBooks closing dates and can validate accounting dates before synchronization. Users can select an appropriate accounting date where permitted, helping prevent bills from being posted unintentionally into a closed accounting period.

inBuild includes retainage calculations and mismatch checks for supported subcontractor and payment-application workflows. It also supports configurable tax handling, including QuickBooks tax-code mappings and Canadian tax workflows. Setup varies by accounting integration and company configuration.

Yes. The application supports multiple QuickBooks Online integrations and provides project-to-integration mapping so a company can direct projects to the appropriate QuickBooks connection.

inBuild maintains mappings between Procore and QuickBooks entities, including vendors, projects or customers, accounts, items, WBS or cost-code values, and tax codes. AI-assisted recommendations and mapping-management screens help users establish, review, and publish those relationships.

inBuild can create and update supported bills, bill line items, vendors, project or customer references, accounts, products or services, classes, tax codes, payment information, and related mappings. The exact payload depends on whether the company uses QuickBooks Online or QuickBooks Desktop and how its workflow is configured.

The implemented accounting integrations include QuickBooks Online and QuickBooks Desktop. QuickBooks Desktop connectivity is provided through Conductor. Integration availability and supported workflows depend on the company's configuration and subscription.

Yes. inBuild includes configurable workflows that can synchronize eligible Procore payment applications to QuickBooks as invoices. The workflow supports mappings, retainage items, consolidated or detailed line items, and Canadian tax-code scenarios when configured.

Yes, when the relevant features are enabled. inBuild includes workflows for tracking Procore invoice payments, reconciling QuickBooks bill payments, and creating payment records in Procore from supported QuickBooks activity.

Yes. inBuild includes configurable commitment processing and commitment change-order workflows. It can use Procore commitment schedules of values, cost codes, quantities, units, and change-order information while preserving safeguards around invoice-entered amounts and synchronization state.

inBuild supports construction invoice workflows involving subcontractor invoices or requisitions and direct costs. Depending on company configuration, invoice data can be mirrored from Procore, synchronized back to Procore, or used to create commitments and related invoice records.

inBuild connects to Procore through OAuth and company-scoped APIs. It can cache and use Procore projects, vendors, commitments, budget structures, WBS codes, billing periods, direct costs, requisitions, payment applications, and related data to support invoice processing and synchronization.

Yes. inBuild supports in-app notifications, reviewer invitations, review reminders, pending-review emails, and assignment email digests. Notification behavior and delivery timing can depend on company and user settings.

Yes. Users can assign financial documents, add notes, mention company users, and view approval activity. These collaboration features keep invoice-specific context attached to the document instead of spread across separate email threads.

inBuild supports configurable dispute-return behavior. A company can determine how a disputed review returns through the approval chain, and the application records review history so teams can understand the document's current state and prior actions.

Yes. Approval rules can evaluate configured conditions and route documents through ordered review tiers. The system tracks reviewer states such as pending, approved, and disputed and maintains approval activity for each financial document.

Yes. inBuild supports configurable approval rules for Procore invoice workflows and accounting bill workflows. Approval chains can contain tiers, named reviewers, and Procore project-role reviewers, with company settings controlling how approvals and disputes progress.

Yes. The platform includes duplicate-detection and duplicate-marking workflows for financial documents, including Procore-originated requisitions and direct costs. Duplicate handling is designed to surface potential conflicts for review rather than silently creating repeated accounting entries.

Yes. inBuild provides editable invoice details and line-item grids so authorized users can review, correct, assign, map, and validate information before approval or sync. AI output is treated as workflow assistance rather than an irreversible final entry.

inBuild can analyze invoice documents and populate header and line-item information used in construction AP workflows, including vendor, project, invoice number, dates, amounts, commitments, cost codes, quantities, units of measure, retainage, and accounting mappings. Exact fields depend on the document and configured workflow.

Yes. inBuild includes a multi-file upload workflow with bounded-concurrency processing and document previews. Teams can upload batches while selecting the appropriate document workflow, subject to the features enabled for their company.

Invoices can enter inBuild through connected Microsoft Outlook mailboxes, direct file upload, multi-file upload, or manual document creation. The application also supports creating financial documents from email attachments and, in supported workflows, email-body content.

inBuild uses AI-assisted document analysis to classify financial documents, extract invoice information, hydrate line items, and recommend mappings such as vendors, projects, accounts, items, and cost codes. Users can review and correct results before downstream synchronization.

No. inBuild works alongside Procore and accounting systems such as QuickBooks Online and QuickBooks Desktop. It provides the invoice intake, review, approval, mapping, and synchronization layer between those systems rather than replacing the project-management or general-ledger system.

inBuild reduces manual invoice entry, fragmented email approvals, duplicate processing, coding inconsistencies, and reconciliation work between construction and accounting systems. It gives teams a central inbox for reviewing documents and tracking their processing, approval, and sync status.

inBuild is designed for construction companies and their accounting, project management, and operations teams. It is especially relevant to organizations that manage project-based invoices, commitments, subcontractor billing, direct costs, approval chains, retainage, and accounting-system synchronization.

inBuild is a construction accounts payable platform that helps teams capture, code, review, approve, and sync invoices. It connects invoice workflows with systems such as Procore, QuickBooks Online, QuickBooks Desktop, and Microsoft Outlook so finance and project teams can work from a shared process.