This issue can occur even when the Batch Gift Entry (BGE) license has been assigned, and all required object permissions, field-level permissions, and object visibility settings have been configured correctly. A common cause is a user synchronization issue between the customer org and the Apsona License Management Org (LMO).
As part of troubleshooting, first verify that the BGE license is assigned, all required object and field permissions are granted, and the necessary objects are visible according to the BGE setup documentation. If the Batches object still does not appear in the menu bar, check the user's record in the LMO by locating the customer's Org ID under Licenses, opening the org record, and searching for the affected user under Apsona Users.
In many cases, the user is not present in the LMO due to a synchronization issue. When this occurs, assigning a BGE license is not effective because Apsona does not recognize the user as licensed.
To resolve the issue, ask the Salesforce administrator to navigate to Apsona → Settings → Manage Licenses and, under the Assigned Users tab, click Edit and then Save without making any changes. This action triggers a user synchronization process. Afterward, the affected user should clear the Apsona cache by navigating to Apsona → Settings → Clear Cache.
Once the synchronization completes and the cache is cleared, the Batches object should appear in the Apsona menu. When BGE access issues persist despite correct permissions and licensing, always verify that the user exists in the LMO, as user synchronization issues are a common root cause.