This is the shortest process list in the series, and the omissions are the point. There is no order to cash, no lead to quote, no returns process for customers. A restaurant or hotel does not take orders in its finance system, it takes them at a till or a front desk, and what reaches NetSuite is a summary of the day. What the edition does carry instead is a point-of-sale integration and a full fixed asset lifecycle, which is a fair description of the industry: a lot of property, and revenue that arrives already totalled. This is the leading practice reference for restaurants and hotels: every process area, the flow it follows, the rules that govern it, and a copy-ready skill file for each one.
How to Use This
Each process area below carries three things. A flow, which is the sequence the process actually runs in. A short set of rules specific to restaurants and hotels rather than generic ERP advice. And a skill file you can copy straight out of the page, written as markdown so it can be handed to an AI assistant, dropped into a project repository, or used as the basis for a design document.
The skill files are deliberately short. They are checklists for people who already know the domain, not tutorials. Each one names the roles that own the process, the flow, the rules, what to verify before go-live, and the failure modes that recur.
Methodology note. This reflects the Hospitality, Restaurants and Hotels edition as applied by Azdan across its NetSuite delivery in the UAE, Saudi Arabia, and Egypt. Module availability differs by edition and license, so confirm against your own before treating any rule as available. Where a point is a recommendation from delivery experience rather than a documented rule, it is labeled as one.
The 7 Process Areas
Master Data Management → Item Management → Point-of-Sale Integration → Procurement and Replenishment → Return to Debit → Acquire to Retire → Financial Management
Process area
Primary owner
What it covers
Master Data Management
Controller
Accounts, customers, vendors and the segment structure a multi-site operator reports against.
Item Management
Chief Financial Officer
Items, and the decision that governs them.
Point-of-Sale Integration
Administrator
The boundary every sale crosses, and the process area with no equivalent anywhere else in this series.
Procurement and Replenishment
General Manager
Buying food, beverage and everything else a site consumes, with much of the paperwork arriving through an integration rather than being typed.
Return to Debit
Purchasing Manager
Vendor returns, credits and refunds.
Acquire to Retire
Controller
Fixed assets, from proposal through depreciation to disposal.
Financial Management
Controller
The close, reporting and multi-entity operation.
1. Master Data Management
Accounts, customers, vendors and the segment structure a multi-site operator reports against. In hospitality the customer record is unusual, because the customer is a till rather than a person.
Define accounts and segments → Create locations → Create a POS customer per site → Load vendors → Validate
Leading practice rules
Where the point-of-sale or property management system sends summary store-level sales by invoice, create a single POS customer record for each point-of-sale, so transactions can be analyzed by the till that produced them.
Use custom segments to segment data further for reporting, applied on sales transactions.
Lead and prospect records exist for the order path that does not come through the till, such as catering and events.
Skill file: Master Data Management
---
name: hospitality-master-data-management
description: NetSuite leading practice for Master Data Management in restaurants and hotels
---
# Master Data Management - Restaurants and Hotels
## Roles
Controller, Administrator, Accounting Analyst
## Process flow
Define accounts and segments → Create locations → Create a POS customer per site → Load vendors → Validate
## Leading practice rules
- Where the point-of-sale or property management system sends summary store-level sales by invoice, create a single POS customer record for each point-of-sale, so transactions can be analyzed by the till that produced them.
- Use custom segments to segment data further for reporting, applied on sales transactions.
- Lead and prospect records exist for the order path that does not come through the till, such as catering and events.
## Check before go-live
- [ ] One POS customer record per site, agreed before the integration is switched on
- [ ] Custom segments defined for the reporting cuts the business actually uses
## Known failure modes
- A single customer record shared across sites, so revenue cannot be analyzed by till or location
## Scope note
This reflects the Hospitality, Restaurants and Hotels edition. Confirm against your own licensed
modules and edition before treating any rule as available.
2. Item Management
Items, and the decision that governs them. The edition makes the item strategy conditional on something outside NetSuite: where inventory is actually managed.
Decide where inventory lives → Create non-inventory items for sale → Set tax schedules → Map menu pricing → Release
Leading practice rules
The item strategy depends on the inventory management platform chosen. Most operators leave inventory management in the point-of-sale or property management system.
Create non-inventory items for sale on the point-of-sale, with the item number, display name and description set, and the product category held as class.
All item prices are managed in the point-of-sale, which may use its own price levels to vary them, such as a happy hour price.
Menu item pricing on the NetSuite invoice comes from the sale price set in the point-of-sale and arrives as a custom price. The NetSuite item record does not reflect the point-of-sale price level.
Define tax schedules so NetSuite knows which items are taxable and which tax code to apply when they are sold or purchased.
Skill file: Item Management
---
name: hospitality-item-management
description: NetSuite leading practice for Item Management in restaurants and hotels
---
# Item Management - Restaurants and Hotels
## Roles
Chief Financial Officer, Controller, Administrator, Purchasing Manager
## Process flow
Decide where inventory lives → Create non-inventory items for sale → Set tax schedules → Map menu pricing → Release
## Leading practice rules
- The item strategy depends on the inventory management platform chosen. Most operators leave inventory management in the point-of-sale or property management system.
- Create non-inventory items for sale on the point-of-sale, with the item number, display name and description set, and the product category held as class.
- All item prices are managed in the point-of-sale, which may use its own price levels to vary them, such as a happy hour price.
- Menu item pricing on the NetSuite invoice comes from the sale price set in the point-of-sale and arrives as a custom price. The NetSuite item record does not reflect the point-of-sale price level.
- Define tax schedules so NetSuite knows which items are taxable and which tax code to apply when they are sold or purchased.
## Check before go-live
- [ ] A written decision on whether inventory stays in the point-of-sale or moves to NetSuite
- [ ] Tax schedules assigned to every sellable item
## Known failure modes
- Expecting NetSuite item records to carry menu prices, when pricing lives in the point-of-sale and reaches the invoice as a custom price
## Scope note
This reflects the Hospitality, Restaurants and Hotels edition. Confirm against your own licensed
modules and edition before treating any rule as available.
3. Point-of-Sale Integration
The boundary every sale crosses, and the process area with no equivalent anywhere else in this series. What arrives is a summary of the day, not a stream of orders.
Close the day in the POS → Summary invoice into NetSuite → Payment per tender → Discounts, tips and tax mapped → Voids after tender as credit memos
Leading practice rules
A summarized customer invoice is created in the point-of-sale and sent through the POS middleware, and once closed it creates an invoice in NetSuite through the integration. It carries the discounts, tips, taxes and tenders of the transactions behind it.
A payment record is created for each tender. Where a check was settled by more than one tender, several payment records are applied to the same summary invoice to close it, such as cash plus card.
The tax rate is calculated in the point-of-sale and written back to NetSuite, which then calculates the tax amount and tax code.
Discounts map to a discount item, shown on the invoice at line or header level depending on the discount type in the point-of-sale.
Tips map to a service item and appear on the invoice.
Gift cards are a tender type. There is no gift card liability tracking in NetSuite.
A transaction voided before payment is not sent to NetSuite at all. A transaction voided after payment creates a credit memo, covering both adjusting payment on a closed check and reopening a closed check to void an item.
Skill file: Point-of-Sale Integration
---
name: hospitality-point-of-sale-integration
description: NetSuite leading practice for Point-of-Sale Integration in restaurants and hotels
---
# Point-of-Sale Integration - Restaurants and Hotels
## Roles
Administrator, Controller, Accounting Analyst
## Process flow
Close the day in the POS → Summary invoice into NetSuite → Payment per tender → Discounts, tips and tax mapped → Voids after tender as credit memos
## Leading practice rules
- A summarized customer invoice is created in the point-of-sale and sent through the POS middleware, and once closed it creates an invoice in NetSuite through the integration. It carries the discounts, tips, taxes and tenders of the transactions behind it.
- A payment record is created for each tender. Where a check was settled by more than one tender, several payment records are applied to the same summary invoice to close it, such as cash plus card.
- The tax rate is calculated in the point-of-sale and written back to NetSuite, which then calculates the tax amount and tax code.
- Discounts map to a discount item, shown on the invoice at line or header level depending on the discount type in the point-of-sale.
- Tips map to a service item and appear on the invoice.
- Gift cards are a tender type. There is no gift card liability tracking in NetSuite.
- A transaction voided before payment is not sent to NetSuite at all. A transaction voided after payment creates a credit memo, covering both adjusting payment on a closed check and reopening a closed check to void an item.
## Check before go-live
- [ ] Gift card liability given an owner and a home outside NetSuite
- [ ] Multi-tender settlement tested end to end, including a check split across cash and card
- [ ] Void behavior tested on both sides of tender
## Known failure modes
- Assuming NetSuite holds gift card liability, so unredeemed balances appear nowhere
- Reconciling till counts to NetSuite and finding gaps, because pre-tender voids never left the point-of-sale
## Scope note
This reflects the Hospitality, Restaurants and Hotels edition. Confirm against your own licensed
modules and edition before treating any rule as available.
4. Procurement and Replenishment
Buying food, beverage and everything else a site consumes, with much of the paperwork arriving through an integration rather than being typed.
Roles: General Manager, Purchasing Manager, A/P Analyst, Controller
Process flow
Plan against anticipated demand → Purchase order → Receive → Vendor bill manually or by integration → Pay → Review vendor performance
Leading practice rules
Before raising a purchase order, plan to determine the supply required to meet anticipated demand.
For food and beverage item orders, enter vendor bills manually where needed. Otherwise vendor bills are entered automatically through the integration.
Where the vendor bill rate differs from the item receipt rate, consider updating the receipt rate to match, so cost of sales is accurate and vendor bill variances need not be posted.
Generate payment files for the bank portal, where the designated approver logs in and approves the payment run.
Analyze vendor performance through vendor scorecards and KPIs.
Skill file: Procurement and Replenishment
---
name: hospitality-procurement-and-replenishment
description: NetSuite leading practice for Procurement and Replenishment in restaurants and hotels
---
# Procurement and Replenishment - Restaurants and Hotels
## Roles
General Manager, Purchasing Manager, A/P Analyst, Controller
## Process flow
Plan against anticipated demand → Purchase order → Receive → Vendor bill manually or by integration → Pay → Review vendor performance
## Leading practice rules
- Before raising a purchase order, plan to determine the supply required to meet anticipated demand.
- For food and beverage item orders, enter vendor bills manually where needed. Otherwise vendor bills are entered automatically through the integration.
- Where the vendor bill rate differs from the item receipt rate, consider updating the receipt rate to match, so cost of sales is accurate and vendor bill variances need not be posted.
- Generate payment files for the bank portal, where the designated approver logs in and approves the payment run.
- Analyze vendor performance through vendor scorecards and KPIs.
## Check before go-live
- [ ] Which vendors bill through the integration and which are manual, documented per supplier
- [ ] A vendor scorecard defined for the main food and beverage suppliers
## Known failure modes
- Vendor bill rates accepted without checking the receipt rate, so cost of sales drifts from what was actually agreed
## Scope note
This reflects the Hospitality, Restaurants and Hotels edition. Confirm against your own licensed
modules and edition before treating any rule as available.
5. Return to Debit
Vendor returns, credits and refunds. In a kitchen these arise constantly, from short deliveries to product that fails on arrival.
Roles: Purchasing Manager, General Manager, A/P Analyst, Controller
Process flow
Identify short or rejected delivery → Vendor return or credit request → Approve → Vendor credit → Apply to payable
Leading practice rules
Raise vendor returns and credits from the originating purchase transaction so the payable reconciles.
Raise credits for contract breaches such as short or late deliveries, not only for goods physically sent back.
Apply vendor credits to reduce accounts payable.
Skill file: Return to Debit
---
name: hospitality-return-to-debit
description: NetSuite leading practice for Return to Debit in restaurants and hotels
---
# Return to Debit - Restaurants and Hotels
## Roles
Purchasing Manager, General Manager, A/P Analyst, Controller
## Process flow
Identify short or rejected delivery → Vendor return or credit request → Approve → Vendor credit → Apply to payable
## Leading practice rules
- Raise vendor returns and credits from the originating purchase transaction so the payable reconciles.
- Raise credits for contract breaches such as short or late deliveries, not only for goods physically sent back.
- Apply vendor credits to reduce accounts payable.
## Check before go-live
- [ ] A route for crediting short deliveries, which rarely involve a physical return
## Known failure modes
- Short deliveries absorbed by the kitchen and never credited, because nothing went back to the supplier
## Scope note
This reflects the Hospitality, Restaurants and Hotels edition. Confirm against your own licensed
modules and edition before treating any rule as available.
6. Acquire to Retire
Fixed assets, from proposal through depreciation to disposal. A hotel is a large asset with a business inside it, and this is the process area that reflects that.
Roles: Controller, Accounting Analyst, General Manager
Process flow
Propose or create asset → Review and generate → Depreciate → Revalue, split or transfer → Dispose by sale or write-off
Leading practice rules
Every asset carries an asset type, which drives reporting and pre-populates asset attributes.
Asset records can be created from purchases, expenses and inventory transfers, or manually, individually or in batch by CSV import.
Asset proposals are generated from the Asset Proposal page, reviewed individually and edited as temporary records, then either generated into real asset records or rejected.
Capitalize assets by journal entry where they do not flow neatly through purchase order, item receipt and vendor bill, which is common for buildings and vehicles.
Run depreciation on all assets monthly, quarterly or annually. An alternate depreciation method can be assigned after an asset is generated, with a different lifetime and residual value.
Assets can be revalued up or down, split into several assets, and transferred across asset types, subsidiaries, classes, departments or locations.
Dispose of an asset at the end of its life by sale or by write-off, and use the searches that come with the fixed assets bundle for reporting.
Skill file: Acquire to Retire
---
name: hospitality-acquire-to-retire
description: NetSuite leading practice for Acquire to Retire in restaurants and hotels
---
# Acquire to Retire - Restaurants and Hotels
## Roles
Controller, Accounting Analyst, General Manager
## Process flow
Propose or create asset → Review and generate → Depreciate → Revalue, split or transfer → Dispose by sale or write-off
## Leading practice rules
- Every asset carries an asset type, which drives reporting and pre-populates asset attributes.
- Asset records can be created from purchases, expenses and inventory transfers, or manually, individually or in batch by CSV import.
- Asset proposals are generated from the Asset Proposal page, reviewed individually and edited as temporary records, then either generated into real asset records or rejected.
- Capitalize assets by journal entry where they do not flow neatly through purchase order, item receipt and vendor bill, which is common for buildings and vehicles.
- Run depreciation on all assets monthly, quarterly or annually. An alternate depreciation method can be assigned after an asset is generated, with a different lifetime and residual value.
- Assets can be revalued up or down, split into several assets, and transferred across asset types, subsidiaries, classes, departments or locations.
- Dispose of an asset at the end of its life by sale or by write-off, and use the searches that come with the fixed assets bundle for reporting.
## Check before go-live
- [ ] Asset types defined before the first proposal is generated
- [ ] A capitalization policy covering assets that will not flow through procurement
## Known failure modes
- Proposals generated into asset records without review, so lifetimes and residual values are wrong from the start
- Refurbishment capitalized inconsistently across sites, making property returns incomparable
## Scope note
This reflects the Hospitality, Restaurants and Hotels edition. Confirm against your own licensed
modules and edition before treating any rule as available.
7. Financial Management
The close, reporting and multi-entity operation. Two things here are unusual: the period settings are deliberately loosened, and the most useful numbers in the business are not monetary.
Set periods and settings → Post allocations and intercompany → Record statistical data → Reconcile → Close → Report
Leading practice rules
To prevent posting period errors, set allow transaction date outside of posting period, set the default posting period for a transaction dated in a closed period to the current period, and enable creating and editing inventory transactions dated in closed periods and outside the posting period.
Use statistical accounts to hold non-monetary data, altered by statistical journals, so it can be referenced on reports and income statements. This is how covers, room nights or occupancy reach a per-unit view of performance.
Use allocation and amortization schedules rather than entering complex recurring journals by hand.
For groups, maintain intercompany entities, paired intercompany purchase and sales orders, intercompany invoices and journals, and keep intercompany accounts separate from ordinary receivables and payables.
The trial balance report is not restricted by location, so a user with a location-restricted role may see an apparent imbalance where a transaction has lines in both accessible and inaccessible locations.
Set the Report by Period preference to All Reports so period-end subledger figures agree with the trial balance.
Skill file: Financial Management
---
name: hospitality-financial-management
description: NetSuite leading practice for Financial Management in restaurants and hotels
---
# Financial Management - Restaurants and Hotels
## Roles
Controller, Accounting Analyst, Chief Financial Officer, A/P Analyst
## Process flow
Set periods and settings → Post allocations and intercompany → Record statistical data → Reconcile → Close → Report
## Leading practice rules
- To prevent posting period errors, set allow transaction date outside of posting period, set the default posting period for a transaction dated in a closed period to the current period, and enable creating and editing inventory transactions dated in closed periods and outside the posting period.
- Use statistical accounts to hold non-monetary data, altered by statistical journals, so it can be referenced on reports and income statements. This is how covers, room nights or occupancy reach a per-unit view of performance.
- Use allocation and amortization schedules rather than entering complex recurring journals by hand.
- For groups, maintain intercompany entities, paired intercompany purchase and sales orders, intercompany invoices and journals, and keep intercompany accounts separate from ordinary receivables and payables.
- The trial balance report is not restricted by location, so a user with a location-restricted role may see an apparent imbalance where a transaction has lines in both accessible and inaccessible locations.
- Set the Report by Period preference to All Reports so period-end subledger figures agree with the trial balance.
## Check before go-live
- [ ] Statistical accounts defined for the operating measures the business manages by
- [ ] The loosened period settings applied deliberately, with a compensating review of late postings
## Known failure modes
- Chasing a trial balance imbalance that is a location permission artifact rather than a real difference
- Loosened period settings left without a review routine, so late postings quietly change closed months
## Scope note
This reflects the Hospitality, Restaurants and Hotels edition. Confirm against your own licensed
modules and edition before treating any rule as available.
Where to Start
Decide first where inventory and pricing live, because the edition makes the item strategy conditional on it and most operators leave both in the point-of-sale or property management system. That single decision sets what NetSuite can ever report on food cost. Then design the point-of-sale integration, since it is the boundary every sale crosses. Procurement, returns and fixed assets follow, with financial management running throughout.
The single highest-value check before go-live: decide who tracks gift card liability, because NetSuite will not. The edition is explicit that gift cards are a tender type with no gift card liability tracking in NetSuite. Unredeemed gift cards are a real obligation and a real balance, and they need a home, whether that is the point-of-sale, a controlled spreadsheet, or a deliberate build. Discovering the gap at the first audit is the expensive version.
Published by Azdan, an Oracle NetSuite Solution Provider operating across the UAE, Saudi Arabia, and Egypt. Guidance in this article reflects Azdan's process design work with restaurants and hotels. Content checked August 2026.
Blog
News & Insights
Fresh thinking and real-world advice to help you scale smarter, faster, and with more clarity
.svg)
.png)
