Release notes

What changed in each version of Ledger Doctor. New checks arrive on their own once a day; these are updates to the program itself.

Implementation partners: release notes for the partner application are on their own page.

0.40.4

November 2026. Check library 0.23.0 (unchanged).

• Fixed asset depreciation history for your partner. Your partner's package now carries each fixed asset's depreciation and cost changes by date, from GP's corporate book. When your fixed assets move to Sage Intacct after go-live, your partner uses it to work out each asset's balances on the day before, to the penny.
• Fixed asset IDs with their suffix. GP's asset ID suffix now reaches your partner's package, so an asset and its child (SAMPLE001-1 and SAMPLE001-2) are told apart.
• Your Management Reporter report definitions, if you choose. A new setting on the Migration page shares your Management Reporter row, column and tree definitions with your partner, read straight from its database. No amounts and no people are sent. Your partner uses them to check the new chart and dimensions against how you report. It's off until you turn it on. More
• Fixed asset cost changes. A cost change made in GP's Asset Book window now counts toward the asset's cost in your partner's package, so the asset isn't left out.
• Your company's setup for the new entity. Your partner's package now carries GP's company name, address and currency for setting up your Sage Intacct entity. The company's tax ID goes only with your permission, like vendors' tax IDs. When Ledger Doctor can't read it, the package tells your partner why.
• Retired fixed assets. A retired asset's cost and accumulated depreciation in your partner's package come from GP's cost before retirement and its life-to-date depreciation.
• What each package carried. The job log now counts the customers, vendors, fixed assets, items and employees each package to your partner carried, and says how many retired fixed assets were left out.

0.39.1

November 2026. Check library 0.23.0 (unchanged).

• More of GP's history for your partner. Your partner's package now carries the GP values they use to tie Sage Intacct back to GP: each GL line's original account, journal entry, source document and originating document, and GP's vendor, customer and asset IDs. Tax IDs and bank details still go only with your permission. More

0.38.2

November 2026. Check library 0.23.0 (unchanged).

• A reopened close task's history shows people's names and the same date format as the rest of the close page.

0.38.1

November 2026. Check library 0.23.0: beginning balances that don't roll forward from the year before (C88), every open year named (K11), and open documents with no applications (C75) with fixes to set the full amount. Tested as 0.38.0.

• Let your partner download your data for the migration. On the Migration page, under each connection, an admin can allow your partner to download your data for implementation and data migration. That's needed when your Sage Intacct company doesn't have Web Services, so your partner imports files instead. While it's allowed, your vendors' tax IDs, 1099 setup and bank details go to your partner encrypted. Turning it off tells your partner to delete them. Each change is in the security log. More
• Small team, tidied. With Security on, the last Approver can't be removed. Choosing a Windows group as the one approver says that everyone in it gets the approver's powers. An undone fix shows again in its check right away, and the undo is in the security log.
• Reopen a close task. An Approver can reopen a task someone completed or reviewed. It's kept in the task's history and in the close binder.

0.37.2

November 2026. Check library 0.22.1 (unchanged). Tested as 0.37.0 and 0.37.1.

• Vendor tax IDs and bank details go straight to Sage Intacct from your server. Your partner can send your Ledger Doctor a Sage Intacct web services sign-in for your own company. When they ask, Ledger Doctor reads each vendor's tax ID, 1099 form and box, and EFT bank details from GP and sets them in Sage Intacct itself, so those numbers never go through your partner. The sign-in is sealed to your server and never shown. The Migration page says it's there, and an admin can delete it. It's deleted when the connection ends or after GP's last day for the migration. More
• Go-live and GP's last day. When your partner reports that a company went live in Sage Intacct, and when GP's last day for the migration is, the Migration page shows both, with any modules still in GP until a later date. Nothing changes on its own: Ledger Doctor keeps working. After GP's last day, nothing more goes to your partner for that company.
• Documents reduced in GP with no record of how. An invoice or bill whose open amount GP shows as reduced, with no application or write-off record at all, is taken at what GP shows for any date. It's named in a warning on the AR or AP tie-out and in your partner's package, with its own reconciling item, instead of stopping them. If an apply was removed rather than the balance loaded that way, fix it first (check C75).
• Small team sets the roles up for you. Ticking Small team on Security now asks how your team works: one person doing the accounting, or a small team with one approver. One click makes the right people Approvers (and anyone you tick a Processor) and turns Small team on, so nobody is left a Processor whose fixes wait with nobody to approve them. It names any Windows group being made an Approver and says when two or more approvers would be left. Each change is written to the security log. If one person does the accounting, or one person approves.

0.36.3

November 2026. Check library 0.22.1 (unchanged). Tested as 0.36.2.

• Outstanding checks and deposits at cutover. When your partner asks for open items, the migration package also carries, for each checkbook, the checks and deposits that hadn't cleared the bank on the cutover date, the last reconciliation before it, and GP's book balance that day. They're checked to the penny here first: the reconciled balance plus deposits less checks has to equal the book balance.
• Bank tie-outs read your reconciliation history again. Ledger Doctor now finds GP's reconciliation columns whatever their capitalization. Until now, some GP versions' bank tie-outs left out past reconciliations.
• Documents fully paid with no record of how. An invoice or bill GP shows as fully paid, but with no application or write-off record at all (usually from an earlier conversion or integration), is treated as closed for any date. It's named in a warning on the AR or AP tie-out and in your partner's package, with its own reconciling item, instead of stopping them. A partly applied document whose history doesn't add up is still refused, by name.
• The Migration page shows transfers under 1 MB in KB.
• Checkbooks reconciled only after the cutover. A checkbook is called never reconciled only when GP shows no sign of any reconciliation. If GP's only reconciliations on record are after the cutover, its reconciled balance on that date can't be known, so its outstanding checks and deposits aren't sent, and your partner sees why in plain words.

0.36.1

November 2026. Check library 0.22.1 (unchanged). Tested as 0.36.0.

• Bank accounts, 1099 balances and budgets for your partner's migration. The migration package carries your checkbooks with their banks and GL accounts, and this year's and last year's 1099 amounts by vendor, form and box. Of each bank account and routing number, only the last 4 digits ever leave your server. When your partner asks, it also carries your GP budgets from the year they choose. Only for a company you've confirmed for a paid migration. More
• GL history in detail, kept on your server. When your partner chooses to load every GP journal entry as its own entry, Ledger Doctor reads and checks the detail here: each entry has to balance, and the detail has to tie to GP's history to the penny. Only a summary goes to your partner until they ask for the full detail and accept its size. Then it goes encrypted, and the Migration page lists each transfer. More
• Open documents as of an earlier date. A document with an application from a payment or receipt that isn't posted yet no longer stops your partner's open items, or an AR or AP tie-out, as of an earlier date: like GP's Historical Aged Trial Balance, its amount on that date leaves the application out. Only documents whose history really doesn't add up are refused, by name.
• Currencies go to your partner with their ISO codes (USD rather than Z-US$).

0.35.4

November 2026. Check library 0.22.1 (unchanged). Tested as 0.35.3.

• Open documents for your partner's migration carry their GL distributions, so your partner can load them into Sage Intacct as historical documents with the same accounts GP used. A document GP has no distributions for is named, so it can be fixed in GP first. A document in another currency carries the exchange rate GP posted it at, or says plainly that GP has none.
• The company picker always fits in whole words, closed or open, and leaves out "close not started" rather than cutting it.

0.35.2

November 2026. Check library 0.22.1. Tested as 0.35.0 and 0.35.1.

