Date of production synchronization server patch: 21st October 2026 / 18:00 Geneva time
Latest user rights files updated: UF42.1 can be found here
Note that no user rights need to be loaded at each HQ. This will be done at the Sync Server by the Core team and will update the user rights via Sync for all HQs and missions.
UF42.1 Fixed a bug where IN/INT from scratch lines stayed “Not Available” after header confirmation, forcing line-level validation before reception. Lines now switch to Available on confirmation.
Different OCs flagged the issue of the performance of the ‘Export Invoice Lines’ function in various objects, such as SI, STV and ISI. The action of clicking on the ‘Export Invoice Lines’ button took a considerable time to process and the file became corrupted after downloading. This has now been corrected.
OCG flagged the issue of the action “Search for Mass reallocation” in the Grant Management module which when launched the process never displayed results. The issue was due to an increasing number of Destinations and the configuration of G/L accounts linked to these destinations. The computation used by the process has been streamlined to be able to manage these volumes and report is now correctly displayed.
Issue flagged by OCA due to erroneous data returned in view which is used for their integration with Wefin, some missions were displayed with incorrect last closing date. This is now corrected.
Latest user rights files updated: UF42.0 can be found here
Date of production synchronization server patch: 16th September 2026 / 18:00 Geneva time
Note that no user rights need to be loaded at each HQ. This will be done at the Sync Server by the Core team and will update the user rights via Sync for all HQs and missions.
JIRA filter for all integrated tickets: https://jira.unifield.org/issues/?filter=12579
Two related master data problems with local products are fixed in UF42.0. At coordination level, the Product Creator and Standardization Level fields now default to “Local” and “Non-Standard” and cannot be changed — this does not apply at HQ. Trying to save a local product with a UF Status of “Archived” or “Forbidden,” from the product card, now raises a blocking error: “The combination of Product Creator ‘Local’ and selected UF Status are not allowed.” A data fix cleaned up existing records. Active local products sitting as “Archived” or “Forbidden” are moved to Phase Out, with the usual pipe and stock check: if open pipeline or stock exists, the product is marked as Phase Out; if nothing is found, it deactivates automatically. Where automatic deactivation at coordination level is not possible, a Product Mass Update document named “US-15593 Local_Products UF Status Archived/Forbidden Correction” is created automatically so users can handle the remaining cases without having to search for them.
A “New” button is now available directly in the Supplier Catalogue menu Partners > Suppliers > Supplier Catalogue, allowing users to create a catalogue without having to go through the partner page first; when using this button, the Partner field is editable so the supplier can be selected manually.
The Procurement Method field on IR and FO documents is now blank and non-editable by default, removing the previously confusing pre-filled value that had no operational meaning before sourcing. Once a line is sourced via the OST, the field updates automatically with the procurement method encoded there, and the value is retained even if the line is subsequently cancelled or cancelled-R. In the Order Follow-up (screen, PDF, and XLS), unsourced lines display “N/A” in the Procurement Method column.
UF42.0 introduces the ability to merge multiple Inbound Transport Objects (ITOs) into a single ITO via a new “Merge ITOs” action in the Action menu, following the same model as PO merging. For two or more ITOs to be merged, they must share identical Shipment Type (Inbound), Zone Type (International), Supplier Partner, Shipment Flow, Macroprocess, Custom Regime, and Original Cargo Reference (either identical or all empty — mixing filled and empty references is not allowed). Merging is permitted up to the “At Customs Entry Point” status, and only ITOs in the same status can be merged (Draft+Draft, Planned+Planned, etc.). The merged ITO inherits steps and Custom Regime from the template ITO; Transport and Custom fees are carried over in whatever status they held at the time of merging; OTO references are concatenated with a semicolon separator, and a flag is added to indicate when an ITO has already been merged.
This release also includes a broader set of C&T module improvements. A new “Draft” status is introduced for manually created ITOs and OTOs ahead of “Planned,” and several status and dashboard labels are renamed to better reflect the actual process — most notably “Under Pre-Clearance” becomes “Pre-Arrival” and “At Border Point” becomes “At Customs Entry Point.” Steps are now numbered per macroprocess, Track Changes coverage is extended to steps and fees, and the Custom/Transport Fees tabs gain a Status field. Two new printable PDF info notes for Transport and Customs Fees are available from the Action menu, alongside a “Step date definitions” explanation.
Synced user profiles holding the Sign_document_creator_supply or Sign_document_creator_finance UR were receiving e-signature notification emails from all instances where e-validation was active, resulting in inbox spam for system support profiles. A new “Enable e-mail notification” checkbox is now available on synced user profiles (visible only when electronic signature is enabled for the instance and only on synced user): unchecked by default, it can be ticked per instance when email notifications are needed for testing or support purposes.
Previously, it was possible to add or change signees on a locked PO after signatures had already been applied, which could result in signing out of sequence or a PO incorrectly showing as fully signed. As of UF42.0, the rules are enforced: signees can still be changed or backed up while a PO is partially signed, but only in sequence and only for users who have not yet signed; the “Manage users allowed to sign” button becomes unavailable once the PO is fully signed, at which point the only option is to unlock the PO and restart the signature process.
A new “Location Classification” sub-module is added under Supply Configuration > Warehouse Configuration > Regular Warehouse Management, allowing users to flag each ECU with a new “External System Managed Stock” attribute. The attribute is mandatory when editing, restricted to Sup_Supply_Config UR. This improvement is used by and useful also for the SDE/SmartScan application.
2.8 (US-12708) New Reason Types and movement restrictions
This ticket restructures reason type logic across several movement flows to make the recorded reason types (RT) match what is actually happening to the stock.
Moves between regular stock locations (IS/LOG/MED/EPREP/ICU) and Quarantine (Analyze) is bidirectional and limited to RT 7 – Internal Move. From Quarantine or directly from stock, moves to Expired / Damaged / For Scrap are restricted to 12.1- Loss/ Scrap, 12.2 Loss/ Sample, 12.3 Loss/ Expiry, 12.4 Loss/ damage and new RT 12.5 – Loss / Batch; no reverse move is permitted from Exp/Dmg/Scrap back to Quarantine or regular stock. The only valid onward move from EXP/DMG/SCRAP is to the Destruction location, using the new RT 23 – Destruction; the Destruction location is blocked from selection in incoming shipments.
For claim movements during incoming shipments, RT 7 applies when moving from an MSF or Other Supplier to Quarantine; manually created claims going to Exp/Dmg/Scrap keep RT 12.4 – Loss/Damage.
Movement from and to cross-docking are not impacted by new release.
A patch script has been applied to retrospectively adjust/correct historical stock movements to be in line with the new reason type logic introduced in US-12708. The Expired/Damaged Report now includes RT 12.5 – Loss / Batch Recall as a selectable filter, pulling the corresponding movements when selected.
Previously, deactivated stock locations were invisible in the location lookup pop-ups of several warehouse reports, meaning that running a report over a historical period could return different results depending on which locations were active at the time of export.
As of UF42.0, Active and Inactive filters are added to the location selection pop-up in the Expired/Damaged Products, Receptions Report, Deliveries Report, and Export IR Follow-up reports, allowing users to include inactive locations (intermediate stocks, ECUs, ICUs) when needed. Active is the default; Inactive can be enabled alongside it, and the filters work in combination with all existing report filters.
2.11 (US-15693) Select Parcel IDs pop-up redesigned as a vertical scrollable list
The Parcel ID selection pop-up has been reworked from a horizontal box layout to a vertical scrollable list with checkboxes, sorted alphanumerically, making it significantly easier to browse and select Pack IDs.
A cancelled Physical Inventory can no longer be reactivated via “Set to Draft” — if a new count is needed, it must be initiated through the New button, keeping the cancelled record intact for traceability. This is taken into account for the SDE/SmartScan related flows also.
Track Changes is now enabled on Physical Inventory document, Pack Types and Pre-Packing List. Please see tickets for detail on exact fields which are tracked for each.
A new line state filter is added to the Delivery Order and Picking ticket, aligning with the existing filter behaviour on other supply documents. Ssers can now filter by unprocessed, all, not available, and cancelled lines. The Delivery Order PDF and XLS exports gain a new “Qty in Stock” column showing the real available quantity at the source location, the “Quantity” column is renamed to “Qty to Pick,” and the Asset column is removed.
Emails pushed for partial or failed PO Auto-VI updates now include the file name in the subject line, with the Job ID moved to the email body for easier identification. In addition, the PO import job report now provides a clear comment message explaining errors on exception lines caused by an Analytical Distribution financial destination that is not accepted for the product, so users can pinpoint the issue directly.
During UniData product pulls, if the expected root nomenclature ( e.g. MED/LOG – L – LEAF – YYYY) does not exist, the product is now automatically linked to the closest existing sequence of nomenclatures (e.g. LIB – L – LEAF – YYYY nomenclature) instead of failing with a linkage error.
The introduction of US-15016 in UF41.0 allowed for PPL sequence to have gaps. The PPL parcel label report now reflects the actual pack sequence, so labels are generated only for parcels that exist in the packing list. Where the sequence contains gaps, a new notice is displayed on the first label listing the missing pack numbers.
When an Auto VI PO import ends in Exception or Partial Process, the import job report now includes the reason a line was rejected. This gives support teams enough diagnostic detail to identify the cause.
A new Matching Report API has been introduced to support the integration of UniField Journal Items with WACA’s HQ NetSuite system. The report provides reconciliation-related information, including DB ID, Reconcile Number, Reconcile Date, Unreconcile Number, and Unreconcile Date. The API is designed to return only relevant Journal Items based on reconciliation activity and accounting period criteria, enabling a more accurate synchronization of reconciliation statuses between UniField and NetSuite.
This enhancement strengthens the reliability of the reconciliation process between UniField and NetSuite.
A new API has been introduced for WACA to export Balances by Account, Instance, and Currency for a selected mission and accounting period. The export provides the same balance information previously available through CSV files, including starting, calculated, and closing balances in both booking currency and EUR. This enhancement supports the validation of accounting data before and after Journal Item integration into NetSuite, helping ensure consistency between UniField and the external accounting system.
The solution delivers balance data through a paginated JSON-RPC API and is available only for mission-closed periods, ensuring that exported information reflects finalized accounting data.
A new API has been introduced to support the extraction of Journal Items from UniField for integration with WACA’s HQ accounting system (NetSuite). The API provides accounting data by mission and accounting period through a paginated JSON-RPC service and includes all key information required for financial integration, such as journal details, accounting entries, partner and employee references, currencies, amounts, cost centres, destinations, and funding pools. The solution ensures that only eligible mission-closed periods can be exported, supporting a controlled and reliable integration process between UniField and NetSuite.
In addition, a new Export HQ System (WACA) monitoring screen has been added to allow users to track mission-period exports and manage export snapshots. The first extraction creates a frozen snapshot to guarantee data consistency across Journal Items, balances, and matching reports, while authorized users can refresh the export when required. The API was further enhanced during testing with additional fields such as Journal ID and Employee ID.
The Ubuntu Vertical Integration UpfileToD365 export file has been enhanced with two new computed columns: EUR Amount and KES Amount. These columns automatically calculate amounts based on existing export data, applying the required formulas and rounding values to two decimal places. This improvement helps align the export file with Microsoft Dynamics 365 import requirements and reduces manual calculations during the integration process.
To ensure accounting accuracy, the export logic now automatically balances EUR and KES amounts at sequence level by applying any necessary rounding adjustment to the largest amount within the sequence. Additional adjustment information is also available in the raw data export for improved transparency and troubleshooting.
Following the UF41.0 update, the OCB HQ job used to export financial data from UniField to the HQ accounting system encountered an error due to a regression introduced by a previous change in the XML-RPC API response. The issue caused the export process to fail with a data type mismatch, preventing the successful transfer of accounting information between UniField and the HQ accounting platform.
A code correction has been implemented in UF42.0 to restore compatibility with the export process. The fix addresses the API call finance.hq.vi_get_ocb_export, ensuring that the expected data structure is correctly returned and processed.
The OCP Vertical Integration (VI) export process has been enhanced to prevent the generation of incomplete accounting export files. Previously, a coordination could export a period as soon as the coordination instance reached the Mission Closed status, even when some active project instances had not yet completed their period-closing process. This situation could result in accounting entries being synchronized after the export had already been generated, leading to discrepancies between exported data and final accounting balances.
The tax name management process has been improved to ensure consistent tax naming across synchronized instances. The update prevents incomplete multilingual updates and guarantees that tax name changes are correctly propagated between coordination and project levels. As a result, users will now see the same tax names across all synchronized instances, improving data consistency and reducing maintenance effort.
Track changes are now recorded for AD modifications on invoices and AJIs, allowing users to review the history of analytical distribution updates directly through the existing tracking mechanism. The enhancement applies to changes made after the creation of the AJI and is not retroactive to historical data. This provides stronger auditability and helps finance teams identify and review AD modifications when required.
Users can now download the Journal Entry Import template directly from Accounting > Journal Entries > Import Entries. The template includes translated column headers and is readily available within the import form, making it easier to prepare compliant import files and reducing preparation errors. User interface adjustments have also been made to improve the visibility and usability of the import controls.
The Product field has been removed from the Direct Invoice form. This change streamlines the user interface, ensures consistency with other finance processes, and reduces the risk of entering information that is not used within the Direct Invoice workflow.
The invoice line export files now include the instance code and export date in the filename. For example, exported files follow a format similar to InstanceCode_Export-Invoice_YYYYMMDD, providing clearer identification, improving file organization, and reducing the risk of confusion when storing or sharing exported invoice data.
To support regulatory and reporting requirements, especially in OHADA countries, two new fields have been added to the Partner form: Tax Identification Number (TIN) and Business Registration Number (RCCM). These optional free-text fields, with a maximum length of 15 characters, allow to store key supplier and customer identification data directly in UniField, improving partner record management and supporting local compliance needs.
Journal deletions are now synchronized across all related instances. When an eligible manually created journal is deleted, the deletion is automatically propagated through synchronization, ensuring consistent journal structures throughout the mission hierarchy. To protect accounting integrity, deletion remains blocked when the journal is already used in a Journal Item, liquidity register, or transfer, and users receive an appropriate notification explaining why the deletion cannot be performed.
Users can now create journals and registers of type Other Financial Institutions, linked to dedicated liquidity accounts and the new OFIN analytic journal. The enhancement, requested by Ubuntu, includes dedicated register screens, statement reconciliation processes, support for liquidity reporting, synchronization behaviour consistent with financial registers, and integration with existing accounting workflows. This improvement provides clearer financial reporting, better segregation of liquidity accounts, and more appropriate management of mobile money and other financial institution transactions across missions.
The Duplicate action has been removed for bank register lines originating from cheque imports. This prevents the creation of duplicate pending cheque entries while preserving the duplication feature for other eligible register lines. The change helps maintain the integrity of cheque processing workflows, reduces reconciliation problems, and encourages the use of standard correction methods for cheque-related transactions.
The report generation has been optimized through performance enhancements, the introduction of a progress indicator during report creation, and the adoption of the.xlsx format as the default spreadsheet output. The system now also proactively checks report size limits and displays clear error messages when the requested output exceeds supported thresholds, preventing processing failures and improving the user experience. These improvements apply to both the General Ledger and Trial Balance reports, providing faster and more reliable report generation.
PSQ has been upgraded to version 14.24. All instances already on v.14 will be automatically upgraded. Those on previous versions (v.9 etc) will not be automatically upgraded as manual intervention is needed.
APIs have been developed in UniField to allow data flows for Packing Lists and Physical Inventories. The APIs were developed to use JSON RPC. This completes all UniField objects which were due to have APIs developed for SDE/SmartScan.
OCG flagged this issue of a notable increase in RAM at certain times. This was due to previous updates to the Mission Stock Report. The format of the report has now been changed to reduce memory usage.
APIs which had previously been developed for WaCA have been converted from XML-RPC to JSON format. This was completed for APIs for Partners, National Staff and Journals.
New APIs have been developed for Currencies, Rates, Expats, HQ Entries for WaCA, specifically to allow data flows with the WaCA HQ accounting system Netsuite. APIs were developed in JSON format.
An “eye” icon has been added in the system for fields where password values can be entered. By default the password remains non-visible, but the user can click the icon to see the password they are typing / have typed. This does not allow other users to see stored passwords in the system.
As requested for Ubuntu, a new protocol option can be selected for automated exports and imports. As well as the options “FTP” and “SFTP” is it now also possible to select “OneDrive” as the protocol in the Tools>Tools>Automated imports / Automated Exports configuration page to allow direct exports to/imports from OneDrive.
Date of production synchronization server patch: 17th June 2026 / 18:00 Geneva time
Latest user rights files updated: UF41.0 can be found here
Note that no user rights need to be loaded at each HQ. This will be done at the Sync Server by the Core team and will update the user rights via Sync for all HQs and missions.
JIRA filter for all integrated tickets: https://jira.unifield.org/issues/?filter=12571
UniField 41.0 introduces email notifications for the e-signature workflow. With this new functionality, if the instance is configured to be able to send emails it means that when a document requires electronic validation, the designated signee now receives an automatic email alert prompting them to complete their signature in UniField. Notifications follow the cascade signature logic — each signee is notified in turn once the previous signature is collected. Notifications include the document type, reference, and instructions to access the Signature Follow-up screen. A daily consolidated reminder is also sent for any pending signatures with an additional alert when a signature is approaching expiry.
The feature is configurable in Administration >Email> Email Notification for Signatures Configuration per document type and is inactive by default. It applies across all e-validation-enabled document types in both supply and finance modules, including Purchase Orders, Incoming Shipments, Delivery Orders, Supplier Invoices, Cash Registers, Bank Registers, and Physical Inventories.
Email logs are accessible under Tools > Email Logs > Signature Email Logs for traceability.
Previously when a loan return was created, the requested delivery date at line level was calculated using days instead of months for the loan duration, while the Delivery tab showed the correct date. This mismatch has been corrected — the RDD at line level now aligns with the loan duration in months, consistent with the Delivery tab.
Previously, UniField enforced strict parcel sequencing rules: sequences had to start at 1 and be continuous with no gaps. Any deviation — such as a shipment starting at parcel 2, or sending only selected parcels from a larger range — would cause the system to block with an integrity error. This made it difficult to handle real operational scenarios where only specific parcels need to be dispatched or re-dispatched. As of UF41.0, the strict sequencing rules have been removed: parcel sequences no longer need to start at 1, and gaps between parcel numbers are now accepted. Pack ranges remain available for user convenience, and when a partial number of parcels is processed without manual selection, the system now defaults to selecting from the beginning of the sequence in ascending order.
The Partner/Customer field in the Pick-Pack-Ship process was previously editable, allowing users to change the destination and risk data inconsistencies. As of UF41.0, the field is read-only — if the destination needs to change, the document must be cancelled and a new FO flow created.
When an OUT with reason type “Deliver to Unit” is converted to a Pick-Pack-Ship, the External Consumption Unit (ECU) is now propagated to the PPS header and displayed as the destination location, replacing the previously misleading internal partner reference. The ECU information is also reflected in the Deliveries and IN & OUT reports, as well as in the picking ticket, packing list (PDF/XLS), and freight manifest — giving full visibility of the actual delivery destination throughout the process.
The Country field in the postal address of external partner cards is now mandatory. The behaviour differs depending on context: for new partners, country must be filled before saving; for existing partners in edit mode, the field is enforced only for the address currently visible on screen — other addresses will be validated individually when opened.
Local Market is excluded from this requirement, and country data is synchronised downstream only (not upstream).
This change originally came from a request relating to SDE (single data entry project) in order to facilitate mapping of MSF entities + countries.
2.7 (US-15619) New “MSF Entity” attribute on external partner card
A new “MSF Entity” checkbox has been added to the external partner card, positioned between “Partner status” and “Active.” This attribute allows users to flag whether an external partner is in fact an MSF entity, and when ticked, a mandatory dropdown appears to select the corresponding MSF section (OCA, OCB, OCG, OCP, OCBA, UBUNTU, WACA). The field is available at HQ, coordination, and project level, applies to external partners only, and is excluded for partners of type EXXX (OCB specific partners). All changes to the checkbox and dropdown are captured in Track Changes. This improvement is a prerequisite for the SDE project.
2.8 (US-15633) Export PO Follow-up: inactive partners now selectable
Previously, when generating the Export PO Follow-up report, users could not select inactive or deactivated partners through the Partner/Supplier lookup filter, making it impossible to report on historical POs linked to partners who had since been deactivated. As of UF41.0, the supplier lookup in the Export PO Follow-up report now allows selection of active, phase-out, and inactive partners, and the generated report includes POs linked to all partner statuses.
When manually correcting the Expected Receipt Date at the incoming shipment header level, the header field now correctly reflects the new date — previously it remained stuck on the old value.
When a product code is merged in UniData, UniField now automatically triggers the same merge at HQ level after each UD pull, replacing the non-kept code with the kept product across UniField and synchronising the result downstream — previously this had to be done manually. The automatic merge applies the same conditions as manual merging: the six product attributes (Type, Subtype, Expiry Date Mandatory, Batch Number Mandatory, Main Type, and Default Unit of Measure) must match. Merges between LOG and SRV product types are permitted; merges involving MED products remain blocked. If any of these conditions are not met, the merge is skipped and logged as an error, which can be reviewed and retried via the new menu Tools > UniData > Products Auto Merge;
Successful merges (both manual and automatic) are visible in the existing Merged UD Products Report (Warehouse > Reporting).
2.11 (US-15197) Merge of multiple local codes into the same UniData code
Previously, UniField blocked merging more than one local code into the same UniData code, which prevented database cleaning when duplicate local codes had been created independently over time. As of UF41.0, there is no longer any limit on the number of local codes that can be merged into a single UD code. The standard merging conditions still apply: products must share the same Batch Number and Expiry Date rules and product type to merge without restriction; if products belong to different families but have matching BN/EXP rules, the merge is allowed with a warning message; if BN/EXP rules or product types differ, the merge remains blocked. All merges are captured in Track Changes and synchronised to projects.
Following the release of UF40.0 the possibility to re-activate NSL code in Valid status was limited only to Administarator UR. With the release of UF41.0 UR Sup_Product_Manager has a right to re-activate NSL Code at coordination level
2.13 (US-15129) MSR and Consolidated MSR export format changed from XLS to XLSX
The Mission Stock Report (MSR) and Consolidated MSR are now generated in XLSX format instead of XLS, resolving the column limit issue (256 columns) that previously caused generation errors on large reports; the CSV export option has also been removed, and report headers are now frozen for easier scrolling.
2.14 (US-14299) State column hidden in OST “Need Sourcing” filter view
In the OST, the State column is now automatically hidden when the “Need Sourcing” filter is active — since all lines in that view are by definition in a validated state. The state column remains visible under all other filter combinations (Sourced, Need Sourcing + Sourced, or no filter)
2.15 (US-13048) Add Items / Remove Items buttons in Kit Composition List
Kit assembly in the field is rarely a perfectly controlled process — components may need to be swapped out, quantities adjusted, or items added based on what is physically available in the warehouse. Previously, UniField offered no structured way to handle these adjustments within an active KCL, forcing users to work around the system. As of UF41.0, two new action buttons — “Add Items” and “Remove Items” — are available directly on the KCL screen for any KCL in Draft or Completed status. “Add Items” lets users select any item (not restricted to TKC content) from a chosen Source Location; “Remove Items” lets users select existing KCL lines and redirect the stock to a Destination Location. Both flows include an expiry date modification step, in line with the existing Substitute Items process.
Beyond the screen-level interaction, every Add or Remove action automatically generates and processes an internal transfer document (INT/KITXXXXX, reason type 15 – Kit), ensuring that warehouse stock levels are accurately updated and the movements are fully traceable. This removes the need for manual workarounds or off-system tracking, gives warehouse teams a clear record of kit adjustments, and keeps the KCL aligned with physical reality throughout the kitting process.
For Direct Invoices, the fields “Posting Date” and “Register Posting Date for Direct Invoice” in Temp status were made editable when they were within the same month as the register.
A new field called “PO Details” was created under the field “Additional Info” in the “Other Info” tab. This field was populated with the data from the “Details” field of the Purchase Order (PO). The field was successfully created and the data was correctly transferred from the PO. It was added to the list of exportable fields for Supplier Invoices (SI). It was made editable in the following states: Closed, Draft, Open, and Paid.
The previous behavior allowed the closing of a cash register even when amounts in “Unrecorded Advances” and “Unrecorded Expenses” were not equal to zero. This could lead to a register and its corresponding period being closed while some entries had not yet been recorded.
An issue was identified where AJI corrections (REV and COR entries) performed simultaneously at Coordo (COO) and Project levels led to duplicate REV and COR entries, which were not detected by the “Entries Data Integrity” report.
Issue Description
When a Journal Entry (JE) was approved on the Project (e.g., January 2026 with lines 30100 / 66006) and synchronized to Coordo, and the mission period was closed,
If a Cost Center change was then performed simultaneously at both Project and Coordo levels, REV/COR entries were generated and synchronized,
This resulted in duplicate REV and COR entries, which were not flagged by the “Entries Data Integrity” report.
The issue only became visible under specific conditions:
Implemented Change
Controls were introduced to prevent or detect duplicate REV and COR entries generated during simultaneous AJI corrections at Coordo and Project levels.
The Entries Data Integrity report was improved to ensure such inconsistencies are properly identified.
OCBHT127: not runs with model res.currency.rate to solve
US-13993
Fix on intermission flow: use case with commitment vouchers validation and cancellation in INcoming (ENG)
US-14960
Direct Invoice: “Posting Date” and “Register Posting date for Direct Invoice” in Temp status : to make them “editable” within the same month of the register
X
US-15072
To add in a tab of the supplier invoice (SI), the field name “Details” from the purchase order (PO)
X
US-15410
Taxes: to add more decimal digits in the field Amount (8 instead of 4)
US-15432
In the currency parameters: To add a code fix to change the default value + a patch script to change the already created currencies with rounding = 0.
US-15433
No previous fiscal year in WaCA instances
US-15447
Only for the Dec registers: to prevent the closing of a cash register if amounts in “Unrecorded Advances” and ” Unrecorded expenses” not equal to Zero
X
US-15481
Finance integrity report: double AJI correction at coo and project
X
US-15498
OCA: Prevent draft instance to block revaluation process
X
US-15536
Do not allow to import new rates on closed currency table
X
US-15567
DF OCA_HQ : Please synch deletion of the currency rate related to the ticket US-15537
US-15609
Combined journal report – export file naming
X
US-15744
Ubuntu: Vertical Integration file UpfileToD365
X
US-15834
Ubuntu: config file to improve for currency activation and FP analytic account synchonization
As part of regular upgrades, the PostgreSQL version of UniField has been upgraded to 14.23. All instances which are already on a version 14 will have been upgraded automatically. For instances on older versions a manual intervention is necessary. Details on how to do this are in US-14042
Several APIs have been developed for the SDE (Single Data Entry / SmartScan) project in UniField. These are based on Supply objects Incoming Shipments, Delivery Orders and Picking Tickets. See ticket specifications for more details.
Security measure flagged by OCP / Hack4Value, now if UF instance URL is modified to add a suffix (for example https://176.176.79.99/blablabla ) then no technical information is disclosed.
As soon as an instance receives the UF41 patch, the login screen will change to include 2 additional buttons: “Forgot login?” And “Forgot password?”
When the functionality/button “Forgot login”, is used/clicked on, UniField requests further information from user: email address and (if multiple instances are on the server) the name of the database.
If information submitted matches with a user in the database/instance, UniField will try to send an email to the given email address with the details of the user login associated.
When the functionality/button “Forgot Password”, is used/clicked on, UniField requests further information from user: User login, Email address and (if multiple instances are on the server) selection from the dropdown list of the name of the Database.
Once submitted UniField will check that user profile corresponds to these details and if confirmed will send an email with a Temporary code to given email address.
This Temporary code can then be entered into UniField, in the same “Password management” screen by clicking on the “Add temporary code” button.
In the following screen the Temporary code can be added and the values should be filled by user for their New password and Confirmation of new password. When the “Change password” button is clicked on the user’s password will have been reset.
This resetting of a user password via Temporary code will be logged in the Track Changes for the user profile.
N.B.:In order for UniField to be able to dispatch emails, each UniField instance must have the necessary configuration completed. The menu where the configuration can by made by IT responsible is via menus: Administration > Configuration > Email > Email configuration and requires information specific to that instance / infrastructure.
Even if this configuration had already been completed, this may need to be checked / reset once UF41 has been released.
Users may need to check in their Quarantine/inbox for any emails generated by UniField for this functionality, depending on the sending email address configured by their IT for their instance.
This functionality is not intended to be used by synched users, nor by users who share the same email address with other users in that instance.
Date of production synchronization server patch: 29th April 2026 / 18:00 Geneva time
Latest user rights files updated: UF40.1 can be found here
Note that no user rights need to be loaded at each HQ. This will be done at the Sync Server by the Core team and will update the user rights via Sync for all HQs and missions.
Issue preventing Order Calculation files from being imported in Replenishment Rules has been resolved. The problem was caused by inconsistencies between the updated export template and import validation checks. Users can now successfully import edited Order Calculation files without format errors.
3.1 (US-15685) Cash/cheque registers – Register Responsible now copied to the newly created registers
We identified and fixed a bug occurring when creating the new April registers.
Normally, the Register Responsible is copied from the previous month’s registers to the newly created ones. After the fix, the responsible is now correctly copied for all register types (bank, cash, and cheque), ensuring consistent behavior across instances.
Date of production synchronization server patch: 11th February 2026 / 18:00 Geneva time
Latest user rights files updated: UF39.1 can be found here
Note that no user rights need to be loaded at each HQ. This will be done at the Sync Server by the Core team and will update the user rights via Sync for all HQs and missions.
The system now allows the same step to be used more than once within an ITO/OTO. This makes it possible to record different sub-steps under one main step.
For example, Pre-arrival processing can be added several times with different labels such as Customs, MOH, or MO. Each entry is treated separately but remains linked to the same main step.
This change helps better reflect daily operations when several actions or authorities are involved under the same step.
In addition, ITO/OTO steps can be reused only when the combination of step + sub-step is unique. If the same combination is entered more than once, the system will display an error message and prevent duplication.
3.1 (US-15312) Mass HQ entries validation: Dec + other period: REV is posted in Dec
There was a bug while validating the HQ entries in mass when we had 2 different periods. The periods of the correction were not the correct ones. This has now been fixed.
The new OC/OD “UBUNTU” has been created in the UniField structure meaning that we can meet any future request for a new HQ and other instances for this instance to be created and this will be recognised by the synch server.
An issue meaning creation of new instances was halted at initial synch stage if the next_exec_date in the config file was in the past has now be resolved with this ticket.
Date of production synchronization server patch: 3rd December 2025 / 18:00 Geneva time
Latest user rights files updated: UF39.0 can be found here
Note that no user rights need to be loaded at each HQ. This will be done at the Sync Server by the Core team and will update the user rights via Sync for all HQs and missions.
A set of improvements related to E-validation introduces additional restrictions on modifying signatures for Confirmed, Closed, or Canceled POs. If a PO uses E-validation, a warning message now clearly explains the steps the user must follow to edit a locked PO.
Additionally, the “Approved By” and “Value” fields have been removed from the IN signature table.
Compared to the previous UF version, the PO Allocation Report includes minor changes to column names and introduces a new column displaying the status at the line level.
With these improvements in the PO Catalogue tab, users can now see the positive or negative price deviation per unit in the PO compared to the supplier’s catalogue, when applicable. The deviation is shown at the line level, and the header displays the total percentage deviation between the PO subtotal and the theoretical catalogue subtotal (for catalogue lines only). Additionally, the readability of the PDF PO report has been improved, ensuring that comments are split correctly. The “Date sent” field has also been renamed to “PO Confirmed Date.”
When a local code is merged with a UD code (via manual process), the “New code” field in the non-kept PMD is updated with the kept UD code. This action is available in Coordination and will sync down to the projects.
In Warehouse → Delivery → Shipment, the existing default “Not empty” filter is complemented with two additional default filters: “Draft” and “Ready to Ship.”
A new Order Category filter has been added to the Internal Request (IR) list view page. This aligns the IR view with the existing functionality available on PO, FO, and most warehouse documents. The filter is implemented as a drop-down selection, similar to the one used in the Incoming Shipment list view.
Additionally, a new Order Category column has been introduced in the IR list view to improve visibility and sorting options.
In Partners → Suppliers → Supplier Catalogue, a new filter by product has been added. This allows users to search for a product code across both active and inactive supplier catalogues.
The ticket aligns the behaviour between Intersectional and Intermission flows by allowing the use of local codes in intersectional transactions. With this improvement, the restriction introduced in US-12176 is lifted, and local codes can now be used in Intersectional flows.
When a user tries to validate a PO/FO for an IS Partner containing local products, a non-blocking warning message will appear (one message for all product codes):
“Warning! Line(s) XXXX (line numbers & product codes) contain Local products (which may not synchronise). Please check if these can be replaced with a UniData code, or contact your help desk for further support.”
Several enhancements have been added to Warehouse → Reporting → Expiry → Product Likely to Expire.
A new consumption option, RR-AMC, is now available. When selected, an automatic explanation appears:
“The RR-AMC (Average Monthly Consumption) lets you choose one or more internal source locations, and one or more destination locations so you can view consumption based on specific locations, ECUs or External Partners.”
This note appears only when RR-AMC is selected.
When using RR-AMC, selecting a Source Location becomes mandatory (highlighted in blue). RR-AMC calculations use only the selected source location, and a destination is not required.
The field previously named “Location” has been renamed to “Source Location.”
When the AMC – Average Monthly Consumption option is selected, the Source Location field is no longer displayed.
In Warehouse → Reporting → Unreserved Stock Report, the report will now show only the lines where the stock level is greater than zero. Previously, the report also displayed lines with negative stock, but these will no longer appear.
A new improvement allows users to export a pre-packing list that includes all active packing types in the instance. The exported Excel file now contains a drop-down list enabling users to select a packing type, and the dimensions of the selected pack are automatically filled into the corresponding columns.
To ensure data consistency, UniField now blocks the import when a single parcel range contains more than one packing type. In such cases, the following message is displayed:
“Parcel From 1 To 1 contains multiple pack types. Please assign only one pack type per parcel.”
The same message appears if a parcel range mixes assigned and non-assigned pack types.
Two new buttons have been added to the RFQ, similar to the functionality in validated POs. For RFQs in the “Sent” status, the existing “Import RFQ” button has been replaced with two buttons: “Import RFQ” on the left and “Export RFQ” on the right. Clicking “Export RFQ” allows users to export the modified RFQ file. Clicking “Import RFQ” enables users to import a file that updates the Price and Confirmed Delivery Date fields, while modifications to other columns are not allowed. The Header “Valid Till” field can also be updated via the import file.
Consolidated Mission Stock cannot be generated when the number of columns exceeds 256. This limitation is linked to the format of the generated XLS report.
A temporary fix has been introduced: the system now blocks the generation of the consolidated mission stock when the number of columns exceeds 255 and displays a clear error message advising the user to generate the MSR per individual instance.
A permanent solution will be delivered in the next release, as it requires changing the report format for both the Consolidated MSR and the standard MSR.
We have developed an adjustment to the report criteria so that a journal is listed if a register has been created for the period or if the balances are not zero.
We have developed and implemented the requested enhancement, viewable in the “Companies” menu under the “Configuration” tab.
A new mandatory dropdown field named “Extra Accounting Behavior” has been added. This field becomes read-only once the instance is created, to prevent discrepancies and ensure consistency across instances.
The dropdown includes three predefined options, each corresponding to specific booking permissions for periods P13, P14, and P15:
As this field is read-only after instance creation, changes (e.g., switching from OCB to OCA behaviour) will not be possible via this configuration.
We have implemented the requested control in the Human Resources tab.
For employees flagged as “Not to be used”, the system now prevents users with coordination rights from setting their status to “Active”. If such an action is attempted, a warning message is displayed:
“You cannot activate an employee flagged as not to be used.”
(French: “Vous ne pouvez pas activer un employé marqué comme ne plus utiliser.”)
This measure was introduced to ensure data consistency and avoid unintended reactivation of inactive employee records.
We have added the track changes feature to the “Not to be used” field in the employee form.
This enhancement allows for better tracking and review of any updates made to this field, ensuring improved auditability and accountability in employee data management.
We have implemented the requested export enhancements in the Supplier Invoice (SI) module.
If the invoice line is split across multiple analytic dimensions, all elements are displayed with a separator (no percentage shown), ensuring full visibility of the allocation.
These changes are export-only and have no impact on the user interface or manual data entry.
We have updated the warning message implemented under US-12267 to improve visibility and reduce user errors during period closing.
Previously, the red warning message was displayed above the “Cancel” and “Confirm” buttons, which made it easy for users to overlook the message and mistakenly freeze the balance of the current period while closing the previous one.
To address this, we have:
These changes aim to reduce the risk of accidental actions and improve the overall user experience during period closing.
This change means that at the password addition stage of AiO installation, there is no default password already there, meaning user must enter a new password for each field.
This development has 2 components: i)where a server contains multiple UniField databases, where the filter is set so that the URL displays a targeted database (by default), this instance will be displayed by default as the selected instance on the login page. As only one of the instance on this server will act as the master for the synch server user connection, this “master” instance will be displayed on the login page also.
APIs have been developed based on WaCA’s request for integration with their planned HQ Accounting system. Tables have been made available to export Local employees, Partners and Journals.
These 2 tickets already implemented for OCA have now been released meaning that files are not blocked due to folder layers or zipper folders in destination locations for SharePoint exchanges.
With this release, the version of PostgreSQL has been upgraded to 14.20. All instances having a recent version of PSQL will automatically be upgraded. However those with v.9.6 will not be as they require manual intervention.
Date of production synchronization server patch: 8th October 2025 / 18:00 Geneva time
Latest user rights files updated: UF38.1 can be found here
Note that no user rights need to be loaded at each HQ. This will be done at the Sync Server by the Core team and will update the user rights via Sync for all HQs and missions.
JIRA filter for all integrated tickets: https://jira.unifield.org/issues/?filter=12551
Regression linked to ticket US-12325 released in release UF38 meaning that the balance of historical quantities and current stock quantity on a stock card were not displayed in the correct order. This has now been corrected.
Regression linked to ticket US-9592 which introduced Pack ID in release UF38 identified by OCA meant that when user added and saved a new parcel comment in a Shipment List, this comment was not visible either onscreen or in PDF. This has now been corrected.
This bug identified by OCB meant that it was possible to source products with status “Phase out” to an ESC type supplier by using the multiple source lines option in the Order Sourcing Tool and then choosing to Source default.
2.1 (US-14870) OCP: GL selector: Not reconciled/Open items at – “an application error has been reported”
Regression due to US-13945 in released in UF38 caused this bug affecting the output of the selection in the GL selector. This issue has now been fixed, and the selection output is working as expected.
2.2 (US-14864) OCBPL101 Import of entries error “charmap” in prod, but in sandbox works
Regression due to Python migration in previous release caused this bug that prevented the import of entries when special characters were present. This issue has now been resolved, and the import can be performed without any problems.
This was a major issue and is the reason for the intermediate release as was impacting OCs in multiple ways.
Due to a Microsoft/SharePoint decision to change the allowed authentication method, UniField could no longer connect to SharePoint as it previously did. This connection was essential for allowing certain back-ups of UniField instances to be sent to a SharePoint repository as well as for Vertical Integration imports where OCs had configured UniField to pull data for imports such as International Invoice Lines, Expats and HQ entries from SharePoint. With this ticket, new fields are introduced into Tools>Tools>Automated Imports screen so that if the Protocol “OneDrive” is selected additional fields appear and can be filled for the Tenant-id, App-id and Certificate. These are used by SharePoint to verify the connection with UniField.
The equivalent fields are also in Synchronization > Backup > Cloud Backup Config and where values are added for these at HQ for an instance, they are synched to that instance and facilitate the back-ups of that instance to be sent via Direct push to SharePoint protocol.
Date of production synchronization server patch: 17th September 2025 / 18:00 Geneva time
Latest user rights files updated: UF38.0 can be found here
Note that no user rights need to be loaded at each HQ. This will be done at the Sync Server by the Core team and will update the user rights via Sync for all HQs and missions.
The ticket focuses on unlocking the use of MISC roots for Local codes.
Please note that the MISC root is archived in UniData. However, due to specific operational flows, SPINCO platform members agreed to allow its use exclusively for Local codes.
If the MISC root is selected for a non-local product, a blocking message will be triggered.
Additionally, with US-14269, a new rule has been introduced: when an archived root is selected in PMD, a pop-up blocking message appears — “You cannot create a product with an archived Root Nomenclature.”
(Currently, this message is only displayed when the user clicks Save / Save+Edit.)
With these improvements the use of the product creator Temporary is blocked.
Also some modifications are introduce in Local codes creation process.
When creating a new code at Coordination level the default product creator is set to “Local”;
The system improvements include the following: introducing an immediate blocking message if the entered code contains fewer than 11 characters, with the text: “The code must be between 11 and 18 characters. Please adjust and try again” (note: code creation is already limited to a maximum of 18 characters);
A non-blocking warning message appears at the moment of selecting nomenclature when the selected nomenclature does not correspond to the code (e.g., code CWATZAF0001 with nomenclature ADAPXXXXX), displaying: “Warning: you are about to create a product which does not correspond to the nomenclature, do you wish to proceed?”.
The ticket introduces a functionality allowing merging of 2 Local codes. With this release, two Local products can be merged at Coordination level, even if they are in stock or have open transactions. Once the merge action has been performed for the 2 Local products, the selected (non-kept) product will be de-activated in Coordination. After synch, this non-kept product will be de-activated in all Project instances, and any quantities in stock or open or closed transactions will be updated so that the active “kept” product will appear in its place. “New code” field will be updated with the kept product code in the non-kept PMD.
If 2 Local codes have inconsistencies in Product type/Main type the blocking message will prevent merging of 2 Local codes. User rights for merging products at Coordination level have been added to the group Sup_Product_Mgr_Coordo.
If 2 codes were merged at UniData level, in the “non-kept” production UniField, a new code value is pulled through the API. This value will appear in the PMD “New Code” field, and will wipe any pre-existing value in the field. Active track change makes it possible to track updates to the new code field. Please note that merge at UniData level does not indicate the product has been merged at UniField level. All merges in UniField must still be triggered manually.
The improvement focuses on enhancing the readability of the Stock and Pipeline report available in Tools at HQ level. When a code is present in stocks and pipelines across multiple instances, the information is consolidated into a single table, making it easier to analyze.
Currently when the TO BE SIGNED filter is ticked documents that are in status cancelled still display for the user to sign. This ticket changes Signature Follow-Up Screen to ensure that cancelled documents are not displayed under the “TO BE SIGNED” filter.
The improvement introduces a new way of managing external partners. This tickets support cleaning of the partners at instance level. New De-Activate / Re-Activate Supplier buttons have been added on supplier records.
If open documents for the external partner exists, the partner is set to the status Phase-Out
Users can either manually re-check if the partner can be deactivated, or wait for the new automated daily task that will attempt to deactivate Phase Out partners.
Partners in Phase Out cannot be used for new supplier invoices or new draft POs, but existing validated processes can continue until closure.
Partner activation, deactivation, creation, and phase-out actions remain managed at instance level only.
If the supplier is in status Inactive or Phase Out, it is possible to reactivate them using the Re-Activate Supplier button (same behavior as the De/Reactivate product button).
Phase Out Principle (similar to code deactivation flow)
When a partner moves from Active → Phase Out:
Financial documents:
If a supplier is in Phase Out status, new manual supplier invoices or new direct invoices cannot be created.
Other operations remain possible: registers, manual journal entries, refunds, reconciliations/unreconciliations.
Supplier invoices coming from Supply remain allowed.
Supply documents:
Processing of opened PO/FO/IN/OUT/PPS linked to a Phase Out partner is possible.
If PO is in Draft and the supplier is Phase Out → warning message: “The selected supplier is Phase Out. Select another supplier.”
Phase Out partners are automatically deactivated when all linked documents are closed.
Partner (Phase out) in different Configurations
When External partner is configured as Supplier / Manufacturer / Transporter
Draft PO with Phase Out supplier cannot proceed.
Draft PO can be cancelled/recreated with a new partner, or partner can be changed directly in the draft.
Validated PO and statuses after can continue until closed.
New filter introduced: Show Phase Out (alongside existing “Show Active” and “Show Inactive” filters).
Reports including partners will continue to display Phase Out and Inactive partners.
When External partner is configured as Customer
Draft FO for Loan can proceed if the partner is in Phase Out.
Draft PO for Loan Return can proceed until closure, even if the partner is Phase Out.
Donations and Programmatic Donations with validated FO/PO can continue until closure, even if the partner is Phase Out.
When External partner has Mixed Configuration (Supplier + Customer + Transporter + Manufacturer)
Validation will be applied per role, following the same rules described above.
The task is available under Tools > Tools > Delete Old ESC Catalogues. It is deactivated by default and if active will run with a default interval of six months between executions.
The functionality will be extended with a new “Specific Partner” field, allowing users to delete ESC catalogues only from a selected supplier. This field is mandatory.
The deletion configuration is defined at instance level.
For visibility, a new sub-menu is introduced at instance level. The list will display:
Source instance
Date of deletion
Number of catalogues deleted
Clicking on a record will show these details plus the Last Execution Message (including the catalogue names).
Since AMC/RR-AMC is calculated based on past months and the current month (Max), the improvement is limiting the selection of months for the AMC/RR-AMC calculation to a maximum of the current month.
Additionally, when RR-AMC is selected, an explicit explanatory message will be displayed: “The RR-AMC (Average Monthly Consumption) lets you choose one or more internal source locations, and one or more destination locations so you can view consumption based on specific locations, ECUs or External Partners”.
Physical Inventory rules are designed to ensure only one active inventory process exists per location at a time: users cannot open multiple Full, Partial, or Stock Correction inventories simultaneously, nor mix these types for the same location. Multiple inventories of any type are only allowed if their status is Confirmed or Closed. If a user tries to generate a counting sheet for a new inventory while another is already open at the same location (in any status other than Draft, Confirmed, or Closed), a blocking pop-up will appear stating: “Only one Physical Inventory can be open per location at the same time. Please finalize or cancel Physical Inventory [xxx] before creating a new one for this location.”
A new state “Partially Processed” was introduced in auto-VI to indicate cases where some lines were rejected but the import was not in an error state; in this state, the system correctly counted the number of rejected lines and displayed the corresponding error messages from those rejected lines.
To support introduction of a single pack ID, new information in regards to Single pack ID can be imported in UniField. After import of the e-PL via Vertical Integration the parcel IDs are displayed in the processing screen of the Incoming Shipment including the possibility to filter the content of the IN on specific parcel ids.
When processing the IN to SHIP the parcel ids are promoted to the PPL as it is done with the supplier packing list so that there is no need to re-label boxes and to use the parcel ids.
If the Pack ID was imported for the IN, the corresponding checkbox “P.ID” is ticked in the In Process pop-up window, and users can view the Pack IDs by hovering over the parcel number.
Packing list (PDF/XLS) will also contain information about Pack ID identification after the import.
We have added a checkbox to the currency table configuration: “Is for revaluation?”
Implemented Behavior:
EoY Revaluation Restriction:
We restricted the application of EoY revaluation to tables marked as “for revaluation.”
The system now limits the list of available tables to those that are active and flagged for revaluation.
This ensures that OCs not performing revaluation do not need to change their current processes.
WeFin Automation:
We excluded revaluation tables from the automation of actuals in WeFin to avoid incorrect usage.
This setup helps prevent situations where WeFin rates could be mistakenly used for EoY revaluation, which would result in non-correctible entries. The use of designated revaluation tables ensures proper data flow and supports balanced entries.
We have applied a fix to the trial balance export to ensure it correctly accounts for reversing accruals as of 31.12.XXXX, in the context of end-of-year closure.
This adjustment ensures that the trial balance reflects the financial reality more accurately at year-end.
We have identified an issue where it was previously possible to close a period even if accruals were still in draft status. Although an error message was displayed, it did not block the process.
To address this, we have requested the implementation of a blocking mechanism:
If accruals are in draft, the system will prevent the period from being closed until those entries are posted.
This change is intended to reinforce data integrity during the closing process and avoid inconsistencies.
We have created an import file accessible from the “Actions” menu in the Fixed Assets module, specifically for the “Asset Reference” data.
This import file allows users to trigger both the External ID and the Asset Code, streamlining the process of asset registration and ensuring consistency in data entry.
We have set the menus “Asset Types” and “Asset Events” to read-only at the project level.
Previously, it was possible to edit these fields without any alerts or controls in place. This posed a risk, as these parameters are meant to be managed centrally.
With this update:
These fields can no longer be edited at project level.
All configurations must be defined at HQ level and are now synchronized accordingly.
This change ensures consistency and prevents unauthorized modifications.
We have encountered a situation where no synchronization runs were triggered for the model account.move, due to the inactivation of bank and cash journals before the last entries were synchronized to HQ.
What We Observed:
Journals were inactivated while entries were still pending synchronization.
The system did not alert us or block the process, leading to missed data transfers.
This issue is new to us, as journal inactivation was not previously possible, and therefore such synchronization problems had not occurred before.
This synch rule has been fixed to avoid this problem.
We have reviewed the behavior of Operational Advance Management regarding the ability to link advances to a Purchase Order (PO).
What We Observed:
In the Cash Register, the system allows linking the advance to a PO.
However, in the Bank and Cheque Registers, this option was not available.
What We Have Done:
We have aligned the behavior across all liquidity registers, ensuring that the PO link is now available in both Bank and Cheque Registers, just as it is in the Cash Register.
This update ensures consistency with the documentation and improves usability for teams managing operational advances.
We have extended the export functionality for the Balance Specification Report to cover additional scenarios beyond the Coordination screen.
What Has Been Done:
The report can now be exported from HQ, including for closed periods, specifically for the HQ instance.
Export is also enabled for inactive proprietary instances, which was previously not possible.
This update ensures that even when a proprietary instance is closed and no longer accessible via Coordination, the report can still be retrieved from HQ.
Export Availability Matrix:
HQ Instance
Coordination Instances
This enhancement ensures continuity in reporting and access to critical financial data, even after instance closure.
We have made a display improvement in the Balance Specifications Report to enhance clarity.
When the “End of Year” option is selected in the wizard, the FXA tab (Sheet #2) now shows in cell B4 the label: “Full year export YYYY” (e.g., “Full year export 2025”) instead of the standard period format.
This change helps clearly distinguish annual exports from monthly ones and improves the readability of the report.
This was a high-priority ticket which means it is now possible for users to import their scanned signatures into their signature space in UniField. This signature can be used in the same way as the previous digitally written signature: when user clicks to sign a document, this signature appears on the onscreen document, and also on the relevant PDF. It can be deactivated and replaced. The original digitally written signature still remains as an alternative option for users if they still prefer this. When adding their signature, user can choose “Type of signature creation” options “importing” (scanned signature) or “drawing” (directly in UniField with mouse etc). For the import option, the template can be exported, and then user must sign in the designated signature zone. This should then be scanned and saved as*.png, *.jpg, *.jpeg or *.pdf file. This can then be added to the field “Import your signature” by clicking to add attachment.
Development requested by Supply to make email usage more user-friendly, a new E-mail column has been added to the list view under Administration → Users → Users. Additionally, new E-mail filter is introduced to make it easier to search for users by their e-mail address.
Date of production synchronization server patch: 13th August 2025 / 18:00 Geneva time
Latest user rights files updated: UF37.0 can be found here
Note that no user rights need to be loaded at each HQ. This will be done at the Sync Server by the Core team and will update the user rights via Sync for all HQs and missions.
UF 37.0 introduced changes to the Incoming Shipment (PDF) signatures that inadvertently altered how the electronic signature is displayed. This ticket aims to restore the correct behavior—ensuring the electronic signature appears on the Incoming Shipment PDF—and to unblock missions already using UniField’s E-Validation feature.
The OCP HQ Workday VI export for the report “Monthly export” has been changed so that before UniField rounds/adjusts the Functional credit and Functional debit values to match, it checks first that the relevant Booking currency credit and debit values match. If they do not then no rounding is made on the functional columns. This change will allow OCP users to more quickly identify issues such as duplicate / unbalanced entries which previously were causing issues with closure after integration into workday. There is no change to the way UniField calculates any system values, so no impact on other OCs / exports.
In this dev, raised by OCB, a bug in openerp is corrected so that for servers / machines which host multiple instances of UniField, it is possible to specify a domain name for each, and when link is clicked on, only the relevant UF database is displayed on login page.
It is now possible to add in openerp-web-oc.cfg config file, this new directive to filter the list of dbs on the login page.
Date of production synchronization server patch: 11th June 2025 / 18:00 Geneva time
Latest user rights files updated: UF37.0 can be found here
Note that no user rights need to be loaded at each HQ. This will be done at the Sync Server by the Core team and will update the user rights via Sync for all HQs and missions.
To reduce the potential for data encoding errors that can lead to incorrect picking locations when users are using the Order Sourcing Tool (OST), we are implementing a change regarding the “Stock” warehouse location. This update involves removing the “Stock” location as the default preselection when sourcing items “from stock.” The goal is to decrease the likelihood of mistakenly sourcing goods from the “Stock” warehouse location.
The default location will now be set to empty, rather than defaulting to “Stock.”
Note: Location is a mandatory field. If no location is selected, a blocking message will appear, similar to the behaviour when the procurement method “On order” is chosen. The “Stock” location will remain available in the dropdown list for selection.
To improve visibility and utilize the new ranking feature for sourcing management at the user level, a new column called “Ranking” has been added to the Order Sourcing Tool. This column displays the line ranking from the selected supplier catalogue (sourced from the product card). If two supplier catalogues exist for the same code/ranking, the supplier with the lowest price is selected.
Previously, suppliers were chosen in alphabetical order when all other conditions were equal.
A bug fix addresses the export behaviour of the FO follow-up report and adjusts the column positions. The issue was identified in the previous UF version.
As the Loan Return PO is created automatically via the Loan flow, and not from scratch. With this correction a change of a partner in a loan return document is not possible anymore.
The improvement renames the report from Product Inconsistencies Report to BN/ED Inconsistencies Report. The location of the report moves the report from “Tools” to Warehouse >Traceability (under “Batch Location”). Abbreviation of the report is adjusted to make it easy to read.
A new Standardization level column is introduced in Product Status Inconsistency report. The values pull information from the product card (Standard/ Non-Standard/Non- standard Local).
The report moves from Tools to Product> Reporting (new submenu is introduced under “Product update”)
Naming of columns is changed to improve readability of the report.
N.B. Columns “Total Quantity Likely to Expire” and “Total Value of Likely to Expire Quantity” excludes qty and value of already expired products.
2.10 (US-13923) Multiple lines AD missing on PO/FO: change of warning message
This improvement enhances the visibility of lines missing Analytical Distribution in PO/FO. A new dynamic pop-up warning message on PO/FO notifies users about lines missing Analytical Distribution: “Analytical distribution is missing for lines A, B, C. It must be added manually.”
The warning message dynamically lists only the lines missing Analytical Distribution. If the Analytical Distribution for a line is corrected, that line is automatically removed from the error message.
A new column, “Approved by” has been added to the Incoming Shipment PDF. It is positioned after “Received by” and “Controlled by” The French translation has been aligned with standard supply terminology.
This improvement standardizes the behaviour of warning messages for blocking and non-blocking attributes related to the Local Code/UD Merge functionality.
When merging Local and UniData codes, if the Main Type differs between the Local Code and UniData codes, users receive an immediate blocking message.
“There is an inconsistency between the selected products: Main Type need to be the same. Please update your local product Product Type and then proceed with the merge. Products XXXX and XXXX”
As part of the Programmatic Donation development, this improvement introduces a new field, “External Partner,” in the Historical Consumption Report when using the RR-AMC function. The goal is to enable AMC extraction for a specific customer or multiple customers. Additionally, “Source” and “Destination” have been renamed to “Source Locations” and “Destination Locations.”
The RR-AMC will continue to be calculated as usual but will only consider outgoing moves involving the selected partner(s).
The following rules apply to the new field:
– If an External Partner (Type: Customer) is selected as the destination location, the source location must be either Internal Locations or Cross-Docking.
– The source location can also be left empty, in which case only movements from Internal Locations and Cross-Docking will be included in the RR-AMC calculation.
– An External Partner can be combined with an External Consumption Unit as the destination location.
– If “Other Customer” is selected as the destination and you attempt to select one or more External Customers, a warning message will block this action.
– Similarly, if “External Customer” is selected as the destination and you attempt to select “Other Customer” a warning message will also block this action.
This release improves landing pages for Sign-only Users, makes UniField easier to navigate. The role/function titles aligned between the PDF (Incoming Shipment, Internal move, and Delivery Order).
With new improvement E-validation is available in Physical inventory in “Validated”, “Confirmed” Statuses. The signature order in the PDF follows this sequence: Warehouse Responsible, Supply Responsible, and Stock Owner (with the Stock Owner’s signature being optional). If the signature is accepted on validation and the Physical Inventory is set to Re-count or Regenerate Discrepancy, all E-signatures are removed. To confirm inventory, the PI must be signed. If no signatures are provided during the confirmation process, a blocking message will appear:
“The Warehouse Responsible role must be a signer in order to confirm inventory.
If the signature is provided physically, please select ‘Sign Off-line’.”
3.1 (US-13520) “Fixed Asset Register”: creation of a new report for audit purposes (in the asset form menu)
A new register for all fixed assetshas been created in the screen Asset form, in the right action menu.
The report can be issued in PDF and Excel formats.
3.2 (US-13582) Fixed Asset: to allow to delete generated UNposted depreciation entries in the asset form (same functionality as in the recurring entries)
We can delete the Unposted entries via the button Delete Unposted entries
After this deletion, we can generate the entries again
3.3 (US-13662) Fixed Asset: to add restrictions when we create an asset form from scratch from a JI
We have done a fix in order to avoid errors. We have prevented that the initial line creation when the JI will be on a depreciation Account.
3.4 (US-13716) Fixed Asset: Account code restriction for manual creation at Journal Item level (in the Asset Forms screen) + renaming
The list of Journal Items (JI) available for selection on the manual asset form was restricted to those linked to account codes where “Prevent Fixed Asset on HQ entries”had not been ticked.
This meant that when an account had been tagged as “Prevent Fixed Asset on HQ entries”, the system did not display journal items from that account in the “Journal Item” field of the asset form used for manual creation.
If the checkbox had not been ticked, journal items were displayed for manual asset creation and HQ entries capitalization was allowed.
If the checkbox had been ticked, journal items were not displayed, and the account could not be used for HQ entries capitalization.
It should be noted that asset capitalization accounts were not meant to be ticked, and therefore were displayed in the list of journal items for manual asset creation — serving as a workaround for capitalization of multiple items from HQ entries.
In the “Search: Accounts” screen, the checkbox on the “Chart of Accounts” (COA) section and its corresponding filter were renamed as follows:
: Prevent capitalization of entries
: Empêcher la capitalisation des écritures
3.5 (US-14168) Fixed Asset: Colour in blue draft + grey disposed asset form on list view
The draft asset forms are in blue and the fully disposed are in grey.
3.6 (US-13624) Combined Journal report: Bad selection results “exclude journal” ENG
In the combined journal report: we are now able to exclude from the selection the analytic journal ENG. This was not possible before, so it has been fixed with this ticket.
3.7 (US-13801) Internal transfers: to add a new constraint to prevent to change the account code on a counterpart line
There was already a constraint to prevent to change the 3rd party on a counterpart line with a transfer account (US-12678). Here we have added a new constraint to prevent to change the account on a counterpart line.
3.8 (US-13963) Not to be able to select an inactive staff when booking an entry in the cash registers
Since UF34.0 release, based on the ticket US-12274, users created via duplication no longer inherit the last connection date value from the original user. This ticket cleans the historical data = sets users_last_login.date to null for the users whose users_last_login.date is earlier than res_users.created date.
Users created via duplication inherit the last password change value from the original user while users created from scratch have last password change equal to create date. This ticket ensures that all new users, including those created via duplication, will now have last_password_change set to their create_date. Moreover it cleans the historical data – sets res_users.last_password_change to res_users.create_date for the users whose res_users.last_password_change is earlier than res_users.create_date and for the users whose res_users.last_password_change is before June 16th, 2021 (when the res_users.last_password_change column was introduced).
Entries related to property_product_pricelist_purchase, property_product_pricelist, property_account_receivable and property_account_payable were deleted from ir_property table since property_product_pricelist_purchase, property_product_pricelist, property_account_receivable and property_account_payable columns in the res_partner table have been modified in US-10652.
With this ticket, an adjustment has been made so that with current version of Python version used in UniField, an email can be triggered by UniField. This is a technical ticket as no rules have yet been defined to launch the emails.
With this ticket, the version of PostgreSQL for all instances already on v.14.16 will be updated to v.14.18. This ticket is one of several measures relating to IT security via regular upgrades. For any instances not yet on v.14.16 (e.g. those still on v.9.6) there will be no change as they would still need manual intervention.
Last password change of duplicated users + cleaning historical data
X
US-14124
Cleaning ir_property table
X
US-14239
Email configuration: adapt code for python3
X
US-14148
Possibility to extract translation file via UI of UF
US-14105
Upgrade of version PostgreSQL: Patch from v.14.16 to v.14.18
X
US-13877
Patch application: unable to restart unifield-server
We use cookies to ensure that we give you the best experience on our website. If you continue to use this site we will assume that you are happy with it.
