Controller's Checklist for Reviewing Schedule Accounts Monthly

A controller's monthly schedule accounts review should verify that all ROs match your accounting records, confirm all labor and parts charges are properly coded to the right cost centers, check for unbilled work or erroneous credits, reconcile service revenue against DMS records, and flag any discrepancies for correction before month-end close. This checklist protects your P&L accuracy and catches billing errors before they compound.

Why Controllers Need a Structured Monthly Review Process

You know that moment when you're closing the books on the 28th and realize there's a $7,400 discrepancy between what your service department says they billed and what actually hit the general ledger? That's what happens when schedule accounts don't get reviewed systematically.

Most dealerships run three to five service lanes every day. Each lane generates ROs. Each RO has labor hours, parts costs, waste disposal fees, and miscellaneous charges. When you multiply that by 20 business days a month, you're looking at hundreds of transactions flowing into accounts receivable and service revenue accounts. Without a structured review, errors compound. A tech codes a job to the wrong labor category. A service advisor forgets to add a disposal fee to the RO. A parts person pulls inventory but doesn't log it properly. By month-end, your numbers don't match reality.

The controller's monthly review of schedule accounts catches these problems before they cascade into the next month and become ten times harder to find. This is the kind of workflow Dealer1 Solutions was built to handle—flagging mismatches in real time so you're not scrambling during close.

Here's the hard truth: if you're not doing this review, you don't actually know whether your service department is as profitable as you think it is. You're flying blind on one of your largest revenue streams.

What Are Schedule Accounts and Why Do They Matter to Your Controller

Schedule accounts in a dealership context refers to all the open ROs—the service records that have been written but not yet closed, billed, or fully paid. These are jobs in progress. A customer's vehicle comes in for an oil change and brake inspection. The service advisor opens an RO. Labor and parts get added to that RO as the technician works. Once the work is done and the customer pays, the RO closes and the revenue posts to the service revenue account.

But here's where the controller's job gets complicated: between the moment that RO opens and the moment it closes, the numbers have to flow through multiple systems. Your DMS tracks the RO. Your accounting software tracks the revenue. Your parts inventory system tracks what was used. If these three don't talk to each other perfectly, your month-end numbers are wrong.

Schedule accounts matter because they represent unbilled or partially billed work. If a vehicle has been in service for 9 days and nobody can tell you why, that RO is sitting in your schedule accounts aging. If you don't catch it, you either forget to bill the customer or you write it off as a loss. Either way, your numbers are wrong and your profitability looks better or worse than it actually is.

A typical scenario: a customer drops off a 2019 Subaru Outback for a transmission fluid service, $340 job, 1.2 hours labor. The tech finishes in 1.5 hours. The RO should show 1.2 billed hours. But the tech logged 1.5. Now you've either overcharged the customer or undercharged them, depending on how your DMS handles it. The controller catches this in the monthly review and flags it for the service manager to correct.

The Core Checklist: Seven Steps for Your Monthly Review

Step 1: Reconcile Total RO Count and Aging Report

Pull your aging report from your DMS. This report shows you every open RO and how many days it has been sitting. Cross-reference it against your accounting records. The number of ROs in your DMS should match the number of line items in your accounts receivable subledger. If they don't, you have a data integrity problem.

Look for ROs that are over 14 days old. In a healthy dealership, almost all ROs close within 5–7 days. If you have vehicles sitting for 14, 20, or 30 days, that's a workflow problem. Either the work isn't finished, the customer hasn't paid, or something fell through the cracks. Write down the RO numbers and vehicle information. You'll investigate these in Step 3.

This step should take 15 minutes. It's mechanical but critical. A mismatch here means your entire review is built on a faulty foundation.

Step 2: Verify Labor Hour Coding and Rate Accuracy

Pull a sample of 15–20 closed ROs from the month. For each one, check:

Were the labor hours charged at the correct flat-rate or hourly rate?
Does the labor category match the work performed (e.g., "scheduled maintenance" vs. "engine repair")?
Are warranty hours coded separately from customer-pay hours?
Are internal jobs (loaner repairs, demo vehicle prep) coded to the right cost center, not to customer service revenue?

This is where your techs' behavior shows up. If a tech consistently logs more hours than the flat-rate allows, you're either overpaying them or overcharging customers. If parts are being coded to labor instead of parts, your gross margin looks inflated in one category and deflated in another.

Spot-check is acceptable here. You don't need to audit every single RO. But if you find errors in your sample, pull a larger batch and see if there's a pattern. If one service advisor is consistently logging jobs to the wrong category, that's a training opportunity.

Step 3: Investigate Aged ROs (Over 7 Days Open)

Go back to your aging report. Pull any RO that's been open for more than 7 days. Call the service manager and ask: "Why is this vehicle still here?" The answer should be one of these:

Waiting on a customer decision or approval
Waiting on a parts order to arrive
Customer hasn't picked up yet (work is done, customer hasn't paid)
Work is still in progress (tech has been pulled off to urgent jobs)

Any other answer is a red flag. If the work is done and the customer has paid, the RO should be closed. If the work is done but the customer hasn't picked up, the service advisor should be calling the customer daily. If you're waiting on a part, that part should have an ETA and a clear follow-up date.

This step protects two things: cash flow and customer satisfaction. A vehicle sitting in service for 21 days is a customer satisfaction disaster and a working capital problem.

Step 4: Cross-Check Parts Charges Against Inventory Records

Pull a second sample of 10–15 ROs. For each one, verify:

Every part listed on the RO shows a corresponding inventory deduction in your parts system
The part number, quantity, and cost match between the RO and the parts ledger
Core charges (for items like alternators or batteries) are listed separately
Waste disposal and shop supplies are not coded as customer-facing parts

This is important because parts are your second-largest service revenue stream after labor. If a tech installs a $340 alternator but the parts system only shows a $280 deduction, you're losing $60 per job. Over 100 jobs a month, that's $6,000 in missing revenue.

Also check for parts that were pulled but not used. Sometimes a tech will pull three belts, use one, and return two. If your system doesn't reflect the return, you're writing off good inventory as waste.

Step 5: Verify All Discounts and Credits Are Justified

Service departments love to give discounts. A loyal customer gets 10% off. A tech overcharged the customer last month, so you comp the next oil change. A customer complained about the wait time, so the service advisor knocked $50 off the bill.

Discounts and credits are fine. But they need to be documented and approved. Pull your ROs for the month and list every discount or credit over $25. For each one, verify:

Was it approved by the service manager or general manager?
Is there a note on the RO explaining why the discount was given?
Is the discount coded to the right account (warranty, customer satisfaction, promotion, etc.)?

A pattern of large, undocumented discounts is a profit leak. It also signals that something is wrong with your pricing or your service process,either you're overcharging initially and then correcting it, or you're using discounts to cover up quality issues.

One note: sometimes a discount is legitimate but not properly documented. In that case, work with the service manager to add the note retroactively. Don't just accept the discount without explanation. You need an audit trail.

Step 6: Reconcile Service Revenue to DMS Records

This is the core reconciliation. Pull your service revenue account from your general ledger for the month. Add up all the ROs that closed in that month according to your DMS. These two numbers should match (or be within 0.5% accounting for rounding).

If they don't match, you have a posting error. Here are the common causes:

An RO closed in the DMS but didn't post to the general ledger (system integration failure)
An RO posted to the general ledger but hasn't closed in the DMS yet (timing issue)
A credit memo or adjustment was applied in one system but not the other
A cash payment was recorded in the DMS but the revenue wasn't recorded in the general ledger

Identify the specific RO numbers that are out of sync. Usually this is a one-person job for your bookkeeper to investigate and correct, but the controller needs to flag it and oversee the resolution.

Step 7: Review Warranty Claims and Reconcile to General Ledger

Warranty work is service revenue, but it flows through a different account than customer-pay work. Pull all ROs coded as warranty for the month. Verify:

The warranty type is correctly identified (manufacturer, dealer, extended, etc.)
The warranty claim has been submitted to the manufacturer or warranty provider
The amount claimed matches the amount billed on the RO
The RO is not double-coded (warranty AND customer pay)

Warranty claims are a common source of month-end surprises. A tech does a warranty repair but forgets to flag it in the DMS. Or a claim is submitted to the manufacturer but you've already expensed the labor and parts. When the manufacturer reimburses you three months later, the revenue lands in the wrong period.

This step should include a reconciliation of warranty receivables. If you submitted a $4,200 claim to the manufacturer in March, and they paid you in May, you need to account for that timing difference properly.

What to Do When You Find Discrepancies

Your review will surface errors. Here's the process for handling them:

Minor Errors (Under $100, Clear Cause)

If a technician coded 1.5 hours instead of 1.2 hours on a $340 job, and the error is clear, ask the service manager to correct it in the DMS and repost the RO. Document the correction in a spreadsheet so you have an audit trail. This should be done before month-end close if possible.

Moderate Errors ($100–$500, Ambiguous Cause)

Meet with the service manager and the technician or service advisor involved. Understand what happened. Was it intentional (a discount given without approval)? Was it a system error? Was it a misunderstanding of the job scope? Once you understand the cause, decide whether to correct it retroactively or leave it as-is with a documented explanation.

Large Errors (Over $500)

These need to go to the general manager or dealer principal. A $2,000 discrepancy between what the DMS says was billed and what the general ledger shows is not a small problem. It signals either a serious control issue or a system integration failure. Get senior leadership involved in the decision on how to handle it.