• Every company you look after, at a glance. When you can see more than one GP company, My work opens on all of them, grouped by company, with each company's close for last month. The company picker shows each company's state next to its name ("4 tasks, 2 findings" or "all clear"), and a line under the header on every page names the other companies that still need you, so one company being clean or closed never reads as everything done. All companies in the picker adds things up on My work, the Health summary, Needs approval and the Close page. The daily email and the task reminders name every company with work. Each person sees only the companies their role covers. More
• Before you start, for posting Sales batches, now names the invoices GP won't post and why: serial or lot numbers not assigned, quantities not fulfilled when the document type fulfills separately, back-ordered quantities on a document type that doesn't allow back orders, and a currency with no exchange rate in force on the document date.
• The guide for an unposted batch shows what GP would stop on in that batch, with Check again.
• A batch open in your own window. When the batch someone has open is yours, Before you start says to close your own batch entry window, then post. Add your GP user ID in My preferences for this.
• Fix previews while someone is in GP. A fix's preview lists the rows it would change even while someone is signed in to that company, and names who is. Apply still waits until everyone is signed out.
• New checks. Checkbook balances that don't match their transactions (C85). GP tables whose columns differ from your other companies (C86). GP procedures missing that your other companies have, which GP's SQL Maintenance can rebuild (C87). Database settings GP doesn't expect, such as auto close or auto shrink (S15). GP sign-ins (S14): Ledger Doctor notes who's signed in every 15 minutes and shows each day's peak, sessions open over 24 hours, and active users who haven't signed in for 90 days. Full control of SQL Server (S13) names the GP users who have it.
• History and open items for your partner's migration. When your partner asks, the migration package carries the GL's activity summarized by account and fiscal period for the dates they choose, and your open receivables and payables on the cutover date, each checked to the penny against GP before it goes. Fiscal periods still open in GP are a warning, not a stop. Only for a company you've confirmed for a paid migration. More
• An AR or AP tie-out as of an earlier date is no longer refused because of a document posted after that date. A document posted on or before it still stops the tie-out when GP's history doesn't add up.
• Ledger Doctor's check-in tells us the name of the computer it runs on, so we can tell your servers apart when you write to us.

0.34.20

November 2026. Check library 0.21.5.

• Once you confirm a company for your partner's migration, its full data goes at the next check-in, within minutes, instead of at the next daily send.
• When your partner installs an update, they're told when it's finished (or if it failed), not only that it started.
• Unposted Sales batches (K02) no longer lists a batch holding only quotes, orders or back orders. GP transfers those to invoices instead of posting them.
• Settings has a new Updates section. Install new versions automatically installs each new version in a window you choose, overnight by default, the same way Install update now does. Let my partner install updates lets your implementation partner tell this server to check for a new version and install it right away. Either way it's only our signed version, checked on your server, and each install is in the job log and the security log.
• Overapplied customer documents (C11) and their vendor counterpart (C09) have a one-click fix for a document showing more remaining than its own amount: it becomes what its applications leave. A document applied for more than its amount still goes to the guide, since which application is wrong is your call.
• The guide for an unposted Payroll batch points to the Payroll menu. For computer checks it lists GP's check run, and it says what to do when GP can't find the payroll tax table.
• Before you start, for posting Sales and Receivables batches, stops a cash receipt that's applied to a document GP doesn't have, and says how to correct it before posting. It also checks the dates of waiting cash receipts.
• Before you start says an inactive account blocks a GL batch (GP stops on it), and that an account closed to entry only needs a look.
• Voided customer document still open (C22) no longer lists a voided receipt with nothing remaining. GP keeps those until Paid Transaction Removal.
• Applications in both the open and history tables (C58) now lists only a copy left behind once both documents are in history. GP keeps both copies on purpose while either document is still open, and the one-click fixes no longer remove them.
• The Payables and Receivables tie-outs count payments and cash receipts that are applied but not posted yet as timing, so posting them no longer looks like a new difference.
• The Health dashboard lists the close work, in order, under Issues to resolve.
• Before you start names a batch GP stopped on errors and says to fix its entries. The posting guide says how to handle an entry that was only ever a test.
• Issues are listed in a recommended order of correction, step by step, and each says what to finish first so one fix doesn't stop another later.
• Before you start: before posting waiting batches or building an adjusting entry, Ledger Doctor checks GP for what would stop it (a closed period or year, batch approval, a batch someone has open, accounts closed to entry) and says where to change it.
• After a restart, Ledger Doctor waits for SQL Server for as long as it takes to start, instead of giving up after a few minutes.
• Unposted payroll batches are read from GP's payroll batch list. The year-end close and the retained earnings account it needs have guides from their own checks.
• When Ledger Doctor can't open a company's database (offline, or restricted to administrators), the scan says so on every check instead of showing the last scan's results.
• Accounts missing from GP's account index have a Check Links guide, and a payroll posting missing from the GL can be marked as expected once it's explained.
• When a guide resolves a record, any other guide still open for the same record closes too. Migration readiness says where to find what it lists from the close checklist.
• Every issue can be cleared. We checked that each check can be cleared the way a customer or their accountant would, and changed the ones that couldn't:
  • AP, AR and inventory tie-outs aren't flagged when unposted GL entries already account for the difference.
  • A failed SQL Agent job clears once it runs successfully.
  • Fixed Assets history rows and books left behind by a deleted asset have one-click fixes.
  • Records that are right as they are can be marked as expected: an out-of-balance posted entry once its correcting entry is posted, assets mid-setup or never depreciated forward, recurring and payroll batches, backups taken by another tool, and SQL Server Agent turned off on purpose.
  • Version rows GP left behind for a deleted company aren't flagged, and a login that can't read SQL Server's job and backup history is reported.
