2699296 - Migration of Accounting Transaction Data Cross-Check Balances - The balance of the migration reconciliation account is not zero

While migrating Accounting Transaction data, on the Cross-Check Balances step, the following warning appears: "The balance of the migration reconciliation account is not zero. Correct data and restart simulation".

SAP Business ByDesign

1. Go to the Business Configuration work center.
2. Go to the Overview view.
3. Find Migration of Accounting Transaction Data activity.
4. Press Open.
5. Press Migrate accounting transaction data using the migration tool.
6. Select the respective Migration Unit.
7. Press Cross-Check Balances Preview.

A warning appears: "The balance of the migration reconciliation account is not zero. Correct data and restart simulation."

Such warnings appear whenever the balance on the Migration Clearing Account is not zero: The balances maintained in the G/L Accounts migration template do not tally with the amounts derived for these G/L accounts from the Subledger Migration template

To analyse where exactly differences exist navigate to the Cross-Check Balances Preview:

1. Go to the Business Configuration work center.
2. Go to the Overview view.
3. Find Migration of Accounting Transaction Data activity.
4. Press Open.
5. Press Migrate accounting transaction data using the migration tool.
6. Select the respective Migration Unit.
7. Press Cross-Check Balances Preview.

From here check the balances on the Migration Clearing Accounts, for example

• Initial Data Carryforward A/R Accounts
• Initial Data Carryforward A/P Accounts
• Initial Data Carryforward Inventory Account
• Initial Data Carryforward Asset Account
• Initial Data Carryforward Cash Account

etc..

For these Accounts, the LC Amount should display zero, as, ideally, the amounts posted to the Migration Clearing Account from the G/L Account Migration template and from the Subledger Migration template should clear to zero.

If there is an amount higher than zero, the warning will appear.

Example: 

Let's assume there is an amount of 500,00 EUR appearing on the Migration Clearing Account for Fixed Assets, here Initial data Carryforward Asset Account.

1. In the Cross-Check Balances Preview extend the Migration Clearing Account.
2. For each G/L Account of type Fixed Assets, here G/L Account AAA a line is displayed showing the amount maintained for the account in the G/L Accounts Migration template (AAA represents the G/L Account ID).
3. Check the Amounts displayed in the LC Amount column for the Account IDs displayed in the Source column:
4. Then click on the Fixed Assets link in the Source Column.
5. In the next screen you see the amounts and G/L Accounts derived from the Fixed Assets Migration template:
6. Compare these amounts with the amounts displayed for the G/L Account Migration and then make the respective adjustments, either correct the amounts in the G/L Migration template or correct the amounts for the specific items, such as Inventory IDs, Invoice IDs etc. in the subledger template.
7. If the Migration is already finished you might have to either execute further migration for the missing data.
8. It might also be possible to reverse migrated Accounting Transaction Data, by reversing the respective source documents. Please see KBA 2107052-Mass Reversal of Incorrect Migrated Financial Data.

2107052 - Mass Reversal of Incorrect Migrated Financial Data

Potential issue when we leave the non-zero balance of accounting transaction data cross check during migration: balanced amount left in g/l account.

When we migrate accounting data, we need to migrate both the g/l balance and the subledger posting to offset the g/l balance.

That is, for example, when we migrate the cash g/l balance, we need to migrate the same of cash subledger to offset the g/l balance.

But in the migration, there is only g/l balance uploaded, but no subledger part. So during the cross check for balance, there is the warning such as "G/L account AAAA(AAAA stands for Cash G/L account) replaced by migration clearing account"

Because there is no subledger posting that offsets the GL Account posting - so instead we replace the GL account given with the migration clearing account and offset this with the SAKOMIG. If later there is a subledger posting (via another migration unit) then we take the value from the clearing account and post it to the GL Account that had been provided.

Once the subledger posting relevant for these accounts gets posted (in migration) then the clearing account will be cleared and the GL account will show the balance as expected. It needs to be considered as a two sided posting - If I post a normal payment for example, it will have an effect on the subledger cash account and also the balance of cash account. So when I only migrate one side of that posting (GL accounts) through the migration, there's going to be differences between cash register (ops) and cash ledger (accounting) - we need to avoid such differences and so when the corresponding subledger posting is missing in the migration, we use the migration clearing accounts as a stop gap, so that until such time as there is a corresponding subledger posting (by migrating bank or open checks details in the case of the cash subledger), our between register and ledger will still be 0 - if we don't do this, we will have a difference.

This gets resolved as soon as the corresponding subledger that offset this GL account are posted.

If there's not going to be any further migrations then yes a manual journal entry voucher could be used to move the amount between the migration clearing accounts and the GL accounts but this is not our recommended course of action.

migration, migration tool, warning, The balance of the migration reconciliation account is not zero, Initial Data Carry Forward, difference, balance , KBA , migration , the balance of the migration reconciliat , balance , cross-check balances , correct data and restart simulation , difference , SRD-FIN-GL , General Ledger , How To