Agiblocks 3.21.4 Release Notes

Version 3.21.4 is a minor release for Agiblocks that contains an optimization that allows Forex requirements to be created automatically when contracts are created. A fix for how contract realization date is recognized in certain modules and an option called Harmonization about when Agiblocks values physical commodity assets have been included. A variety of customer support requests have also been fulfilled.

A fix was made so that all assets that are realized at a certain date are treated as realized in the Mark to Market snapshot with that same date in Mark to Market/P&L Insight screens and downloads. For non-derivative assets, the same applies when looking at current data in Mark to Market/P&L Insight; when these become realized as per today then they are immediately treated as realized. For derivatives this is different in current date, as they are not realized until the end of their expiration date.

On contracts until this release, when Agiblocks detected a currency risk related to the settlement currency or position currency difference, Agiblocks gave the trading user a warning or, depending on contract status, an error. This told a user they should create an FX Requirement and next they should create it.

This process has been made easier in this release. Instead of giving the trader the warning/error, Agiblocks will create the FX requirement automatically. However, automatically created FX requirements are meant to make things easier, but not take away oversight or the ability to make adjustments:

•	Trading users can still change them, e.g. adjust the rate or amounts or maturity date

•	Trading users can also delete them; as soon as you do this, Agiblocks will stop automatically creating FX requirements for this delivery, assuming you prefer to do it manually for this case.

o	The settlement or position currency differs from the price currency

o	The trading user did not yet create the FX requirement themselves

•	It uses the full amount in price currency as the from-amount

o	For settlement risk, you sell this for a purchase, or buy it for a sale

o	For position risk you buy this for a purchase, or sell it for a sale

•	It uses the latest rate from market data and calculates the to-amount in the other currency

•	The maturity date is based on the delivery period and payment terms:

•	The middle date + number of days specified by the payment terms

Additional FX requirements are created for subsequent changes to the settlement currency/position currency:

•	For the from-amount it will then use the to-amount of the last FX requirement

As before, treasury users of the Forex allocation screen, can still decide for any FX requirement, to hedge it differently (e.g. at a different rate), or not to hedge it at all.

Agiblocks normally harmonizes the valuation parameters that control how any physical commodity asset is valuated. This means that all non-sales assets that are reserved for delivery to a specific sale, will be valuated in the same way as that sale. The effect of this is that on reservation you already get an unrealized P&L in which the spread between market prices and market premiums is eliminated. This is typically a more correct predictor of the final realized P&L. However, if you reserve a long time in advance with substantial market spreads between the asset and the sale, this prediction may be less correct unless you add to your cost sheet the cost-of-carry.

For customers who reserve a long time in advance, Agiboo has made it possible switch off this harmonization upon reservation to sales. This switch can only be done by an Agiboo consultant. Harmonization will then take place only once you execute the sales delivery.

Important: Harmonization upon reservation to sales can only be switched on or off for you by Agiboo consulting, as it requires Agiboo to run a new evaluation of all your open assets to make the system consistent. If you wish more information about this topic, please contact your Agiboo Project Manager.

When generating logistics and financing documents, it is now possible to include merge fields with details from the purchase or sales invoices. For this purpose we added these 2 merge field properties to the logistics delivery line model for document generation:

•	This provides a collection of Invoice Line items allocated to the Purchase cost item of this logistic delivery line. This is empty when this delivery line has no purchase side.

•	This provides a collection of Invoice Line items allocated to the Sale cost item of this logistic delivery line. This is empty when this delivery line has no sales side.

For both cases the individual invoice lines can be accessed using TableStart and they have all the properties as documented for Invoice Line in the template guide. To access the merge fields of the invoice header details (e.g. invoice number and total amount) each Invoice Line has a property Invoice.

To also support accessing the purchase invoice for delivery from inventory, Agiboo added another merge field property to the logistics delivery line model: OriginalPurchaseDeliveryLine. This gives access to the delivery line of the original purchase, and from there you can access the PurchaseInvoiceLines mentioned above.

•	The report model for contracts has been extended to include the field Extra contract text from the contract form.

•

When scrolling horizontally on the Position screen, the first column in both tabs showing the futures period or reporting period will now stay in place at the left side of the screen. Please note that the scroll bar to scroll the screen horizontally now appears under the table instead of at the bottom of the screen.

•	On the Realized P&L and Unrealized P&L screens, the first column shows the currencies and currency rates will now stay in place at the left side of the screen. Scrolling the screen horizontally is also done at the bottom of the grid.