• Book what a tie-out can't explain. When AP, AR or inventory still doesn't tie to the GL after you've worked through what its page explains, an approver can have Ledger Doctor build an adjusting entry for the difference, against an offset account they pick. It's an unposted journal entry in a GP batch: you review it and post it in GP, and Ledger Doctor never posts. It can't be booked twice, and the manual-entries-to-control-accounts check leaves it out. More
• An adjusting entry says up front when a control account doesn't allow account entry, and how to build it anyway. Its offset is one line, so GP's batch total matches. GP's eConnect errors say what they mean.
• A GP user with no SQL login who can't use any company gets a guide to delete them, instead of one asking for a new password.
• A company's pages show only the access that company still needs. Records show the GL account number without its index beside it.
• Beginning balances that can't be compared because the closed year's detail was never kept, and reviewed manual entries to control accounts, can be marked as expected.
• Find a GP partner. Wherever Ledger Doctor says to take something to your GP partner or consultant, it offers to recommend one. Say what you need and how to reach you, and we'll recommend a Dynamics GP partner, consultant or reseller (VAR), separate from the implementation partner introduction for a move off GP. More
• Fewer things left to your GP partner. One-click fixes now cover a batch record with no batch ID, inventory history lines whose header is missing, GL summary rows in the wrong year's table, voided documents still showing an amount remaining, and a batch stuck in Posting where nothing in it posted (it can be posted again without posting anything twice). Each is previewed, backed up and can be undone.
• Applications in both the open and history tables: the fix now removes the right copy. When a document is still open it keeps the open copy, which GP's Receivables and Payables Reconcile use for the amount remaining, and removes the history copy. Neither copy is held back by a closed year, because only an exact duplicate of a copy that stays is removed and no balance changes. Each row shows the application's date.
• A batch stuck in Posting that's empty can be made available again too, and its row says Ledger Doctor can fix it.
• Your SQL Server administrator can turn on fixes for one company: EXEC LedgerDoctor.dbo.usp_grant_access @company = N'TWO'; or usp_grant_amount_fixes @company = N'TWO'. The preview names the company it's for.
• Sales documents in another currency are compared with their lines in that currency, so GP's rounding of each converted line to the cent isn't reported. A sales document whose total doesn't match its lines can be marked as expected.
• Fix previews name the GL account, the item and the documents and amounts involved, and show an amount set to zero as 0.00. Inventory rows name their item and their document type in words.
• A voided document that has nothing left remaining says which GP step moves it to history. A mark on a currency revaluation row lasts past the next period end, and marks that no longer match anything are counted and listed apart, with one button to remove them.
• Migration readiness counts each open invoice, payment or application problem once.
• A voided customer document's next step gives the right place for GP's Paid Transaction Removal (Tools > Routines > Sales) and says to set both cut-off dates past the customer's latest document, payments included.
• The new-company notice and the one-click fixes' access notice can be closed. The access notice names the companies that still need access, gives the line for that company, and goes away by itself once it's given.
• Removing many marks that no longer apply takes one click and one recheck. Fix previews show document numbers as typed and a blank GP date as (none).
• Customer and vendor balance checks say when a card has no summary record yet (run GP's Reconcile once) or when a voided document that's still open explains why GP's Reconcile gets another figure. The sub-penny and amount-remaining fixes point to Ledger Doctor's own one-click balance rebuild.
• Mark every record on an issue as expected at once, with one reason.
• A guide for giving a company access to a currency and its exchange rate table (Multicurrency Access), for a new or copied company.
• Ledger Doctor says when it finds a new GP company on its own. Server-wide checks say which company each row belongs to. Fix previews show each changed value before and after, side by side, with plainer column names.
• Migration readiness doesn't count database code you marked as expected as custom code.
• More of your records for your implementation partner. Once your partner's paid project covers a company, its migration package also has its customers and vendors with their addresses and contacts, employees' names and jobs (never Social Security numbers, birth dates or pay), items, warehouses, and fixed assets with their book values, plus the payment terms and classes they use. Only records used since the date your partner's conversion starts, or created in the last 18 months, are sent. Vendors' tax ID numbers and bank details stay in GP. More
• The migration package's fixed asset classes also carry each class's GL accounts and its depreciation rules on the corporate book (method, averaging convention, useful life and salvage), so your partner can set up matching asset classifications in Sage Intacct.

0.33.2

November 2026. Check library 0.20.2. A data-safety fix.

• Applications in both the open and history tables (C58) now lists only an open copy left behind once both documents are in history. GP keeps both copies on purpose while either document is still open, for example a payment in history applied to an invoice that's partly paid. Its one-click fixes no longer remove those copies, which GP still needs.

0.33.1

October 2026. Check library 0.20.1 (unchanged). Tested as 0.33.0.

• How do I…? Ask how to do something in Ledger Doctor, from the top of any page or the foot of it. The answer comes from the help center only, with links to the pages it used. Only your question is sent, nothing from GP. Every plan has 50 a month, and they don't use up Explain with AI. It needs AI turned on in Settings. More
• Explain with AI on an issue sees up to 30 of its rows (was 15), with the columns by the names the issue page uses (Employee, What's wrong, Same number as), and a check's own "what's wrong" text isn't masked.
• A blockers report's PDF says which scan "Ledger Doctor still finds N records" counts from, as the Migration page does.
• The nightly scan SQL Server Agent runs shows under Background jobs in Settings, like the scans the service runs.
• Turning on adding users to DYNGRP (usp_grant_dyngrp_fix) logs one line for each company in the security log, with its company.

0.32.1

October 2026. Check library 0.20.1. Tested as 0.32.0.

• Payroll year-end and W-2 checks. If you run US Payroll in GP, the Health page's Payroll area finds employees paid this year whose record is missing something their W-2 needs or would be rejected for: a Social Security number that's blank, isn't 9 digits, can't be a real one or is the same as another employee's (usually a rehire under a new ID), a blank name, or a missing or incomplete address. Ledger Doctor never shows the Social Security numbers themselves. It also says when last year had payroll but GP has no year-end wage file for it, which W-2s are printed from. More
• New check: reversing entries whose reversal didn't come back right. A reversing journal entry that posted, but whose reversal is a different amount, leaves an account out, or is filed in a different period from its date, so part of the accrual stays in the GL. Reversing entries still waiting to post past their date are found as before. More
• Rebuild summaries with one click. An approver can rebuild a vendor's or customer's balance from its open documents, and an open year's period summaries from the posted GL detail, to the cent, the way GP's Reconcile does: previewed, backed up and undoable. The GL rebuild changes what the summary trial balance shows, so it can't touch a closed period, needs a second approver once Security is on, and works once your SQL Server administrator has run usp_grant_amount_fixes. Beginning balances, history years and the vendor's and customer's period amounts are still GP's Reconcile. More
• Add users missing from DYNGRP (admins). On that issue's page, a Ledger Doctor admin ticks the GP users to add to the company's DYNGRP role, instead of clearing and reselecting the company in GP's User Access Setup for each one. It asks first, changes nothing else about their security, is recorded in the security log and can be undone. Your SQL Server administrator turns it on once by running usp_grant_dyngrp_fix; Ledger Doctor's own login can't change roles. More
• What's still found after "done". On the Migration page and in its PDF, a problem from your partner that's marked done but that the latest scan still finds says so, like "Ledger Doctor still finds 3 records". Marking problems done and answering your partner's decisions are now in the security log. More
• The tie-out workbook says who prepared it as "Ann Lee (CONTOSO\alee)", like the other workpapers for auditors, instead of the Windows login alone.

0.31.2

October 2026. Check library 0.19.1 (unchanged).

• People by name. Screens show who did something by their display name, not their Windows login: who completed and reviewed close tasks, ticked guide steps, asked for, approved and applied fixes, marked or answered migration items, started a job, and the like. The security log, security settings and "signed in as" still show the login, since that's the record. The access review, close binders, auditor requests and the other Excel workpapers show both, like "Ann Lee (CONTOSO\alee)", since auditors need both.
• The migration package and your partner's list of what's in the way leave out checks about the company database's setup: company access without a database user, users missing from the DYNGRP role, SQL triggers on GP tables, users who own the company database, and database code added or changed in the last 30 days. They're for your IT, not a move.
• Releasing batches held by logged-out users releases only the batches you tick. Before, ticking one of a user's batches released every batch that user held.

0.31.1

October 2026. Check library 0.19.1 (unchanged). Tested as 0.31.0.

• No Windows sign-in names go to your partner. Who marked an item done, confirmed a project or ran the assessment travels as their display name only, never a login like DOMAIN\user, which would name your network. Ledger Doctor also leaves such names out of what it shows from your partner.
• The security log names the company your partner's project covers as you know it, like "Fabrikam, Inc. (TWO)".
• The migration package your partner gets lists only findings about the company's own data, not the server's (SQL Server logins, backups and database code aren't in the way of a move).
• What's in the way of your migration, from your partner. Your implementation partner can send a list of what's holding up your move: problems in GP to fix, each with a link to its issue, its guide or its one-click fix here, and decisions only you can make, with their choices. It shows on the Migration page. Mark fixes done (a processor) and answer the decisions (an approver), and your partner sees it at once; download it as a PDF to email to whoever fixes things in GP. Like everything you share with your partner, it travels encrypted so only your Ledger Doctor and theirs can read it. More
• The migration package your partner gets lists what Ledger Doctor found in the company (each check, how many records and whether it has a guide or a fix), so their list can point to each issue.
• The security log says when your partner's paid project starts covering a company, since that's when its full data starts going to them (and when it stops).

0.30.2

October 2026. Check library 0.19.1. Tested as 0.30.0 and 0.30.1.

• Nothing is ticked for a fix until you tick it. Tick the rows to fix, or choose Tick every row; Untick all clears them. Before, every row the fix could take started ticked.
• Payables documents in the new payments check show their type by name (Invoice), not its number.
• Customer checks entered twice: the financial impact now says cash is overstated and the customer's balance understated, as its guide does.
• Every row of an issue, not just the first 500. When a check finds more than 500 rows, its issue page pages through them, 500 at a time (up to 10,000), and the rows you tick for a fix stay ticked as you move between pages. Tick every row on every page picks them all at once. More
• New check: Payables documents showing payments that aren't applied. An open vendor invoice whose payments recorded on the document don't agree with what's applied to it: payments recorded with nothing applied and its full amount still open, or payments recorded above the document's amount. GP's vendor inquiry shows it as paid while the aging says it isn't, so it could be paid again. More
• A guide for a customer check entered twice: keep one receipt, move anything the extra one paid to it, and void the extra (or delete it if it isn't posted yet). More
• Open fiscal periods in old years are listed in year and period order.
• The AP and AR tie-outs show a document in another currency in that currency too: its original amount and what GP has remaining today.
• Setup's install and Update are recorded in Ledger Doctor's security log, with who ran them and the permissions they gave.
• The Migration page says when the license server no longer lists a company's connection to its partner (usually a changed license key), what to do, and when it ends otherwise.
• The job log says when a send to your partner was at their request.
• Emails look like Ledger Doctor: every email (the daily report, close task emails, notices) comes in Ledger Doctor's colors with a plain-text copy, through Microsoft 365 too.
• A video on every help page, narrated, with captions. Help

0.29.1

October 2026. Check library 0.18.2. Tested as 0.29.0.

• Your implementation partner's project. Once your partner accepts a company's connection, Ledger Doctor sends them a short quoting summary of it: its name, how many GL accounts, vendors and customers it has, its years of GL history, the modules in use and a few account numbers. When they pick your companies for a project, the Migration page shows which ones and exactly what data goes to them; an approver for each company confirms it or sends it back with a note. The full data goes only once they've paid for the project. Both are in the security log. Moving off GP
• The job log says whether a send was the quoting summary or the full package.

0.28.2

October 2026. Check library 0.18.2. Tested as 0.28.0 and 0.28.1.

• Multicurrency checks. If your company has documents or GL entries in other currencies, the Health page has a Multicurrency area: currencies GP can't convert (not set up, the company has no access to them or to a rate table, or no exchange rate for an open document's date or the last period end), Receivables and Payables documents whose multicurrency record is missing or whose amounts don't match their exchange rate, GL lines whose amounts don't match their own rate, balances in other currencies not revalued since the last period end, and realized gains and losses posted away from their currency's accounts. Multicurrency is no longer listed as a module nothing checks. More
• Amount remaining in other currencies. The check for an amount remaining that doesn't match the applications now covers documents in other currencies too, in both their amounts: the one in your company's currency and the one in the document's own currency. An approver can set either with one click, only where the math is certain (the document's multicurrency record is complete, every application is in the same currency with no realized gain or loss, and both amounts agree at the exchange rate). It changes posted amounts, so it needs a second approver and can't touch a closed period. More
• The AR and AP tie-outs list each document's currency. Amounts stay in your company's currency, as GP's aging and the GL hold them.
• The schedules Excel lists the month's entries once they're built too, with their batch and journal entry number.
• Running LedgerDoctor.Service.exe grant is recorded in Ledger Doctor's security log, with the Windows user who ran it.
• Setup refuses a partner license key (one starting LDP-) straight away, before it contacts the license server.

0.27.5

October 2026. Check library 0.17.1. Tested as 0.27.0 to 0.27.4.

• Bank matching (Close plan). Upload a checkbook's bank statement (CSV, OFX or QFX, or BAI2) and Ledger Doctor matches its lines to GP's checkbook transactions that aren't cleared yet: by check number, by amount within a few days, and receipts deposited together. Match the rest by hand, mark a fee or interest as not in GP yet, and the statement is proved to the cent against GP's book balance. The Excel lists exactly what to mark in GP's Reconcile Bank Statements. More
• Prepaid and accrual schedules (Close plan). Spread a prepaid over months, or book an accrual each month end that reverses the next day. Each month an approver builds the entries in GP as one unposted batch, through GP's own eConnect procedures; someone reviews it in GP and posts it. Ledger Doctor never posts. The schedules fill in those accounts' reconciliations. More
• Matching on reconciliations (Close plan). For a clearing, accrual or suspense account, match the GL lines that cancel each other (an entry and its reversal, the same reference in and out); what's left is what the balance is made of, and it can be the reconciliation's supporting balance. More
• The close binder includes each bank statement ending in the month and the schedules.
• The intercompany Excel's difference shows its value in viewers that don't calculate formulas.
• GP access review names GP's Lesson User status (the sample company's LESSONUSER1 and LESSONUSER2) instead of a status number.
• The certificate authority's download answers a HEAD request too, not only GET.
• Running the program with a word it doesn't know (like help) prints what it can do instead of starting a second copy of the service.
• Setup won't take a key that belongs elsewhere: a partner key, a key for a different license than the Ledger Doctor already on the server, or one in use on another server. Uninstalling frees the license for another server. If you've lost your key, get a new one.
• A connection to your implementation partner that the license server stops listing (for example, after the wrong license key was entered) isn't ended right away: Ledger Doctor keeps asking about it for a week and picks it back up as soon as it's listed again.
• If the license server refuses Ledger Doctor's check-in, Check for updates and the log say why, instead of reporting the version you have as the latest.
• A grant command for IT. LedgerDoctor.Service.exe grant, run as an administrator in Ledger Doctor's folder by someone who is a SQL Server sysadmin, gives the service its SQL Server permissions again without running setup. Add --sql-user to sign in to SQL Server with a SQL login instead.

After updating, if you'll build schedule batches, give Ledger Doctor the right to run GP's eConnect procedures that create the unposted entries: run LedgerDoctor.Service.exe grant as above, or run setup again and choose Update, or have a SQL Server admin run EXEC LedgerDoctor.dbo.usp_grant_access;.

0.26.1

October 2026. Check library 0.17.1. Tested as 0.26.0.

• HTTPS. Ledger Doctor can encrypt everything between browsers and the server, on the same port, and the old http:// address sends people to https://. Use a certificate Ledger Doctor makes for the server (it renews itself; each computer trusts it once, or IT sends it out with group policy), a .pfx you upload, or one from the server's certificate store. Admins change it in Settings > HTTPS certificate, and are told 30 days before any other certificate expires. Setup offers it too. More
• New installs use port 47474, a port nothing else uses by default. Existing installs keep theirs.
• Intercompany reconciliation (Close plan). Pair the due to and due from accounts that should net to zero across your GP companies, or between divisions in one company; each period end shows both balances from GP and an approver signs each pair off, with a note when it doesn't tie. More
• Auto-certify low-risk reconciliations (Close plan). An approver sets an amount for an account; in a period when its balance and activity are both within it, the reconciliation certifies itself, as long as a person reconciled it within the last 3 months. More
• GP access review (Controls add-on). Who can do what in GP, from GP's own security: POWERUSER, and duties one person shouldn't hold together in a company, like setting up vendors and paying them. Active users with no roles are listed too. Review everyone each quarter, keep or change with a note, sign it off, and give your auditor the workbook. More
• Auditor requests (Controls add-on). Your auditor's request list in Ledger Doctor: import their spreadsheet, give each request an owner and a due date, answer with files, record what the auditor accepted, and download it all for them in one zip. More
• The Controls add-on and the Full package can be bought from Ledger Doctor: Add Controls on a Controls page, and the trial's buy buttons include Essentials + Controls and the Full package.
• The close binder includes the auditor request lists and intercompany pairs for its period end.
• After an update, pages show the new version straight away, without a hard refresh.
• When your implementation partner asks for fresh data or GP's balances, Ledger Doctor sends them within a few minutes (it checks every 2 minutes, not every 15).

0.25.8

October 2026. Check library 0.17.1. Tested as 0.25.7.

• Connecting to your implementation partner (Migration, beta): the package sent to your partner now includes your fiscal calendar and which GP accounts are bank, retained earnings, receivables and payables accounts, so their migration plan can keep each bank account on its own account in Sage Intacct and convert only the history you choose.
• When your partner chooses the date the conversion starts, Ledger Doctor works out GP's trial balance at the start of that date (balances brought forward plus everything posted before it) and sends it with each package, for their opening balance entry. It's checked first: the balances have to add to zero, and GP's posted entries have to match its period totals. The job log says when a package carried it. It starts from the first year GP's fiscal period setup marks as open, so a closed year still in GP's open-year tables isn't counted again; unit accounts send their quantities on their own, not as money; and when GP's setup has no retained earnings account, the earlier years' net income comes as its own amount for your partner to place. When a check fails, it names the account periods to look at.

0.25.6

October 2026. Check library 0.17.1. Tested as 0.25.4 and 0.25.5.

• Connecting to your implementation partner (Migration, beta): the last sent time is in your server's time, each package sent is in the job log, connecting and ending are in the security log, and ending a connection asks first. The partner code box hides while a connection is waiting or connected. When myledgerdoctor.com turns a request down (a partner code that doesn't exist, say), the page gives its reason.

