Hi James,

There are pros and cons to all methods and you may need to work out which one is the best configuration for your situation.   In some cases you can have a combination of methods being used to achieve the desired result.

Using Fiscal Period you run the risk of missing transactions entered into a prior Fiscal Period.  Using Posting Seq you could select the incorrect seq.   If the data set is not too large I prefer Posting Seq and pull in the transactions.   If there is a duplication you can always reverse the batch.   If you maintain backups of the Consol data you can always restore and start again.

If it is totally screwed up you can create a new consol database and start from scratch.

Thanks for the response.  Sorry, I have a couple of further questions.  If using "Net Changes" as the export method, do you know how duplication/missing data is avoided/mitigated during consolidation? If using "Transactions" by "Fiscal Period", how does GL Consolidation know that you are importing only new transactions for a fiscal period where new batches have been posted into that fiscal period?  Are there any sample data sets available to demo GL Consolidations?

GL Consolidations is not aware of duplication when you  import, it is up to you (the end user) to keep track of what has been imported. If you export net changes for the same period and then import it, you will get duplication of the previously imported net changes. The option to export by posting sequence is there for that reason, if you have say one batch that needs to be exported/imported after the initial export/import then export only the one posting sequence in order to avoid duplication.

When you export a previously exported period (using net changes or transactions by period) you do get a warning that the period has previously been exported.

An alternate option is to reverse the batch that was imported, then export the period (net changes or transactions) again and import again - if you must include transactions that were added after the initial export was done.

GL Consolidations is not aware of duplication when you  import, it is up to you (the end user) to keep track of what has been imported. If you export net changes for the same period and then import it, you will get duplication of the previously imported net changes. The option to export by posting sequence is there for that reason, if you have say one batch that needs to be exported/imported after the initial export/import then export only the one posting sequence in order to avoid duplication.

When you export a previously exported period (using net changes or transactions by period) you do get a warning that the period has previously been exported.

An alternate option is to reverse the batch that was imported, then export the period (net changes or transactions) again and import again - if you must include transactions that were added after the initial export was done.