Native reports

Build a valid QuickBooks native report call before you touch SQL.

Pick a QuickBooks Desktop native report, choose the allowed date mode, select supported enum values, and generate the final CALL qb_report(...) statement and MCP payload. The builder enforces the same report families, date modes, and required filters that Syntra uses in-app for ODBC, PostgreSQL, Power BI, Python, and MCP workflows.

The builder guarantees a valid query shape for the selected report and options. It cannot verify company-specific names like account full names unless you run the final query against your own QuickBooks file.

SQL report docs

See every native report call format, human vs raw output, and options_json examples.

Query Explorer

Run generated QuickBooks report SQL inside the built-in Explorer and inspect the result shape instantly.

MCP workflows

Turn the same report selection into an MCP payload for Claude, Cursor, or your own agent workflow.
human output

Date inputs

Common options

Modified date filter
List filters

account_filter

entity_filter

item_filter

class_filter

Summary layout

Detail layout

Generated output

The builder emits the generic native report call because it covers the full QuickBooks report catalog. Use the generated SQL directly in Query Explorer, ODBC, Power BI, Python, or any SQL client.

SQL call

 
 
 
 
options_json
  
 
 
 
 
 
MCP payload
  
 
 
 
 
What stays manual
 
     
  • Comma-separated full_names and include_column_list values still come from your company file or report preference.
    •  
  • The builder prevents known bad shapes such as missing required dates or a MissingChecks call without an account selection.
    •  
  • Company-specific availability such as sales tax setup or site-based inventory still depends on the QuickBooks file you run the final query against.
    •