2022 R3 release for Levridge is officially available! The feature set for this release is focused on responding to client requests. Key New Features in 2022 R3 1. Ability to define shipment delivery times on load requests and load orders Via a parameter in Commodity Accounting Parameters > Commodities > Loads, you can set a […]
Grain shipped not invoiced is used when a company gets an invoice and settlement sheet from the buyer of the grain. The company is trying to match the customer invoice/settlement sheet to the company’s scale tickets. Shipped not invoiced bulk is used when the selling company is originating the invoice/settlement sheet and the customer has to match them.
There are several posting accounts needed for commodity accounting when processing inbound and outbound tickets and settlements. This blog outlines each place posting accounts are needed and when they will be used.
Business Events are a way Dynamics 365 Finance and Operations (D365) can communicate with external systems. Levridge created our own business events in D365 to create XML files following the AgXML framework.
Purchase advances can be created in Levridge using the following steps. Under the Commodity accounting module create a purchase contract and apply scale tickets to the contract.
Levridge has support for seal numbers on scale tickets and on sales orders for packaged products. On all scale tickets, seal numbers can be added by clicking the Seal numbers button on the scale ticket form.
The inbound in-transit feature allows a buyer of a commodity to know that a commodity is in-transit from the seller. This will help inform the buyer of the quality of the commodity, and its estimated delivery from the seller. This feature can help the buyer better manage their inventory and schedule production based on the quality of the incoming commodity.
The logic for validating the ticket lies within Levridge and is usually communicated to the user via an Info log message. When Levridge Exchange attempts to push data to Levridge via an OData data entity and entity validation fails, the OData framework in FinOps generates an exception populated with the Info log messages for that entity.
The first part of the mark to market process is to create the Market Price Entry. This will be the lines that will determine the market board and basis prices to be used in the mark to market calculations. When creating the new market price entry you can give it a unique schedule ID along with a description.
The 2022 R2 Release for Levridge is available with several new features integral to making a difference in businesses in the commodity processing market. View the overview below or read the full release notes here Key Additions in 2022 R2 Levridge Release: 1. Inbound in-transit scale tickets Larger commodity processors and elevators buy commodities from […]
