How Epicor BAQ Criteria Work
Criteria are configured in the BAQ designer and applied to selected fields from the query's data sources. A condition typically identifies a field, an operator, and a value. The operator determines how the field is compared with the selected value, while logical connectors determine how multiple conditions work together.
For example, a query may filter invoices where the invoice date falls within a reporting period and the posted status equals the required value. The date condition narrows the period under review, while the status condition determines which transactions qualify. The precise fields and available operators depend on the table, field type, and BAQ designer options.
When working with Epicor ERP, criteria can help users create repeatable views of operational and financial records. The same query structure can support recurring reports, provided users review date values and other parameters that change between reporting periods.
Common Criteria Operators and Conditions
The operator determines the comparison a BAQ performs. Choosing the appropriate operator helps align the query with the intended business rule.
- Equals: Returns records matching a specific value, such as a selected supplier ID or transaction status.
- Not equal to: Excludes records with a particular value, such as transactions already marked with a specified status.
- Greater than or less than: Filters numeric or date fields based on a threshold, such as invoice dates after the start of a period.
- Between: Selects values within a defined range, such as transaction dates for a month or amounts within an approval band.
- Contains or begins with: Searches text fields for a phrase or prefix when the selected field and operator support that comparison.
- Null or non-null checks: Identifies records where a field has no stored value or contains a value, useful for reviewing missing references.
Several conditions can be combined with AND or OR logic. AND requires all connected conditions to be satisfied, while OR allows a record to qualify when at least one of the connected conditions is satisfied. Parentheses or grouped criteria may be needed when a query combines both forms of logic.
Practical Examples for Finance and Procurement
Consider a month-end accounts payable report that should show open invoices for a selected company and accounting period. The analyst can select the relevant company, apply the required invoice status, and set a date range. This focuses the output on transactions that need review rather than the full invoice history.
Procurement teams can use criteria to identify purchase orders awaiting approval, orders above a defined value, or transactions associated with a particular supplier. A purchase order review may combine requisition details, approval status, and supplier records. For more context on evaluating procurement workflows, the Purchase Order Automation Demo & Evaluation Guide discusses success criteria and proof-of-concept scenarios for purchase order automation.
For ERP planning and configuration decisions, the Cloud ERP System Evaluation Checklist: Guide for 2026 provides a framework for comparing system capabilities and requirements. When an organization extends epicor through integrations, BAQ criteria can help control which records are included in downstream reports or supported workflows. The appropriate conditions should reflect the actual business process and data model.
Best Practices for Accurate BAQ Criteria
Start by stating the business question in precise terms. Identify the records that should qualify, the fields that express those requirements, and whether the conditions should be combined with AND or OR. Then test the query with known records before relying on the results for operational or financial decisions.
- Confirm field meaning: Check whether a date represents the transaction date, posting date, due date, or another milestone.
- Validate company context: Apply company-specific conditions when required by the database structure and reporting purpose.
- Check boundary values: Verify whether date ranges include the intended start and end dates and whether amount thresholds handle equality correctly.
- Review logical grouping: Test combined AND and OR conditions with sample records that should qualify and records that should be excluded.
- Compare results: Reconcile record counts and financial totals with a trusted Epicor screen or report.
For example, if a report must show invoices dated from April 1 through April 30, test transactions on both boundary dates. Confirm the field being filtered and how the BAQ handles date and time values so the reporting period matches the finance team's requirements.
Criteria in Integrated Finance Workflows
BAQ criteria can also define the records passed into reporting tools, dashboards, and integrated finance processes. Epicor Integration Finance describes the broader connection between ERP information and finance workflows, where consistent selection rules help teams work with relevant transaction data. The Acquisition Criteria concept, by contrast, describes requirements used to evaluate acquisition opportunities; it is a separate business use of the word criteria rather than a BAQ filtering feature.
The Hyperbots Platform supports company-specific ERP integrations, workflows, roles, and general ledger structures through configurable implementation options. Process Specific Capabilities align automation with defined finance activities, while Ready to Deploy Capabilities include pre-trained agents and ERP connectors. Self Learning Capabilities use human feedback to refine supported decisions, and Human in the Loop enables review and approval when a workflow requires oversight.
When criteria identify customer receipts that need review, finance teams may also need to match payment references and remittance details before posting cash. How Hyperbots AI Agents 10x Epicor Finance Operations explores finance automation around Epicor, including cash application and related workflows. BAQ criteria help define the relevant data population; the downstream business rules determine how those records are processed.
Summary
Epicor BAQ Criteria filter query results using field values, comparison operators, ranges, and logical conditions. They help finance, procurement, and operations teams retrieve records that match a defined reporting or review requirement. Accurate results depend on choosing the right fields, validating boundary values, combining conditions correctly, and comparing query output with trusted records. Well-designed criteria make recurring reports more focused and support consistent operational and financial decisions.