Subscription Billing & Revenue Recognition Suite

The problem you are actually facing

NetSuite handles a clean, flat, annual subscription well. The trouble starts the moment your commercial model stops being clean. A customer wants to upgrade from 50 seats to 90 seats on the 14th of the month and expects a prorated invoice on the next cycle, not a credit memo and a re-issued contract. A usage-based plan needs to rate 4.2 million API calls against a tiered price book with a committed minimum and an overage rate. A bundle sells a platform subscription, a one-off implementation service and a hardware unit on one line group, and your auditors want each element allocated at its own standalone selling price with its own revenue timing.

What happens instead is that someone rebuilds the arrangement in a spreadsheet, calculates the allocation by hand, and journals the result into NetSuite at period close. The revenue arrangement in NetSuite becomes a record of what finance decided offline rather than a system of record. Every amendment widens the gap, every audit request means reconstructing the working, and closing the books gets slower as the subscription base grows.

What ECOSIRE builds

This is not an existing app you download. We build it as a NetSuite customization inside your own account, scoped to your commercial model, and you own the resulting SDF project.

Contract and plan model

We create custom records for subscription contracts, contract lines, rate plans and rate plan tiers, related to the standard Customer, Subscription, Item and Contract records so that everything stays navigable from the customer record. Rate plan tiers support flat fee, per-unit, tiered, volume and committed-minimum-plus-overage shapes. Item types are respected: a service item behaves differently from an inventory item or a non-inventory item for sale, and the build reflects the item types actually in your account rather than a generic assumption.

Usage rating engine

Usage events land in a custom usage record either through a SuiteScript 2.1 RESTlet that your product calls directly, or through a scheduled pull from a staging table or SFTP drop. A Map/Reduce script rates the accumulated usage for each billing period: the map stage groups raw events by contract line and rating dimension, the reduce stage applies the tier structure and writes a rated usage summary. Map/Reduce is used specifically because it yields between stages, so a month of high-volume usage does not hit governance limits the way a single scheduled script would.

Mid-term amendments and proration

Amendments are first-class records rather than edits that destroy history. An upgrade, downgrade, quantity change, plan swap, term extension, pause or cancellation is captured as an amendment record with an effective date. A User Event script on approval writes the resulting delta lines, calculates proration on your chosen convention (actual days, 30/360, or full-period), and adjusts the downstream billing schedule. The prior state remains readable, which is what makes an audit trail worth having.

Billing generation

A scheduled script builds the billing run: it selects due contract lines through saved searches, pulls in rated usage, applies proration deltas, and creates Invoices or Sales Orders depending on the flow you use. Runs are grouped by billing cycle and subsidiary so that a OneWorld account can bill each subsidiary on its own calendar and its own base currency. A pre-run preview record lets a controller inspect and approve the run before invoices are created.

ASC 606 revenue recognition

Performance obligations are identified per contract line and carry a standalone selling price, either from a configured SSP list, a saved-search-derived observable price, or an estimation method you specify. Allocation runs across the arrangement, writing allocated transaction price back to each obligation. Revenue schedules are generated per obligation with the recognition method that fits it: ratable over term, point in time on delivery, percentage of completion against milestones, or usage-as-consumed. A Map/Reduce recognition script produces the period journal entries against your revenue and contract-asset or contract-liability accounts, tagged with a custom segment for revenue stream so reporting slices cleanly.

Reporting and controls

We deliver saved searches and dataset-backed reports for deferred revenue rollforward, revenue waterfall by period, MRR and ARR movement (new, expansion, contraction, churn), unbilled usage, and an allocation audit trail showing SSP inputs and the resulting allocated amounts. SuiteFlow workflows route amendment and billing-run approvals to the right roles. Permissions are set so a billing clerk can prepare a run but only a controller can approve recognition journals.

Who this is for

Software and SaaS companies on NetSuite whose pricing has outgrown flat annual plans. Managed service providers billing a committed minimum plus consumption. Equipment businesses selling hardware with an attached subscription and installation service. Any NetSuite finance team currently allocating revenue in a spreadsheet and journaling the answer in.

It is a poor fit if your subscriptions are genuinely flat, annual and never amended — native functionality already covers that, and we will say so on the scoping call rather than sell you a build you do not need.

How delivery works

1. Scoping call. We walk your actual contracts, rate cards and current close process, and look at your account: edition, whether OneWorld is in play, which item types you use, what already exists in your revenue arrangements.

2. Fixed quote and specification. You receive a written specification listing every custom record, script, workflow, saved search and role change, plus the fixed price and timeline. Nothing gets built before you approve that document.

3. Build. Development happens as an SDF project under source control, against your requirements rather than a generic template.

4. Install in sandbox. We deploy to your sandbox or a Release Preview account first, load representative contracts and usage volumes, and run a parallel billing and recognition cycle against your existing numbers so you can see the two agree before anything touches production.

5. Install in production. After your sign-off we deploy to production during a window you choose, migrate open contracts, and stay on hand through the first live billing run and the first period close.

6. Support window. A defect-fix support window follows go-live, with the code and SDF project handed to you so your own team or any other partner can extend it.