A log of every accounting exchange

Every push and pull writes a row naming the entity, the direction, the outcome, the HTTP status and a readable message, so a failed sync can be diagnosed after the fact.

What it is

A sync-log table written by the customer, invoice and project paths. Vendor fault envelopes are parsed into a readable message stored alongside the raw status, so the same text can be shown to a user.

Also called: QuickBooks error · why did the sync fail · accounting audit trail

See it
A log of every accounting exchange
CustomerBuildingAmountStatus
Delia YoderBarndominium$11,460Open
Delia YoderRiding Arena$13,740Paid
Sutter Kline30×40 Garage$9,180Open
Marlin HooverBarndominium$4,240Paid
Marlin HooverRiding Arena$7,850Paid
A log table: direction, entity, both ids, status, and the readable message, filtered to errors. Sample data — no customer information appears here.
How it works
  1. 1Each accounting interaction calls a log writer with the entity type and both ids.
  2. 2Success and error rows are both recorded, with the HTTP status.
  3. 3The parsed vendor fault message is stored as the user-facing message.
  4. 4Log write failures are warned about but never break the operation.
Why we built it

The customer module states it as a standing rule: 'Every QB API interaction is logged to quickbooks_sync_log per Rule 3.' The readable-message extraction exists because the vendor's fault envelope is not something a builder can act on directly.

The problem
  • Accounting failures left no diagnosable trail.
  • Raw vendor faults were unreadable to the person affected.
Sound familiar?
What you get
Every exchange is traceable to an entity and an outcome.
The error shown to a user is a sentence, not an envelope.

See it on your own jobs

Twenty minutes, your numbers, no slide deck. We’ll build one of your real buildings in front of you and send you the estimate link at the end — yours to keep either way.

or keep browsing features →