Acumatica reporting beyond generic inquiries and pivot tables.
Generic inquiries are the best list builder in any mid-market ERP. Tau picks up where they stop: paginated output with real page breaks, matrices with pivot columns, dashboards that drill to the lines, and PDFs delivered on a schedule.
Where Acumatica reporting stops being quick.
Generic inquiries make a filtered, sortable list out of almost any set of tables in minutes, and pivot tables slice them. Both are genuinely good. Then someone asks for the same numbers as a printed document, and you are in the Report Designer: a separate Windows application, a layout model that takes days to get pixel-perfect, and a report that only a developer wants to touch again.
Dashboards in Acumatica are widgets over generic inquiries, which works until you want filters that narrow every widget at once, a right-click drill from a bar to the orders behind it, or a chart type that is not in the list. Cross-tenant or cross-source reports, such as Acumatica sales next to BigCommerce or Shopify orders during a migration, are outside what the built-in tools can join.
And delivery is per report instance: scheduling a PDF pack to a list, or one statement per customer, is a project each time. Excel exports lose the layout on the way out.
What Tau reads from Acumatica, honestly.
Acumatica runs on SQL Server. If you self-host or run in a private cloud, Tau connects with a read-only SQL login and reads the tables directly, with the tenant column respected in every query, so SOOrder, ARInvoice, and INItemSite are as close as a query. There is no Acumatica-specific connector to install because none is needed.
On Acumatica SaaS, where the database is not exposed, publish the generic inquiries you need as OData V4 and Tau keeps a local mirror of them: a queryable copy refreshed by polling every minute, with webhooks when Tau has an HTTPS address. Either way, a single Tau report can combine Acumatica with the SQL Server behind the system you are leaving.
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 Acumatica 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 Acumatica.
Open sales orders by customer
Grouped by customer with order, line, and shipment status in bands, page N of M, delivered as a PDF to each rep on Monday morning.
See this report type in the demo →Inventory valuation matrix
Item classes down the side, warehouses across the top, quantity and cost in each cell, with totals and a drill to the item site rows.
See this report type in the demo →Customer statement
Pixel-perfect statement with the company header, invoice detail, payments, and aged buckets, bursted as one PDF per customer.
See this report type in the demo →AP aging dashboard
Open payables by vendor and bucket, scheduled as Excel with live formulas to accounts payable, and a click through to the bills.
See this report type in the demo →Tau and Acumatica: the questions we get asked.
Do I need database access to use Tau with Acumatica?
It is the fastest path: a read-only SQL Server login to a self-hosted or private-cloud instance. Without database access, publish generic inquiries as OData V4 and Tau mirrors them locally.
Does Tau respect Acumatica tenants and restriction groups?
Tau filters by the tenant column in every query. Restriction groups and row-level security inside Acumatica are not applied by the database, so Tau enforces sharing through its own spaces, groups, and per-report permissions.
Does Tau replace the Acumatica Report Designer?
For paginated reports built from queries, yes: bands, groups, running totals, subreports, and page numbers, designed in the browser. Acumatica's own document forms, such as invoices printed from within a screen, stay where they are.
See it on your Acumatica data.
Tell us how you run Acumatica and the one report you wish you had. We will build it with you, live, and tell you plainly how Tau would connect.