The Documentation You Need to Keep

Create a monthly checklist document. Use it every month. Keep it in a shared folder so the next controller or accountant can follow your process. Here's what should be in it:

The date the review was completed
The name of the person who completed it
The total number of ROs opened in the month
The total number of ROs closed in the month
The number of ROs still open (and their aging breakdown)
Total service revenue posted to the general ledger
Total service revenue according to the DMS
The variance (if any) and the explanation
A list of any ROs over 7 days old and the reason for the age
A list of any discrepancies found and how they were resolved
Initials of the service manager and general manager confirming the review

This documentation serves two purposes. First, it creates accountability. Everyone knows the review is happening and that discrepancies will be caught. Second, it protects you in an audit. If your CPA or an outside auditor asks, "How do you know your service revenue is accurate?", you can show them a systematic process you follow every month.

Common Pitfalls and How to Avoid Them

Pitfall 1: Reviewing Too Late in the Month

If you wait until the 28th to start your review, you won't have time to correct errors before close. Start on the 22nd or 23rd. That gives you a week to investigate discrepancies and get them fixed.

Pitfall 2: Not Involving the Service Manager

The service manager knows why ROs are aged. They know if a discount was legitimate. They know if a tech is consistently overstating hours. Don't do this review in isolation. Make it a partnership. The service manager should be your second set of eyes on every significant discrepancy.

Pitfall 3: Accepting "I Don't Know" as an Answer

If you ask the service manager, "Why has this RO been open for 16 days?" and they say, "I don't know," that's not acceptable. Press them. Look at the RO notes. Call the customer. Find out what's actually happening. An RO doesn't stay open for 16 days by accident.

Pitfall 4: Not Tracking Trends

Do the same review next month. And the month after. Keep a spreadsheet of your findings. Is the number of aged ROs getting worse? Is one service advisor consistently giving unauthorized discounts? Are warranty claims taking longer to submit? Trends matter more than individual months. A single $300 discrepancy is noise. Three consecutive months of $300 discrepancies in the same category is a signal.

How Modern Systems Make This Easier

If your DMS integrates directly with your accounting software, a lot of this work is automated. The RO posts to the general ledger in real time. A discrepancy shows up as a red flag immediately instead of waiting for month-end. You can set alerts for ROs over 5 days old so the service manager gets notified to follow up with the customer.

Even without perfect integration, a good DMS will give you the reports you need to do this review efficiently. You should be able to pull an aging report, a revenue summary by category, a warranty claim status report, and a discount/credit report with a few clicks. If you're manually digging through 200 ROs to find discrepancies, your system is holding you back.

Frequently asked questions

How often should a controller review schedule accounts?

Monthly is the standard for most dealerships. Some controllers do a weekly spot-check on high-dollar ROs (over $2,000) to catch problems faster. The full monthly review should be completed by the 28th of each month so discrepancies are resolved before month-end close.

What's the difference between a schedule account and an accounts receivable account?

Schedule accounts are open ROs,work that has been performed but not yet fully billed or collected. Accounts receivable are customer balances that are owed but not yet paid. An RO becomes an AR balance once it's closed and invoiced. The schedule account is the staging ground; AR is the final resting place.

If an RO has been open for 30 days, should it be written off?

Not automatically. First, find out why it's open. If the work is done and the customer hasn't paid, keep trying to collect. If the work isn't done, figure out the bottleneck and get it finished. Only write off an RO if the customer explicitly requests it or if you've made a business decision to comp the work for goodwill. Even then, document the decision with approval from the GM or dealer principal.

Can the service manager do this review instead of the controller?

The service manager should review their own ROs operationally,catching errors in real time and following up on aged work. But the controller's review is a financial control. The controller needs to be independent of the service department to catch problems the service manager might miss or overlook. If your service manager is also your controller, you have a separation-of-duties problem and should reconsider your organizational structure.

What should I do if I find a pattern of discrepancies in one service advisor's ROs?

Document the pattern. Pull 30 days of ROs from that advisor and summarize the errors (coding mistakes, unauthorized discounts, hour overages, etc.). Present the summary to the service manager and the advisor. It's usually a training issue,they don't understand the right way to code an RO, or they're trying to be helpful to customers by discounting without approval. Address it directly and recheck their work for the next two months to make sure the behavior improves.

How do I handle a discrepancy between the DMS and the general ledger that I can't explain?

First, make sure both systems are showing data for the same date range. A one-day timing difference is common. If the discrepancy persists, involve your bookkeeper or accountant and your DMS support team. It could be a posting rule that's set incorrectly, a batch that failed to post, or a system integration issue. Don't close the month until this is resolved. A mystery discrepancy now becomes a nightmare in next year's audit.