The following updates have been added to RamBase Cloud ERP:
Production
New context menu option available in the Production work order (PWO) application
Classification: USEFUL
A new menu option, Copy serial numbers from source LCMs, has been added to the Production (PWO) application. Currently, products that are reworked get a new serial number based on the new corresponding Product unit (LCM). This can be useful when a product is being reworked to another product but not necessarily in cases where a product’s physical composition remains unchanged after reworking. The Copy serial numbers from LCMs menu option allows you to copy the serial number of the original product to the reworked products. This update allows for a clearer overview over reworked products.
New Company setting (CSV) for Production work orders (PWO)
Classification: USEFUL
A new Company setting (CSV), Unlink purchase order for external work when splitting PWO, has been added to allow for split Production work orders (PWO), with external operations, to automatically be linked to pending purchase (PUR). When this setting is turned on, the source Production work order (PWO) is linked to the pre-existing Purchase order (SPO) or Purchase order response (SOA). The Purchase order (SPO) or Purchase order response (SOA) is thereby reduced by the split Production work order (PWO) and the destination Production work order (PWO), the split Production work order (PWO), is linked to the pending purchase (PUR). If this setting is turned off, the destination will continue to be linked to the pre-existing Purchase order (SPO) or Purchase order response (SOA).
Rental
Enhanced rental unit return validation and basket overview in Rental unit check-in (RUI)
Classification: IMPORTANT
The Rental unit (RUT) check-In process has been enhanced with a new Select check-in basket workflow in the Rental units ready for check-in (RUI) application, providing greater visibility and control when returning Rental units (RUT).
Previously, users had limited visibility into which Rental units (RUT) were selected for check-in. In rental environments where a single rental contract can contain anywhere from a few units to several thousand Rental units (RUT), returns are often processed in multiple batches and by different users. This increased the risk of selecting incorrect Rental units (RUT), overlooking units that should be returned, or initiating check-ins with invalid return criteria.
Errors during the return process can have significant operational consequences, including incorrect closure of rental contract calendars, inaccurate revenue generation, and updates to rental allocation registers that require manual correction.
With this update, users can collect Rental units (RUT) transactions into a dedicated return basket before initiating the check-in process. The basket provides a detailed overview of the selected Rental units (RUT), including information about the related Rental contract (RCT) and Rental contract item (RCTITEM), enabling users to review and validate their selections before any Goods receptions (SSA) are created.
The new validation capabilities allow users to verify whether selected Rental units (RUT) can be returned based on criteria such as return date and stock location. If any validation rules fail, clear and user-friendly messages are displayed before processing begins, allowing users to correct issues without affecting the remaining units in the basket.
The following improvements have been introduced:
Basket-based return workflow for collecting and reviewing Rental units (RUT) before check-in.
Detailed overview of selected Rental units (RUT), including related Rental contract (RCT) and Rental contract item (RCTITEM) information.
Validation of return criteria such as return date and stock location before processing.
User-friendly validation messages explaining why selected Rental units (RUT) cannot be returned with the chosen criteria.
Ability to remove individual Rental units (RUT) from the basket without affecting other selected units.
Support for setting default stock locations for all units in the basket while allowing unit-specific stock location overrides.
Support for setting default return dates for all units in the basket while allowing unit-specific return date overrides.
Restriction preventing Rental units (RUT) with different check-in locations from being added to the same basket.
Stock location selection limited to locations associated with the selected check-in location.
Overview of the total number of Rental units (RUT) currently included in the basket.
Basket sorting prioritized by Rental contract item (RCTITEM), followed by Rental contract (RCT).
Visibility of rental unit ownership both before and after the return process.
Information showing the number of rental units on rent before and after the planned check-in process at both Rental contract item (RCTITEM) and Rental contract (RCT) level.
Visibility of future planned rentals and the first expected future checkout date for returned rental units.
Summary view after processing displaying completed returns and created Goods receptions (SSA).
Direct access to returned rental units and the generated Goods receptions (SSA) after processing.
Clear error reporting for Rental units (RUT) that fail during the check-in process.
Ability to update the return date after processing if an incorrect date was used during check-in.
These enhancements provide greater transparency and control throughout the rental return process, reducing the risk of operational errors while ensuring accurate updates to rental contracts, allocation registers, and revenue-generating rental calendars.
Read more about the Rental unit check-in (RUI) application here
Release date: Already released
Finance
Support for SAF-T Financial version 1.40
Classification: USEFUL
We have added support for SAF-T Financial version 1.40 to help Norwegian customers meet the updated reporting requirements from the Norwegian tax administration.
Previously, RamBase supported SAF-T Financial version 1.30, which remains valid for fiscal year 2026 and earlier. From January 1, 2027, the Norwegian tax administration requires system providers to support SAF-T Financial version 1.40 for new reporting.
With this enhancement, users can generate SAF-T files that comply with the version 1.40 schema, ensuring they meet the latest regulatory requirements while maintaining compatibility with previous reporting periods where applicable.
This enhancement helps Norwegian customers remain compliant with statutory reporting requirements and ensures that RamBase continues to support the latest SAF-T standard.
Karisma Davis
The following updates have been added to RamBase Cloud ERP:
Production
New context menu option available in the Production work order (PWO) application
Classification: USEFUL
A new menu option, Copy serial numbers from source LCMs, has been added to the Production (PWO) application. Currently, products that are reworked get a new serial number based on the new corresponding Product unit (LCM). This can be useful when a product is being reworked to another product but not necessarily in cases where a product’s physical composition remains unchanged after reworking. The Copy serial numbers from LCMs menu option allows you to copy the serial number of the original product to the reworked products. This update allows for a clearer overview over reworked products.
New Company setting (CSV) for Production work orders (PWO)
Classification: USEFUL
A new Company setting (CSV), Unlink purchase order for external work when splitting PWO, has been added to allow for split Production work orders (PWO), with external operations, to automatically be linked to pending purchase (PUR). When this setting is turned on, the source Production work order (PWO) is linked to the pre-existing Purchase order (SPO) or Purchase order response (SOA). The Purchase order (SPO) or Purchase order response (SOA) is thereby reduced by the split Production work order (PWO) and the destination Production work order (PWO), the split Production work order (PWO), is linked to the pending purchase (PUR). If this setting is turned off, the destination will continue to be linked to the pre-existing Purchase order (SPO) or Purchase order response (SOA).
Rental
Enhanced rental unit return validation and basket overview in Rental unit check-in (RUI)
Classification: IMPORTANT
The Rental unit (RUT) check-In process has been enhanced with a new Select check-in basket workflow in the Rental units ready for check-in (RUI) application, providing greater visibility and control when returning Rental units (RUT).
Previously, users had limited visibility into which Rental units (RUT) were selected for check-in. In rental environments where a single rental contract can contain anywhere from a few units to several thousand Rental units (RUT), returns are often processed in multiple batches and by different users. This increased the risk of selecting incorrect Rental units (RUT), overlooking units that should be returned, or initiating check-ins with invalid return criteria.
Errors during the return process can have significant operational consequences, including incorrect closure of rental contract calendars, inaccurate revenue generation, and updates to rental allocation registers that require manual correction.
With this update, users can collect Rental units (RUT) transactions into a dedicated return basket before initiating the check-in process. The basket provides a detailed overview of the selected Rental units (RUT), including information about the related Rental contract (RCT) and Rental contract item (RCTITEM), enabling users to review and validate their selections before any Goods receptions (SSA) are created.
The new validation capabilities allow users to verify whether selected Rental units (RUT) can be returned based on criteria such as return date and stock location. If any validation rules fail, clear and user-friendly messages are displayed before processing begins, allowing users to correct issues without affecting the remaining units in the basket.
The following improvements have been introduced:
These enhancements provide greater transparency and control throughout the rental return process, reducing the risk of operational errors while ensuring accurate updates to rental contracts, allocation registers, and revenue-generating rental calendars.
Read more about the Rental unit check-in (RUI) application here
Release date: Already released
Finance
Support for SAF-T Financial version 1.40
Classification: USEFUL
We have added support for SAF-T Financial version 1.40 to help Norwegian customers meet the updated reporting requirements from the Norwegian tax administration.
Previously, RamBase supported SAF-T Financial version 1.30, which remains valid for fiscal year 2026 and earlier. From January 1, 2027, the Norwegian tax administration requires system providers to support SAF-T Financial version 1.40 for new reporting.
With this enhancement, users can generate SAF-T files that comply with the version 1.40 schema, ensuring they meet the latest regulatory requirements while maintaining compatibility with previous reporting periods where applicable.
This enhancement helps Norwegian customers remain compliant with statutory reporting requirements and ensures that RamBase continues to support the latest SAF-T standard.