NetSuite BigQuery integration schedule and the quota math behind it
6 min read Finance The Adapters team
Field mapping auto-plugged · tap a port to rewire
Plug a source port into
Transform on this cable
JSON in
JSON out
5 sample records ready
A NetSuite BigQuery integration should load hourly, not every minute. NetSuite lets all your integrations together use only 5 to 20 concurrent requests, and BigQuery accepts 1,500 modifications per standard table per day, failed loads included. Hourly loads use 24 of those 1,500, leave NetSuite slots free for the rest of the business, and are fast enough for any finance dashboard.
Key takeaways
- Two ceilings, not one. NetSuite caps concurrent requests per account, BigQuery caps table modifications per day.
- Backfill is the real load. A SuiteQL query stops at 100,000 results, so history is loaded in date windows.
- Use NUMERIC for money. It holds 38 digits with 9 decimals, exact for any currency.
- Reconcile, do not trust the log. A green run is not a matching trial balance.
How often should NetSuite sync to BigQuery?
Hourly for operational dashboards, daily for the trial balance. The reason is arithmetic, not taste. Google's quotas page states that a standard table can take 1,500 modifications a day, that each load, copy or query job that appends or overwrites data counts as one, and that failed load jobs count toward the limit. It is enforced as a rate across the day, so a burst can trigger quotaExceeded even when the daily total looks safe. Here is what each schedule spends on a single table.
| Schedule | Load jobs a day | Share of 1,500 | Verdict |
|---|---|---|---|
| Every 5 minutes | 288 | 19% | Fine on quota, but every run spends NetSuite slots even when nothing changed |
| Every minute | 1,440 | 96% | One retry storm or one backfill tips the table into quotaExceeded |
| Every 15 minutes | 96 | 6% | Comfortable, and enough for an intraday cash position |
| Hourly | 24 | 2% | Right for most finance dashboards and close tracking |
| Daily | 1 | under 1% | Enough for the trial balance and board reporting |
The quota is per table, so ten NetSuite tables each loading every five minutes are ten separate budgets of 288. The trap is a pipeline that loads once per page of results instead of once per run, which turns a backfill into thousands of jobs against one table. Ask any vendor whether it stages a whole window and issues one load.
How long does a NetSuite to BigQuery backfill take?
Count requests first. A SuiteQL page holds up to 1,000 rows, so a two million line transaction history is at least 2,000 requests. A single query returns at most 100,000 results, so that same history needs a minimum of 20 date windows, in practice more, because busy months exceed the average. Those 2,000 requests then queue for your concurrency slots: 5 on Standard, 15 on Premium, 20 on Enterprise and Ultimate, shared with every other integration. Measure how many pages per minute your account actually sustains on a quiet Sunday, divide, and you have the real duration. Do not run it in close week, because the first thing to starve is your own storefront connector. The slot math is spelled out on NetSuite concurrency limits.
Which BigQuery column types should NetSuite amounts use?
NUMERIC for every currency amount. Google documents it as precision 38 and scale 9, so cents are exact. FLOAT64 is binary floating point, and the sum of a few million cent values in it drifts by small amounts that never match NetSuite exactly. BIGNUMERIC, with scale 38, is overkill for money. Partition the large transaction table by transaction date, so a month-end query scans one month rather than the full history, which is what BigQuery bills on. Details are in Google's standard SQL data types reference.
Does BigQuery have a NetSuite connector?
No. The BigQuery Data Transfer Service lists Salesforce, ServiceNow, HubSpot, Shopify, Stripe, PayPal and the Oracle database among its sources on the page read on 16 November 2026, and NetSuite is not one of them. You need a tool. The options, with billing units and where each loses, are scored on NetSuite to BigQuery integration tools, and the wider warehouse comparison is on NetSuite data warehouse options for finance teams.
A check that proves the schedule works
After the first full close on the new pipeline, run one query per table in each system: count of internal IDs, distinct count of internal IDs and sum of amount, grouped by month. Equal counts with unequal distinct counts mean a retry appended a page twice, because BigQuery enforces no primary key. A higher count in BigQuery means deleted or voided records never left. Matching sums to the penny means types and windows are right. Run it monthly, not once.
If NetSuite also carries subscription revenue, remember that a warehouse can only report what was billed. Teams that lose revenue to declined cards often pair the reporting work with Revrescue to recover failed payments before they reach the books. When you are ready to map the records, open the NetSuite to BigQuery connector, review plans on pricing, and read Oracle's own SuiteAnalytics Connect documentation for the bulk route.
NetSuite in BigQuery on a schedule that fits both limits
Map the records once, declare exact decimals, backfill by date window, then sync only what changed. Flat plans from $49 a month, with retries, alerts and per-record logs.
The live demo needs no card, and Starter is $49 a month.