The answers to these questions shape the integration design and delivery plan.
BOCHK statements carry HKD, USD, and RMB entries that all need FX conversion before NetSuite can post them. Your team does that math in spreadsheets.
Oracle ERP Expertise CertifiedTransparent PricingPost Go-Live Support

The Problem
Raw MT940 data needs conversion rates, GL mapping, and matched journal lines before NetSuite can post it.
If you bank with BOCHK and run NetSuite, the routine is familiar: download MT940 files, open a spreadsheet, convert and match line by line. It holds together when volume is light. But multi-currency accounts across HKD, USD, and RMB, trade finance settlements with embedded FX, and daily CHATS payments push that process past its limit. One wrong conversion rate cascades through your trial balance.

Finance downloads BOCHK statements, opens them in Excel, and matches transactions to NetSuite records one at a time. Slow, error-prone, and nobody wants to own it.
MT940 and BAI2 files from BOCHK are parsed and imported into NetSuite's bank reconciliation module. Transactions match against open invoices, bills, and journal entries using reference numbers, amounts, and dates. Your team handles exceptions, not the routine.
Someone pulls a vendor pay list from NetSuite, reformats it for BOCHK's autopay or CHATS template, uploads it, then goes back into NetSuite to mark bills as paid.
Approved vendor bills in NetSuite generate a BOCHK-formatted payment file ready for upload — autopay, CHATS, or RTGS. Payment status syncs back after processing.
Your team checks BOCHK's posted rates and types them into NetSuite. If someone's out sick, transactions post at yesterday's rate and corrections pile up at month-end.
BOCHK's published exchange rates feed into NetSuite's currency tables each business day. HKD, CNY, USD, and any other currencies you hold at BOCHK stay current without manual entry.
Letters of credit, trust receipts, and bills of exchange sit in the banking portal and email threads. Nobody can find the LC tied to a specific purchase order without digging through attachments.
LC references, trust receipt numbers, and trade finance status attach directly to NetSuite purchase orders. When a letter of credit clears or a trust receipt matures, the PO record reflects it.
BOCHK processes payroll disbursements. NetSuite has payroll journal entries. Every pay cycle, someone compares two spreadsheets hunting for the difference that won't resolve.
BOCHK payroll transactions map to NetSuite payroll journals by employee reference and amount. Variances surface immediately instead of hiding until the close.
Multiple BOCHK accounts in HKD, CNY, and USD means your actual cash position lives in the banking portal. NetSuite only knows what's been manually posted.
Balances across all BOCHK accounts flow into NetSuite. Cash position by currency and subsidiary, updated daily. No more logging into the portal mid-meeting to answer a board question.
Bank of China HK
What We Need to Scope BOCHK
The answers to these questions shape the integration design and delivery plan.
Which BOCHK accounts are in scope (HKD operating, multi-currency, RMB cross-border) and how many subsidiaries bank there.
How you receive statements today (iGTB, corporate portal CSV/MT940, manual) and whether that changes the integration approach.
Whether NetSuite needs to generate payment files for AUTOPAY, FPS, CHATS same-day clearing, or cross-border RMB remittances.
Whether RMB/HKD settlement or mainland supplier payments are in scope, plus your monthly volume and matching rules.

We use this to specify the file formats, payment channels, cross-border handling, and build plan.


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
BOCHK statement files are parsed into NetSuite daily, transactions are matched against open records automatically, and payment files for autopay, CHATS, and RTGS are generated directly from NetSuite AP.
Most BOCHK + NetSuite integrations are scoped in under two weeks and live within 6 to 8 weeks. Let's figure out yours.

Connect J&T Express to NetSuite so COD remittances reconcile automatically, tracking events flow into fulfillment records, and per-shipment costs post without waiting for monthly invoices.

Airwallex holds balances across 20+ currency wallets. Getting those wallets, conversions, and payouts into the right NetSuite accounts takes more than a flat-file import.

Ninja Van's API varies by country, so COD remittance cycles, tracking payloads, and return-to-sender flows each need per-market logic inside NetSuite.

Reconcile WeChat Pay settlements against NetSuite deposits, handling the gap between transaction-level records in the merchant dashboard and batched payouts to your bank.

Sync Lazada orders, settlements, and returns into NetSuite across all six SEA markets with fees and voucher discounts properly decomposed.

JD.com settlements net out commissions, logistics fees, and promotional subsidies before paying you. Getting that lump deposit to match individual NetSuite sales orders is the real integration problem.
Showing 6 of 34 Banking Integrations
The main cost drivers for BOC(HK) integration center on their ERP integration service, which requires installing a dedicated gateway machine at your site for real-time account enquiries and payments—unlike pure cloud solutions from other banks. Since NetSuite doesn't have native connectors for any Hong Kong banks, you'll need custom development to parse BOC(HK)'s bank statements (typically MT940 or BAI2 formats) and handle their corporate banking portal's payment file workflows.
Complexity jumps when you add Traditional Chinese interfaces, MPF reporting, or need to manage HKD/RMB/USD reconciliation across multiple entities through BOC(HK)'s specific file formats that often don't match NetSuite's standard import definitions.
Each BOCHK account maps to the corresponding NetSuite bank account and currency. HKD, CNY, USD, or any other currency you hold. Transactions post to the right subsidiary with the correct exchange rate. FX differences between BOCHK's settlement rate and NetSuite's daily rate post as realized gains or losses automatically.
Yes. Approved vendor bills in NetSuite generate payment files formatted for BOCHK's autopay, CHATS, or RTGS portals. Upload the file instead of entering payments one by one.
Typically 6 to 8 weeks. The first phase maps BOCHK's statement formats to your NetSuite chart of accounts and defines matching rules. Build and testing takes another four to six weeks, including a parallel run where automated imports are validated against your existing manual process.
It can. Letters of credit, trust receipts, and bills of exchange from BOCHK link to NetSuite purchase orders. This matters most for Hong Kong importers and exporters who use BOCHK's trade finance heavily. The exact scope depends on which instruments you use, so we map that during the scoping phase.
Statement files transfer over encrypted channels. No banking credentials are stored in NetSuite. The integration reads exported files from BOCHK's portal or SFTP.
Yes. Each BOCHK account maps to the right subsidiary. Hong Kong, mainland China, Singapore. Adding a new entity means adding one more account mapping.
MT940, BAI2, and CSV. The integration handles whichever format BOCHK provides for your specific account type and currency.
Ready to connect Bank of China (Hong Kong) 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.