How Breaking and Routing Work Together
The process typically begins when a user or scheduled task runs a report. The report retrieves the required data and produces an output. Breaking rules determine how the output is divided, and routing rules determine how each resulting document is distributed.
Breaking may use a customer number, supplier account, company, site, or another supported field to separate records into meaningful groups. Routing then applies destination rules, such as sending a document to an authorized recipient, making it available for printing, or delivering it through a supported electronic channel.
These are separate decisions. A report can be broken into individual documents without automatically being sent to external recipients. Similarly, a routing rule can direct a complete report to one team without separating it into individual records. Administrators should verify which capabilities the specific Epicor report and delivery configuration support.
Key Components and Configuration
A practical setup starts by identifying the document, its data structure, the intended grouping field, and the destination for each output. Administrators should review the report definition and its parameters before configuring distribution behavior.
- Source report: Defines the data and layout used to generate the original output.
- Breaking criteria: Identifies the field or business rule used to separate records into individual documents or groups.
- Routing criteria: Connects each output or group to the correct recipient or delivery destination.
- Delivery format: Establishes the supported output format and distribution method.
- Access controls: Ensures that financial and customer information reaches authorized recipients.
- Validation: Confirms that the output is complete, correctly separated, and delivered as intended.
When configuring these components, use stable identifiers and confirm that the selected fields contain consistent values. A customer statement should be grouped by the appropriate customer identifier rather than a field that could combine unrelated accounts.
Practical Finance and Procurement Examples
In accounts receivable, breaking and routing can help prepare individual customer statements from a consolidated reporting run. Each statement can then be directed to the appropriate destination, supporting collection follow-ups and customer account reviews. For cash application, separate payment and remittance reports can help finance staff identify receipts, investigate unapplied cash, and review deductions. Document distribution supports these activities but does not itself match payments to invoices or post accounting entries.
In accounts payable, supplier-specific remittance documents can be separated from a payment run and delivered according to established supplier communication rules. Procurement teams may also distribute purchase order reports to buyers or managers responsible for spend oversight. A documented Purchase Order Approval Process: Policies & Routing 2025 establishes how purchasing requests move through approval roles; report routing separately ensures that supporting documents reach the people who need them.
Organizations extending epicor finance workflows should map report generation and distribution to the relevant ERP process. Resources such as How Hyperbots AI Agents 10x Epicor Finance Operations and Closing Epicor Finance Gaps with Hyperbots AI Agents discuss broader finance automation, including payment matching, remittance processing, and posting receipts.
Controls, Exceptions, and Best Practices
Breaking and routing rules should be tested with representative data before they are used for routine financial reporting. Confirm that each intended group produces the correct document, that no records are omitted or duplicated, and that the destination matches the business rule. Pay particular attention to customer contact details, supplier information, and reports containing confidential financial data.
When a document lacks a valid recipient or fails a defined business condition, a documented Exception Routing process can direct the case to the appropriate employee for review. Maintain clear ownership for updating recipient information and revisiting rules when customers, suppliers, organizational structures, or reporting requirements change.
The Hyperbots Platform supports finance automation and ERP integration, while Process Specific Capabilities address distinct finance workflows. Its Ready to Deploy Capabilities provide pre-trained agents and ERP connectors with configurable implementation options. For organizations extending their processes, Self Learning Capabilities can use human feedback to refine supported workflows, and Human in the Loop keeps people involved in exceptions and approval decisions. Company-specific workflow and integration requirements can be addressed through Company Specific Configurations.
Integration and Approval Considerations
Breaking and routing operate within a wider system of data access, integration, and business approvals. Epicor ERP provides the operational context in which reports are generated, while Epicor Integration Finance concerns the connection of finance workflows and data with the ERP environment. Clear integration ownership helps ensure that the data used for document separation is consistent with the underlying transactions.
Document delivery should also remain distinct from Approval Routing. Routing a report to a manager does not necessarily constitute approval of the transaction described in it. Where a financial document requires authorization, the relevant approval workflow must record the decision and apply the organization's control requirements separately.
Summary
Epicor Breaking and Routing combines document separation with destination-based distribution. Breaking organizes a report into useful outputs, while routing sends those outputs to the intended recipients or delivery channels. By defining grouping criteria, validating destinations, protecting sensitive information, and testing exception scenarios, organizations can improve reporting consistency and support timely financial and operational decisions.