The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
docs	Ready	Preview	Aug 3, 2026 7:42am

PR Summary

Medium Risk
Journal entries and deposits post directly to live QuickBooks books; explicit posting confirmation and balanced-line validation reduce accidental writes, but mistakes still affect financial records.

Overview
Extends the QuickBooks block and docs with general accounting workflows alongside existing sales and purchasing coverage, bringing the integration to 39 operations.

New capabilities include Read Accounting Transactions (list or by-ID for journal entries, deposits, and read-only transfers) and create/update tools for journal entries and deposits. The block adds matching operation dropdown entries, an accounting transaction-type selector, JSON fields for journal and deposit lines (with wand prompts), and a Confirm Posting gate on journal create/update. Parameter mapping uses accounting_utils parsers and folds accounting reads into the same pagination and list-output patterns as other transaction readers.

Descriptions in integrations.json and the QuickBooks docs page are updated for accounting scope. A workflow template and skill content shift from credit/refund review to journal adjustments and deposits; parseConfirmation now accepts a field name for clearer validation errors.

^{Reviewed by Cursor Bugbot for commit d15b309. Bugbot is set up for automated code reviews on this repo. Configure here.}

@greptileai

Greptile Summary

The PR adds bounded QuickBooks journal-entry, deposit, and transfer reading plus create/update operations for journal entries and deposits.

• Adds strict journal/deposit line parsing, balanced integer-cent validation, posting confirmation, and sparse header-only updates.
• Registers five accounting tools and wires them through the QuickBooks block, generated metadata, registry, documentation, and tests.
• Keeps transfer support read-only and disables automatic retries and pagination.

Confidence Score: 5/5

The PR appears safe to merge from a code-review perspective, with no actionable changed-code defects identified.

The accounting operations use fixed entity mappings, bounded validated inputs, exact journal balancing, explicit posting confirmation, header-only sparse updates, and registry/block parity without a concrete reachable failure remaining.

%%{init: {'theme': 'neutral'}}%%
flowchart LR
  Block[QuickBooks block] --> Params[Resolve and validate parameters]
  Params --> Reader[Read accounting transactions]
  Params --> Journal[Create or update journal entry]
  Params --> Deposit[Create or update deposit]
  Reader --> Types{Transaction type}
  Types --> JE[JournalEntry]
  Types --> DP[Deposit]
  Types --> TR[Transfer - read only]
  Journal --> QBO[QuickBooks Online API]
  Deposit --> QBO
  JE --> QBO
  DP --> QBO
  TR --> QBO

_{Reviews (1): Last reviewed commit: "fix(quickbooks): balance journal entries..." | Re-trigger Greptile}