Summary
Learn how to import a Sage 300 ERP general ledger into MindBridge.
Notes/Prerequisites
Note that the general ledger column mapping section of this guide is based on data exported using our Sage 300 ERP: Export the general ledger guide and after transforming using our Sage 300 ERP: Transform the general ledger guide.
Import data
- Import your general ledger file into MindBridge through the File Manager, or by importing directly to the General Ledger section on the Data page. For step-by-step instructions, follow our Import a general ledger guide until the Map Columns step.
- At the Map Columns step, map the Sage 300 ERP fields as follows:
MindBridge Column | Sage 300 ERP Field | Fields Used in MindBridge | Used in Analytics* | Notes |
---|---|---|---|---|
Account ID | Account Number | Required | Yes | |
Effective Date | Doc. Date | Required | Yes | Appears in format M/D/YYYY |
Debit and Credit | Debits and Credits | Required | Yes | |
Transaction ID | Batch-Entry | Recommended** | Yes | Please refer to our Transaction ID guide if one is not readily available. Also see note ** below this table. |
Memo | Reference or Second Reference | Recommended*** | Yes | This will enable the Empty Text control point and allow you to see the memo field for each transaction/entry. |
Account Description | Description | Optional | No | Can be left out as this field will be picked up from the Chart of Accounts. |
Type | N/A | Optional | Yes | |
User ID | N/A | Optional | No | Use to sort and filter results for reports. |
Entered Date | N/A | Optional | Yes | |
Source | Source | Optional | No | Use to sort and filter results for reports. |
* Optional columns, even if not used in the analytics, can be included for filtering and other visualizations, as indicated under Notes.
** Transaction ID is required but does not necessarily need to be in one single column. In the Review Data step of the ingestion process, MindBridge will recommend a transaction ID based on your data, or you can choose and/or combine different columns to create one. For more information: Understand Transaction ID and data integrity.
*** In our experience clients use Sage 300 ERP in different ways so we recommend looking at the columns "Reference" and "Second Reference" yourself to decide which is the most appropriate column to map as the Memo. Select the column with the most relevant useful information.
Previous step: Sage 300 ERP: Transform the general ledger
What do you think of this guide? If you have any feedback, or you think you can help us improve it, then we would love to hear from you! Let us know if this article was helpful or not below. We are offering rewards for any information that leads to the improvement of a guide or the creation of a new one.
Anything else on your mind? Chat with us or submit a request for further assistance.