20+ years of combined team expertise in Salesforce & NetSuite. Talk to an Expert →
← GuidesNetSuite · Ontario

NetSuite for Ontario Businesses: Built for Scale and Cross-Border Trade

Ontario is Canada's largest economy, with companies that range from startups in Waterloo to manufacturers in the Golden Horseshoe, financial firms in Toronto, and agricultural producers elsewhere. Many sell into the United States, many are growing through acquisition, and nearly all must manage the harmonized sales tax and the province's employer obligations. This guide describes the planning points that matter in an Ontario NetSuite implementation. It is general information; confirm your obligations with your advisors.

Talk to an Expert →

HST: one combined tax, many scenarios

Ontario participates in the harmonized sales tax, which combines the federal and provincial components into one tax administered by the Canada Revenue Agency. That simplicity at the invoice hides complexity underneath: different rules apply to exports, zero-rated and exempt supplies, sales to other provinces, and purchases for resale. Configure tax codes so each scenario produces the correct tax and the right reporting category.

Test unusual cases early: sales shipped to customers in other provinces, services delivered to the United States, and imports. Most tax errors come from the exceptions, not the standard transaction.

  • Separate tax codes for taxable, zero-rated, exempt, and out-of-scope transactions.
  • Track input tax credits on purchases and capital assets.
  • Reconcile tax accounts to returns every filing period.

Employer obligations: health tax and workplace insurance

Ontario employers may owe the employer health tax above an exemption threshold and must manage premiums to the provincial workplace safety and insurance board. These costs affect job costing, margin, and budgets. Even though payroll is typically run outside the ERP, the cost accounts and allocations belong in the ledger, and project-based businesses should apply them to jobs so margin reports are realistic.

NetSuite integration services →

Selling into the United States

Proximity to the U.S. market makes cross-border trade routine for many Ontario firms. Multi-currency pricing, invoicing in U.S. dollars, revaluation, and hedging considerations all land on the finance team. Sales tax obligations in U.S. states can arise when economic thresholds are met, and customs paperwork accompanies physical goods. Decide early which currency each customer is billed in and how exchange differences are reported.

Growth by acquisition and multi-entity structures

Ontario has an active acquisition market, and a company that buys several smaller businesses inherits several charts of accounts and systems. A multi-entity design with a consistent chart, shared customers and vendors where appropriate, and intercompany eliminations makes it practical to consolidate and to onboard the next acquisition with a repeatable process. Document the onboarding steps so each integration is faster than the last.

Our NetSuite ERP practice →

Sectors you will see in the province

Manufacturing and automotive supply chains, financial and professional services, technology, agri-food, and public-sector suppliers are all common in Ontario. Each has specific needs: inventory and costing for manufacturers, project billing for professional firms, subscription revenue for technology companies, and traceability for food. Choose partners and configurations that match your sector, not a generic template.

See our industry experience →

Decisions to settle before configuration starts

  • Entity structure. Decide which legal entities will exist in NetSuite and which will be added later, and how intercompany transactions will flow.
  • Currency policy. Define the functional currency of each entity and when customers are billed in U.S. dollars.
  • Tax preparer. Agree who prepares returns and what reports they need from the system.
  • Payroll interface. Choose the provider and define cost allocations that reach jobs and departments.

A realistic first 90 days

  • Days 1 to 30. Confirm entities, tax registrations, and currencies, and design the chart of accounts and segments.
  • Days 31 to 60. Configure tax, banking, and the first integrations, and load master data with reconciliation to the legacy system.
  • Days 61 to 90. Run parallel closes, reconcile tax, and finalize training and cutover plans.
Implementation and integration services →

Pitfalls in Ontario projects

  • Assuming one tax code covers everything. Exports, inter-provincial sales, and exempt items need their own treatment.
  • Delaying acquisition planning. If the first deal closes before the structure is ready, the team improvises. Plan for it.
  • Forgetting indirect labor costs. Payroll-related taxes and insurance left out of job costing overstate margin.
  • Skipping foreign-exchange reporting. Currency movements can change a quarter's results. Build the reports before the first big swing.

Talk to a NetSuite Expert About Ontario Operations

Share where you are today and a Cold Sun consultant will recommend a practical next step.

Talk to a NetSuite Expert →
Erik Wiltjer
FAQ

Frequently Asked Questions

Keep Reading

Related Guides

NetSuite for Alberta Businesses: Energy and Growth
What Alberta companies should plan for in a NetSuite project: GST-only sales tax, energy-sector accounting, WCB, joint ventures and project-based finance.
Read Guide →
NetSuite for British Columbia Businesses: PST and Tech
What British Columbia companies should plan for in a NetSuite project: separate PST and GST, technology and resource sectors, WorkSafeBC, and Pacific trade.
Read Guide →
NetSuite for Saskatchewan and Manitoba Businesses
What Prairie companies should plan for in a NetSuite project: provincial sales taxes, agriculture and resource accounting, co-ops and seasonal operations.
Read Guide →