AI, in your work.

Preparing the approval route

On November 6, Microsoft merged a fix into the main branch of BCApps to assign an interim approver before submitting an expense report for approval. The Expense Agent change is recorded in PR #13690.

The change allows that choice to be saved while the report is Released. Assignment preserves both the status and the active approver; subsequent submission starts the interim stage. Commit 76013d8 also updates the page action to use the shared status check.

What each status allows

The logic permits assignment only in Released and Pending Approval. The names below are code identifiers, not a verified mapping to labels in the web app. The distinction appears in the approval management module.

Conflicts are checked again

The agent must be enabled and the approver must meet eligibility requirements. Validation of the actor performing the assignment remains in place, as do conflicts with the report owner and final approver. The code checks conflicts again when recalculating routing on submission, resubmission, or reopening an approved report. Approval code.

If the interim and final approvers coincide after that calculation, the operation raises an error. The change description warns that an approved report may need an approval configuration adjustment before reopening. Compatibility details.

Synthetic example: a project expense

Suppose an employee prepares an expense report for a project. She wants the project lead to review it first, followed by someone in Finance with final approval responsibility. With the report Released, and assuming both people are eligible and there are no conflicts, she configures the interim stage. She has not submitted the report yet.

On submission, review goes first to the project lead and then to Finance. This is a hypothetical example of the described workflow, with no real users, amounts, or results.

Nexo's interpretation is that separating route preparation from activation could help integrations: it allows the reviewer to be chosen before approval starts. That potential benefit does not amount to a measured reduction in processing time.

Availability and verification limits

Microsoft describes Expense Agent for Business Central online as a production-ready preview feature, subject to supplemental terms. That general description does not establish distribution of this particular fix. Expense Agent documentation.

The module manifest at this commit declares version 30.0.0.0. This is a development source value: it does not, by itself, identify an installed update containing the change. The consulted sources do not confirm its deployment date. Application manifest.

The PR documents added tests and adjustments following earlier errors, but its description says the corrected tests had not been rerun in that session. This editorial review does not verify subsequent runtime results. Validation record.

Although the fix addresses API use, a versioned HTTP contract for integrators has not been verified. This article describes the checked AL logic; it provides no production-ready endpoint or request.