2021 R3 Release – Levridge

Levridge is excited to make available the third and final release of 2021. This release has two primary themes:

1. The footprint of splits and split billing have been significantly lightened. Levridge functionality around splits and the ability to split invoices is now much more dynamic and flexible than ever before. Splits can be adopted or ignored based on client business processes and based on the specific customer they are working with. Additionally, split billing functionality does not interfere with ISV or intercompany functionality in the sales order process. Lastly, splits still provide the power and capabilities they had before where invoices can be split as many ways as a client desires, prepayments are automatically applied to split invoices and split invoices can be easily rolled back and corrected when additional changes are needed.

2. The foundation for supporting AgXML document exchanges has been added and the first implementation of that framework, commodity movements, is now supported. With the AgXML foundation, Levridge has added file watching capabilities for reading AgXML physical documents, processing them in the cloud and importing them into Microsoft Finance and Operations. Levridge will continue to expand the types of AgXML documents that can be exchanged throughout upcoming releases.

Key Metrics

In the creation of the 2021 R3 release, the Levridge team:

• Closed 754 tasks and issues
• Created and executed 738 automated check-in tests
  • • All 738 tests are running with each and every change to Levridge code to ensure long-term functional stability and consistency.
• Executed 460 manual tests

Looking Ahead to 2022 R1

In 2022 R1 Levridge is adding the following features and enhancements:

1. Load request and load generation enhancements

• • Add the ability to create a load order not tied to a commodity sales contract. Also, add the ability to apply an outbound scale ticket to that load order and update the load with the customer, ship to and sales contract details. Lastly, extend the AgXML feature built in the 2021 R3 to include support for load orders.

2. Support for perpetual inventory/costing

• • Currently Levridge commodity supports periodic inventory valuations where the value of inventory (and thus COGS) is determined at the end of the month. In the commodity processor market, they often want to keep perpetual inventory, and thus maintain inventory cost and COGS with each transaction.

3. Updates to commodity sales contracts from sales orders

• • When using Ag sales sales order entry, allow the quantities sold and returned via sales orders to be applied to commodity sales contracts.

4. Support for seal numbers

• • Record seal numbers on inbound and outbound scale tickets. Seal numbers are identifiers zip-tied to railcar hatches. The seals are used to track whether or not tampering has occurred while railcars are in-transit from their origin to destination locations.