BeyondERP.Newsletter
Menu

Setup step on the Credit card transactions page · Expense management

Import corporate card transactions

Bring the card provider's file in so employees can report the charges.

Used by
Business Performance Planning app role, Data management administrator, Data management migration user and 3 more roles
Business process
Manage time and attendance
Menu item
TrvPBSMaindataLines
Main table
TrvPBSMaindata
Data entity
TrvCreditCardTransactionEntity
Setup steps
1 on this page
Show what matters for
SETUP GUIDEHow to set it up8 sections. Choose a role to highlight what matters to you.
Everyone

1What it is and why

What it isA page that lists imported corporate credit card transactions and where new transaction files are imported.
What you do hereUse this page to import card transactions manually or on a recurring schedule, so employees can add them to expense reports.
ExampleFor example, when an employee leaves, their open card transactions can be reassigned to another employee so they can still be expensed and reimbursed.
Credit card transactions page in Dynamics 365
The page in Dynamics 365. page title tab to open what to set or check
Functional consultant · Solution architect

2Where it fits

End user · Functional consultant

3How to do it

About the examples: Examples and screenshots in this guide use BEAT, a demo company in a Dynamics 365 test environment. Use your own company's codes and values instead of copying them.

When to run it

When to run itWhen the card provider delivers a new transactions file, so employees can add the card transactions to their expense reports.
How oftenEach time a card file arrives, or on a recurring schedule that matches the provider's delivery.
Batch settingsUse Create recurring data job to import the provider's files automatically at the recurrence you set.
What the output showsImported credit card transactions that show up as unattached expenses for each employee. Missing transactions usually mean a mapping or card type error; look at the execution log or staging data.

Source: Microsoft Learn

Setup steps on this page

Import corporate card transactions

Bring the card provider's file in so employees can report the charges.

Steps from Microsoft

  1. Go to Expense management > Periodic tasks > Credit card transactions.
  2. Select Import transactions, and in Name enter a unique description for the import job.
  3. In Source data format, select the format of the card provider's file, then select Upload and choose the file; each file format needs its own import job.
  4. Select View map to check how the file columns map to the credit card transactions entity, and fix the mapping on Mapping visualization or Mapping details if needed.
  5. Select Import to load the file now, or Create recurring data job to import on a schedule; then look at the execution log or staging data for errors.

Source: Microsoft Learn

Fields on the page

FieldWhat it meansTable column
NameA unique description for the import job.Microsoft Learn Name
Source data formatThe format of the file that holds the card transactions.Microsoft Learn
Card typeThe card type of each transaction; it must match a card type in setup.Microsoft Learn CardType
Card numberThe card the transaction was made with; it must match a card on the employee's worker record.Microsoft Learn
Transaction amountThe amount charged; required in the file together with card number, card type and currency.Microsoft Learn

Common errors and fixes

MessageWhat to do
An employee doesn't see an imported card transactionThe card number in the file must match a card on the employee's worker record (Expense > Credit cards), and the card type must match a credit card type in setup. Correct the setup and import again, or reassign the transaction. Microsoft Learn
The import job stops with mapping errorsEach file format needs its own import job. Open View map and fix the columns on Mapping visualization or Mapping details, then import again; the execution log and staging data show the failing rows. Microsoft Learn
Card numbers are stored in fullChoose Prevent card number entry or Hash card numbers (store last four digits) in the parameters; Store card numbers isn't PCI DSS compliant. Microsoft Learn

Test checklist

  1. The execution log shows no errors.
  2. Employees see the new card transactions as unattached expenses.
  3. The card type of each transaction matches the setup.

Source: Microsoft Learn

Functional consultant

4Setup decisions

Setup stepRecommended value and whyDecision, common mistake and test
Import corporate card transactionsOne import job per file format, set up as a recurring data job that matches the provider's delivery, with card numbers hashed (last four digits).Each file format needs its own job; a recurring job brings the file in without manual work, and hashing keeps card data PCI DSS compliant.How are card numbers stored?Importing the same file twice, so employees see duplicate unattached expenses; remove them with Delete credit card transactions before they are reported.Test: An imported transaction reaches the employee

Feature management and licence

Licence or add-inIn this system Employee and Contractor enter their own expenses, and Expense administrator sets up the module and processes documents. The expense mobile app needs the Employee role, a company on the user account and a link to an employee with active employment. The expense administrator imports card files; employees then see the transactions as unattached expenses. No Feature management feature is needed.

Microsoft Learn

Solution architect

5Design impact

Shared or per companyPer company: each legal entity has its own records. Microsoft data model
Can it be undoneHard to reverse: Imported lines can be deleted only while they aren't on an expense report.
If you change it laterEach file format needs its own import job. Microsoft Learn
Technical architect

6Technical

Menu itemTrvPBSMaindataLines Checked in Dynamics 365
FormTrvPbsMainDataLines Checked in Dynamics 365
TableTrvPBSMaindataShown as “Credit card” in Record infoChecked in Dynamics 365
Data entitiesTrvCreditCardTransactionEntityCredit card transactions Microsoft data model
Who can open itPrivilegesMaintain credit card transactions TrvPBSMaindataLinesMaintainView credit card transactions TrvPBSMaindataLinesViewDutiesMaintain Master entity data for data management DataManagementApplicationMasterEntitiesMaintainView Master entity data for data management DataManagementApplicationMasterEntitiesViewMaintain Reference entity data for data management DataManagementApplicationReferenceEntitiesMaintainView Reference entity data for data management DataManagementApplicationReferenceEntitiesViewMaintain expense management process TrvTravelAndExpenseProcessMaintain
6 security rolesBusiness Performance Planning app role BPPBudgetPlanningAppRoleData management administrator DataManagementAdministratorData management migration user DataManagementMigrationUserExpense administrator ExpenseAdministratorDemand planning app role ScpDemandPlanningAppRoleInformation technology manager SysServerITManager
Checked in Dynamics 365
Roles to set it up and use itTo set it up or change itExpense administrator ExpenseAdministratorInformation technology manager SysServerITManagerBusiness Performance Planning app role BPPBudgetPlanningAppRoleData management migration user DataManagementMigrationUserDemand planning app role ScpDemandPlanningAppRoleGive people one of these roles. On this system, 6 roles can open this page.Checked in Dynamics 365
Actions on the pageOptions: Personalize, Page options, ShareChecked in Dynamics 365
Developer

7Developer

Open it by URLhttps://<your-environment>/?mi=TrvPBSMaindataLines
Integrate withTrvCreditCardTransactionEntity data entity Microsoft data model
Data migrationTrvCreditCardTransactionEntity (Credit card transactions): the import entity behind this page.Load order: This page is the import itself; load employees, their credit cards (TrvEmpCreditCardEntity), card types and card category codes first.Load first: Employees, Employee credit cards, Credit card types, Credit card category codesMicrosoft Learn
Table definitionTrvPBSMaindata columns and relations Microsoft data model
Everyone

8Sources

To cite this step: EM-JOB-010, Import corporate card transactions. Beyond ERP Atlas Hub, 2026-11-11. https://www.beyonderp.cloud/atlas/step/EM-JOB-010