Accounting & payroll data connectors

The finance agents needed the books under them: P&L, balance sheet, A/R and A/P aging, and payroll reads. The catch is QuickBooks Online. Its OAuth is scoped to one company file per authorization, and I run a separate QBO company for every property. So I can address exactly one property's books at a time, not the whole portfolio at once.

How it works

Hosted MCP connectors expose QuickBooks Online and Gusto to Claude as a read layer. QBO hands back the financials and the AR/AP aging. Gusto handles payroll, because the QBO payroll scopes aren't on the grant, so I route payroll reads through Gusto instead. Since Intuit only grants one realm at a time, I designed the multi-property work as sequential re-auth plus a per-property local cache, never parallel access.

• Always call company-info first to confirm which property is authorized right now. I never assume.
• QBO for the books, Gusto for payroll, each on its own connector.
• Per-property JSON caches, so a portfolio roll-up doesn't need ten live sessions open at once.

It's live and boring in the best way. It's the plumbing every finance agent sits on. The next move is caching enough that a cross-property read stops needing a fresh consent screen every time.

This is the seat where I stay CFO and the agents run the back office. The read layer is what lets them work the books without me handing them files one at a time.