fferent ground: 1. **REST Record API** — CRUD by internal ID, no filtering 2. **SuiteQL** — NetSuite's proprietary SQL dialect 3. **Saved Searches** — pre-built queries created in the GUI, executed via SOAP The REST Record API cannot filter. `GET /invoice` returns all invoices paginated, no `WHERE` clause. Ralph must use SuiteQL: ```bash POST https://5839274.suitetalk.api.netsuite.com/services/rest/query/v1/suiteql Content-Type: application/json { "q": "SELECT id, tranid, entity, trandate, status, foreigntotal FROM transaction WHERE type = 'CustInvc' AND trandate >= '2/1/2026' AND status = 'CustInvc:A' ORDER BY trandate DESC" } ``` The table is `transaction`. Not `invoice`. In NetSuite's data model, invoices, sales orders, purchase orders, credit memos, and journal entries share the `transaction` table, differentiated by a `type` column. Customer invoices are `CustInvc`. The status code for "Open" is `CustInvc:A`. Not `open`. Not `pending`. A two-part code — type prefix plus a letter — documented in a 47-page PDF called "SuiteQL Query Capabilities" that is not linked from the REST API reference. The `entity` field in the response is `37482` — a bare internal numeric ID, not a customer name. Ralph needs a JOIN: ```sql SELECT t.id, t.tranid, c.entityid, c.companyname, t.trandate, t.status, t.foreigntotal FROM transaction t INNER JOIN customer c ON t.entity = c.id WHERE t.type = 'CustInvc' AND t.trandate >= '2/1/2026' AND t.status = 'CustInvc:A' ORDER BY t.trandate DESC ``` The `customer` table uses `entityid` for the display ID (like `CUST-0091`) and `companyname` for the human-readable name. Some fields are camelCase, some are lowercase concatenated, some are abbreviated (`tran` for transaction, `custinvc` for customer invoice). Ralph maps them one by one. Ralph retrieves the invoices. Each references line items, but line items live in the `transactionline` table: ```sql SELECT tl.item, tl.quantity, tl.rate, tl.amount, i.itemid, i.displayname FROM transactionline tl INNER JOIN item i ON tl.item = i.id WHERE tl.transaction = 748291 AND tl.mainline = 'F' ``` The `mainline` filter is a trap. NetSuite stores a "main line" row (the header total) and individual line item rows in the same table. Without `mainline = 'F'`, the query returns both, and the amounts double-count. Ralph discovers this after his first revenue calculation returns $84,620 for an order batch that should total $42,310. The main line row carries the invoice total. The line items carry individual amounts. They coexist in the same table. An agent that does not know about `mainline` will produce wrong numbers every time. ## Saved Searches: SOAP in 2026 Rodney's accountant built saved searches in the NetSuite GUI: "Overdue by Channel," "Weekly Payment Summary," "Revenue by Customer." These are the primary reporting mechanism — filters, columns, formulas, formatting — all configured through a point-and-click search builder. Ralph needs the "Overdue by Channel" search. Saved searches are not queryable via SuiteQL. They are not accessible via the REST API. They require the SOAP API — SuiteTalk's original XML-based interface: ```xml 5839274 consumer_key token_id random_nonce 1739001600 computed_signature ``` SOAP. XML namespaces. Schema-specific typ