Split billing in ag is a mess. Your ERP should handle it natively.

A grower walks into your branch and buys 40 tons of fertilizer. Except they're not just buying it. Their landlord is paying for 30% of the application on the north fields. The grower's prepay balance covers the seed but not the chem. And the distributor is running a rebate program that applies to part of the order but not all of it. One sale, three billing relationships, four line items, and your ERP treats it like a single invoice to a single customer.

Welcome to ag.

This is the part of the business that generic ERPs — the ones designed for manufacturing or wholesale distribution — simply cannot handle. In ag, the relationships between who orders, who receives, who pays, and who gets billed are rarely one-to-one. They're tangled by design, because that's how the economics of farming actually work.

The split isn't the exception. It's the default.

In most industries, a sale is between two parties. In ag, a single transaction can involve a grower, a landlord, a retailer, a distributor, and a financing partner — each with their own terms, their own pricing, and their own portion of the bill. Landlord-tenant splits. Retailer-distributor splits. Prepay drawdowns against partial orders. Rebate programs that apply at the product level, not the order level.

Your current system probably handles the simple case fine: one customer, one invoice, one payment. But the moment you need to split a sale across two billing entities — or apply a prepay balance to half the order and invoice the rest — you're in spreadsheet territory. Someone is manually calculating the split, creating separate invoices by hand, and hoping the numbers reconcile at month end.

If your ERP can't split a sale across three billing relationships without manual intervention, it wasn't built for ag. It was adapted for it. Badly.

What splits look like when the system actually understands them

In Horizen, split billing is a first-class concept — not a workaround, not a custom field, not a report you run after the fact. When you create a sale, you define the billing relationships upfront. The grower pays 70%. The landlord pays 30%. The grower's portion draws from their prepay balance up to $15K, and the remainder invoices on net-30 terms. The landlord gets a separate invoice with their own payment terms.

The system generates the right invoices to the right parties with the right amounts automatically. No manual splitting. No duplicate entry. No reconciliation headaches. When the distributor's rebate kicks in, it applies at the line-item level and adjusts the billing accordingly. When the prepay runs dry mid-order, the system flags it and switches to invoice terms for the remaining balance.

This isn't a feature we bolted on. It's how the data model works. Every sale in Horizen can have multiple billing relationships, multiple payment terms, and multiple funding sources — because that's how ag sales actually work.

The downstream cost of doing it wrong

When splits are manual, errors compound. The landlord gets billed for the wrong amount. The prepay balance is off by $800 and nobody catches it until the grower calls in January asking why their statement doesn't match. The distributor's rebate report doesn't tie out because the retailer applied it at the order level instead of the line level. AR aging is wrong because half the invoices were created manually and the dates don't match the original sale.

This isn't a minor accounting problem. It's a trust problem. When your grower's statement is wrong, they question everything. When your distributor's rebate report doesn't reconcile, it delays payments. When your landlord gets an invoice they don't recognize, they call your branch and tie up your team for an hour.

The people doing the manual splitting know this. They're careful. They double-check. They've built their own tracking spreadsheets. But the fact that your best people spend their time being careful about splits instead of selling product or managing relationships — that's the real cost.

Built for the relationships, not just the transaction

Ag is a relationship business that runs on complex economics. The landlord-tenant split has been around for a century. Prepay programs are standard. Distributor rebates are table stakes. None of this is new. What's new is expecting your software to handle it instead of your people.

Horizen was built from the ground up for these relationships — not adapted from a system that thinks every sale has one buyer and one invoice. If your operation deals with split billing, multi-party transactions, or any of the financial complexity that makes ag different from every other industry, your ERP should understand that natively.