Stataris

Industries

Companies whose operations cross the southern border.

The common thread is not the sector. It is that the accounting has to hold up in two countries at once, under two sets of rules, and still close on time.

Manufacturing and distribution

Plants in Mexico, customers in the U.S.

Whether the Mexican operation is an IMMEX plant, a contract manufacturer or a distribution centre, the accounting problem is the same: inventory and cost move across a border while the books have to stay reconcilable on both sides. We set up the costing, the intercompany flows and the consolidation so the transfer does not turn into a month-end argument.

  • Standard and actual costing across two entities
  • Intercompany transactions that eliminate cleanly
  • Landed cost, duties and freight carried into the valuation
  • IMMEX and customs data tied back to the ledger

Mining and resources

Long projects, heavy assets, exacting reporting.

Our group has spent years inside resource companies with operations in Mexico, which is where Sage 300's project and job costing earns its keep. Capital projects, equipment, site-level cost control, and reporting that satisfies a parent company in another country and another currency.

  • Project and job costing at site level
  • Fixed assets and depreciation across jurisdictions
  • Multi-currency reporting to the parent
  • Cost centres that match how the operation is actually run

Wholesale and cross-border trade

Goods moving both ways, margins that do not forgive errors.

Distributors carrying inventory on both sides of the border need order-to-cash and procure-to-pay that work in two currencies and two tax regimes without duplicate data entry. Usually the fix is less exotic than it sounds: one integration, one clean chart of accounts, and invoicing that satisfies the SAT without a separate process bolted alongside it.

  • Order entry and purchasing across entities
  • Multi-currency receivables and payables
  • CFDI invoicing for the Mexican side of the business
  • Inventory visibility that does not depend on a spreadsheet

Tell us what's broken.

Send your Sage 300 version, the modules you run, and where your operations are. You will get an answer from a consultant, not a sales sequence.