NetSuite Process & Workflow FAQs
How NetSuite actually runs your core finance and operations processes – and what makes each one fast or slow in practice.
Find your query
Jump straight to your question.
How does month-end close work in NetSuite?
NetSuite helps finance teams close their books faster by providing a clear, step-by-step checklist that guides you through the entire month-end process, covering subledger locks, currency revaluation, intercompany eliminations and the final period lock.
What does NetSuite give you for the close?
You can lock individual modules like AR or AP as soon as their work is wrapped up, automatically run currency revaluations, and handle OneWorld intercompany eliminations right from the checklist before applying a hard lock that keeps past periods secure. Because the platform supports daily transaction matching, your team can run bank reconciliations continuously throughout the month instead of facing a massive backlog on day thirty.
That said, the software only provides the framework; the real secret to a fast close comes down to operational habits. The fastest finance teams attach backup files directly to scheduled journals, work the checklist in strict order, and strictly limit who has permission to reopen closed periods. The direction of travel backs this up: Gartner predicts embedded AI in cloud ERP will drive a 30% faster financial close by 2028, while noting most CFOs are still held back by data quality and integration complexity.
The moving parts
- Period checklistA native task sequence per period: lock, revalue, eliminate, close, with status visible throughout.
- Module-level lockingSubledgers close independently, so AR can be finished while journals continue.
- Consolidated closeOneWorld runs elimination and translation inside the same checklist.
- Reopen governancePeriod locks with controlled reopen – the ‘final means final’ machinery.
How does NetSuite handle intercompany transactions?
NetSuite OneWorld handles intercompany accounting natively by linking paired sales and purchase transactions across subsidiaries, balancing intercompany journals automatically, and netting down balances for settlement. When activities like cross-charges, management fees or inventory transfers are properly tagged with intercompany flags, the platform automatically generates the required elimination entries during month-end consolidation.
The underlying automation works well, but it relies on consistent setup and execution. The moment a team books transactions outside these established paired structures, the system can no longer automate the balance, turning your month-end close into a tedious manual reconciliation grind. This is why intercompany accounting quality is really determined during initial design. Setting up how entities charge each other and where netting applies during implementation costs a tiny fraction of what it takes to untangle broken flows later on.
What native handling covers
- Paired transactionsIntercompany sale and purchase pairs are created together, so both ledgers move in step.
- Auto-balancing journalsCross-subsidiary journals with due-to/due-from lines generated automatically.
- Netting & settlementBalances offset into settlement runs: a hundred invoices become a few payments.
- Elimination at consolidationTagged intercompany activity is eliminated systematically, retiring the month-end workbook step.
How does NetSuite handle multi-currency?
NetSuite manages multi-currency comprehensively across global operations. Each subsidiary maintains its own base currency, but you can issue transactions in any currency to customers and suppliers anywhere in the world. The platform automatically calculates real-time gain or loss whenever transactions are settled, and handles period-end revaluations on open balances at month-end. When it comes time to consolidate, NetSuite automatically translates every subsidiary’s financials into your parent group’s primary reporting currency using current, average or historic exchange rates as needed.
How do the three currency layers work?
Multi-currency in NetSuite operates on three distinct levels. First is the transaction currency, which is whatever currency you choose to bill a customer or pay a vendor in. Second is the base currency – the primary ledger currency used by that specific subsidiary to keep its books. Finally, there is the reporting currency, which converts every subsidiary’s numbers into one unified currency for parent group consolidation. NetSuite handles the maths at every stage, automatically calculating exchange rate gains or losses when invoices are settled, adjusting open balances at month-end, and translating local financials for corporate reporting without manual spreadsheet work.
Where does multi-currency accounting go wrong?
Multi-currency accounting usually goes wrong because of small setup errors that snowball over time. The most common traps are picking the wrong rate type on a transaction, pointing automatic month-end revaluations at the wrong GL accounts, or relying on manual, unverified rate sources where nobody can track where a specific exchange rate came from. While each of these mistakes can be unravelled and corrected later, it is vastly cheaper to configure your rate tables, account rules and automated feeds properly during implementation.
The working model
- Three currency layersTransaction, base and reporting, each with its own deliberate rate logic.
- Automatic gain/lossSettlement differences calculated and posted at payment – realised FX handled natively.
- Period-end revaluationOpen balances are revalued on schedule – see the run-service for the rhythm.
- Governed ratesOne source, on schedule, logged: the provenance discipline that ends rate arguments.
Want a process to run better in NetSuite?
Talk it through with a solution architect. It’s free, it takes 30 minutes and there’s no sales pitch.
How does revenue recognition work in NetSuite?
NetSuite approaches revenue recognition in two different ways depending on your business model. Standard NetSuite takes a simple approach, recognising revenue right when an order ships or an invoice is generated, which works great for straightforward, point-of-sale style sales. If you have subscription models, multi-element bundles or milestones, you bring in Advanced Revenue Management (ARM). ARM handles complex ASC 606 / IFRS 15 rules by breaking contracts into performance obligations, allocating standalone selling prices, and running deferred revenue schedules automatically behind the scenes.
What does ARM actually automate?
ARM takes the manual labour out of complex revenue accounting by converting customer orders into automated revenue arrangements behind the scenes. It splits contracts into individual performance obligations, applies your standalone selling price (SSP) allocation rules, and posts the resulting deferred and recognised revenue journals on schedule. If a customer alters their contract halfway through, ARM automatically re-allocates the remaining revenue across the updated deliverables without requiring manual recalculations in spreadsheets.
The critical thing to remember is that ARM is an execution engine, not a substitute for policy. Your finance team and auditors still have to establish what counts as a performance obligation, set fair-value SSP baselines and define recognition triggers. ARM simply enforces those decisions at volume.
The recognition stack
- Standard recognitionRevenue at billing is sufficient for despatch-driven models, with none of ARM’s cost and complexity.
- ARM arrangementsObligations, allocations and schedules automated – the IFRS 15 engine.
- Modification handlingUpgrades and amendments are re-allocated properly – the scenario spreadsheets handle worst.
- Policy before configurationSettled accounting positions make ARM builds fast; discovering them mid-build makes them expensive.
How does NetSuite handle approval workflows?
NetSuite gives you two main ways to handle document approvals without writing custom code. The core tool is SuiteFlow, a visual workflow builder that lets you set up approval rules on almost any record – routing requests based on amount thresholds, employee roles or custom multi-step chains. If you want a ready-made solution specifically for financial documents, NetSuite also offers SuiteApprovals, which uses pre-configured approval matrices. Either way, you get automatic out-of-office delegation, escalation rules for stuck approvals, and a complete audit log of every decision.
What approval patterns are covered?
NetSuite handles all the standard approval setups your finance and operations teams need. You can route documents based on value thresholds, send requests to specific department managers or subsidiary leads, and run approvals sequentially or in parallel. Approvers can respond directly from email or their phone, and if someone is on holiday, out-of-office delegation ensures requests do not stall. It works right out of the box for journals, POs, bills and expense reports, leaving the clear audit history that auditors expect.
Approval flows fail socially before technically
Approval flows almost always break down socially before they fail technically. The most common traps are creating complex approval matrices that mirror your org chart rather than actual financial risk, setting value thresholds once and forgetting them, or letting approval queues sit unattended until employees start finding clever workarounds to get things done. Building the workflow rules in NetSuite is only half the battle – keeping approvals fast, clean and compliant takes ongoing operational discipline and regular queue hygiene.
What the platform provides
- Threshold routingAmount bands, roles and org dimensions driving who approves what.
- Delegation & escalationAbsence cover and time-based escalation mean the holiday-proofing is native.
- Actionable notificationsApprove from email or mobile, with friction low enough that the control survives.
- Complete audit trailsEvery decision is logged with actor and timestamp, so the evidence is automatic.
How does NetSuite handle fixed assets?
NetSuite handles fixed assets using a dedicated module called Fixed Assets Management (FAM). Instead of typing equipment purchases into a separate spreadsheet, NetSuite flags purchase bills as potential new assets automatically. From there, the system runs depreciation schedules on your chosen timelines, adjusts for transfers or revaluations, and posts final sales or disposals directly to your accounting ledger. Because every step generates its own general ledger entries behind the scenes, your asset list and financial statements stay in sync.
The lifecycle is covered end to end
NetSuite covers every stage of an asset’s life without requiring outside spreadsheets. It starts in Accounts Payable, where purchase bills automatically trigger proposed asset records so you don’t have to enter the same information twice. You can assign different depreciation rules or useful lives based on your company’s accounting policies, make adjustments for location transfers or impairments mid-way through, and let NetSuite handle the gain-or-loss maths when you sell or throw something away. As a bonus, the module also comes with built-in IFRS 16 features to manage right-of-use lease accounting directly.
Where does fixed asset management slip?
The biggest breakdown in NetSuite fixed asset management isn’t a lack of software capability, it’s a lack of routine discipline. Teams regularly forget to review and approve proposed asset additions from vendor bills, skip scheduled monthly depreciation runs, and only record scrapped or sold assets right when auditors arrive. Setting up the system properly handles the heavy lifting, but keeping your asset register accurate relies on establishing a steady month-end process.
What FAM covers
- AP-to-asset proposalCapital purchases become asset records without rekeying, so the capture discipline is built in.
- Method flexibilityStraight-line, reducing balance and more, per asset class and policy.
- Lifecycle eventsTransfers, revaluations, impairments and disposals with the accounting generated.
- Lease accountingIFRS 16 right-of-use assets and liabilities handled within the module family.
How does NetSuite handle three-way matching?
NetSuite builds three-way matching directly into your standard Accounts Payable workflow. Whenever a vendor bill comes in, NetSuite automatically compares three documents: the original purchase order, the warehouse item receipt and the incoming bill. If the quantities and prices match, it moves right along for payment. If there is a discrepancy, the system flags the issue and holds the invoice until your team resolves it. You can also configure tolerance rules so tiny rounding differences pass through automatically without clogging up your AP queue.
How does the 3-way match work in accounts payable?
In NetSuite Accounts Payable, 3-way matching acts as a digital guardrail for every vendor invoice. When your team enters a bill, each line item links directly back to the original purchase order, while item receipts set the maximum quantity that can actually be billed. If a vendor charges a higher price or bills for items that haven’t arrived yet, NetSuite flags the variance and blocks payment until someone reviews it. Tied directly into your approval workflows, it helps stop unapproved or incorrect invoices from being paid.
Why does the control decay?
Three-way matching is only as strong as the day-to-day discipline of the team managing the AP queue. The system breaks down when warehouse staff post receipts late (blocking valid bills) or when AP teams force-approve price mismatches just to clear the queue during month-end close. Over time, ‘temporary’ loosening of tolerance limits can become standard operating procedure. NetSuite provides the matching framework, but keeping your AP controls transparent takes continuous queue hygiene and clear policy enforcement.
The control anatomy
- Three-document matchPO, receipt and bill, with quantity and price agreement enforced at line level.
- Tolerance rulesMateriality bands auto-clearing noise so humans work real variances.
- Exception holdsMismatches are held from payment until resolved, which is the point of the whole control.
- Receipt dependencyLate receipting blocks matching – the upstream discipline the control inherits.
Last reviewed: 25 September 2026 · Written by the SuiteGeneration team
SuiteGeneration is an independent, senior-led NetSuite consultancy. Every project is designed and delivered by consultants at or close to solution-architect level. We don’t resell licences or carry partner targets. Our advice is ours, whether you’re implementing NetSuite, rescuing a stalled project or fixing a system that never delivered.
