Revenue recognition automation from Salesforce to NetSuite with human review
Build a revenue-recognition pipeline that turns Closed Won sales opportunities into accounting Sales Orders and Invoices in our ERP, applying our revenue-recognition rules (IFRS 15 treatment, selling-entity routing, class/location dimensions, and billing schedules) so a won deal flows through to the ERP without manual re-keying and leaves a full audit trail. Finance/RevOps is the user. Trigger it two ways: Automatic ingest: an inbound webhook (external-id auth) receives a small JSON payload identifying a won opportunity, acknowledges asynchronously (202), and kicks off ingestion. Human review page: a browser UI (space auth) where finance reviews, edits, consolidates, and approves staged deals before anything is written to the ERP. Structure it as an ingest phase and a human-gated processing phase: Ingest — pull the opportunity, account, and line items from the CRM (read-only), map them into a staging deal record, run advisory validation (never blocking), and stop. Deals wait in a queue. Review UI — a multi-view React app: a queue of pending deals (tick multiple opps for the same account to consolidate into one Sales Order), and a review view to edit any deal field or line item, re-validate on save, then approve. Back it with API steps that read staged deals and handle save/consolidate/approve. Processing (on approval) — find or create the ERP customer (plus sub-customer for partner/indirect deals), build and push the Sales Order with the correct revenue treatment and selling-entity/class/location dimensions, generate a billing schedule and push one invoice per period, then mark the deal processed and emit a JSON summary with the audit log. Keep all deal state in a persistent SQLite database on a named volume (staging deals, line items, billing schedule, consolidations, id mappings, sync log), with reference catalogs (product→item mappings, ERP item lists) loaded by a one-time seed utility. Encode the business rules — selling entity, revenue treatment (point-in-time vs ratable), partner selling fees, class, location, payment terms, currency — in shared modules reused across the processing steps. Validation is advisory only; all fixes happen in the Review UI, not in the source CRM. For the CRM use Salesforce — or whatever CRM holds your opportunities. For the accounting/ERP system use NetSuite — or your finance team's ERP. For any notifications, post to Slack — or your team's chat tool. Frame these as swappable choices, not requirements. Tools used: Salesforce (REST/SOQL), NetSuite (SuiteQL + REST records), SQLite, React
What this prompt builds
This workflow automates the revenue-recognition pipeline from Salesforce closed-won opportunities to NetSuite sales orders and invoices, applying IFRS 15 revenue rules, billing schedules, and partner margin calculations through a human-review interface. Finance and RevOps teams review and approve staged deals in a multi-view React UI instead of manually re-keying data, with all deal state, validation, and audit trails persisted in SQLite. The workflow eliminates manual entry errors, removes dependency on institutional knowledge, and allows revenue teams to scale deal volume without adding headcount dedicated to booking and invoicing.
The problem
Revenue operations and finance teams are stuck manually translating every closed-won Salesforce deal into a correctly booked NetSuite transaction — matching customers, determining subsidiaries, calculating partner margins, building sales orders, and generating linked invoices. None of these steps are individually complex, but each is a place where a number gets mistyped, a VAR deal gets booked against the wrong customer, or an invoice ends up disconnected from its sales order. This workload multiplies every close cycle across renewals, expansions, and partner deals, and it only stays reliable if the same experienced person does it every time — that's fragile, and it's exactly the kind of judgment-heavy, repetitive process that shouldn't require a dedicated hire as deal volume grows. This workflow was built to take that institutional knowledge out of one person's head and put it into a repeatable wizard, so revenue teams can review and approve deals instead of manually assembling them.
Solution and impact
The workflow delivers a six-step Tines 3B wizard that takes a Salesforce closed-won opportunity all the way to a fully invoiced NetSuite transaction with zero manual data entry — pulling the deal queue, linking the correct customer hierarchy, building the sales order with proper billing and partner margins, generating linked invoices, and logging a full audit trail, with built-in validation to catch discrepancies before they hit NetSuite. What used to take a person manually reading each opportunity, searching NetSuite, and building records by hand now happens in minutes through a guided review, cutting processing time per deal and eliminating errors like mismatched customers or disconnected invoices. Revenue operations shifts from manual entry to review-and-approve, the process no longer depends on one person's institutional knowledge, and the same team can absorb significantly more deal volume without adding headcount purely to manage booking and invoicing.