Vertically Integrated Produce Supply Chain:
Managing US and Mexican Business in One System
Most produce groups we meet run two entities: Mexico + United States. Reserva lets you apply one operating playbook across both while localizing MXN↔USD currency, Mexican IVA, SAT, and fiscal compliance. Outcomes: cleaner intercompany, a faster close, and clearer accountability. If/when you add Canada, the same model extends without new systems
Why Vertical Integration Is Common in the Fresh Produce Industry
Vertically integrated businesses are common in the fresh produce industry, where companies often operate across multiple stages of the supply chain—such as growing, packing, shipping, importing, and distributing. This structure helps maintain control over quality, timing, and costs in a market where products are highly perishable and speed matters.
It is also typical for produce companies to work across borders, for example growing crops in one country, packing them locally, and selling them through their own distribution networks in another. While vertical integration improves visibility and responsiveness to market demand, it also increases operational complexity by requiring coordination across multiple operations, entities, and financial processes.
Operational Challenges for Vertically Integrated Business
If you operate a Mexican packhouse/exporter and an US importing/distribution entity, you likely feel this every month:
- Broken traceability
- Duplicate item/partner masters and “translation” spreadsheets between MX and US
- Intercompany timing/markup mismatches that create manual eliminations
- FX handled out‑of‑band; invoices in USD, payables in MXN, inconsistent rate sources and revaluation cadence
- Taxes & trade: IVA tracked in spreadsheets; brokerage/duties and pedimento references don’t flow cleanly into US records
- Unclear approvals across borders (who signs off on export charges, label fees, or MX→US transfers?)
This isn’t just tooling—it’s an operating model gap. Different systems create different habits, and those habits show up as slow, stressful closes: Contpaq in Mexico, Quickbooks in the US. Excel everywhere.
Reserva allows corporate roll up reports to see your business globally.
Our Approach: One Playbook, Localized Where It Matters
We co‑write a single operating playbook both entities follow, then localize the rules that must differ.
Standard in both entities
- Chart of accounts and reporting structure (shared master, entity tags)
- Cost policies and allocation bases (freight, brokerage/customs, repack/labeling, finance fees)
- Intercompany pricing/markup and services (labels, special pack, brokerage recovery), with documented rationale (transfer‑pricing readiness)
- Roles, approvals, and segregation of duties (cross‑entity maker/checker)
Localized by country/entity
- Currency & FX: posting vs. settlement currency, daily/average/contract rate source, and revaluation cadence for unrealized gains/losses
- Taxes & trade: Mexican IVA handling on inputs/credits; US tax treatment where applicable; landed‑cost items (duties, brokerage); pedimento capture and reference through to financials
- Statutory needs: bilingual documents where required; country‑specific fields and archive rules
One login. Shared master data. Entity‑aware workflows. Consolidated reporting that respects US & MX rules—and is CA‑ready when you are.
What This Means for Your Day-to-Day Operations
Shorter Close
Fewer cross‑entity reconciliations; close moves from days to hours
Audit Readiness
Pedimento numbers, IVA treatment, and FX logic are documented and traceable
Less Context Switching
Teams stop hopping tools based on which side of the border they’re in
Clearer Accountability
Consistent approvals and limits across both entities
Cleaner Intercompany
Mirrored policies reduce mismatches and manual eliminations
A Cross‑Border Week
If you run a Mexican packhouse and a US importer/distributor, this is what happens:
- MX sells to US at a standard markup tied to a documented policy; US adds services (labels, special pack) and shares freight
- Duties, brokerage, and IVA hit at different stages in different currencies
- Incoterms and responsibility for customs/transport are clear and reflected in cost policies
BEFORE: each entity books charges its own way; FX revaluation happens out‑of‑band; pedimento numbers live in email; eliminations rely on bespoke spreadsheets. Month‑end becomes forensic accounting.
AFTER: intercompany pricing rules and cost policies apply the same way, every time. Local taxes and FX are handled by design. Pedimento references flow through; eliminations are predictable; approvals are identical across borders. The close becomes a review, not an investigation.
Signals You’re Ready to Consolidate
- You maintain separate item/partner lists for each entity
- Intercompany out‑of‑balance items show up every month
- Your close drifts into the second week
- Auditors or lenders ask for consistency you can’t prove quickly
Reserva ERP Implementation: Policies, Controls, and Cross-Entity Setup
- Entity Map: legal structure, goods/cost flows, and reporting needs across MX & US
- Policy Design: standardize allocation bases and intercompany pricing rules (freight, brokerage, repack, services). Define when exceptions are allowed and how they’re approved.
- Localization: configure currency handling and revaluation cadence; align IVA and US tax treatment; capture and retain pedimento references end‑to‑end.
- Controls: define roles, limits, and approval paths that travel across both entities (who can release intercompany, who approves FX rates, who signs off on duties/brokerage).
- Validation & Migration: dry‑run prior months to confirm outcomes match intent; migrate master data to a shared catalog with entity‑specific attributes.
- Change Management: train finance and ops on the playbook; publish a RACI; schedule a cross‑entity close calendar with hand‑offs.
Governance is the point. Policies have owners; changes are tracked; audits are calmer.
Key Metrics to Watch in the First Month
Ready to work as one team across the border?
Let’s review your structure and show how a single OS with localized rules can clean up intercompany and shorten your close
Schedule a Demo