Why a Payment Didn't Reach QuickBooks

A checklist in the order to actually check it, so you can find in minutes why a payment you logged in MonuDesk has not shown up in QuickBooks — including the two causes that fail silently.

Written By Dennis Rodin

Last updated 15 days ago

You logged a payment in MonuDesk, you went looking for it in QuickBooks, and it is not there. Work down this list in order — the first four causes account for almost every case, and two of them fail quietly with no error shown anywhere.

Pro feature. The QuickBooks integration is included with the MonuDesk Pro plan. If a Pro plan or trial has lapsed, nothing syncs to QuickBooks until it is active again.


1. Is QuickBooks connected for the right office?

On a multi-office account, QuickBooks is connected per office, and a payment posts to the QuickBooks company of that order's office — not the office you happen to be looking at.

Go to Settings → Integrations → QuickBooks, set Managing location to the order's office, and look for the green Connected badge and the QuickBooks company name underneath it. A connection can drop on its own when Intuit expires the authorization, so an office that worked last month is worth re-checking.

Gotcha: if the customer's contact record is assigned to a location, that location's QuickBooks company is used instead of the order's office. A contact filed under the wrong branch sends its payments to the wrong books.


2. Was the payment marked "I already entered this in QuickBooks"?

On the Log Payment screen there is a checkbox reading I already entered this in QuickBooks, with the note "Keeps it on the order balance but leaves it out of the QuickBooks sync, so the same payment is not recorded twice."

A payment saved with that box ticked behaves exactly like any other payment inside MonuDesk. It lowers the balance due, it appears on the order overview, it gets a receipt, and it shows on the Activity Timeline. It is simply never sent to QuickBooks, on purpose, because you told MonuDesk it is already there.

So the two figures differ by design: the received total is every payment on the order, and the syncable total is only the payments MonuDesk is responsible for pushing. If a payment is missing from QuickBooks and the money is already in your books by hand, this is almost certainly why — and nothing is wrong.

The checkbox is set when the payment is recorded. To change your mind, delete the payment and log it again with the box in the state you want.


3. Has the order itself reached QuickBooks yet?

A payment attaches to a document. If the order never created one, the payment has nothing to attach to.

Under Settings → Integrations → QuickBooks you choose what a quote creates in QuickBooks, and there are three answers. Confirmed orders always sync, whatever this is set to.

  • Estimate (recommended) - QuickBooks' own quote document. It is non-posting: nothing lands on your books while the job is still a quote, so a payment logged at the quote stage has no invoice to apply to yet. The estimate becomes an invoice when the customer confirms the order.

  • Invoice - the quote is billed straight away, so an invoice exists from the quote stage on and payments have somewhere to land.

  • Nothing - quotes stay in MonuDesk and create no QuickBooks document at all. The invoice is created when the order is confirmed.

This matters most when Order document type is set to Invoice, the default. In that mode a payment is applied to the order's QuickBooks invoice, so if no invoice was ever created, the payment silently has nowhere to land. Confirm the quote into an order, and the invoice and its payments follow.

Last in this check: the order's own QuickBooks switch. An order created with Send this order to QuickBooks turned off on the Review & Create step is deliberately kept off the books — no invoice, no sales receipt, no journal entry, and none of its payments are ever pushed. The giveaway is that the order does not appear in Order sync activity at all: search its number there and nothing comes back.

That switch can only be set while the order is being created, so it cannot be turned back on afterwards. If the order does belong in your books, enter it in QuickBooks by hand and tick I already entered this in QuickBooks on any further payments you log against it.


4. Was the order created before you connected QuickBooks?

Orders that predate the office's QuickBooks connection are deliberately skipped. MonuDesk cannot know whether that income was already entered by hand before it was connected, so it refuses to post it rather than risk double-counting your revenue.

The same guard applies to an order whose income was already recorded another way. If you want an old order in QuickBooks, enter it there by hand, and tick I already entered this in QuickBooks on any further payments you log against it.


5. Does the order's type have an income account mapped?

