⚖️ Quick Guide - Storage (Load Tickets and Contracts)

The Storage module handles what happens at the scale: what comes in after harvest, what goes out sold, and everything that gets weighed along the way. It answers the end-of-season questions: how much each field yielded, how much is in the warehouse and how much is still left to ship on each contract.

The chain is short and worth understanding before you start: the discount table defines how much the grading deducts; the season and the contract say which discounts apply in each case; the inbound load ticket brings the load from the field into inventory; the contract holds the deal and the tax data; and the outbound load ticket ships the load, deducts it from the contract and generates the invoice.

📍 Location in the system

Menu: Storage

🧩 What needs to be ready first

Storage is an end-of-line module: it uses records set up in other menus. Check these four before harvest starts:

• Product & Service — the grain, the lint, the cottonseed. It is what will be moved.
• Storage Location — the silo, the warehouse, the cotton gin. It is where the load goes in and where it comes out.
• Entity — buyers, third-party growers and carriers. To issue invoices, the municipality IBGE code must be filled in.
• Season Planting — without a planted field, there is nowhere for the harvest to come from.

⚙️ Setup in three steps

1. Register the scales

In Scale, add one line for each scale on the farm. For electronic scales, fill in IP and Port: that is what lets the capture buttons read the weight straight from the indicator, with no typing. With no scale registered, load tickets still work — the weights are just typed in.

2. Build the discount tables

In Standard Discount Table, create one table for each combination of type and product: "Moisture Soybean", "Impurity Soybean", "Moisture Corn". Each table is a list of ranges — measured grade and percentage deducted. The system always applies the highest range that is less than or equal to the value typed on the load ticket. If you already have the table in a spreadsheet, upload it all with Import from Excel.

3. Link the tables to the season

The tables only come into play when someone selects them. For harvest, this is done in the harvest parameters tab of the Season, by crop: which discounts exist, which table to use for each one and which will be typed in by hand. Without that parameter, the harvest load ticket will not save — it is the most common error when a season is getting started.

🌾 Harvest coming in

With the combine in the field, the day-to-day screen is the Inbound Load Ticket (Harvest/Purchase): you pick the field, weigh the truck full and empty, type in the grading and the system does the rest. Each saved load ticket:

• posts the final net weight into the storage location;
• adds to the total harvested for the field and the variety, building the season's yield;
• is deducted from the contract, when the load comes in under one.

Two safeguards help the operator: the load ticket number and the authorization number (the source ticket) cannot repeat within the same season, and the list shows in red the date of load tickets that still have only one weight.

🤝 The closed deal

Once the sale is agreed, it becomes a Sales/Purchase Contract: quantity, price, shipping window and which discounts the buyer accepts. If invoices will be issued, this is also where the tax data lives — it is worth spending time on it, because it saves you from retyping tax, series and carrier for every truck. An internal sale, with no invoice, skips this part.

The contract always shows how much has shipped and how much is left, but note: it does not move inventory. Signing a contract does not take anything out of the balance — the outbound load ticket does. That is why a contract can be closed even before the crop comes in.

🚛 Shipping

Each truck that hauls product out is an Outbound Load Ticket (Sale). Once the contract is selected, the product and the storage location come from it; you weigh the truck, and the final net weight is taken out of inventory and deducted from the remaining quantity. Then the Generate NF button builds the outbound invoice in awaiting transmission status, with everything that was on the contract.

One precaution that saves rework: a load ticket with a generated invoice can no longer be edited. To fix a weight, you have to deal with the invoice first — by deleting the movement, if it has not been transmitted yet, or by canceling the invoice, if it has.

🔁 What is not harvest

Fuel coming in, lime, transfers between warehouses, technical shrinkage: all of that goes on the Standalone Load Ticket, which has five types and does not depend on a field or a contract. Watch one detail: on inbound loads, the net weight is the 2nd weight minus the 1st — the order in which the truck went onto the scale, not whether it was loaded or empty.

📊 Where to check the numbers

• View inventory, a button on all three load ticket screens and on the contract: current balance by location and product, without leaving the screen.
• View Contracts, on the inbound and outbound load tickets: every contract in the season with quantity, shipped, remaining and totals at the bottom.
• List totals: kilos, bags and count for the filtered period — your end-of-day close without exporting anything.
• Reports ▼ on each screen, and Print on the form, which prints the load ticket template defined in the company settings.

❓ Frequently asked questions