QuickBooks Integration · updated 2026-08-22

Edge cases, honestly: voids, refunds, homonyms and accountant edits

Real ledgers have messy moments. This guide documents exactly how the integration behaves in each edge case, including its deliberate limitations, so you and your accountant are never guessing.

1. 1

   Invoice voided or deleted AFTER it synced

   The integration does not silently void things in your ledger. Instead, the sync log shows a clear alert: the invoice was voided in Dumpster Controls after syncing, with the QuickBooks id, asking you to void it in QuickBooks. One manual click on your side, zero surprise numbers.

2. 2

   Two customers with the same name

   John Smith the homeowner and John Smith the contractor stay separate. The integration only links to an existing QuickBooks customer when the email matches; a name-only match creates a new customer with a unique (DC-xxxxxx) suffix. Shared emails (a property manager handling several properties) link to the same QuickBooks customer, which is usually what accountants want.

3. 3

   Partial and net refunds

   The credit memo always carries the actual refunded amount. When a refund is net of processing fees, the ledger shows the net; when it is a full refund, the full amount. If the integration cannot determine the correct amount for an unusual case, it fails the item into the sync log for review instead of guessing.

4. 4

   A payment edited after it synced

   Payments are immutable in QuickBooks once synced (V1 decision). If a payment's amount is later changed in Dumpster Controls, the sync log flags the divergence explicitly with both values so you can adjust in QuickBooks; the log never claims success on a divergent payment.

5. 5

   Your accountant's edits in QuickBooks

   Re-categorizing, renaming the service item's account, adding memos: all safe, the integration will not fight back. One caveat to know: when an invoice is edited in Dumpster Controls, its QuickBooks copy is rewritten in full, so custom fields, classes or terms your accountant added ON THAT SPECIFIC INVOICE are replaced. Fields on customers are preserved (customer updates are sparse). Invoice-level customizations are best made in Dumpster Controls or after the invoice stops changing.

6. 6

   An invoice paid in QuickBooks terms

   If an invoice total changes in Dumpster Controls after its payment synced, QuickBooks will show it as partially paid (total went up) or show a customer credit (total went down). The sync log plus the DC- document numbers make these cases easy to spot and resolve; they are rare because paid invoices seldom change.

7. 7

   Timezones and dates

   Transaction dates use the record's UTC date. For companies far from UTC, a late-night invoice can land dated one day off from your local calendar. Totals are unaffected; if a date matters for a period close, adjust it in QuickBooks.

8. 8

   Historical data

   Nothing from before your connection date is exported automatically, by design: your existing books were built by your accountant and the integration respects them. A guided historical backfill is on the roadmap; matched customers (same email) already link correctly when new activity references them.