An idempotent push: once an accounting invoice id is recorded on the platform invoice, it is never re-created. It resolves the accounting customer, reads the account's default item mapping, and records both a sync-log row and an error field on the invoice when something goes wrong.
Also called: push invoice to QuickBooks · invoice in my accounting · ACH through QuickBooks · push invoice to quickbooks · invoice in my books · accounting copy of the invoice
- 1Send is pressed on a platform invoice.
- 2If an accounting invoice id already exists, the push is a no-op.
- 3The accounting customer is resolved or created.
- 4The account's mapped default item carries the invoice total.
- 5Failure writes an error onto the invoice and a sync-log row; the platform send still completes.
The module header states the design and its non-blocking posture: 'on platform Send, mirror our invoice into the builder's QuickBooks so they have a copy and can send it for payment via QB (QB has ACH built in). Idempotent — once invoices.quickbooks_invoice_id is set we never re-create. Best-effort: a failure here never blocks the platform send.'
- Invoices had to be re-entered into accounting manually.
- An accounting outage would otherwise block sending an invoice to a customer.
- Retries could have created duplicate accounting invoices.
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 →