Use Cases How MPE shows up in the field

Three customers, three problems

Agriculture · Food production · United States

Worker wallets for a commercial poultry processor with a Mexican and Central American workforce

Customer profile

US-based commercial poultry processor
11 processing and packing facilities across five states
≈3,400 hourly workers; ~78% of payroll-day remittance volume sent to Mexico, Guatemala, and Honduras
Existing payroll: ADP-style provider, weekly direct deposit

The challenge

Workers were losing 5–9% of every paycheck to remittance fees and FX spreads at storefront money-transfer outlets in the small towns near the facilities. Several locations had only one or two MSBs operating, and pricing reflected it. Families on the receiving end were often paying additional cash-out fees at local agents.

HR was hearing about the problem at every site visit. Retention in the highest-volume facilities was visibly worse than at sites where workers had family in the US. The producer had no appetite to change payroll, take custody of funds, or become a financial institution — they wanted a benefit that quietly improved take-home outcomes.

What MPE deployed

MPE Balance was deployed as the producer's white-labeled workforce wallet. Enrollment was designed for the workforce reality: any government-issued ID was accepted, including matrícula consular and foreign passports. No SSN was required to open or operate a wallet.

Workers can route some or all of their net pay into the MPE wallet, hold balances in USD, send money home with zero fees, and order optional family debit cards delivered to the destination address. Payroll integration sat alongside the existing direct-deposit flow — no payroll system replacement.

Outcome

~6 weeks

from kickoff to first wallet enrollments

5–9% → $0

remittance cost on in-wallet transfers

+12 pts

year-over-year retention at pilot facilities

changes to the existing payroll provider

Supply chain · Consumer goods · US ↔ South & Southeast Asia

Early-invoice financing for a consumer goods importer with suppliers across South and Southeast Asia

Customer profile

Mid-market consumer goods importer (apparel and home category)
Supplier base of ~140 manufacturers in Vietnam, Bangladesh, India, and Pakistan
Standard payment terms: net 90–120 days from invoice approval
Annual GMV through the supplier base: roughly $180M

Product: MPE OS

The challenge

Suppliers in Dhaka, Ho Chi Minh City, and Tiruppur were sitting on approved invoices for three to four months while trying to fund the next production run. The smaller suppliers in particular were turning down purchase orders because they could not finance materials and labor against receivables that wouldn't pay out until well past the next cycle.

The importer didn't want to pay early out of working capital — net-120 was the entire reason their margin model worked. Traditional bank-led supply chain financing programs wouldn't underwrite the smaller foreign suppliers, and local factoring rates in-country were prohibitive.

What MPE deployed

MPE was deployed as the financing and settlement layer between the importer and its supplier base. Once an invoice is approved in the importer's ERP, the supplier can elect to take early payment from MPE within 48 hours, in their local currency, at a transparent discount rate. The importer pays MPE on the original net-120 due date, in USD.

Settlement to suppliers routes through licensed local partners in each country. FX is locked at the moment the supplier elects early payment, so delivered amounts in VND, BDT, INR, and PKR are known up front. The importer's balance sheet stays clean — terms are unchanged from their accounting perspective.

Outcome

~$62M

annualized invoice volume financed in year one

48 hours

from invoice approval to supplier receiving funds

+28%

growth in active supplier base over 9 months

−41%

supplier churn vs. the prior 12-month baseline

Construction · Infrastructure · GCC, MENA, Southeast Asia

MPE Workforce for a multinational construction firm running projects across 17 countries

Customer profile

Multinational engineering and construction firm
Active project sites across the GCC, North Africa, the Levant, and Southeast Asia
≈14,000 total workforce; 1,800+ contractors and specialty consultants paid each month
Mix of full-time staff, sponsored expatriates, day labor, and project-specific specialty firms

Product: MPE Workforce

The challenge

Contractor payments across 17 countries were running through five different PSPs, three EOR providers, and a long tail of country-specific bank portals. Approvals lived in email threads. FX was guessed at the moment of payout. Withholding and statutory tax compliance varied by country and was tracked in a regional spreadsheet.

Contractors were regularly paid late, paid in the wrong currency, or paid through the wrong entity. Project managers had no real-time view of who had been paid for what milestone. Treasury had no consolidated view of monthly contractor liability across the portfolio.

What MPE deployed

MPE Workforce was deployed as the single operating layer for contingent workforce payments across the firm's footprint. Contractor onboarding, KYC, contract storage, and tax documentation flow through one workflow. Approval policies are policy-driven and entity-aware, with maker-checker thresholds and full audit trail per contractor.

FX is locked at the moment of approval, not at payout. Disbursement routes through licensed local partners by country and currency, with the same lifecycle states across markets. Project managers get a real-time view of contractor status by project and milestone. Treasury gets one consolidated liability view across the portfolio.

Outcome

1,800+

contractors paid per month across 17 countries

11 days → 36 hours

median approval-to-payout cycle

1 layer

replacing 5 PSPs and 3 EOR providers in the payment path

100%

of contractor payments under one audit trail

Different shape, same operating layer

Every engagement above runs on the same MPE control plane: governed approvals, locked FX, multi-currency settlement, and a single audit trail. The product wrapper changes by use case; the underlying infrastructure does not.

Request Access Platform architecture