Expose Upcharge Details and Overrides in MFCS Transfer and Allocation REST Services

User_EEWPP

The current MFCS Transfer and Allocation REST Services do not expose the required upcharge information in their request payloads. As a result, external systems that calculate transfer- or allocation-specific costs cannot pass these values to MFCS at the time the transaction is created.

In our integration architecture, the external system is responsible for calculating the applicable upcharges based on operational and business rules, including components such as freight, handling, duty, and internal logistics costs. These values need to be preserved and reflected in MFCS as part of the transaction cost information.

Currently, the external system has no supported API mechanism to provide these calculated values or override the MFCS-derived/default upcharge values during Transfer or Allocation creation. The available workaround is to create the transaction first and subsequently perform manual adjustments or backend data corrections. This introduces additional operational effort, is not suitable for high-volume automated integrations, and creates a risk of discrepancies between the source system and MFCS.

We believe this would be a valuable enhancement to the MFCS REST API model. Ideally, both the Transfer and Allocation Creation APIs should expose a structured upcharge section in their request schemas, allowing the consuming application to provide, where applicable:

• Upcharge Group / Type
• Cost Component
• Rate and/or Amount
• Currency, where applicable
• Item-level or transaction-level applicability
• Ability to explicitly override the MFCS default/calculated value
• Multiple upcharge components for the same transaction, where supported by the MFCS costing model

The enhancement should also ensure that the externally provided upcharge information is validated according to the same business rules applicable to MFCS-managed upcharges and is correctly incorporated into the resulting transaction and costing information.

This capability would allow external planning, logistics, and execution systems to remain the source of the calculated upcharge information while ensuring that MFCS receives the complete transaction cost data at creation time. It would eliminate manual post-processing, improve automation, and reduce discrepancies in inventory valuation and landed cost calculations.

We would appreciate Product Management's guidance on the recommended API model and whether the existing MFCS upcharge/cost component framework can be exposed through the Transfer and Allocation REST Services.