Overview
The QQube Data Warehouse for QuickBooks contains 40 data models. Each data model provides a complete set of information for a specific business area or reporting subject.
Each data model is designed to be used on its own. Combining data models should be a last resort for a custom requirement when QuickBooks does not store the needed information together in the way the report requires.
Complete subject-based data models
For example, the Job Cost Details data model brings together information from many areas of QuickBooks:
- Sales transactions.
- Cost transactions.
- Original and remaining committed costs, including purchase orders.
- Estimates.
- Receive Payments.
- Bill Payments.
- Time Tracking.
- Vehicle Mileage.
- General Ledger details.
You do not need to connect separate sales, purchasing, payroll, time, and accounting data models to create a complete job-cost report.
QQube connects the dots
Intuit does not expose QuickBooks Desktop data as a traditional set of database tables. Connectors can present the extracted information in a table-like format, but users must still determine how the transactions, lists, relationships, and accounting logic fit together.
QQube performs that work before the data reaches your reporting application.
- Related QuickBooks information is combined into subject-based data models.
- Relationships and accounting logic are already applied.
- Known QuickBooks and SDK limitations are handled where possible.
- Reporting fields are presented in a consistent format.
Select the fields you need in Excel, Power BI, Access, Crystal Reports, Tableau, or another supported application. You do not need to reverse-engineer the QuickBooks data structure.
When the same filters and reporting rules are used, QQube results are designed to match QuickBooks.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article