> For the complete documentation index, see [llms.txt](https://kb.bevica.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://kb.bevica.com/roadmap/bevica-roadmap/business-central-resource-hub/business-central-wave-2-2026-v29.0/wave-testing-guidance-and-support.md). # Wave Testing Guidance and Support An overview of the key areas recommended for testing based on changes introduced in this release. ### Introduction All Bevica and Microsoft changes included in this release have undergone rigorous development, quality control and testing procedures before being made available to customers. Whilst every effort is made to validate these changes in standard environments, individual customer implementations often contain configurations and third-party or bespoke extensions that cannot be replicated during testing. As every organisation uses Bevica differently, it is not possible for Bevica to test every customer-specific process. Customers should review and test their critical business workflows to ensure the system continues to operate as expected within their environment. This guide highlights areas that may be impacted by the release and should be used to support your own upgrade testing and validation activities prior to sign-off. ### Duty, Tax and Compliance #### International Duty As part of the new International Duty extension, several underlying enhancements have been made to Bevica Duty Management. Whilst these changes are not expected to impact existing processes, customers should validate their standard duty-related workflows, including sales and purchase transactions with and without duty transfers. Verify that transactions post successfully and that Duty Ledger entries, duty calculations, and related postings continue to be created as expected. #### Production Date Tracking If Production Tracking is relevant to business process, we recommend trying out this feature. First, create an item with **Production Tracking** enabled and generate stock using an Assembly Order or Item Journal. Verify that the production date is recorded on the resulting Item Ledger Entries. Then perform a duty transfer transaction, such as a sales shipment or item reclassification, and confirm that Bevica uses the stored production date to determine the applicable duty rate. Also verify that the production date is visible on the relevant Item Ledger, Duty Ledger and HMRC Ledger entries for audit purposes #### **Dutiable Volume for Cask-Conditioned Products** If this feature is relevant, enable the Dutiable Volume functionality in Bevica Setup and configure a Dutiable Volume on a test item. Verify that the Unit Duty Amount updates as expected and confirm that duty calculations and postings use the configured Dutiable Volume rather than the standard item volume. Customers using cask-conditioned products should pay particular attention to scenarios where duty relief for undrinkable sediment is applicable. #### HMRC Duty Relief for Spoilt or Destroyed Products To setup and test this feature, we suggest first creating a Return Reason Code configured for Duty Reclaim and process a Duty Paid Sales Return Order for qualifying inventory. Confirm that the correct Duty Ledger Entry is created, the original duty transaction can be linked and reversed, inventory is removed as expected, and the appropriate General Ledger postings are generated. Where item tracking is in use, verify that tracking information remains accurate throughout the process. ### Paid Reserves #### Paid Reserve Inventory Posting Group If you use the Bevica Fine Wine extension, we recommend reviewing and testing the Paid Reserve Inventory Posting Group functionality as part of your upgrade validation.\ Refer to the [Paid Reserve Setup](/documentation/guides/paid-reserves-and-fine-wine/private_reserves_setup.md#inventory-posting-group) article for guidance on configuring the feature. Once setup is complete and any existing Paid Reserve records have been updated, we suggest testing key processes including Sales into Reserve, Paid Reserve Duty Transfers, and Paid Reserve Withdrawals. Verify that the resulting inventory and financial entries are posted as expected and align with your business processes. #### Paid Reserve Journal and Item Tracking Customers using the Bevica Fine Wine extension with Item Tracking enabled should review and test the Paid Reserve Journal functionality as part of their validation activities. Recent changes have introduced a mandatory Rotation No. requirement for tracked items to help maintain data consistency, along with updates to the way item tracking information is assigned within the journal. We recommend testing key processes including Stock into Paid Reserve, as well as splitting Paid Reserves and transferring ownership between Paid Reserves, to confirm that item tracking and resulting transactions behave as expected. #### Additional Fields on Paid Reserves If you use Additional Information fields on Paid Reserves, such as Provenance, Source, or Condition, we recommend validating that these values are carried through correctly during transaction processing. Review the resulting Paid Reserve Ledger Entries to confirm that the additional information is copied as expected and remains available for reporting, traceability, and operational processes. #### Cancelling a Paid Reserve Updates have been made to the calculation and display of the Unit Cost (LCY) when selecting a Paid Reserve for cancellation. Customers managing Paid Reserves in multiple currencies should include this area in their validation testing. We recommend processing a selection of Paid Reserve cancellations across different currencies and verifying that the resulting Unit Cost (LCY) values are calculated and displayed as expected, in line with your inventory valuation and reporting requirements. #### Paid Reserves and Inventory Warehousing If using Inventory Warehousing, test your standard Paid Reserve workflows and confirm that stock can be created, allocated, moved, and processed through warehouse operations as expected. Verify that inventory quantities, ownership records, warehouse transactions, and any related Paid Reserve entries remain accurate throughout each stage of the process. ### Sales Process #### Available Inventory on Sales Line Worksheet Updates have been made to the Available Inventory triggers used by the Sales Line Worksheet to ensure inventory availability is refreshed when reservation entries are cancelled. Customers should validate that cancelling reservations correctly updates the available inventory displayed within the Sales Line Worksheet. We also recommend testing scenarios involving the deletion of Sales Lines, Sales Orders, and Unpaid Reserves to confirm that reservation releases are processed correctly and that availability changes are reflected in the worksheet as expected. #### Updating Sales Prices on Sales Line Worksheet Changes have been made to the Sales Line Worksheet pricing update process to ensure revised sales prices are correctly copied to the temporary Sales Line Worksheet records. Customers using price groups should validate this functionality as part of their testing. We recommend creating quantities on the Sales Line Worksheet, changing the Price Group on the related Sales Header, and running Update Sales Pricing. Confirm that the revised price is displayed on the Sales Line Worksheet and, once the worksheet lines are created, verify that the updated sales price is carried through and applied correctly to the resulting transaction. #### Soft Allocations for Sales Order Stock Commitments Where visibility of intended stock commitments is required without creating formal reservations, Soft Allocations can be used. to try out this feature, enable Soft Allocations and test a range of sales order scenarios by applying, updating, and removing Soft Allocation quantities. Verify that available inventory is reduced appropriately in the Item Availability and Sales Line FactBoxes, whilst ensuring no formal reservations are created. Test the interaction between Soft Allocations and Bevica Reservations, confirming that allocations are cleared when reservations are applied and that system rules are enforced. Where applicable, validate warehouse, item tracking, and 3PL processes to ensure stock can be correctly converted to standard reservations before fulfilment and posting. ### Items and Price Lists #### Item Card Changes have been made to the calculation and display of Unit Costs on the Item Card, removing unnecessary Variant Code filtering to improve accuracy and consistency. Customers should include this area in their post-upgrade validation, reviewing a selection of items to confirm that the Unit Cost values displayed on the Item Card are accurate and align with their expected inventory valuation. Particular attention should be given to items that utilise variants, ensuring costs are calculated and presented correctly following the update. #### Sales and Purchase Price List Descriptions Bevica has introduced a new feature that [automatically synchronises Item Descriptions between the Item Card and related Sales and Purchase Price Lists](/documentation/guides/items-and-inventory/creating_new_items.md#copying-price-list-descriptions). Customers are encouraged to enable and validate this functionality as part of their testing activities. Once enabled, updates made to an item's description on the Item Card should automatically flow through to any linked Sales Price Lists and Purchase Price Lists, helping to maintain consistency and reduce manual updates across pricing records. ### Prepayment #### New Prepayment Invoice Fields New fields have been added to Posted Prepayment Invoices to improve visibility of the original item quantities and units of measure. The Original UoM, Original Quantity, and Original Quantity (Base) fields are now available and will be displayed when a Posted Sales Invoice is printed using Bevica's Standard Sales Invoice layout. Customers who use prepayments should include this functionality in their testing, generating and printing a Posted Prepayment Invoice to confirm that the new fields are populated correctly and appear as expected on the printed document. ### Business Central Changes The following guidance covers relevant Microsoft changes for Business Central 2026 Wave 2 (V29). Test only features that you use or plan to enable. ### Shopify Connector If you use the standard Shopify connector, test a complete order lifecycle. Include a new order, an amended order, an exchange, and a refund. Confirm that the correct sales documents are created and remain aligned with Shopify. Review the **Shopify Shop Card** settings before testing. Where enabled, validate **Use Shopify Order No.**, **Process Returns as**, **Sync HS Code**, and **Country of Origin**. Confirm that product origin and tariff data synchronise as expected. If you use Shopify B2B, test company mapping, catalogue assignment, and price synchronisation. Review **Skipped Records** and **API Errors** after each synchronisation run. Confirm that your Shopify API version and access tokens remain valid. ### Payables Agent and Copilot If you use Payables Agent, test invoice matching against purchase orders and posted receipts. Include differing line amounts and expected receipt dates. Confirm that draft finalisation follows your **Receipt on Invoice** settings. If you enable the unified Copilot chat experience, test it with representative user permissions. Confirm that answers and suggested actions respect company access and internal data policies. **Caution:** Do not enable MCP Server access without your security team's approval. Test its data access, permissions, and audit requirements in a sandbox first. ### Financial Management If you use self-billing, create and post invoices for vendors with different number series. Confirm that each vendor receives the expected document number. If you use fixed assets, test the accelerated depreciation methods with representative assets. Verify depreciation entries, book values, and reports before using the methods in production. Business Central now supports standard excise duty and withholding tax enhancements. Bevica Duty Management remains the recommended duty solution. Test these features only where they form part of your process. ### Reporting and Financial Reporting Test any business-critical document layouts after the update. Confirm that report themes, shared headers, footers, and conditional visibility render correctly in PDF output. If you manage custom layouts, verify their availability status on the **Report Layouts** page. Confirm that users can select only approved layouts. Run key financial reports and validate figures against your pre-upgrade baseline. If you use report packs, test immediate runs and scheduled delivery. Review the change log after amending financial report definitions. ### Supply Chain and Quality If you use warehouse-enabled locations, test direct transfer orders from creation through posting. Include locations that require inventory picks or warehouse shipments. Confirm that inventory and warehouse entries are correct. If you use subcontracting, test purchase orders with routing comments and attachments. Confirm that instructions reach the subcontractor. Test put-aways and picks where basic warehouse processes support subcontracting. If you use quality inspections, complete a passed and failed inspection. Verify that passed and failed quantities populate correctly. Confirm that posting errors link users to the blocking inspection. Test planning and production workflows if you use manufacturing. Include Planning Worksheet creation, capacity calendar changes, and production BOM or routing errors. ### Sustainability Management If you use Sustainability Management, test posting and reversal scenarios in a sandbox. Include purchase documents, item journals, reclassification journals, and fixed asset transactions where applicable. Verify CO₂, CH₄, N₂O, and CO₂e values against expected calculations. For tracked items, test the **Specific** tracking method with serial or lot numbers. Confirm that sustainability ledger entries remain traceable after reversals. ### User Experience and Administration Test critical pages after the update with each affected user role. Confirm that saved list views, analysis tabs, and Tell Me searches remain available. Verify that recent searches and lookup suggestions do not create confusion in operational workflows. If you use agents, test review notifications and permission requests. Confirm that users can identify documents requiring review and grant only necessary permissions. Administrators should test SIFT index changes in a sandbox before applying them. Monitor page performance and validate that key reports still produce expected results. Review **Open in Excel** telemetry if your compliance processes require export auditing. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://kb.bevica.com/roadmap/bevica-roadmap/business-central-resource-hub/business-central-wave-2-2026-v29.0/wave-testing-guidance-and-support.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.