0.25.3

October 2026. Check library 0.17.1.

• Connect to your implementation partner (Migration, beta). If your partner uses the Ledger Doctor partner application, an approver enters their partner code on the Migration page. Once the partner accepts, Ledger Doctor sends them this company's migration assessment, chart of accounts, GL summary balances, customers and vendors, encrypted so only that partner can read them. Either side can end it. More

0.25.2

October 2026. Check library 0.17.1. Tested as 0.25.0 and 0.25.1.

• Journal entry review (Controls add-on). Every manual journal entry posted in the dates you pick, riskiest first: large or round amounts, posted late, on a weekend or out of hours, entered and posted by one person, to an account nobody used all year, by someone who rarely posts, or straight to a cash or control account. Approvers mark each one reviewed, with a note, and it downloads to Excel for your auditor. More
• Payables fraud signals (Controls add-on). Possible duplicate vendor invoices, and payments to vendors created, or whose bank details or remit-to address changed, within 30 days before. More
• Files on close tasks. Attach the support for a close task; the files go into the close binder. More
• The journal entry review picks entries by the date they were posted or the date they're dated, flags entries dated well after they were posted, and says how many entries have a usable posting time. Payables fraud signals leave out change times that most rows share or that are in the future, and say so.
• An entry's amount, in the journal entry review and the large, round, late, weekend and same-person checks, leaves out unit (statistical) accounts, whose amounts are quantities, not money.
• The close binder's checklist names each task's files, and its README lists the files in order.
• Notes on fix requests. Whoever asks for a fix can say why, and why again after a turn-down; an approver can say why they turned it down, still in one click. Needs approval, the issue page and Fix history show them.

