Use eConnect SmartConnect to import journals to future periods without opening the periods manually

(4) Share

Report

Posted on by Kristie McNulty

1,008

Has anyone figured out a way to use eConnect or SmartConnect to import future period journal entries without the integration failing? We have no intention of posting the journal entries until it's time to post entries in any given period, but we do have batches which will contain future period revenue activity which we want to be able to import without requiring manual user intervention to manage the opening and closing of periods each time an integration is run.

As an example, we want to import GL activity to December 2030, but we do not want to have to ask accounting to open the period, then we run the integration to import the journal, then have to ask accounting to close the period, as we can have up to 60 periods to open during each month-end. These transactions are originating from a source outside of Dynamics GP. We are using Dynamics GP 18.5 with analytical dimensions.

Any insights or solutions would be greatly appreciated!

Categories:

Microsoft Dynamics GP

I have the same question (0)

All responses (2)

Answers (1)

Verified answer

Holly Huffman 6,554 Super User 2026 Season 1 on at

Like (1)

Report
Copy link

Link copied!
Hi there! Good morning, evening, or afternoon - depending on where you are :) Hope you are well today! I see you posted this a while ago - hoping you have resolved by now but incase not, here are a few thoughts:

The challenge of importing journal entries into future periods without manually opening and closing those periods is a common scenario in Dynamics GP. Here are some potential solutions and workarounds to address this:

1. Use the Allow Posting to History Feature

In Dynamics GP, you can enable the Allow Posting to History option in the General Ledger Setup window.

Navigate to Microsoft Dynamics GP > Tools > Setup > Financial > General Ledger.

Check the box for Allow Posting to History.

This allows you to import journal entries into closed periods without opening them manually.

2. Modify the eConnect or SmartConnect Map

Update your eConnect or SmartConnect integration map to bypass the period validation logic.

Use a custom script or pre-map task to set the period status to "open" temporarily during the import process.

After the import, the script can revert the period status back to "closed."

3. Use a Holding Period

Create a "holding period" in your fiscal calendar (e.g., Period 99) to temporarily store future period journal entries.

Import all future period transactions into this holding period.

When the actual period opens, move the transactions to the correct period using a journal entry or reclassification process.

4. Automate Period Management

Use a SQL script or PowerShell script to automate the opening and closing of periods during the integration process.

The script can open the required periods, run the integration, and then close the periods automatically.

This eliminates the need for manual intervention by the accounting team.

5. Validate Analytical Dimensions

Ensure that the analytical dimensions in your journal entries are correctly mapped and validated.

Incorrect or missing dimension values can cause the integration to fail, even if the period is open.

6. Test in a Sandbox Environment

Before implementing any changes, test the integration in a sandbox environment to ensure it works as expected without impacting your production data.

Hope this helps some!

Was this reply helpful? Yes No
Kristie McNulty 1,008 on at

Like (0)

Report
Copy link

Link copied!

Thank you Holly. We have option 1 in place already, but we're still blocked from creating journal entries into future periods. We will take your other scripting/PowerShell ideas and give them a try. Thank you for responding, it truly is useful information you have supplied.

Was this reply helpful? Yes No