Dynamics 365 Asset Leasing Data Migration and D365 Lease Import From Lease PDFs

Short answer: Asset leasing in Dynamics 365 Finance calculates lease liabilities, right of use assets and journal entries once each lease exists in the system. It does not read lease documents. Microsoft says so plainly in its own getting started article: the lease information source is the lease contract and management decision, both of which are done outside of Dynamics 365 Finance. Getting an existing portfolio in is therefore a data job. Upload the lease PDFs here, get the fields back cited to their pages, and load them through the Lease import framework.

What Dynamics 365 Asset leasing does once a lease is in

Microsoft describes Asset leasing as a capability for managing, tracking and automating financial transactions for leased assets in Dynamics 365 Finance, compliant with ASC 842 and IFRS 16. Lease books also support ASC 840, IAS 17 and cash basis accounting, which is how companies run a statutory book next to a US GAAP or IFRS book. The module classifies each lease as finance, operating, short term or low value according to the thresholds on the book, calculates the net present value of the payments, builds the payment, amortization, depreciation and expense schedules, and posts initial recognition, monthly entries, impairments and terminations to the general ledger. It ties into Accounts payable for lessor invoices and into Fixed assets for the right of use asset.

Before any of that works, an administrator turns the feature on. In the Feature management workspace you find the feature named Asset leasing and select Enable now. That part takes a minute. Filling the lease records takes the rest of the project.

How the D365 Asset leasing Lease import framework works

Microsoft documents three data entities for bringing leases in from outside the system: Lease staging, Payment contract staging and Executory contract staging. You load them through the Data management workspace, then open Asset leasing, Lease import framework, Import header, where every import of those three entities is listed. From there you can view the staging data, edit it, compare it with what is already in the system, validate it and migrate it.

Each staged lease carries one of three process types:

• Add record creates a new lease. Microsoft notes that the payment schedule must then be confirmed manually and the initial recognition journal entry posted manually after the migration.
• Update record changes field values on a lease that already exists, limited to the fields you pick on the Update field selection setup page. Microsoft recommends nonfinancial fields here, because this type does not adjust the lease.
• Adjust record adjusts the lease, which is a financial lease modification. The system builds a new payment schedule from the imported data but does not confirm it or post the adjustment entry.

Validate and Migrate run on one lease or on many at once through the Periodic menu. Compare and the Differences report only work for Update and Adjust, because an added lease has nothing in the system to compare against. Since version 10.0.41 import records can also be deleted more easily, which helps when a test load goes wrong. The practical consequence is simple. For a first migration almost every lease is an Add record, so nothing in the system checks your numbers against anything. The staging rows are only as good as the person who read the leases.

Asset leasing D365 data migration field checklist

These are the values a migration team needs from each document. We return all of them with the page they came from, in the column order you set:

• Lease header. Lessor, lessee entity, lease reference, execution date, commencement date, expiration date, term in months and currency. Microsoft says all lease calculations run from the commencement date and that it should fall at the start of a period, so the exact date in the lease matters.
• Payment schedule lines. Start date, number of periods, period interval, payment frequency and payment amount for each rent step. The first payment cannot start before the lease start date, or Asset leasing returns an error, so we keep both dates as found.
• Payment breakdown. Base rent, parking, storage or other itemized amounts when your parameters allow a payment amount breakdown by payment amount type.
• Index terms. CPI or other index language, base index month and caps, the source for the index rate type and revaluation setup.
• Executory and nonlease costs. Operating expenses, CAM, real estate tax and insurance language, separated from base rent so your team can decide what belongs in Executory contract staging.
• Options and clause text. Renewal, termination and purchase options with notice windows, plus the clause wording, so the person setting the lease term reads the actual option rather than a summary.

Some fields on the lease book are not in the document at all. The incremental borrowing rate, the asset fair value, the useful life used in the classification test, the annuity type and the compounding interval are accounting inputs. Your controller sets them. A field the model cannot find is marked no value found, and a value it cannot tie to a page is marked no source page. Those two flags become the review list for the migration, and the lease book inputs stay with the people who own them.

Midlife leases and transition books

Most Asset leasing projects convert leases that are already running, often from spreadsheets, Dynamics AX or a separate lease system. Microsoft documents transition options on the book setup, including Cumulative Catchup Option A and Option B, with an incremental borrowing rate at transition that the lease can inherit. The opening balances come from your old records. The remaining payments, remaining term and live options still come from the documents, and those are where conversions go wrong: a rent step in an amendment nobody pulled, a renewal exercised by letter, an abatement that ended last year. Reading the current documents before you stage them is how you find those before the opening entries are booked.

The short term threshold on the book is entered in months and the low value threshold as an amount. Both depend on the term and payments you load. A lease migrated with the wrong expiration date can land in the wrong classification without any error message.

Is Asset leasing available in Business Central?

No. Microsoft documents Asset leasing as a Dynamics 365 Finance capability. Dynamics 365 Business Central has no built in lease accounting, so companies on it buy an AppSource app or a separate lease system. We compare those apps, with published prices where they exist, on Business Central lease accounting. The lease data each app needs is the same set of fields listed above.

How much does a Dynamics 365 Asset leasing migration cost?

Asset leasing is part of Dynamics 365 Finance, so the license question is your existing Microsoft agreement. Migration effort is usually priced inside the partner statement of work. The cost that grows with the portfolio is reading. Abstracting a commercial lease by hand is commonly estimated at 4 to 8 analyst hours, and outsourced abstraction is priced per lease, with Springbord publishing 90 to 250 dollars.

Our plans are on the pricing page. Starter is 49 dollars a month with 2,500 Base AI pages or 500 Pro AI pages and a 25 page per document cap. Plus is 149 dollars a month with 10,000 Base or 2,000 Pro pages, unlimited pages per document, 50 file batch uploads, custom extraction templates and up to 3 seats. Pro adds the REST API. A lease with its amendments often runs 20 to 60 pages, so Plus covers roughly 30 to 100 leases a month on Pro AI. For a migration wave, batch upload and custom templates are the parts that matter, and bulk lease upload shows how a whole folder runs at once.

Who uses this before a D365 Finance go live

• Corporate real estate and lease accounting teams moving from spreadsheets or a standalone lease tool into Asset leasing.
• Dynamics 365 implementation partners who own the lease migration workstream and want a cited inventory instead of a hand built staging file.
• Controllers upgrading from Dynamics AX who want lease data checked against the documents rather than copied forward.
• Auditors testing completeness and accuracy of the migrated population against source leases.

Asset leasing or a separate lease accounting system

Some lessees on Dynamics 365 Finance keep a dedicated lease platform and post journal entries to Finance instead of running the native module. We compare the native module with those add-ons in best lease accounting software for D365 Finance. Whichever system runs the calculations, the migration input is the same lease data. Teams on other ERPs follow the same path, covered on Oracle Lease Accounting for the FBDI template and SAP lease accounting data for RE-FX. The general checklist for any system change is in how to migrate lease data to new software.

Security and handling

Documents are protected with 256-bit encryption in transit and at rest; no SOC 2 attestation held today. Your documents are not used to train our own models. Test with a lease you are cleared to share before you run a full migration batch.

Want to see the fields on one of your own leases first? Upload it at the top of this page and check each value against its cited page before you plan the import.