0.24.3

October 2026. Check library 0.17.0. Tested as 0.24.0, 0.24.1 and 0.24.2.

• Inventory ties to the GL. A new check compares the value of what's on hand (each receipt's remaining quantity at its cost) with the GL balance of each inventory account, with unposted GL shown separately. My work gets an Inventory tile when the company has Inventory.
• Payroll's first checks. Payroll postings in the last 13 months that didn't reach the GL in full, and unposted Payroll batches, which also verify a new "Post payroll batches" step on the close checklist. The Health page gets a Payroll area.
• Amount remaining that doesn't match the applications. A new check finds open customer and vendor documents whose amount remaining isn't what their applications leave, and an approver can set it with one click, only where that's certain. It changes posted amounts, so it needs a second approver and can't touch a closed period. More
• More one-click fixes: remove the open copy of an application that's also in history, remove customer applications that point to a document that no longer exists, and close old fiscal periods you pick.
• Fixed assets tie only the book that posts to the GL. A tax book that posts nowhere is no longer a finding.
• Issue pages list up to the first 500 records a check finds (was 50), so a fix for records further down the list, like the Payables half of "Applications in both the open and history tables", can be picked. A fix that closes old periods shows each period's series and window in its preview.
• Tie-outs pair more. One payment applied to several invoices (or several to one) whose differences cancel together is shown as one group that needs no action, and an invoice and a credit that look like they reverse each other are shown together for you to confirm. More
• A tie-out as of today, when some documents' history doesn't add up, lists those documents on their own sheet, each with the reconciling items it's under, or why it needs none.
• Viewers no longer see Apply fix, Rescan now, or an editable reconciliation form. A fix preview that can't count its records while someone is logged in to GP says so.

0.23.3

October 2026. Tested as 0.23.0, 0.23.1 and 0.23.2.

• Assign close tasks to people, by name. The Assignee box on close tasks and close steps is now a list of the people who can complete tasks in that company: Processors and Approvers, with their names from Active Directory. More
• Close task emails. People hear when a task is assigned to them, get a 7:00 AM weekday email of their tasks due soon and overdue, and approvers hear when a close is complete. Each can be turned off in My preferences, where anyone can also give the address to use.
• Your name at the top right is your name from Active Directory.
• The help icon on My work, My preferences and Needs approval opens the part of the help about that page.
• A better balanced My work. Full-width sections, most urgent first: what's waiting on you, whether the subledgers match the GL, then the findings in a grid. Fixed assets (by book) and the bank (checkbooks behind on reconciliation) join receivables and payables when the company has them. More
• The Health page and My work name any GP module the company uses that Ledger Doctor doesn't check yet, such as Payroll.
• Undo, said plainly. Before you apply a fix, the confirmation says what undo can do: for fixes that change posted amounts, a highlighted note that once the period is closed it can't be undone. More
• Needs approval shows its count, 0 included.
• The security log names a changed setting the way the Settings page does, with who made the change by name. When you run setup again, it shows the email setup you have (mail server with its port, or Microsoft 365) instead of an empty Microsoft 365 form, and its review says whether an update keeps the SQL login's password.
• The Close page opens the close that's still being worked (the earliest one not complete), or the one a link names.

0.22.1

October 2026. Tested as 0.22.0.

• My work. A new start page for everyone who isn't a GP expert: your close tasks, what the last scan found in plain words with what to do about each, and whether receivables and payables match the GL. More
• Plain words or everything. Each issue now starts with what's wrong and what to do. GP's table and field names, and check and fix numbers, are under "Details for your GP admin". Anyone who wants it all chooses Everything in My preferences, and issues open with the details already shown. More
• Choose the page Ledger Doctor opens on: My work, Health, Close, or Needs approval.
• A close task can be unassigned again, and changes to Settings are kept in the security log with who made them.
• A tidier menu: My work and Needs approval first, then Health (with Fix history) and Month-end (the close checklist, Flux and Reconciliations). Help, Settings and Security are small icons at the top right, your name opens My preferences (where light or dark now lives), and Report a bug and Request a feature are at the bottom of every page.
• The close binder says who reviewed each task, and lists anything done alone under the small-team rule. Reopening a reviewed task clears its review.
• Open documents with no GL distributions is now two checks, one in Payables (C71) and one in Receivables (C72), so each shows in its own area instead of an "AP/AR" tile of its own. Check library 0.16.2.

0.21.1

October 2026. Tested as 0.21.0.

• Security. A new Security page, for Ledger Doctor admins, gives four roles (Viewer, Processor, Approver and Admin) to Windows groups or people, for one GP company or all of them. Once an admin turns Security on, only people with a role can use Ledger Doctor, and each sees only their companies. Until then, everything works as before. The roles
• Approval rules. Whoever completed a close task or prepared a reconciliation can't review it, and fixes that change posted amounts need two approvers. A small team can let one approver do both, and each time is logged.
• Needs approval. Processors can ask an approver to apply a fix. Approvers see what waits on them (fix requests, second approvals and close tasks to review) in one place, and Fix history names everyone involved.
• Close tasks can be reviewed, and the checklist shows who reviewed each one.
• Viewers see what they can read, without the buttons for work they can't do, and Settings and Security say they're for admins.
• Share my assessment: after you share, the agree box clears, so a second click doesn't send it again. Your downloaded copy shows its divider lines.

0.20.1

October 2026. Tested as 0.20.0.

• Your options. The Migration page ends with three paths, each marked Recommended, Possible or Not yet with the reason from your results: Essentials, Close, or migrating.
• Share my assessment. An approver can share a summary of the assessment with Ledger Doctor for an introduction to an implementation partner: counts, modules, the integrations Ledger Doctor found, the grade, and anything you add. No names, account numbers or amounts. You see exactly what's sent before anything is, and keep a copy. More
• The Migration page lists integrations Ledger Doctor can see: SQL logins that post GL entries without being GP users, and SQL Agent jobs that run in the company. It also counts open receivables and payables documents.

0.19.2

October 2026. Tested as 0.19.0 and 0.19.1.

