Dynamics Community Forum Thread Details

Asset Leasing imports

Hi there,

I'm importing a large number of leases into D365 F&O and want to check my approach.

Context:

Most of these leases commenced before the start of the current financial year.
I don't want to reopen prior periods.
At year-end we posted journals recognising movements in ROUA and lease liability, so those accounts already hold balances.

My planned approach is to import each lease with its full set of payment lines (including those falling in locked periods), then manually adjust the dates on those lines to the current year-end. After posting the resulting journals, I'd reverse the amounts to avoid double-counting. The goal is for each lease to show its correct current balance within D365, so reviewers can see everything in one place rather than reconciling a spreadsheet against D365.

If this is the best method, I plan to create the journals via batch creation, then use Data Management to export them and shift the dates to year-end. I'm just not sure which data entity to use for the export.

My questions:

Which data entity are asset leasing journals exported under?
Is there a better approach overall?

Thank you,

Categories:

Dynamics 365 Finance

@CU20070517-0
stop the proposed approach before it goes further — importing full schedules, manipulating system dates, posting, and reversing will permanently corrupt the subledger-to-GL audit trail and create reconciliation failures that are very difficult to unwind.

On the data entity question — there is no DMF entity for importing or exporting Asset Leasing journals directly. This is intentional. The Asset Leasing module is a strictly governed subledger and all journals must be generated natively by the leasing engine. You can export the GL impact using LedgerJournalEntity but you cannot re-import that data back into the leasing subledger.

The correct approach for historical lease migration without reopening prior periods is the GL Integration toggle method. Go to Asset leasing → Setup → Lease books → select your lease book → set Post to general ledger to No. With this off, the system calculates and updates subledger balances but suppresses all GL voucher creation. Import your leases using the Lease V2 and Payment schedule contract entities with their true historical commencement dates. Generate Initial Recognition, run Payment Schedules, then run the periodic batch jobs for Depreciation, Interest, and Payments for all periods up to your cut-off date. The subledger catches up completely without touching the GL.

Once the subledger balances match your GL Trial Balance cut-off figures, go back to Lease books and toggle Post to general ledger back to Yes. From go-live date forward, the system posts current period depreciation and interest correctly based on the historically accurate amortization schedule. No manual reversals, no fake dates, no audit trail corruption.

Hope that helps — feel free to mark as verified if it resolves the issue.

Quick Links

Leaderboard > Finance | Project Operations, Human Resources, AX, GP, SL