@CR-02121529-0
The root cause is a literal string mismatch between how ER serializes your NoYes enum and what you typed in the applicability rules matrix.
The Tax Calculation engine uses strict literal string matching. ER natively serializes a D365 F&O NoYes enum as a Boolean — true or false — or its integer value 1 or 0. When you configure applicability rules using Yes and No the engine evaluates true == Yes which returns no match and skips the rule entirely.
The fix — add an IF formula in your ER Model Mapping:
Go to Workspaces > Electronic reporting
Open your extended Tax Calculation Model Mapping configuration
Click Designer to open the Model Mapping designer
In the Data Model tree locate your custom extended tax line field
Instead of binding the NoYes field directly — click Edit formula
Enter this exact formula:
IF(@.YourCustomNoYesField, "Yes", "No")
Save the formula
Change the ER configuration version status to Completed
This forces ER to serialize the Boolean into the exact literal strings Yes and No in the JSON payload sent to the Tax Calculation service. The applicability rule now finds a perfect match and returns the correct Tax Group.
Alternative ,if you prefer not to modify the ER mapping, change your applicability rule values from Yes and No to True and False to match the raw Boolean output. But the IF formula approach is cleaner and more readable for end users maintaining the tax configuration.
If it helped marked as answer.
