QuickBooks reporting that is not limited to the reports Intuit ships.
QuickBooks Online lets you customise the reports it comes with. Tau lets you build the ones it does not: statements bursted per customer, a sales matrix by item and class, job profitability with a drill to the transactions, and a PDF pack on a schedule.
Where QuickBooks reporting hits the wall.
QuickBooks Online custom reports are the built-in reports with different filters, columns, and groupings. You cannot join lists the way you would in a database, cannot lay out a printed document, and cannot add a column that QuickBooks did not think of. The Custom Report Builder in the Advanced tier widens the choices but stays inside the same model.
QuickBooks Enterprise and Desktop have the Advanced Reporting module and ODBC access through a third-party driver, which gets the data out but still leaves you building the report in Excel or a separate tool.
Companies outgrow this at a predictable moment: multiple entities that need consolidating, a warehouse or e-commerce system that holds half the story, or a customer who wants a statement that looks like it came from a real company. At that point the reporting question is usually the first sign of a coming ERP migration, and a report tool that can read both the old and the new system becomes useful.
What Tau reads from QuickBooks, honestly.
Tau does not have a native QuickBooks connector today. Tau reports over a replica of your QuickBooks data: the SQL Server, PostgreSQL, or MySQL database that a sync tool keeps up to date from QuickBooks Online, an ODBC extract from QuickBooks Enterprise or Desktop, a data warehouse export, or an OData feed if your integration publishes one. Tau reads it with a read-only login and builds everything below from it.
A direct QuickBooks Online connector is on the roadmap. It is not shipping, and we will not tell you otherwise during a demo.
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 QuickBooks 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 QuickBooks.
Customer statements
One PDF per customer with invoices, payments, credits, and aged buckets, page N of M, bursted by email on the first of the month.
See this report type in the demo →Sales by item and class matrix
Items down the side, classes or months across the top, quantity and amount in each cell, with totals and a drill to the invoice lines.
See this report type in the demo →AR aging dashboard
Open balances by customer and bucket, collections trend, and a right-click from any bar to the invoices behind it.
See this report type in the demo →Job profitability
Revenue, cost, and margin by customer job, delivered as Excel with live formulas to the owner every Friday afternoon.
See this report type in the demo →Tau and QuickBooks: the questions we get asked.
Does Tau connect to QuickBooks Online directly?
Not today. Tau reads a replica kept in SQL Server, PostgreSQL, or MySQL by a sync tool, a warehouse export, or an OData feed. A direct connector is on the roadmap.
What about QuickBooks Enterprise or Desktop?
Same approach: an ODBC extract or sync into a database that Tau reads. Many Enterprise customers already have one for Excel; Tau starts from it.
Can Tau consolidate several QuickBooks companies?
Yes, as long as each company lands in the replica. Company becomes a column, so one report can filter, group, or burst per company.
See it on your QuickBooks data.
Tell us how you run QuickBooks and the one report you wish you had. We will build it with you, live, and tell you plainly how Tau would connect.