# Path

![QuickBooks logo](https://cdn.brandfetch.io/quickbooks.intuit.com/icon?fallback=transparent)

Payments & Finance

# Build more with QuickBooks.

Cloud accounting software for small businesses. Shape those capabilities into a system that fits your team.

[See what you can build](https://path.dev/guides/integrations/quickbooks#build-ideas)[Get a starter prompt](https://path.dev/guides/integrations/quickbooks#starter-prompt)

Build concepts, not preinstalled apps. Provider plans, permissions, and API availability apply.

The possibilities

## What could you build?

01

### Invoice follow-up workspace

Bring authorized invoice status next to customer context and an owned follow-up queue.

02

### Project financial view

Connect approved accounting records to internal project tracking.

## Start with the invoice follow-up workspace.

Keep the first version small enough to test with the people who will use it.

1.  01
    
    QuickBooks
2.  02
    
    Invoice follow-up workspace
3.  03
    
    Reviewed next action

1.  01
    
    ### Choose the first job
    
    Use the first idea as your brief: Bring authorized invoice status next to customer context and an owned follow-up queue. Name the person responsible and the information they need to act.
    
2.  02
    
    ### Confirm access before connecting
    
    Map customers and document IDs carefully. Review accounting changes with the finance owner before enabling writes.
    
3.  03
    
    ### Shape the app with Scout
    
    Use the starter prompt below. Ask Scout to propose the records, source field mapping, views, and access rules. Preview sample data before connecting QuickBooks; keep source IDs so records stay traceable.
    
4.  04
    
    ### Pilot, then expand
    
    Test with a small approved dataset and a least-privileged user. Check missing records, revoked access, repeated events, and failed requests. Enable live writes or messages only after the responsible owner approves the workflow.
    

## Start with this prompt

Paste into Scout, then adapt it to your team. Do not paste credentials or private customer data.

Create this app with QuickBooks: Invoice follow-up workspace. Bring authorized invoice status next to customer context and an owned follow-up queue. Start with sample data and a small, approved set of records. Before connecting live data: Map customers and document IDs carefully. Review accounting changes with the finance owner before enabling writes. Propose the data model, access rules, and source-to-app field mapping before implementation. Add source links, a last-updated time, and clear empty and connection-error states. Keep credentials out of client code. Require human approval for external messages, source changes, or money movement. Test duplicate events, revoked access, and recovery before publishing.

## Before you build

An authorized QuickBooks account, access to the required APIs, and a clear owner for the data. Provider charges are separate.

## Keep control

Use the narrowest permissions, keep credentials out of public code, and review changes before they affect customers or source systems.

[Connecting tools on Path](https://path.dev/docs#platform)[All integrations](https://path.dev/platform/connectors)

## Also explore

[![Brex logo](https://cdn.brandfetch.io/brex.com/icon?fallback=transparent)Brex](https://path.dev/guides/integrations/brex)[![Mercury logo](https://cdn.brandfetch.io/mercury.com/icon?fallback=transparent)Mercury](https://path.dev/guides/integrations/mercury)[![PayPal logo](https://cdn.brandfetch.io/paypal.com/icon?fallback=transparent)PayPal](https://path.dev/guides/integrations/paypal)

## Make it work your way.

Start with Scout, or map the first build with our team.

[Get started](https://console.path.dev/signup)[Talk to us](https://path.dev/contact-sales)

Source: https://path.dev/guides/integrations/quickbooks
