GP to BC Compare: General Ledger Account Master Record Tables
There are many differences between Dynamics GP and Dynamics 365 Business Central, but this page highlights the technical differences important to me between the primary master record tables for GENERAL LEDGER ACCOUNTS for carrying over this information to BC. BC is not GP in the cloud, as you can see by the underlying table structure differences for these master records.
|
Business Central |
|
Dynamics GP |
||||||
|
Table ID |
Page ID |
Page Name |
Table Columns |
|
Table ID |
Table Name |
Form Name |
Table Columns |
|
15 |
16 |
G/L Account |
74 |
|
GL00100 |
GL Account Master |
Account Maintenance |
44 |
This next table shows the best and most important field matches for the account records between Dynamics GP and Business Central.
|
Business Central |
|
Dynamics GP |
|
The Dynamics Mindset |
||
|
Table 15 |
|
Table GL00100 |
|
GP to BC ACCOUNT Field
Mapping Notes |
||
|
Field |
Field Length |
|
Field |
Field Length |
|
**Filtered and Mapped
Fields |
|
Name |
100 |
|
ACTDESCR |
50 |
|
BC Description is 2x
longer than GP |
|
Search Name |
100 |
|
ACTALIAS |
20 |
|
|
|
Account Type |
Option |
|
ACCTTYPE |
small int |
|
BC has Posting, Heading,
Total, Begin-Total and End-Total options |
|
Account Category |
|
|
ACCATNUM |
small int |
|
Account Categories drive
native financial statements |
|
Income/Balance |
Option |
|
PSTNGTYP |
small int |
|
Balance Sheet / Profit
and Loss |
|
Debit/Credit |
Option |
|
TPCLBLNC |
small int |
|
Debit or Credit |
|
Blocked |
Option |
|
ACTIVE |
tiny int |
|
|
|
Direct Posting |
Option |
|
ACCTENTR |
|
|
Allow account entry |
This table shows the Dynamics GP account master table fields not included in the matched field mapping above.
Many simply don’t fit, or their purpose is conceptually or fundamentally different or incompatible with a clean, straight mapping of data from GP to Business Central.
|
Dynamics GP |
|
The Dynamics Mindset |
|
GL00100 |
|
GP to BC ACCOUNT Field
Mapping Notes |
|
Field |
|
**UN-Mapped Fields |
|
ACTINDX |
|
GL Account Index |
|
ACTNUMBR_1 |
|
GL Segment |
|
ACTNUMBR_10 |
|
GL Segment |
|
ACTNUMBR_2 |
|
GL Segment |
|
ACTNUMBR_3 |
|
GL Segment |
|
ACTNUMBR_4 |
|
GL Segment |
|
ACTNUMBR_5 |
|
GL Segment |
|
ACTNUMBR_6 |
|
GL Segment |
|
ACTNUMBR_7 |
|
GL Segment |
|
ACTNUMBR_8 |
|
GL Segment |
|
ACTNUMBR_9 |
|
GL Segment |
|
ADJINFL |
|
|
|
BALFRCLC |
|
|
|
Clear_Balance |
|
|
|
CNVRMTHD |
|
|
|
CREATDDT |
|
System-generated |
|
DECPLACS |
|
For Unit accounts |
|
DEX_ROW_ID |
|
System-generated |
|
DEX_ROW_TS |
|
System-generated |
|
DSPLKUPS |
|
|
|
FXDORVAR |
|
|
|
HSTRCLRT |
|
|
|
INFLAEQU |
|
|
|
INFLAREV |
|
|
|
MNACSGMT |
|
Main Account Segment |
|
MODIFDT |
|
System-generated |
|
NOTEINDX |
|
System-generated |
|
PostIvIn |
|
Posting level (Summary
or Detail) |
|
PostPRIn |
|
Posting level (Summary
or Detail) |
|
PostPurchIn |
|
Posting level (Summary
or Detail) |
|
PostSlsIn |
|
Posting level (Summary
or Detail) |
|
USERDEF1 |
|
UDF |
|
USERDEF2 |
|
UDF |
|
USRDEFS1 |
|
UDF |
|
USRDEFS2 |
|
UDF |
|
Workflow_Status |
|
System-generated |
This table shows the Business Central account master table fields not included in the matched field mapping above.
Many simply don’t fit, or their purpose is conceptually or fundamentally different or incompatible with a clean, straight mapping of data from GP to Business Central.
|
Business Central |
|
The Dynamics Mindset |
|
Table 15 |
|
GP to BC ACCOUNT Field
Mapping Notes |
|
Field |
|
**UN-Mapped Fields |
|
Account Subcategory
Descript. |
|
Subcategories work
underneath Categories on native financial statements |
|
Account Subcategory
Entry No. |
|
Subcategories work
underneath Categories on native financial statements |
|
Add.-Currency Balance at Date |
|
BC auto-summary field |
|
Add.-Currency Credit Amount |
|
BC auto-summary field |
|
Add.-Currency Debit Amount |
|
BC auto-summary field |
|
Additional-Currency
Balance |
|
BC auto-summary field |
|
Additional-Currency Net
Change |
|
BC auto-summary field |
|
API Account Type |
|
System-generated |
|
Automatic Ext. Text |
|
BC extra text option for
Accounts |
|
Balance |
|
BC auto-summary field |
|
Balance at Date |
|
BC auto-summary field |
|
Branch Code |
|
BC Global Dimension |
|
Budget at Date |
|
BC auto-summary field |
|
Budgeted Amount |
|
BC auto-summary field |
|
Budgeted Credit Amount |
|
BC auto-summary field |
|
Budgeted Debit Amount |
|
BC auto-summary field |
|
Comment |
|
System-generated |
|
Consol. Credit Acc. |
|
BC account in
Consolidation Company |
|
Consol. Debit Acc. |
|
BC account in
Consolidation Company |
|
Consol. Translation
Method |
|
Currency translation for
consolidation (Average, Closing, Historical, Composite, Equity) |
|
Cost Type No. |
|
BC Costing module |
|
Created At |
|
System-generated |
|
Created By |
|
System-generated |
|
Credit Amount |
|
BC auto-summary field |
|
Currency Code |
|
? |
|
Debit Amount |
|
BC auto-summary field |
|
Default Deferral
Template Code |
|
BC Default deferral
template (similar to GP Revenue and Expense
Deferrals) |
|
Default IC Partner G/L
Acc. No |
|
BC Default GL
Intercompany Posting account |
|
Department Code |
|
BC Global Dimension |
|
Exchange Rate Adjustment |
|
No Adjustment, Adjust
Amount, Adjust Additional-Currency Amount |
|
Exclude from
Consolidation |
|
BC Consoldation
option |
|
Gen. Bus. Posting Group |
|
BC GL posting
configuration |
|
Gen. Posting Type |
|
None, Purchase, Sale |
|
Gen. Prod. Posting Group |
|
BC GL posting
configuration |
|
GIFI Code |
|
Canadian financial
reporting |
|
Indentation |
|
BC Native COA /
financial statement display option |
|
Last Date Modified |
|
System-generated |
|
Last Modified Date Time |
|
System-generated |
|
Modified At |
|
System-generated |
|
Modified By |
|
System-generated |
|
Net Change |
|
BC auto-summary field |
|
New Page |
|
BC Native COA /
financial statement printing option |
|
No. |
|
BC Account Number (Main
account from GP) |
|
No. 2 |
|
BC Alternate Account for
internal reporting |
|
No. of Blank Lines |
|
BC Native COA /
financial statement display option |
|
Omit Default Descr. in Jnl. |
|
BC feature to limit
automated text fill on entries |
|
Picture |
|
|
|
Reconciliation Account |
|
BC feature to help
reconcile account activity |
|
Review Policy |
|
None, Allow Review,
Allow Review and match balance |
|
RowVersion |
|
System generated |
|
SAT Account Code |
|
For Community
Development Financial Institution reporting |
|
SAT Classification Code |
|
For Community
Development Financial Institution reporting |
|
Source Curr. Balance at
Date |
|
BC auto-summary field |
|
Source Currency Balance |
|
BC auto-summary field |
|
Source Currency Net
Change |
|
BC auto-summary field |
|
Source Currency Posting |
|
? |
|
Source Currency
Revaluation |
|
? |
|
System ID |
|
System generated |
|
Tax Amt. |
|
BC auto-summary field |
|
Tax Area Code |
|
? |
|
Tax Group Code |
|
BC GL posting
configuration |
|
Tax Liable |
|
? |
|
Totaling |
|
The linked accounts for
a Total type account |
|
Unrealized Revaluation |
|
? |
|
VAT Bus. Posting Group |
|
BC GL posting
configuration |
|
VAT Prod. Posting Group |
|
BC GL posting
configuration |
Author’s note and Disclaimer:
Mapping ERP systems is a complex and subjective task for any one person.
Significant differences between GP and BC will require you to learn more deeply about the product to perform a successful implementation.
There is more than one way to map particular fields, but I think you’ll get a lot out of the references provided.
I am not infallible, so let me know if you spot an issue I need to update. I don’t want to present anything factually incorrect here, however how you map your data in real life is up to you.
I needed to know the differences that really matter between the master records in both Dynamics GP and Business Central. I hope you gain value from my analysis and notes.
As I do more BC implementations, and if / when BC changes, I’ll keep this up to date, and make adjustments and add additional notes where needed. I’ll also work on filling in any holes to make this complete because these are MY personal reference pages too.
Some of the tables on the individual pages probably won’t render very well on some mobile devices, but try tipping it horizontally instead!