Problem Statement

When a document using deferrals (General Journal or Purchase Invoice) is approved after submitting, a user can still open the Deferral Schedule (via the Deferral Header or Deferral Line) and modify the schedule terms directly, for example, changing the deferral period from 12 months to 5 months without triggering any re-approval requirement. The document remains in "Approved" status and can be posted as-is.

Business Impact

From a financial controls perspective, users expect an approval workflow to safeguard against any change that affects how or when a transaction will be recognized, not just changes to a single field.

The current behaviour can:

- Allow the financial impact of an approved document to be altered post-approval without triggering re-approval.

- Create a gap in audit trails, since the Deferral Schedule change is not captured by the approval history.

- Undermine confidence in the approval workflow as a reliable financial control, particularly for regulated or audit\-sensitive customers.

- Require customers to implement manual compensating controls (e.g., permission restrictions) to cover the gap.

- Lead customers to question whether the approval workflow is functioning correctly when they discover schedule changes bypass it.

Although the current behaviour is technically consistent with the condition's configured scope, the resulting approval flow does not fully align with customer expectations of what an approval workflow should protect against.

Proposed Enhancement

Extend the Workflow Approval condition (or introduce an additional condition) to also monitor changes made to the Deferral Header/Deferral Line (Deferral Schedule) tables, in addition to the existing Deferral Code field monitoring on the document journal line. Alternatively, provide a configurable option within workflow setup allowing customers to opt in to monitoring Deferral Schedule changes as part of the "Record Restriction" logic, so this can be enabled only for those requiring tighter financial controls.

Expected Benefit

- Closes the gap between what the approval workflow is designed to protect and what it actually enforces.

- Strengthens auditability by ensuring all changes affecting deferral posting outcomes are captured in the approval trail.

- Reduces reliance on manual compensating controls to cover the current gap.

- Reduces support cases related to confusion over approved documents being modified without re-approval.

- Improves customer confidence in Business Central's approval workflow as a financial control mechanism.