Sage Intacct reporting for the numbers the financial report writer does not cover.
Intacct's Financial Report Writer is excellent at statements by dimension. Tau is for everything around them: open orders, AR by customer with a printed statement, project profitability by month, and the pack that goes out by email on a schedule.
Where Sage Intacct reporting gets awkward.
The Financial Report Writer does its job well: income statements and balance sheets sliced by entity, department, location, and any dimension you have set up. The trouble starts one step outside the general ledger.
Operational questions go to the Interactive Custom Report Writer and Interactive Visual Explorer, which are add-on modules with their own learning curve, a fixed set of joins between objects, and output that is a grid or a chart rather than a document. A customer statement, a printed open-order report grouped by rep, or a project pack per manager is a formatting exercise every time.
So the pattern repeats: export to Excel, rebuild the layout, email it by hand. Multi-entity companies do it once per entity. And any report that needs Intacct data next to a CRM, a warehouse system, or an e-commerce platform is out of reach of the built-in tools altogether.
What Tau reads from Sage Intacct, honestly.
Tau does not have a native Sage Intacct connector today. Tau reports over a replica of your Intacct data: the SQL Server, PostgreSQL, or MySQL database that your integration or ELT tool keeps in sync, a data warehouse export, or an OData feed if your integration exposes one. If you already sync Intacct to a database for Power BI or a planning tool, Tau can start on that tomorrow with a read-only login.
A direct Sage Intacct connector, reading through the Intacct Web Services API, is on the roadmap. We would rather tell you that plainly than have you find out during a trial.
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 Sage Intacct 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 Sage Intacct.
AR aging with statements
Aged balances by customer and entity on a dashboard, plus a paginated statement per customer, bursted by email on a schedule.
See this report type in the demo →Project profitability matrix
Projects down the side, months across the top, revenue, cost, and margin per cell, with totals per department and a drill to the transactions.
See this report type in the demo →Open order lines by warehouse
Order entry lines not yet fulfilled, grouped by warehouse and ship date, delivered as Excel to operations every morning.
See this report type in the demo →Month-end pack per entity
A paginated pack with a cover page, summary, and detail sections, one PDF per entity, with page N of M and consistent headers.
See this report type in the demo →Tau and Sage Intacct: the questions we get asked.
Does Tau replace the Financial Report Writer?
No. Keep it for the statements it does well. Tau covers operational reporting, printed documents, matrices, scheduled delivery, and reports that combine Intacct with other systems.
How does Tau get to Intacct data?
Through a replica in SQL Server, PostgreSQL, or MySQL, a warehouse export, or an OData feed maintained by your integration tool. A direct connector is on the roadmap, not shipping today.
Can Tau handle multiple entities?
Yes. Entity is just a column in the replica, so a report can filter to one entity, group by entity, or burst one PDF per entity to different recipients.
See it on your Sage Intacct data.
Tell us how you run Sage Intacct and the one report you wish you had. We will build it with you, live, and tell you plainly how Tau would connect.