SAP ERP in the Agricultural Sector: Practical Insights and Industry-Specific Considerations

Experienced SAP consultants often smile when they hear users say, “Our processes are unique,” or “We need a special approach.” Truly unique processes that cannot be aligned with standard models are far less common than business users assume. What is essential, however, is the consultant’s ability to distinguish the specific characteristics of an individual company from the structural characteristics of the industry in which it operates.

At an industry level, sector-specific features are real and significant. The operational model of a manufacturing company differs fundamentally from that of a retailer or logistics provider. Agriculture is no exception. In fact, it contains several sub-sectors – crop production, seed processing, grain storage, trading, and agricultural input distribution – each with its own operational profile and critical business processes that must be correctly reflected in SAP.

Drawing on our experience of SAP ERP implementations for seed producers, elevator operators, grain traders, agro-distributors, and seed-treatment facilities, this article highlights the key observations that help agricultural companies avoid implementation pitfalls and achieve a transparent, controlled, and scalable SAP landscape.

Costing for Seed Production: Managing a Long, Multi-Stage Cycle

Seed production is characterized by a long, multi-stage operational cycle. It begins with several months of field activity, followed by post-harvest processing steps – drying, cleaning, calibration, chemical treatment, and packaging. As a result, a production cycle may start in spring and conclude in winter, effectively spanning an entire fiscal year.

Accurate production costing is essential – not only for pricing decisions but also to comply with Ukrainian accounting and tax requirements. The long cycle poses a specific challenge: the valuation of work-in-progress (WIP). For most of the season, no finished product exists physically, yet costs accrue continuously – seed, fertiliser, fuel, equipment usage, labour, and overheads. These costs must be properly reflected as WIP for statutory and management reporting.

In SAP ERP, costing is managed through Material Ledger module with Actual Costing functionality activated, which provides:

tracking of variances between planned and actual procurement prices
allocation of variances from production activities (e.g., labour, machine rates, amortisation)
redistribution of the above differences across production stages during period-end closing
accurate valuation of semi-finished and finished goods at each stage of processing

The challenge in seed production is that traditional Material Ledger calculations operate strictly within monthly periods. A production cycle lasting six months or longer, with dozens of activities, cannot be accurately represented by periodic month-end runs alone. Seasonality adds another layer of complexity: processing stages such as harvesting, drying, and conditioning generate sharp cost spikes, while other months remain nearly idle. This creates uneven cost accumulation, which must be allocated correctly across the entire cycle.

If the configuration is not designed for long-cycle production, the final cost may significantly distort the business picture.

For these scenarios, SAP offers a dedicated functionality – Alternative Valuation Run (AVR). AVR consolidates multiple monthly Material Ledger runs into a unified valuation for the entire production cycle, allowing a single, continuous costing view.

Expertise with Material Ledger AVR is rare – even in large SAP programmes. Errors often become visible only at the end of the full production cycle, sometimes a year after go-live, when recalculation is difficult or impossible. Only consultants who have supported AVR through several full cycles truly understand its nuances and potential risks.

Shifted Fiscal Year: Aligning Agricultural Cycles with Corporate Requirements

A shifted fiscal year is standard practice in agriculture and stems directly from seasonality. Operational and financial cycles follow the production season – not the calendar year.

For seed growers, the operational year begins with spring planting and concludes with the delivery of processed seed the following spring. For elevator businesses, the cycle starts with autumn intake and continues through storage and gradual sales in winter and spring. Consequently, a July–June fiscal year is both logical and widespread across agricultural enterprises.

However, multinational groups often face a structural conflict:

The corporate reporting model requires a shifted fiscal year.
Ukrainian legislation requires statutory reporting based on a calendar year.

SAP ERP resolves this through parallel ledgers, enabling the use of a July–June fiscal year for corporate purposes while maintaining a calendar-year ledger for statutory compliance. This ensures accurate consolidation for the group and fully compliant local reporting in Ukraine.

Nevertheless, multiple fiscal-year variants introduce complexity into period closing, fixed-asset accounting, cost calculations, and other finance processes. For this reason, agricultural companies with a shifted fiscal year should engage consultants who have hands-on experience configuring and supporting parallel ledger scenarios in Ukraine. Proper design from the start eliminates manual adjustments, duplicate processes, and year-end reconciliation risks.

Tolling and Contract Processing of Agricultural Products

Tolling (contract processing) is a central topic in seed production and grain processing. Some companies possess surplus processing capacity. Others specialise only in cultivation, and for small growers, investing in their own infrastructure is not economically viable. Tolling therefore, emerges in two distinct models:

We send our raw materials to an external processor
We receive customer-owned materials for processing on our facilities

Sending own raw material for processing

This scenario is fully supported by standard SAP ERP functionality in MM Subcontracting.

A subcontracting purchase order is created, the raw material is issued to the processor, and it remains on our balance sheet as special stock. After processing, the raw material is consumed, finished goods are received, and the subcontractor’s service cost is posted automatically. The flow is transparent and largely automated.

Receiving customer-owned materials for processing

This scenario is significantly more complex because the company is not producing its own goods – it is providing a processing service. It requires coordinated configuration across SD, MM, PP, and CO.

The typical process includes:

Sales order (SD) as the controlling object – it defines pricing, terms, and acts as the anchor for all subsequent steps.
Receipt of customer-owned material, tracked quantitatively at zero value and posted as special stock linked to the sales order.
Production order(s) (PP) for processing steps, also linked to the sales order.
Consumption of customer material, and, when applicable, consumption of our own components, which must be incorporated into the service cost.
Labour and machine-rate postings, similar to standard production.
Accumulation of all actual costs on the sales order, forming the final cost of the service at the moment of goods issue/ delivery.

Equally important is the exchange of information with the customer – input/output ratios, material balances, and lot-level traceability. Most agricultural companies require structured reporting on customer-owned material usage and yields, often accompanied by customised print forms such as intake certificates, processing acts, or reconciliation statements.

Given the number of modules involved and the multi-step nature of the process, gaps in configuration often lead to incorrect costing, double consumption, or erroneous accounting entries. Experienced consultants know where misalignments typically occur and how to design a robust, audit-proof process.

Conclusion

Agriculture has its own operational and regulatory specificities, and SAP ERP can reflect them precisely – provided the solution is designed with industry context in mind. Long production cycles, the use of Material Ledger AVR, shifted fiscal years, and tolling processes illustrate how critical it is to consider both sector-specific requirements and Ukrainian localisation rules.

Our team has supported SAP implementations across the full agricultural value chain – from seed producers to elevators and processing facilities – and we understand which solutions work in real operational environments and which risks must be addressed at the outset.

It is equally important that key users on the client side are actively engaged from day one. Their operational knowledge is essential for defining accurate requirements and validating process design.

In the next part of this series, we will examine equally important topics for SAP ERP in the Ukrainian agricultural sector: grain-handling processes at elevators (from both regulatory and logistics perspectives) and VAT specifics for agricultural enterprises, including common errors and how to avoid them.