All Collections
Imports and Exports
Unallocated data feed transactions
Unallocated data feed transactions

How to view transactions that have not been delivered to a user.

Written by Jack
Updated over a week ago

Transactions cannot be allocated if the user's statement identifier in the user's profile does not match the user identifier provided by the data feed.

Transactions that have not been delivered to a user's account via the bank data feed can be viewed and reallocated by following the below steps.

Please note: Transactions are received based on the settlement date, which means there can be a 2-3 working days delay between transactions occurring and appearing in ExpenseIn.

  1. Navigate to Finance and select Card Transactions from the Imports and Exports section.

2. Click on the Unallocated tab.

3. Take the user identifier found against each unallocated transaction in the list and check this matches the user's statement identifier within their user profile.

The required statement identifier formats for each data feed are listed below:

  • Allstar

    The required format: Must be an exact match with the name on card.

    Example: Karen L Smith

  • Mastercard

    The required format: First 6 digits followed by 8 stars and then the last 4 digits.

    Example: 654718******1231

  • Visa

    The required format: the last 4 digits of PAN.

    Example: 1231

Please note: Admin permission is required to access user profiles from the Admin Users section and make this update.

To retry unallocated transactions please follow the below steps:

  1. Select the expenses using the tick box or choose the select all option to select all unallocated expenses.

2. Click the Retry Selected button to try to allocate the transactions you selected.

3. The transactions will now appear in the data feed tab when successfully


If transactions have not been allocated, please repeat the process until the statement identifiers all match the user identifiers.

If you are still unable to allocate transactions after updating your user's statement identifier, please contact

Related Articles

Did this answer your question?