BeyondERP.Newsletter
Menu

Job page · Expense management

Delete credit card transactions

A periodic job that deletes imported credit card transactions that aren't attached to an expense report.

Business process
Manage time and attendance
Menu item
action:ExpenseDeleteImportedTransactions
Data entity
None for this page's own settings
Setup steps
1 on this page
Show what matters for
PAGE GUIDEWhat the page does and how to use it8 sections. Choose a role to highlight what matters to you.
Everyone

1What it is and why

What it isA periodic job that deletes imported credit card transactions that aren't attached to an expense report.
What you do hereIt is used by administrators to remove unwanted imported card transactions selected with a filter.
ExampleFor example, an administrator removes transactions that were imported twice or that hold inaccurate data.
Delete 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

Business processManage time and attendance
Menu pathExpense management › Periodic tasks › Delete credit card transactions
Set up firstCredit card transactions Microsoft Learn
Used next byCredit card transactions Microsoft Learn
Related pagesExpenses Microsoft Learn
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 itAfter an import brought in duplicate or inaccurate card transactions.
How oftenOn demand, after a faulty import.
What the output showsThe filtered card transactions that weren't attached to an expense report are deleted. A transaction that remains is usually attached to an expense report.

Source: Microsoft Learn

Setup steps on this page

Remove duplicate or wrong card transactions

Clean up a faulty import before employees report it.

Steps from Microsoft

  1. Go to Expense management > Periodic tasks > Delete credit card transactions.
  2. Select Filter and enter the details that identify the transactions to remove, for example the import date, card number or employee of a duplicate file.
  3. Only transactions that aren't attached to an expense report are deleted; detach or finish reports first if needed.
  4. Run it, then open Credit card transactions and make sure the duplicates are gone and the valid transactions remain.

Source: Microsoft Learn

Fields on the page

FieldWhat it means
Filter (Records to include)Selects the transactions to delete, such as the import date or card number of a duplicate file.Microsoft Learn

Common errors and fixes

MessageWhat to do
A transaction isn't deletedOnly transactions that aren't attached to an expense report are deleted. Remove it from the report first, or leave it. Microsoft Learn

Test checklist

  1. The duplicate transactions no longer appear.
  2. Attached transactions are still there.
  3. Valid transactions outside the filter were kept.

Source: Microsoft Learn

Functional consultant

4Setup decisions

Setup stepRecommended value and whyDecision, common mistake and test
Remove duplicate or wrong card transactionsFilter narrowly on the import date and card numbers of the faulty file, and run it before employees start reporting.Only transactions not attached to an expense report are deleted, and deleted transactions come back only by importing again.Who may delete imported card transactions?Running it with no filter, which deletes every unattached card transaction in the company.Test: Only the duplicate file is removed

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. Only the expense administrator should run this job. No Feature management feature is needed.

Microsoft Learn

Solution architect

5Design impact

Shared or per companyPer company: the job deletes imported card transactions of the current legal entity. Microsoft Learn
Can it be undoneNo: Deleted transactions can't be restored; you would have to import them again from the card file. Filter carefully. Microsoft Learn
If you change it laterOnly transactions that aren't attached to an expense report can be deleted. Microsoft Learn
Technical architect

6Technical

Menu itemaction:ExpenseDeleteImportedTransactions Checked in Dynamics 365
FormDialog Checked in Dynamics 365
Data entitiesTrvCreditCardTransactionEntityCredit card transactions (the transactions this job deletes; the job itself has no entity) Microsoft data model
Roles to set it up and use itTo use itExpense administrator ExpenseAdministratorGive people one of these roles. On this system, 1 role can run this page.Checked in Dynamics 365
Developer

7Developer

Open it by URLhttps://<your-environment>/?mi=action:ExpenseDeleteImportedTransactions
Data migrationLoad order: The delete job has no data entity in Data management, so it can't be loaded from a file or a configuration template. It only removes imported transactions; nothing to migrate.Microsoft Learn
Everyone

8Sources