This is the quiet one. In Settings → Integrations → QuickBooks → Income Account Mapping, each row pairs a QuickBooks income account with a kind of sale. When a sale type has no account and no default is set, MonuDesk has nowhere to book the income — so it does not post, and no error is shown.

  • Fill in the default income account first. It catches everything that does not match a more specific rule, and it is the single most common fix.

  • Then add rows for anything you want kept separate — monument sales to one account, services such as cleaning, lettering and foundation work to another, accessories such as vases, photos and etching to a third.

  • This mapping is set per office, so a second location needs its own.

If your Income account entry type is set to Journal Entry, an unmapped order means the income journal entry is skipped entirely and nothing appears. Set the mapping and log the next payment; earlier ones will need re-syncing or a manual entry.


6. Read the order's QuickBooks activity

MonuDesk records everything it did in your QuickBooks, order by order. Go to Settings → Integrations → QuickBooks and click Order sync activity. Search for the order number or the customer, then click the row to expand it.

The status pill on the row tells you where you stand: Synced, Linked (existing), Partial, Pending, Not synced, Voided or Error. Voided means the order was cancelled and MonuDesk reversed its QuickBooks paperwork, so the revenue is off your books on purpose. Inside the expanded row is a time-stamped list of every action — the customer created or reused, the invoice, the sales receipt, the payment, the income journal entry, the PDF attached — each with its QuickBooks document number, the amount, and the income account it used. Failed steps are listed too, in red, with the reason. A missing connection shows up here as "QuickBooks is not connected for this office."

Read it like this:

  • No entry for the payment — it never left MonuDesk. One of causes 1 to 5 above applies.

  • An entry with a document number — it did leave. Search QuickBooks for that document number; it is usually filed under a customer name you were not expecting. That is a field-mapping or wrong-customer question rather than a sync failure — see cause 7.

  • A red entry — the reason is printed. Fix it and log or re-sync.

  • "No QuickBooks activity recorded for this order yet" — the order has never synced at all. Start at cause 1.


7. It reached QuickBooks, but under the wrong customer

A payment filed under the wrong QuickBooks customer looks missing when you go looking under the right one. The row in Order sync activity still reads Synced and carries a document number; it is the customer name on it that is wrong.

Fix it from that same list. Every row has a Sync Order button, which opens Sync order <number> to QuickBooks. Search the QuickBooks customer list and pick the customer the order belongs to.

If the order was already synced to a different customer, the confirm button reads Void and re-sync to this customer. MonuDesk voids the invoice, the sales receipts and the payments it created under the old customer, then rebuilds them all under the one you chose. It works on orders synced months ago, so an old job filed under the wrong name does not have to be unpicked by hand.

To get it right up front on the next job, set the customer while you write the order. The Review & Create step of New Quote has a QuickBooks customer picker under the QuickBooks sync switch, with a Create a new customer in QuickBooks option when the customer is not there yet.


8. The opposite problem: it is in there twice

MonuDesk stores the QuickBooks document it created for each payment, so re-syncing an order, logging another payment, or opening the order again never posts the same payment a second time.

It goes further before creating anything: it looks for a sales receipt, invoice or journal entry in QuickBooks that already matches the same customer, amount and date, and links to that instead of making a duplicate. When it does, the activity log says so — "Found existing QuickBooks sales receipt 1043 ($2,400.00) — linked it, skipped creating a duplicate."

So a genuine duplicate is almost always a payment that was keyed into QuickBooks by hand and then logged in MonuDesk without ticking I already entered this in QuickBooks. Delete one side, and use the checkbox next time.


9. What to send support

If you have been through the list and it still has not landed, send us:

  • The order number and the payment's date and amount.

  • Which office the order belongs to, and the QuickBooks company name shown on the Integrations page for that office.

  • What the Order sync activity row says — the status pill, and the last few lines from the expanded view, including any red ones.

  • Your Order document type and Income account entry type settings, and whether the sale type has an income account mapped.

That is enough for us to trace the payment without asking you to check anything twice.


Related articles: