Where Should Billing Live? Your CFO Already Knows

This article is for SaaS leaders running Salesforce and NetSuite — especially CFOs, Controllers, RevOps leads, and technical owners — who are trying to decide where billing should live, or dealing with the consequences of a decision that was made without Finance in the room.

• The billing debate isn't a technology debate. It's an organizational one — and Finance should own the decision
• Finance is accountable for revenue accuracy, audit compliance, and the close. That's why they should decide where billing lives
• When billing ends up in the wrong place, the result is manual workarounds, reconciliation cycles, and a longer, riskier close
• The real problem often isn't where billing belongs — it's whether the system can support how the business actually invoices
• Continuous makes both systems work the way they should, so the architecture supports the decision Finance already made

There's a debate that comes up in almost every SaaS company running Salesforce and NetSuite: where should billing live?

Some teams want it in Salesforce. Others insist it belongs in NetSuite. IT has an opinion. RevOps has an opinion. And everyone talks past each other for months while the problem doesn't get solved.

Here's the thing. There's a very simple way to answer this question. Ask Finance.

Who Should Decide Where Billing Lives?

Ask your controller. Ask your CFO. Ask your head of Revenue Assurance.

If they say billing belongs in NetSuite, put it there. If they say billing is part of the CRM, put it there. If they say they just need summary visibility in Salesforce and want the detail in NetSuite, build for that. Finance owns the financial system of record. They know what they need to close the books, satisfy auditors, and report revenue accurately.

Finance is accountable for revenue accuracy, audit compliance, and the close. That's why they should own the decision.

The billing debate isn't really a technology debate. It's an organizational one. And the organization that owns the final answer is Finance — it's what we call the Ownership Gap, when the team responsible for the outcome isn't the one making the decision.

Why Does the Debate Happen in the First Place?

Because the wrong people are usually in the room when the decision gets made.

Sales wants visibility into billing status so they can manage renewals and expansions. IT wants to minimize integration complexity. RevOps wants everything in Salesforce so reporting is easier. Each of these is a legitimate concern. None of them are the deciding factor.

Finance should make the decision about whether they need Orders, Invoices, Payments and Credits in Salesforce or if they want have just Orders and Invoices or any combination therein. Regardless, finance teams need these sales transactions for revenue recognition and they should decide what billing functions belong in CRM or ERP.

What Happens When Billing Ends Up in the Wrong Place?

When billing logic gets forced into a system that wasn't designed for it, complexity accumulates. Workarounds get built. Reconciliation work increases. And at month-end close, Finance ends up cleaning up decisions they had no part in making.

The result is manual adjustments, repeated reconciliation cycles, and a longer, riskier close.

For Finance Ops teams, this often means becoming the connective tissue between systems that should be talking to each other automatically. Someone is exporting from Salesforce, transforming in a spreadsheet, and importing into NetSuite. Someone else is reconciling the AR aging report against what the CRM shows. That's not a finance function. That's a systems problem wearing a finance hat.

What If the System Can't Handle the Complexity?

This is where most teams get stuck.

Finance might know exactly where billing should live, but the system might not be able to support how the business actually invoices.

What if Finance wants billing in NetSuite, but the invoicing complexity — multi-location splits, early billing, usage components, amendment credits — is too much for a standard NetSuite setup to handle cleanly? What if billing needs to run through Salesforce but has to sync perfectly with NetSuite for revenue recognition?

That's not a debate about where billing belongs. That's an architecture problem. The system needs to be built to support what Finance has already decided.

How Does Continuous Approach This?

At Continuous, we don't take a side in the billing debate. We make both systems work the way they should.

When billing is performed in Salesforce, Continuous makes sure those sales transactions are synced to NetSuite so you can run revenue recognition in NetSuite or NetSuite Advanced Revenue Management.

If Finance wants billing in NetSuite, Continuous ensures NetSuite can handle any invoicing scenario — dynamic splits, early billing, usage components, amendment credits — without manual workarounds. If billing needs visibility in Salesforce, Continuous keeps it in sync with NetSuite so Finance always has the right numbers.

The debate ends when the architecture supports the decision Finance already made. That's what we build.

Stop debating. Ask your CFO. Then build the system that makes their answer work.