Return a pallet of tile and the supplier refunds your card. In Buildertrend that becomes a vendor credit. In QuickBooks it becomes a credit card refund. Those two things cannot be matched to each other, and Buildertrend says so in its own FAQ.
Here is what that costs a remodeler over a year, and how to check whether it's already happening in your books.
Do Buildertrend vendor credits sync to QuickBooks?
Not in a way that matches. Buildertrend's own FAQ states its negative bills create vendor credits that cannot be matched to a credit card refund. You have to build a credit card credit from the bank feed instead. Miss that step and the job keeps carrying a cost your supplier already refunded.
Where the handoff actually stops
1. A refund creates two records that can't find each other
Buildertrend's QuickBooks FAQ, verbatim:
"Buildertrend negative bills create vendor credits which cannot be matched to a credit card refund. Therefore, you will need to create a credit card credit from the bank feed instead of using the vendor credit."
So the returned tile produces a vendor credit sitting in one place and a refund sitting in the bank feed in another. Neither knows about the other. Somebody has to notice, ignore the credit that Buildertrend just created, and hand-build a different record from the bank side instead.
This is worth saying before the rest: neither product is broken. Buildertrend models a job. QuickBooks models money moving. A refund is one event in the world and two different objects in two different systems, and no one built a rule for which object wins. That's a boundary between two products, not a bug in either.
2. Your job coding doesn't travel, so someone re-tags every push
"Buildertrend does not link to classes or locations. You can, however, add these in manually after the bill, invoice, or time entry is pushed to QuickBooks."
Read the second sentence carefully. It isn't a workaround. It's the standing procedure: every bill, every invoice, every time entry gets its class or location added by hand, in QuickBooks, after it arrives.
If you use classes to separate divisions, or locations to separate branches, that's a manual step on every single transaction, forever.
3. One person owns the connection
"No, only the person that established the QuickBooks connection can be the QuickBooks administrator. This person is responsible for establishing and adjusting the integration preferences."
Fine while they're there. The problem arrives the day that person leaves, changes role, or goes on holiday during closeout. The settings that govern how your job costs reach your ledger belong to one login.
4. Disconnecting can double your budget
This one deserves a full read, because it's the most expensive item on the page. On switching the integration, Buildertrend warns:
"Bills and invoices not marked as paid before disconnect will lose their accounting link and must be manually marked as paid in Buildertrend after payment is recorded in Intuit"
"The disconnect removes the reference that prevents duplication · Buildertrend may pull previously pushed expenses, duplicating budget items"
A vendor telling you their own product may duplicate your budget items is about as direct an admission as documentation ever gets. If you have ever switched accounting editions and your job costs looked strangely high afterwards, that paragraph is the reason to go looking.
All quotes are from Buildertrend's own QuickBooks FAQ, re-verified 28 July 2026. Read it before you take our word for any of this.
What this actually costs: money that never finds its way back to the job
The pattern is the same in all four cases. A record exists on one side with no matching partner on the other, so a person has to intervene — and the cost lands when nobody does.
An unmatched refund doesn't announce itself. The job keeps carrying the original material cost, because nothing corrects it. Meanwhile the refund sits in the bank feed as an unmatched line. Over enough jobs, that reads as lower margin than you actually have — and you price the next bid off it.
Nothing here shows up as an error. That's what makes it expensive.
Your own number, from your own records
You can check this tonight. It's four numbers and none of them need a meeting.
| Take | From |
|---|---|
| Material returns and supplier refunds in the last 12 months | Your supplier statements, or the credit card feed filtered to credits |
| How many of those are matched against a job in QuickBooks today | QuickBooks — check whether each refund carries a job or project |
| Total value of the unmatched ones | The difference. This is money your jobs are still carrying as cost |
| Your unreconciled credit-card lines older than 60 days | The bank feed. Refunds are the usual reason they sit |
Row three is the direct answer. Anything still sitting in row four is where the rest of it is hiding.
Then take row three and ask what it did to your margin on those jobs — and what it did to the bids you priced off them. A refund you never matched doesn't just cost you the refund. It quietly teaches you that the job cost more than it did, and you carry that lesson into every quote after it.
The fix is structural, not motivational
The obvious answer is a rule: whenever there's a return, remember to build the credit card credit from the bank feed instead of using the vendor credit.
That rule is correct. It's also the exact instruction Buildertrend already publishes, and it's still not happening in most books, which tells you something about rules that live in people's heads.
It fails for an ordinary reason. Returns are rare and irregular. Nobody does one often enough to build the habit, and the person handling it is usually mid-closeout with other work stacked behind them. A procedure that runs four times a year and requires remembering to do the counter-intuitive thing is not a procedure. It's a hope.
Rare events need to be handled by the system, not by the person. That means the return gets caught where it enters — at the bank feed, where it always shows up — rather than depending on someone connecting it back to a credit created somewhere else days earlier. Catch it at the door and nobody has to remember anything.
When you don't need us
If you process fewer than a handful of returns a year and your bookkeeper already catches them, you don't have a problem worth spending money on. Check row three above. If it's near zero, stop here — genuinely.
If you don't use classes or locations, item two on this page costs you nothing. A lot of remodelers don't. Skip it.
If you've never switched accounting editions, item four hasn't happened to you and may never. It's worth knowing before you switch, not worth acting on today.
Act on this when row three comes back as a real number and returns are a monthly event — particularly if the person who catches them is already your bottleneck everywhere else.
Other tool pairs we have documented
Same method each time: the vendor's own documentation, quoted and dated, then the arithmetic to price it against your records.
- Monday.com and QuickBooks — what does and does not reach the ledger, and how to price the retyping.
- Procore and QuickBooks Online — Procore's published list of what never reaches QuickBooks Online.
- AccuLynx and Xactimate — the seam a vendor cannot close, because the carrier owns it.
Where to go next
This is one handoff of several in a typical remodeling operation. The same test — find the record that has no partner on the other side — is what the guide on connecting your business tools applies across the whole stack.