Corporate Card Set-up in production - Transactions imported without Starter File

[rraman96]

During our initial JPMCC corporate card feed rollout in Production, transaction files began importing before the cardholder account shells and employee card mappings were loaded into SAP Concur.  We did not load the starter file first. As a result, over 1,000 transactions imported without matching cardholder profiles and are currently sitting in the Unassigned Transactions queue.

We have now requested for the starter file.  Question:  Will importing the starter file by SAP COncur - automatically re-assign the orphaned / unassigned transactions ?  Or it just will create the shell. 

Thanks

[samasuraj]

Hi @rraman96 

Topic: Corporate Card Set-up in production - Transactions imported without Starter File

Please check the below. Hope this helps.

-----

SAP Concur – JPMCC Corporate Card Starter File and 1,000+ Unassigned Transactions

The JPMCC Starter File establishes the Corporate Card Account Records (called as Card Shells) and Associated Cardholder information. Historical Transaction Recovery depends on Account Matching, Employee Assignment, Importer Behavior

and Transaction-Release Settings.

Since more than 1,000 Transactions are involved, validate a small sample before proceeding with any bulk corrective action.

Also, avoid reimporting the Original Transaction Files without SAP Concur's confirmation, as this could create duplicate transactions.

Do not assume that importing the Starter File will automatically reassign the 1,000+ previously imported transactions.

SAP confirms that when a Corporate Card Account is assigned to an employee, Transactions already associated with that Card can become available to the Employee.

Recovery Sequence:

1. Import the JPMCC Starter File and verify that the expected card accounts are created.
2. Confirm the card-to-employee assignments in Company Cards → Manage Accounts.
3. Check the Transaction Release Period and whether the JPMCC feed uses a configurable importer.
4. Review Manage Transactions to determine whether the historical transactions become associated with the correct employees.
5. If transactions remain unassigned, request SAP Concur Support assistance with historical transaction matching or reassignment.
6. Reconcile the original 1,000+ transactions against the assigned transactions before considering any file reimport, to prevent duplicates.

SAP documents Administrative Assignment and Reassignment Functionality under Manage Transactions.

SAP also documents a Transaction Release Period that controls how far back Eligible Transactions can be released.

This setting applies only to Transactions imported through a Configurable Importer.

Official SAP references: Assign and Unassign Card Accounts and Company Card Settings and Transaction Release.

Thanks & Regards

--

Samantha Prathikantam

SF_EC & ECP / SAP Concur Consultant