---
id: change/bcapps/11712
type: change
title: "#11712 [Master] - Bug 624708: [Expense Management] Users sync - There should be a configuration wizard to ask if the Employees should be created behind if no match is found"
summary: Expense user synchronization gets new logic in the Expense User table and a small change to the Expense Users page. Per the title, it addresses asking whether employees should be created when sync finds no matching employee. Tests were added.
tier: official
language: en
tags:
  - fix
  - main
  - bc30
  - page expense users
  - table expense user
system: development
review:
  state: reviewed
  by: opus
  at: "2026-10-08T02:03:54.058Z"
  flags: []
generated:
  at: "2026-10-08T01:26:53.141Z"
  pipeline: 0.2.0
  prompts:
    extract-change: 1
  input_hash: 4fdcbd1f4d4bc20c097384055148c6314150fb9a
evidence:
  - kind: code
    url: https://github.com/microsoft/BCApps/pull/11712
    title: "microsoft/BCApps#11712: [Master] - Bug 624708: [Expense Management] Users sync - There should be a configuration wizard to ask if the Employees should be created behind if no match is found"
    date: "2026-09-23"
    commit: 4fdcbd1f4d4bc20c097384055148c6314150fb9a
    t: null
    quote: null
links:
  learn: []
  objects:
    - object/page/6951
    - object/table/6923
  features: []
  topics: []
  localizations: []
  videos: []
  posts: []
  guidelines: []
  changes: []
number: 11712
repo: microsoft/BCApps
source_id: bcapps-prs
url: https://github.com/microsoft/BCApps/pull/11712
kind: pr
base_branch: main
major: "30"
merged_at: "2026-09-23T14:58:07Z"
author: v-rohangarg20
author_type: User
community_contribution: false
labels:
  - "AL: Apps (W1)"
  - "Team: Finance"
change_class: code
change_kind: fix
behavior_change: true
breaking: false
files:
  count: 3
  additions: 162
  deletions: 1
  al: 2
apps:
  - ExpenseAgent
objects_touched:
  - key: page/6951
    page: page/6951
    type: page
    id: 6951
    name: Expense Users
    app: ExpenseAgent
    status: modified
  - key: table/6923
    page: table/6923
    type: table
    id: 6923
    name: Expense User
    app: ExpenseAgent
    status: modified
objects_unjoined: []
obsoletions: []
backports: []
fixes_issues: []
work_items:
  - 624708
systems:
  - development
quote: null
joined_against:
  major: "30"
  commit: ecbc028c25dbe83b61313bc566e6c1d41184bb1c
---

# #11712 [Master] - Bug 624708: [Expense Management] Users sync - There should be a configuration wizard to ask if the Employees should be created behind if no match is found

> Expense user synchronization gets new logic in the Expense User table and a small change to the Expense Users page. Per the title, it addresses asking whether employees should be created when sync finds no matching employee. Tests were added.

[Pull request](https://github.com/microsoft/BCApps/pull/11712) · merged into `main` (BC30) on 2026-09-23 by v-rohangarg20 · 3 files (+162 -1), 2 AL · fix · tier official · reviewed (checked by Opus)

## What changed

- Addresses creating employees when user sync finds no match, per the bug title
- Logic added to the Expense User table, with a small update to the Expense Users page
- Tests added to the import expense user test codeunit
- Behaviour changes for users or extensions.

## AL objects touched

- [Page 6951 "Expense Users"](../../objects/page/6951.md), ExpenseAgent: modified
- [Table 6923 "Expense User"](../../objects/table/6923.md), ExpenseAgent: modified

## Context

- Work items: AB#624708
- Labels: AL: Apps (W1), Team: Finance
- Systems: development

Source: metadata of a merged pull request in microsoft/BCApps (bcapps): title, labels, changed paths and counts, with a summary in our words. No source text and no description beyond one short quote (D10, D61).