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.
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:
- Create a Batch ID
- Note: Do NOT re-use existing Batches for this process. This may result in MEM scripts not being properly applied.
- Immediately go to Additional -> "Get Fidesic Vouchers"
- 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.
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.