How Panel Cards Work
Panel cards organize information into visually distinct sections within a customized application layout. Designers determine which data appears, how fields are labeled, and whether supported controls let users navigate to related records or initiate an action. The values may come from the current record, a configured data view, or another supported source available to the screen.
The relationship between the card and its data source is essential. A card showing an invoice balance should display the balance associated with the selected invoice, not a value left over from another record. Depending on the design, events and data bindings can refresh displayed information when users select a different record or update the underlying transaction.
Panel cards should be designed around the task they support. A summary card can emphasize a few decision-making fields, while a detail-oriented card can group related information that users need to review together. Available card layouts and interaction options should be confirmed in the target Epicor Application Studio environment.
Common Uses in Finance and Operations
Panel cards are especially useful when users repeatedly scan the same categories of information to make a business decision. They can provide a consistent visual structure across customized screens.
- Accounts payable: Summarize invoice amount, supplier, due date, purchase order reference, and approval status.
- Accounts receivable: Display customer balance, overdue amount, payment status, and collection follow-up details.
- Purchasing: Group order value, supplier information, receipt status, and approval progress for buyers.
- Financial reporting: Highlight period totals, account balances, or reconciliation status that reviewers need to examine.
- Credit management: Present customer exposure, overdue invoices, credit status, and information relevant to a release decision.
For example, an accounts receivable screen could display separate cards for total outstanding balance, overdue invoices, and recent receipts. A finance employee could quickly identify the account requiring attention, then inspect the relevant transactions before updating a collection record or following the organization's approval process.
Designing Useful and Reliable Panel Cards
Start by defining the decision or action that the card should support. Choose only the fields needed for that purpose, group related values together, and use consistent labels and formats. Currency values should follow the organization's financial display conventions, dates should be unambiguous, and status labels should match the underlying business process.
Data behavior deserves the same attention as visual presentation. Confirm the source of each displayed value, the conditions that refresh it, and the way the card responds when a field is blank or a transaction changes. If a card includes an action, make its purpose clear and ensure that permissions and ERP validation rules govern the operation.
Useful testing should cover different transaction types, user roles, record-selection changes, and relevant workflow states. Compare card values against the source transaction to verify that summaries remain aligned with the underlying records.
Panel Cards, ERP Integration, and Finance Workflows
Epicor ERP provides the operational records and processes that customized panel cards can help users interpret. When organizations extend epicor with integrated finance workflows, cards can present selected ERP context alongside related information from supported connected systems. For example, an accounts receivable card may summarize a customer account while a separate workflow investigates remittance details and matches receipts through cash application. Articles such as Closing Epicor Finance Gaps with Hyperbots AI Agents and How Hyperbots AI Agents 10x Deltek Costpoint Finance discuss broader approaches to extending finance processes with AI agents.
The Hyperbots Platform supports company-specific configuration of ERP integrations, workflows, roles, and general ledger structures through a no-code framework. Its Process Specific Capabilities address distinct finance processes, while Ready to Deploy Capabilities provide pre-trained agents and pre-built ERP connectors. Self Learning Capabilities support learning from human actions to refine decisions, and Human in the Loop workflows enable human review, approval, and feedback where required.
These automation capabilities serve a different purpose from a panel card: the card presents information within the interface, while connected workflow tools can help process and coordinate work across systems. Keeping these roles clear helps teams design screens that support finance decisions without treating a visual summary as a substitute for a validated transaction.
Related Finance Panels and Reconciliation
A panel card can display the status of an Approval Panel workflow or summarize whether a credit decision awaits review in a Credit Approval Panel. In each case, the displayed status should correspond to the actual approval record and current workflow state.
Finance teams can also use card summaries to support Expense Tie Outs by presenting expense totals alongside supporting records, or Data Tie Outs by comparing selected values from connected sources. These summaries help reviewers identify where closer examination is needed; final reconciliation should still rely on the appropriate source records and defined control procedures.
Summary
Epicor Application Studio Panel Cards organize important business information into compact, task-focused sections within customized Epicor Kinetic screens. Effective cards display accurate, relevant values, use clear labels, respond appropriately to record changes, and respect permissions and transaction rules. For finance teams, they can improve visibility into invoice processing, customer balances, purchasing activity, approvals, and reconciliation status while supporting more informed operational decisions.