Multi-Entity Management Import Troubleshooting

These are common errors you may encounter if you are new to using MEM and Fidesic

If you're using Binary Stream's Multi-Entity Management (MEM) module this will help you troubleshoot any import problems. 

Batch Imports into unexpected EntityID and Pay GLs are not what you expect. 

Fidesic for MEM uses the default entity set on the vendor card to determine what batch to import into. Make sure that the default Entity Accounts Payable GL is assigned on the vendor card level and try importing again. 

mceclip0.png

 

Batch Imports, but transactions are not viewable. 

This is usually caused when an Invoice Batch was saved prior to importing. The correct workflow is to: 

  1. Create a Batch ID
    1. Note: Do NOT re-use existing Batches for this process. This may result in MEM scripts not being properly applied. 
  2. Immediately go to Additional -> "Get Fidesic Vouchers"
  3. This will correctly split invoices into Entity related batches with the Entity number affixed to the Batch ID name created in step one. 

Additionally, adding the word "Fidesic" into the BatchID will always result in our MEM processing to take place. If all else fails, add "Fidesic" into the BatchID and see if the import comes across properly. 

 

Batch Imports into the initially created BatchID. 

Fidesic for MEM should import in to individual batches for each entity. If that's not the case, try adding "Fidesic" to the batch ID name. If batches still import into a single, created, batchID, please contact Fidesic support to make sure Fidesic MEM has been properly installed. 

Note: Do NOT re-use existing Batches for this process. This may result in MEM scripts not being properly applied. 

 

If your MEM script has not been updated since before November 2023, you might run into an issue importing if your Payment Voucher Numbers in GP have gotten ahead of your Invoice Voucher Numbers. This should be very uncommon unless someone manually edits the sequence but the fix for this is to update the MEM script. The updated script is available with the latest GP module installer.

Individual Transaction Error Reporting. 

If any transaction encounters an error with GL coding based on the MEM configuration, these posting errors will be available to you prior to actually attempting to post the batch within GP. More info on the MEM posting error is available in the "notes" field of the transaction within GP. 

mceclip0.png

 

mceclip1.png

Configuring To/From Accounts in MEM

To configure to/from accounts navigate to: MS dynamics GP -> Tools ->Setup ->Multi-Entity Management -> Company ->Basic Intercompany Accounts Setup

mceclip2.png

 

Transactions are not importing into the batch associated with our payment entity. Account substitution override setup

To pay out of a different entity than the originating transaction, you can set this up using the MEM Account Substitution Override Setup. 

Navigate to MS dynamics GP -> Tools ->Setup ->Multi-Entity Management -> Company ->Account Substitution Override. 

Make sure to select Payable as the Module and Pay as the Distribution Type.   

Input your destination as the Entity you'd like to pay out of. 

Example, if you'd like to pay every Entity 500 invoices out of 400 instead, you'd modify the destination segment so it reads 400 on the originating 500 line. 

mceclip1.png

If this is configured properly, Fidesic will automatically move invoices into their destination batches on import and pay them out of the correct entity. 

Note: you may also need to configure to/from accounts in MEM for this to function properly. If you import a transaction without the proper to/from accounts set up, this will show you an error on the notes field of the invoice. If this is the case, it will stay in the original batch you created for import with the error in notes.