How to integrate your ERP with farm operations management

When a farm decides to use an ERP and an operations management platform at the same time, the first question is always the same: so what goes where?

It’s a good question, and the wrong answer is expensive. Two systems without a clear boundary become two places where the same information is typed in, with numbers that don’t match at month-end and nobody knows which one is right.

The split that works

The rule is simple: the ERP takes care of the company; operations management takes care of the crop.

The ERP holds the legal entity’s obligations — accounting, tax calculation, statutory filings, payroll, and relationships with banks and suppliers at the corporate level.

Operations management holds everything that happens in the field — work orders, scouting, activity logging, inventory movements on the ground, fleet and maintenance control, cost per area.

That’s the useful boundary: what the operation consumes and executes starts in the field; what the company reports and calculates starts in the ERP.

What flows from one side to the other

The main flow is consumption.

When a work order is executed, it moves real inventory: this much crop protection product went out, applied in this field, by this team, on this date. That actual consumption is the information the ERP needs so its costs reflect the operation — not an estimate entered by someone who wasn’t there.

Without integration, that number is typed twice. With integration, it’s created once, in the field, and reaches the ERP already validated.

What shouldn’t be integrated

Not everything needs to flow, and that’s the part people tend to forget.

Pest scouting, field photos, operation checklists and field history have no reason to go into the ERP. That’s information the operation uses to decide, not information the company uses to report. Sending it there only clutters the database and creates maintenance with no benefit.

Good integration isn’t complete integration. It’s integration at the right point.

How it works in practice

upCampo has its own API and already runs integrated with Sankhya, Aliare (Siagri) and ViaSoft, as well as John Deere Operations Center and other systems.

The integration design is defined together with the customer, because the cut-off point changes with the structure. A group with trading and industrial operations uses the ERP far more broadly than a farm that only runs production — and the boundary needs to reflect that.

It’s also worth noting a situation that comes up often: not every farm needs both. upCampo has tax, finance, purchasing and inventory, and many operations run entirely on it, with accounting handled by an outside accounting firm. The ERP comes in when the corporate structure grows — several companies, activities beyond production, more complex tax requirements.

What changes in the daily routine

With integration in place, three things change noticeably.

Double entry ends: what was logged in the field isn’t re-entered in the office. Less work and, above all, fewer discrepancies.

Costs reflect reality: the consumption that reaches the ERP is what actually left the inventory, not what someone estimated.

And the conversation between the field and the office is about the same number — which, in the end, is the whole point of the exercise.

Before you decide on the design

Three questions worth answering before integrating anything:

• What does the controller’s office need to receive from the field, and how often?
• Which master data should have a single source, and where does it live?
• What is typed in twice in your operation today?

The third one is usually the most revealing. If the answer is long, the gain from integration is already mapped out.

If you want to understand where the ERP stops and the operation begins, the previous article covers it: what the ERP can’t see on the farm.