Partner application release notes

What changed in each version of the Ledger Doctor partner application, the program implementation partners use to plan a customer's move from Dynamics GP to Sage Intacct. Release notes for Ledger Doctor itself are on the release notes page.

0.12.6

November 2026. Management Reporter definitions from the customer's package and the company setup need the customer on Ledger Doctor 0.40.0 or later; a later Fixed Assets go-live with GP depreciated past it needs 0.40.4. Ask AI on the chart and dimension values needs myledgerdoctor.com's update.

• When Fixed Assets go live. Set Fixed assets go live in Sage Intacct on for a customer or combined chart, a first of the month after go-live when the assets move later. The balances by asset are then as of the day before, their own entry, from the GL history's incremental runs and GP's depreciation history, tied to the penny. Assets acquired after it are left out and listed; the import file and Create follow it; the checklist gets a Fixed assets go-live phase, with steps for each company that has assets in scope. It shows on the cutover calendar and the Fixed assets pages too. More
• Fixed asset IDs. An asset's GP ID is its asset ID and suffix (SAMPLE001-1, SAMPLE001-2), so two assets with one ID no longer share a Sage Intacct ID, and a child asset goes in the child assets file with its parent's ID. Sage Intacct's Assets import template has no asset ID column, so while GP's IDs are kept the child assets file is refused: create the assets on the page instead. The assets file's button then says Import file (zip), since it comes with its check totals and a to-check list, and the to-check list says how many child assets aren't in the file.
• A location or department company of a combined chart gives its fixed assets its own ID in that dimension, in the import file and Create.
• Compare sequences shows its answer. On the combined chart's Before records and the company page: a summary, and each sequence's status and what to do. A location or department company says whose sequences it uses.
• The link-back result on the Sage Intacct's IDs card shows its text, how many records were in scope, the records waiting on undecided matches as a count with a list you can open, and a toast when it's off screen.
• After Remove the links, the result shows on the card, where you clicked, instead of only in the message area at the top of the page.
• Setup checks. A new Setup checks tab checks that Sage Intacct's reporting periods cover each entity's start date through the last budget month, and lists the books. A gap goes on the blockers report. Entities are compared with Sage Intacct and created or renamed after you confirm.
• Financial reports. Upload the customer's Management Reporter building blocks (.tdbx), or get them from their Ledger Doctor if they share them. The Financial reports tab lists what the reports confirm about your segments and dimensions, what to look at (possible hidden dimensions), and GP accounts no financial report picks up.
• Sage Intacct assigns record IDs. Customers, vendors and fixed assets can get their IDs from Sage Intacct document sequences (C-, V-, FA-, set in Settings > Record IDs). Ledger Doctor reads the IDs back by the GP ID custom field, and the history, open items, reclass and 1099 files wait until every record is linked. Without web services, upload Sage Intacct's export to link them.
• Fixed asset balances by asset. At the conversion date, the asset cost and accumulated depreciation accounts are put back by asset, with the asset dimension, tied to GP Fixed Assets to the penny. Any difference from the GL goes on one flagged line. Parent assets load before their children.
• Move and Split on the combined chart. Send one GP account to another Sage Intacct account, or give every GP account under a number its own account, with Undo.
• Two default client applications. Settings has an Implementation one (Sage's non-production scope) and a Production one. Each environment's Connection uses its own; Implementation uses the Production one when its own is blank. A non-production application signing in to a production company now says so plainly.
• Entity IDs. Set each Sage Intacct entity's ID by hand on Companies and entities, or give new combined charts a pattern in Settings (E100, E200, E300, in company order). IDs are unique in the combined chart, keep who set them, and can't change once the entity is in Sage Intacct.
• Menu order. Under Chart and dimensions: Segments, Companies and entities, Chart of accounts, then Department and the other dimensions. Records now come right after Chart and dimensions, and the combined chart's Records menu is in the load order, as a company's.
• Split stays near the account. Split proposes the next free numbers in the account's own block of the chart layout, and the new accounts take GP's title without the department name when that leaves each one different.
• Linking records on a combined chart. Uploading Sage Intacct's export links every record that isn't in an undecided match, and lists the others to decide first. On a company in a combined chart, Link says to use the combined chart.
• Why there's nothing to show. Financial reports says why the customer's Ledger Doctor sent no definitions (sharing off, or its reason), and Setup checks says why GP's company setup is missing.
• Ask AI on the combined chart. On the Chart of accounts and each dimension's values: suggested merges, new IDs and clean titles (capitalization, abbreviations). Every suggestion is checked before it's shown, and nothing changes until you accept it.
• Combined chart: an account number with fewer digits than the chart's (a 3-digit 120 beside 4-digit accounts) is suggested with zeros after it (1200), or the next free number in its range.
• Messages from a Save far down the page also show briefly at the bottom of the window.
• Fixed assets on the combined chart. Records now has Fixed assets: each company's assets with their GL accounts from the plan, its import files and Create. Assets stay each company's own; the GP ID field gets the company's prefix only when two companies have the same asset ID. Records also has Before records, with each entity company's document sequences.
• Remove the links. The records' Sage Intacct's IDs card can remove the links from GP's IDs to Sage Intacct's for one environment, after you confirm on the page (Approvers only). Nothing in Sage Intacct changes, and it's logged.
• Entity and location IDs. In Sage Intacct entities are locations, so an entity can't take a location's ID or a Location value's, and a location can't take an entity's. The page says whose ID it is, and the freeze check catches a clash.
• Customers page. Their Ledger Doctor's version shows the newest package's version beside it when they differ, so you know to ask for fresh data.
• The combined chart's link result lists the records waiting on an undecided match, instead of showing "[object HTMLParagraphElement]".

0.11.5

November 2026. Custom field values and the vendor and customer details below need the customer on Ledger Doctor 0.39.0 or later.

• Checklist box. On every customer and combined chart page, a box in the top corner shows the last two checklist steps done and the next three to do, with any that are blocked or waiting. Click a step to go to its work. Minimize it to a small “Next” tab; it stays minimized until you open it again.
• Filters on mapping tables: show only what needs your choice, conflicts, missing IDs, suggestions or left out, with a search box.
• Combined chart accounts. A bank account (a GP checkbook's GL account) is never suggested to merge, and neither are accounts whose titles differ on a word like checking or savings. Suggested titles leave out the other segments' names GP added to them, with GP's own title shown underneath.
• Custom fields from GP. Map your Sage Intacct custom fields to GP values (the original account, journal entry, source document, reference, originating master, document and amount, GP's vendor, customer and asset IDs) in Settings > Custom fields, or per customer. Import them with your defaults. Every file and push for GL history, the opening entry, vendors, customers and fixed assets fills them. A value longer than its field is listed to check, never cut. More
• GL history rules. An optional monthly summary before a date; leave out entries with an unmapped account; export only entries not already exported, for the months between go-live and GP's last day; detail files by entity and quarter; commas, quotes and line breaks cleaned out of text; the customer or vendor dimension on any line whose GP master is one. More
• Reclass by customer and vendor. When the chart has the customer or vendor dimension, an entry for each entity moves the receivables and payables control balances onto each customer and vendor, tying to the open items to the penny.
• Vendors and customers. Always loaded active (inactivate them after go-live); 1099 MISC box 7 becomes NEC box 1, and a 1099 box with no type NEC, on vendor records, in the vendor 1099 setup file and in the 1099 opening balances file, each conversion listed to check; country names made the same.
• Selection window. Records created but not yet used go if they were created in the last 18 months, as before. You can now change the 18 months, from 0 to 120: a default in Settings, and per customer on the Records tab. It needs the customer on Ledger Doctor 0.41.0 or later and myledgerdoctor.com to take it. If it can't be sent, the page says so. More
• On a combined chart, a GP vendor or customer ID that two companies load without merging gets the company's prefix, and is listed to check. Freeze a version says why it can't freeze yet.
• Setup on a team server also offers to make you an Approver for every customer.

0.10.2

November 2026.

• Back to the proposal on accounts. A decided account on a combined chart can go back to its suggestion, with why; the earlier decision stays in its history.
• Segments are approved one by one before freezing, on a combined chart as on a customer's page: a segment still at its proposal is listed as not approved yet.
• A suggestion from Suggest with AI that would put a segment's values in the same list as a company's own location or department value says so beside it.
• Smaller fixes: Cancel on the GL account question puts the choice back; undoing a decision starts with an empty Why box; one checklist line per company for defaults with the same name; a wider Sage Intacct ID box on records, with a link to the record that needs a new ID.

0.10.1

November 2026. Tested as 0.10.0.

• Combined charts work like a customer's page. The same menu and the same Implementation and Production bar, with every company's data together: Summary, Checklist, Blockers report, Plan versions, Segments, Chart of accounts, a tab per dimension, How it will look and Full mapping (with downloads before you freeze), then opening balances, intercompany, history, bank accounts, 1099s, budgets, records and Sage Intacct. More
• Choose each company's GL account segment on the combined chart's Segments tab, along with what every other segment becomes.
• Suggest with AI for every company at once. The AI sees the companies together, so segments that mean the same thing get the same dimension. It counts as one suggestion.
• Customers, vendors and other records merged across companies. Records with the same ID or name are proposed as one. You decide each match, with why, and the merged record loads once.
• A start date for each entity. Companies in one entity still share a date. Each entity's opening entry is dated the day before its own start, with an optional Sage Intacct fiscal year month (in entities.csv as FIRST_FISCAL_MONTH).
• Company pages follow their combined chart. What the combined chart decides is read-only on the company's own page, with a link to the same tab on the combined chart. Its connection stays editable there.
• Ask every company for fresh data from the combined chart's Summary.
• Undo a decision. A records match goes back to undecided, and a segment back to its proposal. Making a second segment the GL account asks what the first one becomes.
• The same account in several companies, moved to a new number, is suggested as one account at that number.

0.9.0

November 2026. Downloading a customer's vendor tax IDs and payment details needs the customer on Ledger Doctor 0.38.0 or later, with their permission.

• Customers without Sage Intacct Web Services. On Connection, tick that the customer doesn't have Web Services, for each environment. Every step that would call Sage Intacct becomes a download, and the checklist says which file to import, where in Sage Intacct, and what to check by hand. More
• Every import file in Sage Intacct's own template columns. The chart of accounts, dimensions, entities, records, opening entries, GL history, open AP and AR, bank accounts, 1099 balances and budgets come out in the columns of the Company setup checklist's templates, with dimension columns named for the dimension, not your customer's label for it. Fixed assets use the New import service's Assets template.
• Big files split themselves. A file over 5,000 lines (change it in Settings, from 100 to 10,000) downloads as numbered files, each with the header row, never splitting an entry, document or budget line, with a file of check totals.
• Checked before you download. Each file is checked against its template's rules first. A missing required field stops the file and names the line. Anything else to look at comes in a file beside the check totals.
• Clean values. Every value in every file is trimmed, with line breaks and doubled spaces made one space.
• Vendor tax IDs and payment details as files, with the customer's permission. When the customer allows it on their Migration page, the vendors, 1099 setup, ACH and bank file payment files carry those details. They're kept encrypted here, never shown on a page, and deleted when the customer withdraws permission, the connection ends, or after GP's last day. Each download is logged. More
• After you send the customer's Ledger Doctor its Sage Intacct sign-in, Connection says it's waiting for their next check-in until it's been picked up.

0.8.2

November 2026. Go-live, GP's last day and the customer's sign-in need the customer on Ledger Doctor 0.37.2 or later. Tested as 0.8.0 and 0.8.1.

• Cutover calendar. Each project's checklist has a calendar per environment: the planned go-live, the dates GP's modules freeze, GP's final close, and Sage Intacct's books closed through the start date, in date order with what's overdue. The cutover steps wait for their dates. More
• Go-live, GP's last day, and modules that stay in GP. Tick go-live in Production with its day, and set GP's last day for each company. A module that moves later than go-live, such as Payables for one more payment run or Fixed Assets for more depreciation in GP, gets its own date. Its steps wait for it, and GL history can come over past go-live up to it. After GP's last day, pulls and requests stop, and the page offers to end the connection.
• Smart rules, events and approvals go on after the loads. Smart rules and events from your defaults import off, and a Testing step lists everything to turn on once the data is in: the rules, the events, and every setting ticked Set after loading on Your defaults. A setting with "approval" in its name comes in ticked, and you can change it either way.
• Tax IDs and payment details without seeing them. Send the customer's Ledger Doctor the Sage Intacct sign-in from Connection. Then on Records > Vendors, choose which fields to send. The customer's server reads them from GP and sets them in Sage Intacct, and you see only whether each one was set. Your XML sender details stay here. A location company in a combined chart sends its entity company's sign-in. More
• Open documents GP shows reduced with no record of how no longer stop open items as of an earlier date. They're named in a warning instead.

0.7.3

November 2026. Outstanding checks and deposits need the customer on Ledger Doctor 0.36.3 or later. Tested as 0.7.2.

• Outstanding checks and deposits at cutover. With open items, Bank accounts lists each account's checks and deposits not cleared on the cutover date, with the last reconciliation and how they tie to GP's book balance, checked again here to the penny. Download one file per account for Sage Intacct's initial open items import. A checkbook that doesn't tie gets no file. A new checklist step tracks them.
• Entries across entities go in at the top level. A GL detail entry whose lines go to more than one Sage Intacct entity is one entry at the top level, each line keeping its entity, and Sage Intacct makes the inter-entity entries. The same goes for a summarized period whose entities only balance together. They get their own import files and their own Compare, Create and Tie out. The tab says how many and reminds you to set up inter-entity relationships.
• GL detail stays when you look at the summary again. Choosing Summarized and then In detail no longer sets received detail aside. Only a new date range or a new summary does.
• Partner defaults give the same result however you import them. Your firm's name is learned from your packages' authors and remembered, so a file imported alone gets the same placeholders as when it's imported with others. Your packages carry your license name as author, never a person's name. Sage's own packages keep theirs. The import answer lists each item once, and a difference between two files names which file has which value.
• A bank account with no file says why. On Bank accounts and in the checklist step, an account whose outstanding checks and deposits don't tie shows No file: and the reason, where the file would be.
• Checkbooks reconciled only after the cutover. When GP's only reconciliations on record are after the cutover, the account says its reconciled balance on that date can't be known, and what to do.
• Re-importing a removed partner default restores it. An item you removed on Your defaults and import again comes back as the same item, counted as restored. Customers that had it see it as before, with their own values, and aren't offered a second copy.

0.7.1

November 2026. Bank accounts, 1099 balances, budgets and GL history in detail need the customer on Ledger Doctor 0.36.0 or later (0.36.1 for currency codes and open items as of an earlier date). Tested as 0.7.0.

• Bank accounts. Each GP checkbook whose GL account is in scope becomes a Sage Intacct checking or savings account, with its bank name, currency, GL account and entity through the chart. Compare, create through the API, or download the import file. Only the last 4 digits of the account and routing numbers come across, to check against the bank's own documents when they're entered in Sage Intacct. The page shows where to start Sage Intacct's bank reconciliation, and warns when GP's checkbook balance and its GL account differ.
• 1099 balances. After go-live, pick the year and the Sage Intacct start date. The 1099 balances tab adds up what each vendor was paid before that date, by form and box, through the vendor choices on Records (merged vendors add up), and ties it to GP to the penny. The file is for Company > Setup > Import data > Vendor 1099 opening balances. A miscellaneous box 7 amount from 2020 on, or a vendor that doesn't convert, stops the file until it's fixed.
• Budgets. Ask for GP's budgets (every year, unless you give one), last in the conversion. Pick the budgets and, within each, the years that come over, whatever the GL history covers. Accounts only the picked budgets use come into the plan at the next freeze. Each one is mapped through the chart like the opening entry and summed per account, dimensions and period, in each account's normal balance. Each budget ties to GP to the penny. Download a file per budget, or create the budgets through the API and tie them out.
• GL history in detail. On History and open items, choose one entry per GP journal entry instead of one per period. The customer's Ledger Doctor checks the detail on its own server and sends a summary. When you ask for the detail, the page says how big it is first. It arrives encrypted over the next check-ins, and is checked against the summary to the penny. Then download the import files (at most 5,000 lines each, never splitting an entry, numbered in order) or create drafts in batches and tie them out.
• Partner defaults, tried on a real partner's files. When the same rule comes in its own file and in a list, its own file wins and differences in spacing alone aren't reported. A rule that compares with journal symbols, or an event that sets a payment term, is flagged to check for each customer. A setting's checklist step shows the customer's filled value. Importing a newer version of a file updates what's there and says what changed.
• When more than 5 open documents repeat a number, the warning says how many more.
• Checkbooks in GP's own currency take the base currency, and the same checkbook ID in two companies of a combined chart gets the company after it, which you can change. A GP fiscal period that starts on the first and ends in the same month gets that month's Sage Intacct name. Messages on a combined chart name its version. GP's 1099 box setup numbering is matched to the vendors', and the file waits when Ledger Doctor can't tell which GP uses.
• An open document that can't be rebuilt as of the cutover date is named on the tab and in the refused-documents file, and no open-items file is made until it's fixed in GP.

0.6.4

November 2026. Open items as historical documents need the customer on Ledger Doctor 0.35.4 or later. Tested as 0.6.3.

• Open receivables and payables go in as historical documents. Each invoice, bill and adjustment has GP's own distribution accounts as its lines, mapped through the chart (cost of goods, inventory, warranty, commissions, discounts and the control account stay out; a partly paid document's lines are scaled to what's still open). Accounts that open documents use come into the plan at the next freeze, and every refused document is listed in a file you can download. Import the files and choose posting type Historical, so they build the subledgers without posting to the GL, which the opening entry and history already carry. Creating them through the API is off until Sage Intacct's API can make historical documents.
• No clearing account needed. It's optional and off by default; the opening entry and history keep GP's receivables and payables accounts.
• The aging difference, up front. Each entity says how far Sage Intacct's AR and AP agings will differ from their GL accounts: the same difference GP had.
• The warning about two companies with identical history shows once, under GL history.

0.6.2

November 2026. History and open items need the customer on Ledger Doctor 0.35.0 or later; everything else works with any Ledger Doctor since 0.25.8. Tested as 0.6.0 and 0.6.1.

• History and open items. A new tab on a customer's page and on a combined chart. Ask for GL history between two dates and open receivables and payables on the cutover date. The GL history is one draft journal entry per entity per fiscal period, one line per GP account, tagged like the opening entry. Open items are invoices, bills and adjustments, one line each, against a conversion clearing account you pick in Settings > Your defaults, which has to be an account in the chart. Every account's history ties to GP's balances to the penny, open items tie to GP's total, and the page says by how much and where when anything doesn't. Download the import files, or check, create the drafts and tie them out in Sage Intacct, in batches that go in whole or not at all. The checklist ticks the steps off once they're loaded and tied. More
• AR and AP control lines to clearing. Once open items are asked for, the opening entry's and the history's receivables and payables control lines go to the clearing account, so the open documents build the control balances and the clearing account nets to GP's own difference. Turn it off per customer or combined chart.
• What a load costs in API calls. Before a load, the page shows how many Sage Intacct transactions it uses, beside what a load of every GP journal entry would have used.
• How do I…? Ask how to do something in the partner application, from the header or the foot of any page. The answer comes from the partner help center only, with links to the pages it used. Only your question is sent. 50 a month.
• Email not set up, said plainly. When the partner application has no email set up, the Customers page and Settings > Email say what won't be sent, and actions that would email say so.
• The check-in tells us the name of the computer the partner application runs on.

0.5.23

November 2026. From the first combined chart on a test company.

• Freezing waits for every company's balances. A combined chart isn't frozen until each company's GP balances on the start date have arrived, and the message names the company still waiting. Before, a version could be frozen while one company's balances were on their way, and its opening entry left that company out.
• Choose the order of the companies. On the new combined chart form, tick the companies and put them in order with Move up and Move down. The first company's numbers win when accounts merge. Change the order later under Companies and layout.
• Dimension value IDs don't start with 0. When a GP value starts with 0 (Division 000, Department 00 to 09), every number value in that dimension is suggested with a 1 in front, at one length (000 becomes 1000, 05 becomes 105). You can still map a value to another ID. A value kept with a leading 0, or number IDs of different lengths in one dimension, are listed under Entities and stop the freeze.
• Values decided before the ID rule are open again. A dimension value already decided with an ID that starts with 0, or isn't its dimension's length (Department 00 kept as 00, say), shows as needing a decision, with its "renumber to" suggestion and the earlier decision. Accept every plain "keep" or "renumber to" takes them, and the earlier decision stays in the value's history. Before, those values blocked the freeze and each had to be mapped by hand. On the new combined chart form, the first ticked company's Move up and the last one's Move down are turned off, as under Companies and layout.
• Each renumbered account shows its own number. Accounts moved into the chart layout's ranges are each suggested their own number, shown as "renumber to 1003". Before, they all showed the range's first number. The same account in two companies still moves to one number.
• Opening balances opens on the newest frozen version, unless you pick another, and its totals have thousands separators.

0.5.20

November 2026. Works with any Ledger Doctor since 0.25.8 (the blockers report needs 0.31.0 or later; updating a customer's Ledger Doctor needs 0.34.18 or later). From the first rounds against a real Sage Intacct company. Tested as 0.5.0 to 0.5.20.

• Entities in a combined chart. In each Sage Intacct entity, one GP company is the entity and the others become a location or department under it. The new Entities table under Companies and layout lists any problems, and a version can't be frozen until they're fixed. entities.csv has one row per entity, the location and department files have a PARENT ENTITY column, and each crosswalk has the entity and the company's location or department.
• Loads use the combined chart. Freezing a combined chart gives each of its companies a plan version from it, with the combined chart's accounts and the entity and the company's location or department on every line. Compare, Create and the other Sage Intacct steps load from that version. The companies need the same start date, and a company in a combined chart isn't frozen by itself (take it out of the combined chart to do that). A location or department company uses its entity company's Sage Intacct company, user, entity, retained earnings account and dimension mapping: Copy from on its Connection page brings them over, and different values aren't saved.
• Opening balances by entity. A combined chart's new Opening balances tab checks, creates and ties one draft entry for each Sage Intacct entity, with a line for each GP account of every company in it. A location or department company's lines carry its value, and the check makes sure that value is in Sage Intacct under the entity. A company in a combined chart doesn't load its opening entry by itself any more. The Intercompany tab lists due to, due from and intercompany balances in two or more companies of an entity, with the net, for you to eliminate, reclass or keep with a reason. Nothing changes the entry by itself.
• Update their Ledger Doctor. On the Customers page, an approver can tell a customer's Ledger Doctor to check for a new version and install it now, if the customer's admin turned on Let my partner install updates. The page shows each customer's Ledger Doctor version and its answer.
• Quoting summary only, said plainly. Accepting a company no migration covers says its quoting summary comes to the Buying page, and its full data once you add it to a migration and the customer confirms. Its customer page says the same instead of "Nothing has arrived".
• Install new versions automatically. Settings can install each new partner version by itself in a window you choose, overnight by default. It waits while anything is loading into Sage Intacct.
• Your partner code on the Customers page, for whoever gives it to a customer (it was only in Settings).
• Starts after a restart on its own. When Windows restarts (after updates, say), the partner application no longer stops if SQL Server is still starting: it waits for it and then opens its workspace. It now starts with Windows' delayed start, like SQL Server.
• A new header. Customers and Buying at the top, then icons: help for the page, a gear for Settings, Partner defaults, Server and HTTPS and Email, a key for Security, and a person for My preferences. The license key, updates, your defaults and the Sage Intacct client application moved from the Customers page to Settings.
• A menu instead of tabs. The customer's page groups its pages in five: Migration (Summary, Checklist, Blockers report, Plan versions), Chart and dimensions, Data and balances, Records and Sage Intacct, with what's waiting counted on each group. Sage Intacct preview is now How it will look.
• Implementation and production. Each customer has both Sage Intacct companies. Switch at the top of the page; each keeps its own company, client application, dimension mapping, checklist and load log. Ticks from before 0.5 belong to Implementation. More
• Compare replaces Preview: for the chart and every mapped dimension, what matches, names that differ slightly, what's to add, what's only in Sage Intacct, and numbers the company already uses for something different. Those wait for your decision (use Sage Intacct's record, or renumber it in the plan) before anything is created. Create only the ticked makes a small test possible.
• Test REST sign-in checks each permission the steps need and says what to give the web services user's role, using the company's own names for dimensions (Fund for Location). It also shows the entities and the chart's size.
• API calls. Before Create runs it says how many calls it takes and how many were made this month; a counter at the top of the page keeps the month's total in view, against Tier 1's 100,000 or the allowance you enter.
• Before a load. Check the opening balance entry against the company: accounts or dimension values missing or inactive, a dimension an account requires left blank, entities missing. Since the last load lists what GP has that the frozen version doesn't, and what's frozen but not in the company yet.
• Configuration. Read the company's preferences through Sage's API and change one value after confirming; it's read back, logged, and Put it back undoes it. Compare with your defaults sets each configuration setting from your partner defaults beside the company: an admin links a setting to its Sage Intacct field once, for every customer; Set it changes the company to your default, and the Checklist step ticks itself off when they match.
• Module settings. Configuration also reads General Ledger, Accounts Payable, Accounts Receivable, Cash Management and other applications' settings, which Sage's REST API doesn't offer, through its XML API, in one call. Enter your XML sender ID and password under Settings and the web services user's password on Connection; all are kept encrypted. Configuration lists its settings by application, each opened on its own. Test XML sign-in on Connection checks the XML sign-in on its own, beside Test REST sign-in. A settings template can name the module setting each default checks and the value Sage stores for it (Sage setting and Sage value columns, such as xml:AP/GLPOSTINGDATECHECK and WARN; several separated by semicolons, or a configuration field such as company-config/company-preference:permissionType): it's linked on import, and Compare with your defaults checks it. Module settings are changed in Sage Intacct, not from here.
• Records. Warehouses, items, customers, vendors, employees and fixed assets go into Sage Intacct as full records before transactions: only those GP used since the start of the history you convert, with an open balance, or created in the last 18 months (Ledger Doctor 0.34.0 or later chooses them). Leave one out or give it a different ID; Check fields compares what's sent with Sage Intacct's definition, Compare shows what's there, what's missing and what's in the way, and Create makes the rest, with the types and product lines they use. Before records checks what they and the journal entries need first (AR and AP terms made from GP's, customer and vendor types, product lines, asset classifications and your journals), creates what Sage's API allows and reads it back (asset classifications from GP's asset classes: the GL accounts from the class's account group through your mapping, the method and useful life from its corporate book, under the Fixed Assets journal rule you choose); the Checklist ticks it off, and Create and the opening entry wait while something they need is missing. More
• The opening balance entry straight into Sage Intacct. On Opening balance, Create as drafts sends one entry per entity to the company you're working in, after checking it against the company. Entries post at the top level, each line's location set to the entity (unless the plan already gives the line a location). Each entry goes whole or not at all, is read back and tied to the penny, and stays a draft for you to review and post there; a draft Ledger Doctor created can be deleted again.
• The retained earnings account can be one the plan creates (it's created first), and Compare suggests it. Values GP has no name for are flagged before they reach Sage Intacct named only by their number.
• Freezing a plan version asks first. Saving the client application, the company and the mapping, sign-in tests, switching environments, decisions, creates and configuration changes go in the security log (never secrets).
• "Not loaded by Ledger Doctor" is now Don't load, and a mapping only shows as chosen once it's saved. Buying calls what you buy for a customer a migration.

0.4.4

October 2026. The blockers report needs the customer on Ledger Doctor 0.31.0 or later; everything else works with any Ledger Doctor since 0.25.8. Tested as 0.4.3.

• What's still found after "done". On the Blockers report tab and in its PDF, a problem the customer marked done whose records their latest package still has says so: "Ledger Doctor still finds 3 records", with the package's date. It comes from what the package already carries. More

0.4.2

October 2026. The blockers report needs the customer on Ledger Doctor 0.31.0 or later; everything else works with any Ledger Doctor since 0.25.8.

• The app and its help say Sage Intacct throughout, such as the Sage Intacct preview and Sage Intacct setup tabs.
• People by name. Screens show who did something by their display name, not their Windows login: who changed and sent the blockers report, ticked off checklist steps, made and proposed decisions, froze plan versions, imported defaults and asked the AI for dimensions. Security settings and "signed in as" still show the login.
• Start the next revision and Refresh from the latest package on the Blockers report tab ask first, saying how many items come in, go and change. Items you edited and your own items are kept, as before.
• The Blockers report tab leaves out checks about the customer's database setup (database users and roles, SQL triggers, who owns the database, database code added lately), also from customers on older Ledger Doctor versions. They're for the customer's IT, not the move.
• Chart of accounts: an account GP has no typical balance for offers Debit and Credit to choose from, so it can be approved. Before, the choice was empty and Approve said the GP accounts disagree.
• The checklist shows when the latest package was prepared as a date and time, like the rest of the application, not as "2026-10-29T14:17:49Z".

0.4.1

October 2026. The blockers report needs the customer on Ledger Doctor 0.31.0 or later; everything else works with any Ledger Doctor since 0.25.8. Tested as 0.4.0.

• A blockers report's PDF says "draft, not sent yet" until it's sent, instead of "prepared by" with no name, and points the customer to "this issue on the Health page" rather than a check number.
• No Windows sign-in names go to your customer. A blockers report says who prepared it by display name, or your firm's name, never a login like DOMAIN\user; logins from a customer are never shown either.
• The Blockers report tab says why warnings start unticked, and leaves out findings about the customer's server (SQL Server logins, backups, database code).
• Blockers report. A new tab on each customer: what's in the way, for the customer. Build it from their latest package (Ledger Doctor's findings, with warnings unticked until you choose them, GP's balances on the start date, and decisions only they can make, such as which inactive customers and vendors move), change the words, leave items out, add your own, and send it. They see it on their Migration page with links to each issue, guide and one-click fix in their Ledger Doctor, mark items done and answer the decisions, and their answers show here (and by email, if you want it). A PDF of it downloads from both sides. Sent encrypted for the customer's Ledger Doctor only; an approver for the customer sends it. More
• Implementation checklist. A new tab: every step from connection to go-live, in order: the customer's data, the plan, Config, Dimensions, GL transactions, Subledger open transactions, testing and cutover. Steps done elsewhere in the application tick themselves off; tick the rest off as you do them, with who and when kept. A step that puts something into Sage Intacct has its import files and how to import them; configuration steps say how to set them up by hand; the dimension values and chart of accounts step has More info, which lists exactly what it would add, then Run it now. The steps that were on the Sage Intacct setup tab moved here, ticks and all. More
• Partner defaults. A new page for your firm's standards, which every new customer starts from: smart rules, smart events and custom packages as Sage Intacct XML (imported as they are), and your setup guide's settings and your security reports from Excel or CSV templates. Choose which are used for new customers and which rules and events are created active. Anything that belongs to one customer, like a login a rule lets through or who gets the security reports, becomes a placeholder you fill in for each customer, and your firm's name is filled in for you. Each customer's checklist lists them with the filled-in file to import. More
• Customers' "Projects" (one chart of accounts across several GP companies) are now called combined charts, so "project" only means the customer project you buy.
• Customer data in the new tabs is stored encrypted, like packages.

0.3.3

October 2026. Works with customers on any Ledger Doctor version since 0.25.8. Tested as 0.3.2.

• Saving Server and HTTPS with nothing changed says so, and leaves "Last changed" as it was.
• Help on every screen. Each page (and each tab of a customer's page) has a Help link to its own help page, with a short narrated video. Partner help
• Questions like "Let computers on your network reach it?" are asked on the page, with Yes and Cancel, instead of in a browser pop-up some browsers block or answer for you.
• Emails look like Ledger Doctor: each one comes in Ledger Doctor's colors with a plain-text copy, through Microsoft 365 too.
• Buying shows a quoting summary's sample account numbers; they showed as "[object HTMLElement]".

0.3.1

October 2026. Buying needs the customer on Ledger Doctor 0.29.0 or later; connections that were already sending data keep working as before. Tested as 0.3.0.

• Buying. A new page, in every page's header. Each accepted company you haven't bought a project for shows its quoting summary: GL accounts, vendors and customers, years of GL history, modules in use, a few account numbers and how many segments the account format has. Pick a customer's companies and propose them; the customer confirms them, and the data that goes to you, in their Ledger Doctor, or sends them back with a note you see here. Then pay on myledgerdoctor.com: $3,500 for a project covering up to 3 companies, $1,000 for each after. The companies unlock and their full data arrives at the customer's next check-in. How buying works
• Customers shows "Quoting summary only" for a company no project covers yet.
• Approvers for a customer propose and pay; each step is in the security log.

0.2.2

October 2026. Works with customers on any Ledger Doctor version since 0.25.8. Tested as 0.2.0 and 0.2.1.

• Who can reach it. Setup asks: This computer only (as before; nothing listens on the network) or Computers on my network, where consultants open it from their own computers and sign in with Windows. On the network it uses the server's computer name, so Edge and Chrome sign people in by themselves, or a full name (setup says what IT adds for silent sign-in). Setup checks each name leads to the server and opens the port in Windows Firewall for the domain network only. http://localhost always works on the computer itself. Change it later, and the address, in setup or Settings, Server and HTTPS, without reinstalling. See Install the partner application.
• HTTPS, as in Ledger Doctor. On the network: a certificate the application makes (its own certificate authority, renewed by itself), one from the server's certificate store, or a .pfx (its password used once, never saved), covering every name people use. Admins replace it in Settings, where it's checked first and the old one comes back if it doesn't work. The http:// address sends people to https://. IT has LedgerDoctorPartner.exe https.
• Security. Admins give Windows accounts or AD groups a role for one customer or every customer: Approver, Processor or Read-only. A consultant sees a customer only once given a role. A Processor's account decisions go to an approver as proposals. Every change is logged, and the last admin can't be removed. Whoever runs setup is the first Admin; on an update from 0.1, they're also an Approver for every customer, so nothing they could do is lost. A solo consultant is simply the only Admin.
• Email. Settings, Email: a mail server (SMTP with TLS) or Microsoft 365, with a test email; the password is kept encrypted. Emails go to each person's address from Active Directory, or the one they give in My preferences, where each email can be turned off: the HTTPS certificate expires within 30 days (Admins), a customer asks to connect (Admins and that customer's Approvers, with a link to accept), data you asked a customer for has arrived (with what changed in its counts), and a new version was installed (Admins).
• Check-in with myledgerdoctor.com. Every 15 minutes the application says which install it is, its version, the Windows and SQL Server versions, who can reach it and its address, how many customers and projects it has, and whether HTTPS is on. Nothing from any customer's data. If myledgerdoctor.com says the install belongs to another partner license, admins see it in Settings.
• Partner license keys only. Setup and Settings check the key with myledgerdoctor.com and refuse a Ledger Doctor customer license key, saying to use the partner key from your welcome email (it starts with LDP-). A partner key that can't be checked because myledgerdoctor.com can't be reached is saved as before.

0.1.17

October 2026. Works with customers on any Ledger Doctor version since 0.25.8. Tested as 0.1.13 to 0.1.16.

• Runs as a Windows service, with a setup wizard. Double-click the program and setup opens in your browser. It asks for the SQL Server, your partner license key (it shows your partner code), the port, and optionally your Sage Intacct client and defaults. It installs a service that starts with Windows, with no window to keep open, and adds Ledger Doctor Partner to the Start menu, which opens http://localhost:5190/ (Edge and Chrome sign you in with Windows there without asking). People sign in with their Windows account (the Customers page says who), and each decision keeps their name; a browser that can't sign in with Windows shows how to. A copy that ran in a window keeps working until you run setup, and setup starts from its SQL Server and port. Setup then moves its keys and customer data to the service, so your customers stay connected. See Install the partner application.
• Suggest with AI on the Segments tab. It sends the segments' names and values (IDs, GP descriptions and account counts; no amounts) and shows a suggestion beside each segment, with a reason. Use these suggestions applies it only to segments nobody has approved; Pick this beside a suggestion puts it in that segment's Becomes box, to save like any change. See Segments and dimensions.
• A segment can be part of the GL account: a sub-account segment (-01 to -04) is joined after the account number, so each becomes an account of its own.
• A dimension you added that became a standard one keeps your name as a label, such as Class (Fund), with how to rename it in Sage Intacct under Terminology. Its row selects what it is now, so Save changes nothing unless you choose something else.
• A segment named Department is proposed as Department, even when another segment's values read like departments. That other segment (a Division, say) goes to its next choice, such as Location.

0.1.12

October 2026. Works with customers on any Ledger Doctor version since 0.25.8; with 0.26.0, their packages arrive within a few minutes. Tested as 0.1.9 to 0.1.11.

• Customer data is encrypted in your workspace. Each customer's GP data (accounts, balances, customer and vendor names) and every frozen plan version are stored encrypted, with keys only your Windows account can use, rather than as readable data in SQL Server. What's already there is encrypted the first time 0.1.9 starts. BitLocker on the disk is still recommended.
• After Accept or Ask for fresh data, the application looks for the package every 30 seconds for 20 minutes, so it shows up within minutes of the customer's Ledger Doctor sending it. The Customers page shows a new package or connection request by itself, without a reload.
• GP accounts that aren't being converted no longer shape the account they're listed under: its title, type and "different descriptions" warning come from the GP accounts in scope, and Split only splits those. Undo on an account a split made puts the whole split back.
• A GP segment whose values read like departments (Administration, Accounting, Sales…) is proposed as Department even when the segment is called something vaguer, like Division.
• The Segments tab lists every dimension, including ones you added that GP doesn't have, such as a Fund. An added dimension can become another (a Fund added as user-defined that is really Class): its values, default and each GP account's value carry over. A Fund, grant or program dimension is proposed as Class.

0.1.8

October 2026. Needs the customer on Ledger Doctor 0.25.8 or later. Tested as 0.1.4 to 0.1.7.

• Updates install themselves. The application checks for new versions; when one is ready, every page offers Install and restart, and Settings has Check for updates.
• One line per GP account in the opening balance entry, so each line ties back to one GP balance, even when several GP accounts land on the same Sage Intacct account and dimension values.
• Your defaults in Settings: the opening entry's journal, the statistical journal, and a custom field for the GP account on each line if your Sage Intacct setup has one.
• The earlier years' result says net loss or net income, and whether it's a debit or a credit to retained earnings; once its account is chosen, the page says where it goes. A dimension with no default gets a note saying why that line has no value for it.
• GP's balances show up on their own after you save a start date: the page notices when they arrive, without Check now or a reload.
• The account for the earlier years' net income or loss is chosen from balance sheet accounts only, never a GP unit account.
• The statistical opening file follows Sage Intacct's statistical journal entry import: Increase and Decrease columns, a state, and the dimension columns that import uses.
• A GP unit account always becomes a statistical account, even if it was approved as a money account in an earlier version; the chart flags the old decision so you can change it.

Initial release

October 2026. What the partner application did before 0.1.8, its first posted version.

• Connecting to customers. A customer connects from the Migration page in their Ledger Doctor with your partner code; you accept on the start page. Their GP data reaches you encrypted for your copy of the application only, through myledgerdoctor.com, which can't read it.
• Chart of accounts. A proposed Sage Intacct chart from the customer's GP accounts: accounts that share a natural account merge, and you approve, change, split, merge or (rarely) exclude each one, with a reason kept for every change. Bank accounts and the accounts Sage Intacct needs on their own are never merged. A split keeps the account number's length. Approve the remaining proposals approves only what nobody has decided yet.
• Dimensions. Approve how each GP segment becomes a Sage Intacct dimension, then each value, with a tab per dimension to rename, renumber, merge, split, add values and set a default. Numeric IDs within a dimension all have the same length and never start with 0. You can add a dimension GP doesn't have.
• How much history. Choose the conversion's start date (current year, a number of years back, or a date). Only accounts and values with a balance at the start or activity since then are in scope.
• Opening balance entry. Saving the start date asks the customer's Ledger Doctor for GP's trial balance at the start of that date, worked out from GP's own tables and checked there first. The entry is checked to the penny before an import file is made. GP unit accounts become statistical accounts with their own entry. When GP has no retained earnings account, you choose where the earlier years' net income or loss goes.
• Files for Sage Intacct. Accounts, statistical accounts, each dimension's values, the opening entries in Sage Intacct's journal entry import layout, GP's trial balance for reconciling, and the full mapping (every GP account with its Sage Intacct account and dimension values) as CSV and Excel. Drafts any time; frozen plan versions for sign-off.