Find what's broken in Dynamics GP before the close does.
Ledger Doctor checks your GP data every night and tells you, in plain English, what's stuck, what doesn't tie and what will cause trouble at month-end. It fixes the simple problems after you approve them, with a backup and an undo button, and keeps your close checklist honest.
Early access: the first 10 customers pay $999 a year for two years.Nightly scan for Ridgeview Supply Co., 5:46 AM
| Area | Checks clear | Status |
|---|---|---|
| Server and backups | 9 of 10 | Warning |
| System | 3 of 4 | Error |
| General Ledger | 3 of 3 | Healthy |
| Payables | 7 of 9 | Error |
| Receivables | 7 of 8 | Warning |
| Sales and purchasing | 8 of 8 | Healthy |
| Fixed Assets | 4 of 4 | Healthy |
| AP aging vs GL | 1,240.18 | Doesn't tie |
All of it is unposted GL. Post batch GLJE-1017 and it ties.
51 checks across GP, every night
Each check looks for a problem GP consultants see over and over, then says what it means and what to do about it. The check library updates itself from our server, so new checks arrive without a reinstall.
- Server and backupsDatabases offline, backups too old, disks filling up, SQL Agent stopped or failing
- SystemBatches held by users who left, leftover record locks, users stuck as logged in
- General LedgerHidden unposted entries, posted entries out of balance, summary vs detail
- PayablesAging vs the AP control accounts, paid documents still open, overapplied documents
- ReceivablesAging vs the AR control accounts, sub-penny balances, applications to missing documents
- Sales Order ProcessingLines with no document, totals that don't match, next-number collisions
- Purchase Order ProcessingPO status vs its lines, receipts that don't add up
- Fixed AssetsAsset cost and depreciation vs the GL, assets with no book
- InventoryTransactions missing their header, history with no site
- Close readinessUnposted batches in every module, depreciation not run through month-end
See the fix before anything changes
Open an issue and you get the plain-English problem, the exact GP records involved and what fixing it would do. Nothing changes until someone you've named as an approver clicks Apply.
- The preview lists exactly which rows will change. Rows that don't meet the fix's safety rule are left alone.
- Every row is copied to a backup first, and every fix has an Undo button and a line in the fix history.
- Four of the most common GP lockups have one-click fixes today: batches held by users who left, leftover record locks, users stuck as logged in, and empty hidden journal entries.
- Everything else, including anything that touches amounts, is explained with what to run in GP or what to take to your GP partner. Ledger Doctor never changes an amount for you.
Subledgers that tie, or a clear reason they don't
Ledger Doctor compares what the Payables, Receivables and Fixed Assets subledgers show today with the GL balance of their control accounts. The control accounts come from your own GP setup, so there's nothing to map.
When they don't tie, it splits the difference into what's just unposted GL and what's left to explain.
A close checklist that checks itself
Start a close for any period and assign the tasks. Tasks tied to a check, like "Post all payables batches" or "AR aging ties to the GL," mark themselves complete when the nightly scan comes back clean. Everything else is ticked off by hand, with a note.
Controllers see what's done, what's at risk and what's overdue, without asking around.
It runs on your server, not ours
Your GP data stays put
Ledger Doctor runs as a Windows service on your network and reads GP straight from your SQL Server. Your financial data never leaves your building.
Not a GP add-in
Nothing is installed on GP workstations or in the GP client, so GP updates and third-party products don't break it. People open it in a browser and sign in with their Windows account.
Least access it needs
It uses its own SQL login: read-only on GP, with delete permission only on the few tables its one-click fixes clean up. Optional status sharing sends us counts and statuses only, never amounts or names.
Who it's for
Controllers and accounting teams on GP
You'd rather know about a stuck batch or an AP difference on the 28th than find it on the 2nd.
The person who keeps GP running
IT or the GP admin who gets the "batch is in use" and "record is being edited" calls, and who'd like to know backups ran.
Companies planning a move off GP
Clean data moves better. Find and fix the open-but-paid documents and the subledger differences before migration, not during it.
Questions
Will it change my GP data without asking?
No. Scans are read-only. A fix runs only when an approver previews it and clicks Apply, the rows are backed up first, and you can undo it from the fix history.
Which versions of GP and SQL Server does it work with?
Tested on SQL Server 2017, 2019, 2022 and 2025, including binary sort order and older database compatibility levels. GP 2016, 2018 and 18.x are expected to work because the checks use GP's long-stable core tables; any check that finds a different table layout reports that it can't run instead of guessing. SQL Server 2014 and older aren't supported. See the requirements.
How long does installing take?
About 20 minutes for someone who can run a script in SQL Server Management Studio and has admin rights on a Windows server. The install guide and video walk through every step.
What does the price cover?
One install: the SQL Server that holds your GP databases, with every GP company on it and as many users as you like. Check library updates are included. See pricing.
What kind of support is included?
Email support at support@myledgerdoctor.com for installing and using Ledger Doctor. It isn't a GP help desk: for fixes that change amounts, it tells you what's wrong so your GP partner can resolve it.
Is it finished?
It's in early access. The checks are tested against SQL Server and sample GP databases, and we're confirming them against live GP companies with our first customers. Founding customers get a lower price for helping us do that.
Start with one server
$1,800 a year covers every GP company on one SQL Server. Founding customers pay $999 a year for two years. Cancel within 30 days for a full refund.