NetSuite reporting that goes past saved searches.
Saved searches and SuiteAnalytics Workbook answer the first question. Tau handles the printed statement, the grouped and subtotaled pack, the matrix by rep and month, and the PDF that has to land in an inbox every Monday.
Where NetSuite reporting runs out of road.
A saved search is the workhorse of NetSuite reporting, and it is built one record type at a time. Joining across transactions, items, customers, and custom records means nested formula fields and summary types that only the person who wrote them can read. Sharing is per role, and a search that works for one subsidiary often breaks for another.
SuiteAnalytics Workbook adds pivots and charts on top of datasets, but the datasets are still assembled inside NetSuite with the same join rules, and a workbook is not a printed document. Financial Report Builder covers the statements. Anything operational, such as open orders by rep with backorder flags, inventory aging with landed cost, or a customer statement that runs to three pages, ends up as a CSV export into Excel.
SuiteAnalytics Connect exposes the tables over ODBC and JDBC, which is exactly what a report tool needs, but it is not a report tool. The gap is between the data being available and a finished report someone else can open.
What Tau reads from NetSuite, honestly.
Tau does not have a native NetSuite connector today, and this page will not pretend otherwise. What Tau connects to is a replica of your NetSuite data: the SQL Server, PostgreSQL, or MySQL database that your integration or ELT tool already keeps in sync, a data warehouse export, or an OData feed if your integration publishes one. Many NetSuite customers already have one of these for Power BI or a warehouse project; Tau reads it with a read-only login and builds everything below from it.
A direct NetSuite connector, reading through SuiteAnalytics Connect or SuiteQL, is on the roadmap. If that matters for your timeline, tell us and we will be straight about where it is.
Runs on your server. One service on Windows or Linux, or a container. A read-only login. Reports are plain files with version history. Nothing leaves your network unless you schedule a delivery.
Reports NetSuite teams build first.
The demo runs on Northstar Coffee, an invented company in a real database. It shows the same report types below on sample data, not on NetSuite.
Open sales orders by rep
Paginated, grouped by rep with backordered lines flagged, page N of M, emailed as a PDF to each rep every Monday morning.
See this report type in the demo →Customer statements
One PDF per customer with invoices, credits, payments, and the aged balance, bursted to each account on the first of the month.
See this report type in the demo →Item margin matrix
Item class down the side, location or month across the top, with cost, revenue, and margin percentage in each cell and totals.
See this report type in the demo →Receivables dashboard
Aging by subsidiary, month-end balances, collections by method, and a right-click drill from any bar to the invoices behind it.
See this report type in the demo →Tau and NetSuite: the questions we get asked.
Does Tau replace saved searches?
No. Saved searches remain the right tool for lists and alerts inside NetSuite. Tau is for the reports that need layout, grouping, printing, pivot columns, delivery on a schedule, or data from more than one system.
Do I need SuiteAnalytics Connect?
Not for Tau itself. Tau reads a replica of your NetSuite data in SQL Server, PostgreSQL, or MySQL, a warehouse export, or an OData feed. Whatever tool fills that replica may use SuiteAnalytics Connect, REST, or SuiteQL; Tau does not care which.
Can Tau write back to NetSuite?
No. Tau is read-only by design. It uses a read-only database login and never changes records in NetSuite or in the replica.
See it on your NetSuite data.
Tell us how you run NetSuite and the one report you wish you had. We will build it with you, live, and tell you plainly how Tau would connect.