Why Your Dealership Payroll Journal Entry Still Gets Re-Keyed Into the DMS

Payroll went out Friday. It’s Tuesday now, and your office manager has the check register open on one screen and a spreadsheet on the other, typing numbers from one into the other so the DMS will take them. Two hours, maybe more. If that sounds familiar, you’re not doing it wrong. Your dealership payroll journal entry just isn’t coming out of payroll in the shape your DMS needs: split by store, split by department, with both sides of every tax and deduction already where they belong. Until it does, somebody rebuilds it by hand every single payroll.

This post walks through why that happens, what it really costs, and what has to be true for payroll to post to CDK, Tekion, Dealertrack, Reynolds & Reynolds, or Autosoft without the retyping.

What Your DMS Expects From a Dealership Payroll Journal Entry

A generic payroll GL report is built for a company with one location and a handful of expense accounts. A rooftop doesn’t work that way. Your chart of accounts probably carries the store in the account number (a prefix or suffix), then the department, then the kind of pay.

So one technician’s check might need to land in several places at once. Flat-rate production pay goes to one service account. Vacation, training, and holiday pay go somewhere else. A service advisor on salary posts differently than one paid hourly. New, used, service, parts, and body shop each want their own labor lines, because the GM and the dealer principal read those departmental numbers every month.

Then there’s the employer side. Every tax and every deduction has two halves: the expense you incur and the liability you owe until it’s paid. Employer FICA, FUTA, and state unemployment (the IRS Publication 15 list most controllers know by heart) all need an expense account and a liability account. So does the employer 401(k) match. Leave any of those out of the export and the entry won’t balance.

That’s the target. Most payroll systems simply don’t aim for it.

Where the Re-Keying Actually Comes From

Nobody sets out to hand-post payroll forever. It usually starts with one gap, and a workaround that was supposed to be temporary. Here are the ones that show up again and again in dealer groups.

The GL mapping never got finished after a vendor switch

Implementation went live, checks went out, and the GL was going to be “done in a couple of weeks.” Three months later, it still isn’t. Or it was set up, but wrong, so accounting moves entries around after every payroll to put them where they belong. Payroll ran. The books didn’t close.

One chart of accounts, different codes at every store

Groups that move to centralized accounting often rebuild the chart of accounts around store prefixes. Smart move for the financial statements. But if payroll can’t produce those prefixes, someone keeps a labor allocation spreadsheet for each store and wonders whether the same employee is posting to the same group every time. A buy-here-pay-here lot on its own EIN, still on separate books, makes it messier.

People who work across departments or stores

The GM’s salary is split across three rooftops. A porter works new and used. The controller supports every store in the group. If payroll puts each of them in one home department, somebody has to split them back out by hand before the entry means anything.

Taxes and 401(k) match keyed back in to make it tie

This one’s common in smaller stores. The payroll report covers wages, so the employer taxes and the 401(k) employer match get entered back into the DMS manually just so the GL matches. Then the same contributions get typed again into the retirement provider’s site. Same numbers, three times.

Workarounds that turn into the process

You’ve probably seen at least one. The check register gets transposed into a Google Sheet that’s formatted just right for a CDK power-post. Reports get downloaded, keyed into a template, and imported into Dealertrack. A placeholder employee gets created only so an import file will pass. Or payroll goes to an outside CPA as a spreadsheet and comes back as a stack of badly formatted Excel reports that someone posts by hand.

And sometimes the problem hides in service. If technician pay posts to work in process but the employee numbers don’t match what the DMS expects, those entries never clear against their repair orders. The WIP schedule grows quietly until somebody has to clear thousands of stale lines by hand.

What Hand-Posting Really Costs a Dealer Group

Start with time. Two people spending two hours per payroll hand-keying the GL is a real, common number. A fractional CFO spending 15 to 20 hours a month posting payroll allocations, deductions, and taxes is another. Multiply by 26 payrolls a year, or 24 if you pay semi-monthly, and it adds up to weeks.

The timing hurts, too. The first few days of the month are already the worst stretch in a dealership office. Commissions are closing, the GM is reviewing the financial statement, and payroll has to be finalized. Adding a manual journal entry to that pile is how things get missed.

Then there’s accuracy. One transposed digit posts a service advisor to parts, and now the departmental P&L is wrong in a way nobody notices until the month’s already closed. Dealers compare their departments against industry figures like the annual NADA Data report. That comparison is only useful if your own departmental numbers are clean.

And there’s the person. When the one person who knows how the spreadsheet works leaves, or just takes a week off, the posting stops. Sound familiar? We covered the broader version of this in 5 Payroll Mistakes Costing Your Dealership Money. The journal entry is where a lot of those mistakes finally land.

How to Get Payroll Posting to the DMS by Store and Department

Whatever system you’re on, the fix follows the same steps. Use this as a checklist with your payroll provider, or as a list of questions if you’re evaluating a new one.

• Map everything, both sides. Every earnings code needs an expense account. Every tax and deduction needs an expense account and a liability account, employer-paid and employee-paid kept apart.
• Build the store and department grid. Pair each department with each base account so a single pay code can land in new, used, service, parts, or body shop, at the right store.
• Decide how split employees post. Home department, or where they actually worked? Pick one on purpose.
• Match tech employee numbers to the DMS. If they don’t match, flag time and WIP won’t tie out.
• Get the GL working before go-live, in writing. Then test it against a real payroll before quarter end, not after.

That’s where Netchex makes a difference. Netchex integrates with Dealertrack, CDK Global, Tekion, Reynolds & Reynolds, Automate, Dominion, and Autosoft, with payroll, time, and GL set up for each system instead of one generic export.

For Dealertrack dealers, tech time and commissions come into Netchex Payroll through an API feed, and GL data pushes back into Dealertrack after payroll runs, with no manual exports. For CDK stores, Netchex sends the last invoiced payroll’s GL transactions to CDK, with account distribution you can consolidate the way your accounting team wants. Tekion and the other DMS platforms get GL output built to match that system, too.

Under the hood, Netchex’s multidimensional GL mapping lets you break payroll costs out by department and account in one grid, one GL code per cell. Taxes and deductions carry their own expense and liability accounts. Anything unmapped is flagged in red, so gaps are easy to spot before payroll runs. And the GL Transactions report allocates by labor distribution, so a split employee posts where they actually worked.

You don’t have to build it alone. Implementation is free and project-managed, including your data import. The support team is trained on CDK, Dealertrack, and Reynolds & Reynolds, and understands flat-rate pay, draws, flag time, and how DMS environments actually work.

Frequently Asked Questions

This guide reflects publicly available product information and independent reviewer data (G2, Capterra, Trustpilot, Yelp, Better Business Bureau, Reddit, Software Advice, GetApp) as of 2026. Feature availability and pricing may vary by plan. Contact each provider for current details.

Disclaimer: Any product roadmap or future plans provided herein are for informational purposes only. They do not represent a commitment to deliver any material, code, feature, or functionality. Plans may change without notification. The development, release and timing of any features or functionality described remain at the sole discretion of Netchex, its affiliates, and partners. Netchex does not give legal, tax, or accounting advice. You are responsible for ensuring your use of Netchex product meets your individual business and compliance requirements.

Print this page