How a Business Activity Query Works
A BAQ defines which data to retrieve, how records relate to each other, and what conditions the results must satisfy. In Epicor's BAQ Designer, users select source tables, establish joins, choose output fields, and apply criteria. The query then returns records matching those definitions when executed.
Its main components include:
- Source tables: Store the business records, such as customers, invoices, purchase orders, suppliers, or inventory transactions.
- Table relationships: Connect related records through joins, allowing information from multiple areas to appear together.
- Selected fields: Define the columns shown in the result, such as invoice date, supplier name, order value, or payment status.
- Criteria and filters: Restrict results to a relevant company, date range, transaction status, or other business condition.
- Calculated fields and grouping: Derive values or summarize records when the required analysis calls for totals, counts, or comparisons.
These elements help users shape query results around a defined business need instead of exporting broad datasets and manually rebuilding the same view.
How to Create and Validate a BAQ
Start by identifying the question the query must answer. For example, to monitor overdue receivables, define whether the output should show individual invoices, customer-level balances, or totals by aging category. That decision determines the tables, fields, filters, and grouping needed.
In BAQ Designer, create a new query or open an existing one, add the relevant tables, establish their relationships, and select the required display fields. Apply criteria such as open status or a specified reporting period. If the output needs a derived value, add a calculated field using supported expressions and suitable data types.
Run the query with representative records and compare its output with trusted Epicor screens or reports. Check that joins do not duplicate records, filters include the intended transactions, and totals agree with the underlying data. Document the purpose of the BAQ and the meaning of important filters so future users can interpret the results consistently.
A query used for tax reporting, for instance, should reflect the appropriate transaction dates, jurisdictions, and exemption rules. A BAQ can organize relevant tax data, but tax treatment must follow the organization's applicable rules rather than assumptions built into a field name.
Practical Uses in Finance and Operations
BAQs help teams answer recurring questions using consistent ERP data. Finance teams can review open receivables, identify unpaid supplier invoices, compare actual spending with budgets, or prepare supporting detail for period-end reconciliation. Operations teams can monitor order status, inventory levels, production activity, and purchasing commitments.
For procurement, a BAQ can show each purchase order with its supplier, approval status, order date, and committed value. This supports spend visibility and helps buyers identify orders requiring follow-up. Where procurement workflows include requisition data, the query can connect the relevant records to give approvers a more complete view of the request and its downstream order.
In financial analysis, a query may organize balances used to review Business Activity Analysis, while a registration or transaction reference may help users distinguish records associated with Business Activity Registration. These concepts serve different purposes from the BAQ itself, but illustrate why clear field definitions and consistent business context matter when querying enterprise data.
Customer-facing teams can also use query results to investigate a Customer Query about an invoice, order, or account balance. A well-designed BAQ can bring together the relevant records for review, subject to the user's access permissions and the data available in the system.
BAQs, ERP Integration, and Automation
A BAQ operates within a broader ERP environment. In Epicor ERP, query results can support dashboards and reporting across the relevant business functions. When extending an ERP implementation, How ERP and Business Processes Work Together provides context for aligning system data with the activities employees perform each day.
Organizations evaluating platforms for growth may compare Best ERP for Medium-Sized Business in 2025 – Full Guide or Best ERP for Small Manufacturing Business (2025 Guide) when assessing reporting, integration, and operational requirements. The appropriate setup depends on business processes, data structure, security, and the reporting outcomes the company needs.
BAQ results may also inform workflows that optimize vendor payment timing. For example, Late Payment Recommendations describes an Agentic AI approach to aligning vendor payments with due dates and cash priorities. A Flexible Workflow can support policy-based accrual approvals, while the Hyperbots Platform supports industry-specific finance workflows and tax validation. These capabilities complement ERP data by applying defined business rules to downstream activities; the BAQ remains the query layer used to retrieve and shape records.
Best Practices for Reliable BAQ Results
Design each BAQ around a specific question, and include only fields that help answer it. Use clear aliases, consistent filter logic, and documented definitions for calculated values. When combining tables, confirm the intended relationship between records and test whether one-to-many joins affect row counts or totals.
For recurring financial reports, verify company scope, transaction status, date boundaries, and currency treatment before publishing the results. Review access permissions because query output should respect the organization's data governance requirements. If a BAQ supports a dashboard or other connected workflow, retest it when relevant table structures, business rules, or report requirements change.
Summary
A Business Activity Query is an Epicor data-query tool for retrieving and organizing business records into useful datasets. By selecting source tables, defining relationships, applying filters, and adding calculations where needed, users can create tailored views for financial reporting, procurement, customer service, and operational monitoring. Clear requirements, careful validation, and consistent documentation help ensure BAQ results support dependable business decisions.