AI, in your work.

Three enhancements in public preview

The update 29.0 release notes list all three Finance enhancements in public preview. That distinction matters when planning an evaluation: inclusion in BC29 does not establish that a feature is enabled in every environment.

The sources reviewed do not provide a complete matrix confirming these three enhancements across all localizations and deployment options. Their titles also cannot establish Spanish tax obligations. The following scope describes documented behavior; applying it to a specific case requires checking the version, localization and configuration.

Excise duties: multiple types per item

The excise tax setup documentation allows multiple types per item, each with its own quantity and unit of measure. The same type cannot be repeated on that item. Fixed assets remain limited to one type; upgrading to version 29 moves existing item setup to the Excise Taxes page.

The accounting limitation deserves attention: according to the registration procedure, registering these taxes calculates amounts for tax reporting and supports transaction review, but creates no general ledger entries. Configuring the calculation therefore does not establish that a company's accounting workflow is complete.

Employee withholding: requirements and dependencies

The employee transaction procedure covers general and payment journals. It requires withholding to be enabled, a nonexempt employee, a nonzero amount and withholding posting groups with matching setup. When tax results, the payable withholding G/L account must be defined.

The withholding setup includes gross or net bases, rates and thresholds. The employee procedure states an explicit limitation: the Document threshold currently evaluates the line just like Record/Line; document-level accumulation should not be assumed.

Integration with expense categories adds its own requirements. The categories and rules documentation states that the Expense Withholding Tax extension requires Expense Agent (Preview) and Withholding Tax. This dependency should not be confused with automatic activation of the entire workflow.

To review the result, Withholding Tax Entries shows the base, tax amount and posting groups. Employee transactions are identified by Party Type = Employee and the employee number.

Self-billing: which number the series controls

The number series documentation allows Self-Billing Agreement to be enabled on the vendor card and Self-Billing Invoice Nos. to be selected. That selection takes precedence over the global series in Purchases & Payables Setup.

The vendor documentation specifies that the series assigns Vendor Invoice No.; the posted purchase invoice's internal number retains its usual series. If the vendor series is missing, the global self-billing series is used; if both are missing, the self-billed invoice cannot be posted.

The process presupposes a self-billing agreement. Vendors with that agreement also cannot receive inbound accounts payable e-documents. This restriction matters when reviewing a combination of self-billing and document integration.

Nexo's interpretation: select by business need

Our editorial interpretation is that these enhancements should be evaluated separately. A company may need to review purchase numbering without using employee withholding; another may focus on quantities and units for excise duties. Selecting by process helps define a specific test and identify the configuration or integration involved.

It also separates three questions: whether the feature is available in the environment, whether it produces the expected functional result and whether that result serves the company's tax workflow. Product documentation provides evidence for the first two, but does not itself establish the tax suitability of every case.

Fictional examples for preparing tests

Prisma Distribution is a fictional company. These examples are Nexo's proposals for designing checks; they do not describe an implementation or verified results.