RealGreen and QuickBooks: who owns the money numbers?

Should RealGreen sync with QuickBooks? Our answer, after watching a lot of lawn companies wrestle with this: connect them, but not the way most people first imagine. Each system owns different money numbers. RealGreen owns the numbers that touch customers: invoices, payments, accounts receivable, prepays. QuickBooks owns the numbers that touch the government and your accountant: the general ledger, payroll, taxes, and the statements your banker reads. The mistake is trying to make them the same system by syncing every transaction across. The pattern that stays sane is a monthly summary journal entry from RealGreen into QuickBooks, plus a reconciliation ritual that catches drift while it is still small.

Who owns which numbers?

Draw the line once and defend it:

• RealGreen: customer invoices, payments and deposits, AR aging, prepay balances, service-level revenue detail, pricing.
• QuickBooks: the chart of accounts, payroll, vendor bills and expenses, loans and equipment, sales tax filings, financial statements.
• Both, by design: total revenue and total cash received, which is exactly what the monthly reconciliation checks.

When someone asks how much a customer owes, the answer lives in RealGreen. When someone asks whether June was profitable, the answer lives in QuickBooks. If either question sends your office to the other system, the line is drawn wrong. RealGreen is built to be the customer ledger: let it do that job fully.

Why transaction-level sync is usually a mistake

Pushing every RealGreen invoice and payment into QuickBooks as individual transactions sounds rigorous and creates two AR systems that disagree by design. Every edit, reversal, write-off, and reapplied payment in RealGreen now needs a twin in QuickBooks; every mismatch becomes an afternoon of archaeology. We have watched accountants inherit files with tens of thousands of synced micro-transactions, a QuickBooks AR balance nobody trusts, and a bookkeeper reconciling customer-by-customer what should have been ten journal lines. There are companies with a genuine need for transaction detail in the GL (unusual entity structures, certain franchise reporting requirements), but for a typical single-entity operator the detail already exists in RealGreen, and duplicating it buys risk, not insight.

The summary journal pattern

Once a month, RealGreen's financial reports become one journal entry in QuickBooks:

1. Run the month's revenue summary by category: lawn program, tree and shrub, pest, aeration, finance charges.
2. Run payments received, broken out by deposit method (checks, cards, ACH), plus adjustments and write-offs.
3. Post one journal entry: revenue by category to income accounts, payments to the bank or undeposited funds, the net change to a single AR control account, and prepay movement to a deferred-revenue liability.
4. Match card totals to processor batch deposits, net of fees, and book the fees as an expense.

Thirty to sixty minutes once the template exists. Prepays deserve particular respect: the cash your prepay campaigns collect in January for services delivered April through October is a liability being earned down, and booking it as January income makes winter look rich and summer look poor, then surprises you at tax time.

The month-end reconciliation that catches drift

Three checks, same order every month. One: RealGreen total payments equals QuickBooks deposits for the month, net of processor fees. Two: the RealGreen AR aging total equals the QuickBooks AR control account. Three: the prepay liability moved by exactly what RealGreen says was sold and earned. When a check fails, the cause is almost always boring: a deposit posted in the wrong month, a card batch that settled across month-end, a write-off recorded in one system only. Catch it at 30 days and it is a note; catch it at year-end and it is a project. The same discipline that makes your weekly operating numbers trustworthy applies here at a monthly cadence.

When is tighter integration actually worth it?

A few situations justify more than the monthly summary. Multi-entity operators (separate LLCs per branch or per service line) often need the summary posted per entity, which is still summaries, just more of them. Franchisees with royalty reporting sometimes owe corporate a revenue breakdown on a schedule and format that argues for a weekly summary cadence instead of monthly. Companies carrying a bank covenant that requires monthly financials by a deadline benefit from tightening the close to the first week. Notice what none of these require: transaction-level sync. Even the demanding cases are almost always served by more frequent or more granular summaries, not by mirroring the customer ledger. One genuine gotcha to build into whatever you do: card processors that deposit net of fees will quietly break the payments check unless the journal books gross payments and fees separately, so settle that convention with your accountant on day one rather than discovering it during a messy month-end.

What about your accountant?

Many bookkeepers reflexively want everything inside QuickBooks because it is the system they know. Hold the line politely: offer read access to RealGreen's AR reports, deliver the summary entry on a fixed schedule, and most objections dissolve, because what accountants actually want is numbers that reconcile. If you are paying hourly for someone to re-key RealGreen detail into QuickBooks, you are paying to make your books worse. The reverse trap also exists: owners who run everything from the RealGreen side and treat QuickBooks as a shoebox discover at loan-application time that their financials are fiction. Both systems deserve their lane. And if what you are really after is operating insight (revenue per round, program penetration, cancel trends), neither system is the right tool: that is reporting territory, the kind our reporting platform builds from synced RealGreen data rather than from the general ledger.

The takeaway: RealGreen is the customer ledger, QuickBooks is the company ledger, and a monthly summary entry plus three reconciliation checks is the whole bridge. Sync transactions and you get two systems that disagree; summarize and reconcile and you get books you can defend.

Close this month cleanly

1. Write the one-page ownership map: which questions each system answers, posted where the office can see it.
2. Build the summary journal template with your accountant once; reuse it every month.
3. Add the three reconciliation checks to the month-end routine, with initials and a date.
4. Confirm prepays sit in a deferred-revenue account, not in income on the day the check clears.
5. If your bookkeeper is re-keying transactions today, price that time against a one-hour summary close.