Octopus + NetSuite Integration

Octopus handles millions of tap-and-go transactions across Hong Kong daily. Merchants get batch settlements. NetSuite gets nothing automatically.

Oracle ERP Expertise CertifiedTransparent PricingPost Go-Live Support

Octopus logo

The Problem

Octopus settles daily with fees deducted. NetSuite needs itemized revenue by location. The gap means spreadsheets.

Almost everyone in Hong Kong uses Octopus to pay. It's not credit cards; it's a stored-value system. But reconciling daily settlements with actual sales is painful, especially with fees and refunds in the mix. Most teams handle it in spreadsheets, which doesn't scale.

When an Octopus + NetSuite Integration Becomes the Better Fit

SOMEONE PROCESSES SETTLEMENT FILES IN EXCEL EVERY MORNING

Your team downloads the daily Octopus report, strips out fees, and manually enters the net amount into NetSuite. Every day, for every location.

SETTLEMENT DATA IMPORTED AND SPLIT INTO THE RIGHT GL ACCOUNTS

Octopus settlement files flow into NetSuite with gross sales, fees, and net deposit amounts automatically separated. Multi-location merchants get each terminal mapped to the correct NetSuite location.

PROCESSING FEES BURIED IN THE NET DEPOSIT

Most teams book the net amount as revenue and never break out what they're paying in Octopus fees. The cost is invisible on the P&L.

FEES POST TO THEIR OWN EXPENSE ACCOUNT

Octopus processing fees land in a dedicated expense account in NetSuite. You can compare what you're paying per location, per month, against other payment methods.

REFUNDS CREATE GAPS THAT ARE HARD TO EXPLAIN

A refund issued Tuesday might not hit your settlement until Thursday. The deposit comes in lower than expected and nobody can immediately say why.

REFUNDS TRACKED FROM ISSUE DATE THROUGH SETTLEMENT IMPACT

Refunds are matched to the settlement batch where Octopus deducts them. NetSuite records both the refund date and the settlement impact date, so the gap is accounted for from the start.

BANK RECONCILIATION TAKES MOST OF THE MORNING

The bank deposit is one line. The Octopus settlement report has hundreds. Matching them by hand takes hours and small errors compound over time.

BANK DEPOSITS AUTO-MATCHED TO SETTLEMENT RECORDS

NetSuite deposit records are created from Octopus settlement data with the exact expected amount. Reconciliation becomes a one-click match instead of a manual puzzle.

PAYMENT MIX REQUIRES PULLING FROM MULTIPLE PLACES

You know total revenue. You don't know what share came through Octopus versus credit cards, cash, or FPS — that data lives in different systems.

PAYMENT METHOD BREAKDOWN AVAILABLE IN NETSUITE

Octopus transactions are tagged by payment method alongside your other channels. Saved searches show payment mix by location and time period so you can spot trends and negotiate better rates.

Octopus + NetSuite Integration

What We'd Ask Before Scoping Octopus

Octopus card payments have unique settlement mechanics that affect how the NetSuite integration is built.

TERMINALS AND SETTLEMENT FILES

How many POS locations accept Octopus, whether each reconciles separately, and how you receive settlement data.

SETTLEMENT LAG AND TIMING

Octopus typically settles T+1 or T+2. How you want to handle the gap between sale date and cash arrival.

CHANNELS, FEES, AND MATCHING

Standard card taps, online payments, or both? How processing fees are structured and how you match settlements to daily POS totals.

Crash illustration

We can then define the data flow, matching rules, and full project scope.

Mattia

ONE Pacific built a custom wholesale portal powered by Workato, allowing distributors to enter order details on their own without involving our staff.

Mattia Lolli

Chief Operating Officer

D1 Milano

OCTOPUS + NETSUITE

How the Integration Works

Octopus settlement files import into NetSuite with gross sales, fees, and refund adjustments split across the correct GL accounts, with each terminal mapped to its NetSuite location.

1
Settlement Files Import on a Daily Schedule
Octopus daily settlement reports are retrieved automatically, parsed to extract transaction totals before any records are written to NetSuite.
2
Gross Sales and Fees Split at Import
Each settlement splits into gross sales, fees, and net deposit at import, with fees directed to a dedicated expense account in NetSuite.
3
Terminals Map to NetSuite Locations
Octopus terminal IDs map to the corresponding NetSuite location record, so multi-location merchants get settlement data posted to the right location.
4
Refunds Matched to the Settling Batch
Refunds match to the settlement cycle where Octopus deducts them, so NetSuite records both the refund issue date and the settlement impact date.
Deposit Records Created for Bank Reconciliation
A NetSuite deposit record is created for each Octopus settlement with the exact expected amount, making bank reconciliation a direct match.

Most Octopus + NetSuite integrations are scoped in under two weeks and live within 4 to 6 weeks. Let's figure out yours.

Octopus + NetSuite Integration

FAQ's

Cost drivers depend entirely on which Octopus product you're integrating—Octopus Energy (the UK energy retailer) needs complex mapping for energy accounts and payment plans through their meter reading APIs and tariff management endpoints, while Octopus Deploy (the deployment tool) requires syncing deployment data with NetSuite projects.

If it's Octopus Energy, you'll face higher costs with direct debit reconciliation, prepayment meter tracking, regulatory scheme handling like Warm Home Discount, and integrating their specific API data structures with NetSuite's Advanced Revenue Management module for energy contracts. The Patchworks iPaaS option simplifies setup but adds subscription costs, while direct API integration means wrestling with NetSuite's daily call limits for high-volume billing data.

Yes. Each Octopus terminal ID maps to a specific NetSuite location or subsidiary. Settlement data posts to the right entity without anyone sorting through terminal reports manually. Adding a new location is just a new mapping entry.

Typically 4 to 6 weeks. The first week covers scoping: mapping your Octopus merchant terminal IDs to NetSuite locations, defining how fees and refunds should post, and setting up the settlement file import format. Build and testing runs three to five weeks, including a parallel period where automated entries are checked against your existing manual process.

Each daily settlement file from Octopus is parsed into its components: gross transaction value, processing fees, refund deductions, and net deposit. These post to separate GL accounts in NetSuite. When the bank deposit arrives, it matches the expected net amount already sitting in the system, so reconciliation is a confirmation step rather than a research project.

The integration records the refund on the date it's issued at the terminal and tracks which future settlement batch Octopus actually deducts it from. NetSuite shows both dates, so your daily revenue stays accurate and the bank deposit shortfall on the deduction day is explained automatically.

The Octopus integration covers Octopus-specific settlement and reconciliation. It sits alongside whatever you're already doing for credit cards, FPS, Alipay HK, or WeChat Pay. The benefit is that all payment methods end up in NetSuite with consistent categorization, so you can report on payment mix across channels without pulling from five different sources.

Hero background

Ready to connect Octopus and NetSuite?

Our engineers will review your setup, map your systems, and, if it makes sense to move forward, provide a clearly scoped proposal. No pressure.