As part of our series on the road to revenue residency, we've been looking at the pressures that drive a company toward a formal presence in a new market. Some of the most persistent ones never reach the customer at all. They show up in the books.
This summer, we the first Netsuite integration purpose-built to help your ERP understand the specificities of usage-based billing. Now, we’re continuing our commitment to supporting lean finance teams by making that integration work for global teams.
Going global early puts a lot on a lean back office
Month-end is where going global early shows up first. Every new country adds transactions to book, report and reconcile, often in a new currency and under new tax rules, and the people closing the books are usually the same small group they were when every customer was domestic.
The rest of international growth doesn't wait for the close to catch up, either. New markets bring VAT or GST obligations, and in some of them buyers keep back part of each payment as tax, which someone then has to reclaim. For a lean team, each of these turns into more reconciliation at month-end.

NetSuite needs all the information, communicated correctly
Getting tax right on the invoice is half of the tax challenge. The other half happens in your ERP, where every invoice has to be booked to the right account, tied to the right tax agency and counted in the right country's tax report.
In NetSuite, those details hang off a nexus: a place, like a country or a US state, where your company has tax obligations. Each nexus has its own tax codes, and NetSuite checks each transaction against the nexus it belongs to. In other words, NetSuite needs to know where a sale belongs before it can book and report it properly, and every new country you sell into can add a nexus.
Small details in your tax data add up at close
When an international sale reaches the books without the right code, the sale is done but the accounting isn't, and someone sorts it out by hand at month-end. One is a quick fix. A close full of them, across many countries, is a real drag on a growing team. The little things in your tax data are what keep a lean global business running without friction, so a small team can keep making big swings.
Billing is where each transaction starts, so it's the natural place to record where that transaction belongs and hand the ERP what it needs.
How it works: one tax code per nexus, mapped once in Orb
In NetSuite, create a 0% tax code for each nexus where you're registered: one per country, or per US state if your NetSuite is set up at the state level. The code is 0% because your tax provider has already calculated the tax before it reaches Orb, so its only job is to tell NetSuite where the transaction belongs.
Then, in Orb's NetSuite integration settings, pick the matching code for each jurisdiction, plus a default code for anything outside them. Orb pre-fills the mapping by country, so you start from a draft. From there, every invoice and credit memo syncs with the code its nexus expects, and NetSuite books it to the right GL account and tax agency and includes it in country-level reporting, like VAT.

Tax amounts land in NetSuite's own tax fields, and neither Orb nor NetSuite does the tax math. Your tax provider calculates, Orb routes and NetSuite books. When you start selling in a new country, you add one more code and one more line in the mapping.
International tax for NetSuite is available in Orb's NetSuite integration. Read the NetSuite setup docs or reach out to your Orb team to get started.