• When a new version is out but not downloaded yet, an approver can download it from the dashboard's update notice and install it with one click, instead of waiting for the daily update check.
• Migration readiness (beta). A new Migration page grades how clean a company's data is to move off GP (A to F, across the chart of accounts, GL history, open receivables and payables, customers, vendors and items, and bank balances) and how big a move it would be (low, medium or high). It shows the chart's segments and the natural accounts left once segments become dimensions, values buried in account names, unused accounts, which GL years are clean (and, for any that aren't, which accounts and by how much), what each area found, the modules in use and the products registered with GP. It only reads GP. An approver turns it on in Settings. How it's scored

0.18.1

October 2026. Tested as 0.18.0.

• Ledger Doctor's database code is protected. Its procedures, functions and views are installed encrypted, and its one-click fixes run only while they, and the fix rules, are exactly what setup installed. If anything was changed in SQL Server Management Studio, the fix panel says what, and fixes stay off until setup runs again. The download no longer includes the SQL scripts; your DBA can ask us for them.
• Backup ages you can set. Settings has a Backups section for how old a full backup can be before the Server area warns you (26 hours, 7 days and 30 days unless you change them).
• Three new security checks. Logins with full control of SQL Server (S13), users who own a company database (C69), and stored procedures, views, functions or triggers added or changed in the last 30 days, outside a GP or add-on install (C70). Each can be marked as expected.
• Fewer trips to your SQL Server administrator. Setup now gives Ledger Doctor's login, up front, the access to GP's housekeeping tables (batch headers, and user, batch and resource activity) that one-click fixes on them need, so a later update's fixes on those tables work as soon as it's installed. When a fix still needs more, the Health page says which, with the one line to run and a message to send. Run setup again (or EXEC LedgerDoctor.dbo.usp_grant_access;) once after this update.
• SQL triggers on GP tables (C66) now recognizes the triggers GP installs itself by name, so it lists only triggers added afterward, by an add-on, an integration or a person.
• Open documents with no GL distributions (C71). Posted Payables and Receivables documents that are still open but have no distribution lines left in GP, so GP can't show what they posted. Check library 0.16.1.

0.17.4

October 2026. Tested as 0.17.3.

• Two new one-click fixes for batches GP itself can't clear. A stuck batch that's only marked for posting, or shows Receiving and hasn't changed today, can be made available again (C04): nothing posts, and a batch that may have started posting is still left to Batch Recovery. An empty single-use batch whose header claims transactions can be removed (C54). Both wait until nobody is logged in to the company, and both can be undone. Until your SQL Server administrator runs Ledger Doctor's setup again (or EXEC LedgerDoctor.dbo.usp_grant_access;), their preview says which access they still need.
• Three new checks. SQL triggers on GP tables that GP didn't create (C66), accounts missing from GP's account index, which lookups and integrations use to find an account by number (C67), and companies or add-ons left on an older version, or with an upgrade that didn't finish (C68). Check library 0.15.4.
• Report a bug and Request a feature change color when you point at them, like Help on this page.

0.17.2

October 2026. Tested as 0.17.0 and 0.17.1.

• Thirteen new checks, each for a problem found in a real GP company that no check caught before:
  • batches that claim transactions they don't have, including Inventory transaction and transfer batches (C54), documents in batches that don't exist (C55), a batch record with no batch ID (C62) and unposted Inventory batches (K13, also a month-end close step)
  • payments and credits applied for more than their amount, including cash receipts that aren't posted yet (C56), customer checks entered twice (C57) and applications in both GP's open and history tables (C58)
  • setup that points to GL accounts that don't exist, on classes as well as on customers, vendors and items (C59), inactive accounts still used as defaults (C60) and customer or vendor balances with a fraction of a cent (C61)
  • GL summary rows with negative totals, one line per year (C63), unposted journal entries with no lines (C64) and posted sales documents whose total doesn't match their lines (C65)
• Where GP has a procedure for it, the new findings come with a guide, written for GP 18.5's windows. Check library 0.15.2.
• Batch statuses use GP's names (status 3 is Receiving). Fix previews leave out GP's row ID and show note indexes as whole numbers. Fix history labels each guide's record. The Reconciliations page offers only the tie-outs for modules you have.
• Bank reconciliation tie-out: general journal entries to each cash account are listed, and the summary shows the GL difference left once they're taken out. (Close plan.)
• Dark theme. Pick light, dark or the same as Windows from the Theme list at the top of every page. It's just for you, and follows you to any computer.
• Help center: every guide is listed with the checks it's for, generated from the guide library itself, and the pages on fixes, issues, messages, reconciling items and the close binder cover what changed in 0.16.2.

0.16.2

October 2026

• One-click fixes check before they start. A fix isn't applied unless Ledger Doctor's SQL login could also undo it. If it couldn't, the preview names the permission that's missing and the procedure your SQL Server administrator runs to give it. A fix that waits until nobody is logged in to the company names who GP shows as logged in. F05 now waits for that too.
• Apply and Undo ask before they change anything. Two clicks, or two people at once, apply or undo a fix only once. Fix history names each fix and what to do next in GP.
• Fix previews leave out GP's setup passwords, and show how many lines go with each document a fix removes.
• When something goes wrong, the message says where the details are: a log file on the server (C:\ProgramData\Ledger Doctor\Logs\service.log), with a reference to find it.
• Issue pages show GP's columns and codes in plain words (Batch, Document type: Payment), amounts with separators and no extra zeros, and say how many records are shown only when there are more.
• Guides fit the record: Unapply only where something is applied, Void a payment only for a payment, and new guides for a user GP no longer lists (C42, C43) and for a batch whose header claims transactions it doesn't have (K01 to K03). Guides that post (C04, K01 to K03, K07) ask for an approver's sign-off.
• The AR and AP tie-outs count a document left in both GP's open and history tables once, and say how many there are.
• C40 shows each inactive account's balance for the current fiscal year, not the last year set up.
• The close binder lists fixes to GP's shared records (users, batch activity, locks) too, and its README lists only the tie-outs and files it contains.
• A scan you start is recorded under your name.
• The flux page lets you pick any period end. Tie-out reconciling items show each document's date, and documents applied to each other whose differences cancel are shown as one pair.
• The General Ledger year-end close also waits for payroll year-end, and the year-end steps' due dates follow their order: the checks first, then the subledger closes, then the General Ledger close.
• The close checklist fits a narrow window: the note box, Mark complete and Edit stack inside their column. A refused Mark complete says why beside the step.
• The checklist list and the close binder show who started each checklist, and the binder names each close-step guide and its period.
• Fixed: the bank tie-out could store "-0" in detail cells and tiny rounding noise in checkbook totals.
• The reconciling item for documents still open on the as-of date because a later-dated payment cleared them is now called "Paid or applied by documents dated after the as-of date".
• Check Links paths start with "Microsoft Dynamics GP >" too. Check library 0.14.2.

0.16.1

October 2026

• Year-end closes verified from GP. The Payables and Receivables year-end steps complete themselves once GP records the close (its Last Closing Date), and payroll once the year-end wage file exists. Inventory keeps no date in GP, so that step stays one you mark complete.
• The General Ledger year-end guide names the year GP will close. Year-End Closing always closes the oldest open year, so if earlier years are still open, the guide says to close them first.
• Year-end steps follow the order on the guided year-end page, and a step can't be marked complete before the step it waits for unless you add a note saying why. The General Ledger close waits for the backup and every other close.
• Approvers can delete a close checklist; Ledger Doctor keeps a record of who deleted which one. A completed step still links to its guide, and the checklist records who started it.
• Check C53 says when the closed year has no history to compare, instead of finding nothing.
• Emails from Ledger Doctor: a welcome when a trial starts or you buy, and a reminder a week before a trial ends. They never include your license key.
• Every GP menu path in Ledger Doctor starts with "Microsoft Dynamics GP >", as GP's menus do.
• Fixed: guides on the close checklist showed today as their period end; the Mark complete buttons could run off the edge of the page.
• Check library 0.14.1.

0.16.0

October 2026

• Guided year-end close. The year-end checklist's closes (payroll and W-2s, Inventory, Receivables, 1099s and Payables, Fixed Assets, and the General Ledger last) each have a guide with GP's exact steps, a backup first, and a sign-off before the GL close. Guided year-end close.
• New checks before the closes: next year's fiscal periods aren't set up (K10), and no usable retained earnings account (K12). After: last year still isn't closed in the GL months later (K11).
• Beginning balances proved: after the GL year-end close, check C53 confirms every balance sheet account starts the new year where it ended, only the net income moved into retained earnings, and every profit and loss account starts at zero.
• The download page no longer asks for a license key, so you can download before starting a free trial. Setup still asks for one.
• The heartbeat now includes the version numbers of SQL Server, the Windows server it runs on and GP, so we can see what our checks run against. Version numbers only; see privacy.
• Every guide's menu paths and window names were checked in GP 18.5. If what you see in your version of GP is different, Report a bug: the report now includes your GP version, so we can tell a version difference from a mistake.
• Sales order deposits: an invoice's GL difference and the deposit applied to it now show as one reconciling item that cancels, instead of two items that each seem to need work.
• Fixed: the bank tie-out could still show "-0"; the close binder numbered two files 5; the updater removed its downloaded copy of the version it had just installed.
• Check library 0.14.0.

0.15.0

October 2026

• Guides for problems you resolve in GP yourself: unapply and reapply, void a payment, a correcting journal entry, closing old periods (or reopening one to post), Reconcile, Check Links, old bank items and bank reconciliations, depreciation, user access, unposted and stuck batches, and the AP and AR reconciling items. Each guide uses the real documents and amounts, checks posting dates against GP's periods, needs an approver's sign-off before anything posts, and ends with Check my work. How guides work.
• When more than one guide fits, AI can pick the best ones for that record and say why. It only picks: the steps are Ledger Doctor's own, tested in GP. Essentials includes 25 a month.
• Guides followed are on the Fix history page and in the close binder, with every step ticked or unticked.
• Backup checks say "never" for a database that's never been backed up. The dashboard tiles say how many checks found something.
• Fixed: a tie-out summary could show a zero difference as "-0".
• Check library 0.13.1.

0.14.0

October 2026

• More problems GP leaves behind are fixed in one click:
  • sales next numbers already in use
  • sales lines and purchase order lines with no document
  • unposted copies of sales documents and receipts that are already posted, with their lines
  • paid documents in both open and history
  • sub-penny open amounts
  The last two change posted data, so they're refused in closed periods and years and need your SQL Server administrator to allow them once. The fixes and their rules.
• A check that looks at two tables has a fix for each, and a fix that changes a value shows the new value in its preview.
• Where GP has its own tool for a problem (Batch Recovery, Check Links, Reconcile, Paid Transaction Removal, Fixed Assets Reconcile, User Access Setup), the check says which one and where to find it.
• Fixed: undoing a fix works for the Ledger Doctor SQL login. Before, putting rows back needed more access than it has.
• Backup checks overlap: no full backup in a day, in 7 days, and in 30 days (or ever). A database 45 days behind now shows in all three instead of leaving two of them looking healthy. Each lists how many days old the last backup is.
• A check that found nothing says "Nothing found" instead of a green Healthy. Green is for an area where every check found nothing.
• Explain with AI is more careful: it's told what detail it was given and doesn't claim something didn't happen when that detail wasn't sent, quotes journal ranges only as computed, recommends a backup only before a routine that changes data, and an answer that would be cut off is never shown or counted. The close summary names the steps that are done and covers every check still finding something.
• Fixed: the bank tie-out could be refused when two checkbooks share a cash account.
• Fixed: in the AR tie-out, a credit memo brought in at go-live and applied during the year with a write-off moved the opening line and showed under "GL amount differs".
• Fixed: weekend journal entries (C49) missed manual entries; old periods still open (K06) counted each series separately; empty batches counted as unposted.
• Reconciliations explain an open period as of today. "Use as the explanation" asks before replacing what you wrote. A dismissed "Update installed" note stays dismissed in every browser, and the update's leftover folders are removed.
• Check library 0.13.0.

0.13.0

October 2026

• Explain with AI (Close plan). One click on a flux variance, the AP or AR tie-out's reconciling items, a check's findings or a close checklist writes a short, plain-English explanation and what to check in GP. On the Flux page, Use as the explanation copies it in to edit. It's off until an approver turns it on in Settings. Vendor, customer, employee and user names and free text are replaced with codes on your server before anything is sent, and every amount in an answer has to match your data or it isn't shown. Explanations are kept, so opening one again doesn't use another. The Close plan includes 200 a month, a free trial 25. What's sent.
• Pick how the Health page's tiles look: tinted tiles, solid badges, or an icon with a check meter. Each person's choice follows them to any computer.
• The Ledger Doctor logo in the app, and Help on this page on every page, which opens that page's help article.
• Report a bug and Request a feature on every page send a short note straight to Ledger Doctor support. What's sent.
• After a one-click update, the dashboard shows the result within a minute instead of the next day. "Update installed" shows for a day and can be dismissed; a failed update stays for three days.

0.12.0

October 2026

• Two plans, and a 45-day free trial. Essentials covers the checks, fixes, tie-outs, close checklist and daily email. Close adds account reconciliations, flux analysis, the bank reconciliation tie-out, and Teams and Slack. Close features are labeled in the app. On Essentials, their pages explain what they do and offer Upgrade to Close, which Stripe prorates for the rest of your term. A free trial gives you the full Close plan for 45 days, with a banner showing the days left and how to buy. If the trial ends, Ledger Doctor turns view only: you can still open your checklists, reconciliations and past results, and buying turns everything back on with the same license key. Licenses bought before the plans existed keep every feature.
• Only approvers can reopen a reviewed reconciliation, the same as reviewing one.
• License problems are explained in plain English (canceled, expired, a payment that didn't go through, or a key that isn't recognized), with what to do next.
• The close checklist's bank reconciliation step offers the bank tie-out, and the close binder's notes list everything in it.
• The backup checks' titles say their age ranges: 1 to 7 days, 7 to 30 days, and over 30 days or never.
• The status-sharing setting uses the same wording in setup and on the Settings page.
• Fixed:
  • The bank reconciliation tie-out works when two checkbooks share one GL cash account.
  • On the AR and AP tie-outs, a go-live document counts in the beginning balance even when a later application posted to the control account.
  • Reconciling items that net to zero show 0.00 instead of a tiny rounding remainder.
  • The risky journal entry checks leave out entries dated in the future and postings from add-on products such as Depot Management.
  • "Old bank items still not cleared" flags a check stored with a negative amount whatever its age.
• Check library 0.12.2.

0.11.0

October 2026

• Install updates with one click. When a new version has downloaded, an approver sees Install update now on the dashboard. Ledger Doctor checks the update's signature and then installs it on the server by itself, keeping your settings, history and close checklists. If the new version doesn't start properly, the old one is put back. Updates are signed by Geekery, and anything without a valid signature is never installed. Adding GP companies, changing the port or changing email settings still means running setup and choosing Update.
• Bank reconciliation tie-out. For each checkbook, Ledger Doctor proves its last reconciliation again from the checkbook transactions: the statement balance plus deposits in transit, less outstanding payments, has to equal the book balance. It then compares each checkbook's balance as of the date with its GL cash account. When GP has no saved reconciliation history, it uses the checkbook's own last reconciled date and balance. A check stored as a negative amount counts the way it really affects the balance.
• New checks for risky journal entries: large manual entries, round amounts, entries posted to an earlier period, weekend posting, entries entered and posted by the same person, new accounts already in use, and reversing entries past their reversing date. A new close check flags recurring batches that haven't posted for the period. You can mark any of them as expected once you've reviewed them.
• Fixes that change amounts are blocked in closed periods. No current fix changes amounts. This guard is in place first, so a future fix like that can't post into a closed period or a closed year. The preview names the periods to reopen in GP, and to close again afterward so balances roll forward.
• Clearer reconciling items on AP and AR tie-outs.
  • Documents brought in at go-live with no GL entries of their own now count in the beginning balance instead of showing as "never posted".
  • Payments and credits dated after the as-of date that are already applied have their own line.
  • An application GP keeps in both its open and history tables is counted once.
• Fixed:
  • "Paid payables documents still open" no longer flags invoices paid by checks that are entered but not posted yet.
  • "Old bank items still not cleared" shows each item's real effect on the balance, and calls out items stored with a negative amount.
  • The unposted-batch close checks now read GP's recurring-batch setting correctly.
• Tie-out downloads are on the Reconciliations page too. Workbooks are saved with their calculated values, so tools other than Excel show the numbers.
• Setup closes itself a few minutes after it finishes.
• Check library 0.12.0.

0.10.8

October 2026

• AP and AR tie-outs explain their difference. The reconciling items sheet breaks the difference into items that add up to the cent, each named down to the document or journal entry:
  • the opening balance difference
  • journal entries posted straight to the control account
  • GL entries with no document behind them
  • documents never posted to the GL
  • discounts available posted to a separate account
  • voids that didn't post
  • documents whose GL amount differs
  • payments applied before they were posted
  • documents closed with no application record
  GL entries are matched to their documents through the document number GP stamps on them, including Purchasing receipts through their vouchers.
• Tie-outs as of today always come out. When GP's application history doesn't add up to what GP shows open, a tie-out as of today uses GP's open balances and lists those documents as reconciling items, instead of refusing. A tie-out as of an earlier date still needs the history to add up.
• Fixed Assets tie-outs as of an earlier date. They're rebuilt from the Fixed Assets financial detail by GL posting date, after checking that the detail reproduces today's balances.
• Reconciliations that prepare themselves. Open AP, AR and Fixed Assets reconciliations fill in their supporting balance from the subledger as of the period end, and are marked prepared when they tie.

0.10.7

October 2026

• Fixed: in 0.10.6, every item in Issues to resolve on the health dashboard was labeled Warning, even errors. They're labeled Error, Attention or Warning again. The area tiles and the daily email weren't affected.

0.10.6

October 2026

• Backup alerts by age. A GP database's last full backup turns the Server and backups area yellow after a day, orange after a week, and red after 30 days or if it's never been backed up. Each has two hours' grace, so a nightly backup that runs a little late doesn't set it off. Orange ("Attention") is a new level between a warning and an error.
• Workgroup servers. On a server that isn't on a Windows domain, setup now opens Ledger Doctor's port on private networks as well as the domain network (never public ones), so other computers can reach it.
• The server checks now work when GP's databases use a different collation from SQL Server's, which is common on older GP installs.
• Check library 0.11.2.

0.10.5

October 2026

• Downloaded updates tidy up after themselves. The folder keeps a copy of the version you're running, for an uninstall or reinstall, and the newest version waiting to be installed. Older copies, versions replaced before anyone installed them, and downloads that didn't finish are deleted at the next check for updates.

0.10.4

October 2026

• Click an area to see every check in it. Each tile on the health dashboard opens a list of all the checks in that area: what each one looks for, and whether it's clear, found something (with how many), has records marked as expected, couldn't run, or doesn't apply. Each links to its details.
• The health dashboard shows which version of Ledger Doctor is running, next to the check library version.
• It's also the first version that servers on 0.10.3 download by themselves: the update notice names the downloaded file to double-click on the server.

0.10.3

October 2026

• Mark as expected. Some findings are correct as they are: deferred revenue set to Balance Sheet under an income category, a control account that's allowed journal entries on purpose, an old bank item you're still waiting on. An approver can now mark that record as expected, with a reason. It stops counting as a problem and moves to a "Marked as expected" list on the finding, until the data in it changes, and then it's flagged again. Marks are listed in the close binder with who made them and why. Checks whose findings always need fixing, such as out-of-balance entries, AP or AR not tying, and backups, can't be marked.
• Check for updates now says both whether a new version of Ledger Doctor is out and whether the checks are current, and the buttons on Settings can't start the same job twice.
• Updates download themselves. When a new version is out, Ledger Doctor downloads it to the server, checks it against the fingerprint we publish, and the notice says exactly which file to double-click there to update. No more going back to the download page or typing the license key. (This starts once a server has 0.10.3: setup's Update creates the locked folder the downloads go in.)
• Check library 0.11.1.

0.10.2

October 2026

• Fewer false alarms. We ran every check against Microsoft's Fabrikam sample company on GP 18.5 and fixed the five that flagged normal data: customer applications from receipts that aren't posted yet, inventory receipts and sales (which never have a header), history years in the trial balance check, accounts deliberately set up differently from their category (now a warning to review rather than an error), and vendor balances already reported as missing vendors.
• New check: GL summary rows filed under the wrong year table (a history year in the open-year table, or the other way round), which makes the summary trial balance show the wrong amounts.
• Status sharing is on by default for new installs. Setup asks, with the box already ticked, and you can turn it off at any time in Settings. It still never includes amounts, account numbers, names or transactions; it now also says which checks found something, so support can tell a backup problem from a data problem.

0.10.1

October 2026

• Setup fix. Setup could stop at "Write the settings file" with "No mapping between account names and security IDs" when the service signs in to SQL Server with its own SQL login. Setup now installs the Windows service before writing the settings file, so it can lock that file to the service's account.
• The settings file is locked to administrators and the service before anything is written into it. If an earlier setup left it readable by other users, running setup again gives the Ledger Doctor SQL login a new password.
• Re-running setup never replaces a newer check library with the older one it carries.
• Setup lists each database it gave Ledger Doctor access to, and its error messages show full file paths.

0.10.0

October 2026

• Account reconciliations. A new Reconciliations page for every balance sheet account due each period: GL balance, supporting balance, reconciling items that carry forward, notes and attached files. One person prepares it when it ties to the cent and an approver who isn't the preparer reviews it. Zero balances and unchanged accounts are signed off automatically, with the reason. If GP's balance changes after sign-off, it's flagged to do again.
• Flux analysis. A new Flux page compares every account with the previous period, the same period last year or a GP budget, and flags changes over your thresholds. Each flagged account shows what moved by vendor or customer and a drafted explanation to edit. Approvers sign off the review. Excel download included.
• Close binder. One zip per close with the checklist and who completed what, the tie-outs as of the period end, the reconciliations and their files, the flux review, the check results and the fixes applied.
• A smarter close checklist. Steps can wait for other steps. The variance review, balance sheet reconciliations and bank reconciliation steps complete themselves when the work is done. A new card shows how each close went: days to close, late tasks, and the steps that are late most often.
• Daily email, Teams and Slack. The daily summary lists overdue close tasks and any AP or AR tie-out whose difference changed since the last scan, and can post to a Teams or Slack channel too.
• AP and AR tie checks keep their history, so you can see the day a difference appeared.

0.9.2

October 2026

• Email through Microsoft 365. Microsoft is turning off password sign-in for SMTP in Microsoft 365, so the daily email can now be sent through Microsoft 365 with an app registration instead. Setup has a Microsoft 365 option, and the install guide shows the one-time setup for your Microsoft 365 administrator. Other mail servers still work as before.
• Send a test email from the Settings page, which also shows how email is set up. When email can't be sent, Ledger Doctor says why in plain words: a wrong or expired secret, a missing permission, a mail server it can't reach, or no email set up yet.
• Running setup again as an update shows the current email setup and keeps it unless you change it.

0.9.1

October 2026

• Update notices. When a new version is available, everyone who uses Ledger Doctor sees it at the top of the dashboard, with a link to these notes, the name of the server that needs the update, and a ready-to-send message for your IT administrator or GP consultant. The daily email report mentions it too.
• Updates marked important (security or data-safety fixes) stay on screen until they're installed.

0.9.0

October 2026

• Setup wizard. Install, update or uninstall by double-clicking LedgerDoctor.Service.exe. Setup finds every GP company, creates Ledger Doctor's own SQL login with a random password, installs the Windows service and runs the first scan. No scripts or settings files to edit.
• Excel tie-outs as of the period end. One-click workbooks for Payables, Receivables, Fixed Assets and the trial balance, or all of them in one file, from the issue pages and the close checklist. Payables and Receivables are rebuilt as of the period end from GP's history, so a September tie-out run in October still shows September.
• Close steps that carry forward. Each company keeps its own close steps from month to month, with extra steps at quarter end and year end. Add your own steps, turn off ones you don't use, and steps for modules you don't have are left out.
• Rescan or recheck one line. Rescan a whole company from the close page, or recheck a single issue or checklist task in seconds after you fix it.
• Four new checks: posting type vs account category, control accounts open to journal entries, inactive accounts that still have a balance, and old periods left open.

Initial release

October 2026. What Ledger Doctor did before 0.9.0.

• Health checks. Read-only checks across System, GL, AP, AR, SOP, POP, IV and FA that find damaged or stuck GP data, each explained in plain English with the records involved, and safe fixes that back up what they change and can be undone.
• Server checks. Databases, full and log backups, CHECKDB, disk space and SQL Agent on the GP SQL Server.
• The service and its web pages. A Windows service on your own server that scans every GP company on a schedule, with a dashboard in the browser. Your GP data stays on your server.
• Setup wizard. Install, update or uninstall by double-clicking LedgerDoctor.Service.exe.
• Close steps. A month-end checklist per company, with steps tied to checks that complete themselves when the check is clear.
• Excel tie-outs. One-click workbooks for Payables, Receivables, Fixed Assets and the trial balance, including as of a past date.
• Licensing, downloads and updates. A license key checked at setup, downloads with your key at api.myledgerdoctor.com, and a daily check for new versions and check libraries, each signed by us and checked before it's used. Licenses are issued and changed only from our admin portal, behind two-step sign-in.
• Plans and free licenses. Buying online, coupons, and free licenses with an end date.
• This website. myledgerdoctor.com, with the install guide and these release notes.