Messages and what to do about them
When Ledger Doctor won't do something, it says why. These are the ones you're most likely to see.
Fixes
| Message | What to do |
|---|---|
| Rows changed since preview (… now, … shown). Nothing was changed; scan again. | Something in GP changed after the preview, like a user logging back in. Choose Recheck, then preview again. |
| None of the selected records can be fixed automatically. | They don't meet the fix's rule, so they need a person to look at them in GP. |
| Only approvers can apply fixes. | Ask an approver. See who can do what. |
| Some of these records are dated in closed periods (…). | Reopen those periods in GP, apply the fix, close them again. See Fixes and closed periods. |
| Nothing was changed: Ledger Doctor's SQL login doesn't have the access this fix and its undo need (…). | Ask your SQL Server administrator to run the procedure the message names, EXEC LedgerDoctor.dbo.usp_grant_access; or, for fixes that change posted data, EXEC LedgerDoctor.dbo.usp_grant_amount_fixes;, in SQL Server Management Studio as a sysadmin. Running setup again also does the first. See Preview, apply and undo a fix. |
| Nothing was changed: this fix waits until nobody is logged in to this company in GP, and GP shows … logged in. | Ask them to log out of GP and try again. If GP shows someone who isn't really working, check C03 (users stuck as logged in) and clear them with its fix first. |
| That fix was already undone. | Nothing to do: the rows are already back. You see this if Undo was clicked twice, or by two people at once. |
| None of this check's guides fits this record. | The record's situation isn't one a guide covers. Ask your GP partner, with the record from the issue page. |
Close checklist
| Message | What to do |
|---|---|
| This task's check still finds problems. Add a note explaining why it can be completed anyway. | Fix it in GP and Recheck, or type a note and choose Mark complete again. |
| There's already a checklist for that period end. | Open the existing one from the Checklists list. |
| Only approvers can add a step to future closes. Add it to this month only, or ask an approver. | Set Repeat to This close only, or ask an approver. |
| That would make the steps wait for each other in a circle. | Pick a different step to wait for. |
| This task is complete, so it stays on the checklist as the record. | Completed tasks can't be removed. |
Reconciliations and flux
| Message | What to do |
|---|---|
| It doesn't tie: … is unexplained. Add reconciling items or correct the supporting balance. | A reconciliation can be prepared only at a 0.00 difference. |
| Someone other than the preparer has to review it. | Ask another approver to review it. |
| Enter the supporting balance to the cent (two decimals). | Type the amount with cents, like 12500.00. |
| … flagged account(s) still need an explanation before the flux can be signed off. | Explain each flagged account first. |
| That date isn't in any fiscal period in GP's Fiscal Periods Setup. | Pick a period end inside GP's fiscal years, or set the year up in GP. |
Tie-outs
| Message | What to do |
|---|---|
| Ledger Doctor can't rebuild AP (or AR) as of … | Run it as of today. See When a tie-out isn't produced. |
| The … tie-out workbook didn't match the database totals, so it wasn't produced. | Email us the message. |
Marks
| Message | What to do |
|---|---|
| Say why this is expected, so the next person (or the auditor) knows. | Type a reason before choosing Mark as expected. |
| That record isn't in the latest results for this check. Recheck, then try again. | The record changed or was fixed since the page loaded. |
License and updates
These show on the Settings page's update job when our server won't send updates. Your install keeps running the checks it has.
| Message | What to do |
|---|---|
| Your Ledger Doctor license is canceled. | Renew on the pricing page, or email billing@myledgerdoctor.com. |
| Your Ledger Doctor license has expired. | Renew on the pricing page, or email billing@myledgerdoctor.com. |
| Your Ledger Doctor license is suspended because a payment didn't go through. | Update your payment details from your Stripe receipt email, or email billing. |
| Our server doesn't recognize this install's license key. | Check the key: run setup on the server and choose Update to change it. See Your license. |
| This install is registered to a different license key. | Email support@myledgerdoctor.com to move it. |
Something went wrong
"Something went wrong. Details are on the server in C:\ProgramData\Ledger Doctor\Logs\service.log (reference …)" means Ledger Doctor hit an error it didn't expect. Nothing half-finished is left behind: fixes and undos run in one transaction. Open that file on the Ledger Doctor server, find the reference, and email the entry to support@myledgerdoctor.com. "SQL Server refused Ledger Doctor's login: …" means a permission is missing: the message names it, and your SQL Server administrator can run EXEC LedgerDoctor.dbo.usp_grant_access;.
Anything else
Email support@myledgerdoctor.com with the message and the page you were on.