Finance Index

Sources and Access Trays in Accounts Payable

Operational segmentation system that routes invoices into the right processing queues and controls visibility by role and organizational boundary.

Sources and Access Trays create operational segmentation within accounts payable workflows, allowing invoices to be routed into specific processing queues based on business unit, department, entity, or operational model. This system controls which users can see and process invoices by role, ensuring that work is distributed according to organizational structure rather than flowing into one undifferentiated queue. The segmentation supports scalable AP operations while maintaining proper segregation of duties and audit readiness across multi-entity organizations.

At a Glance

Aspect Short Answer Why It Matters
Primary Function Routes invoices into role-specific processing queues by tray assignment Reduces manual sorting and ensures proper work ownership
Intake Integration Supports tray-specific email addresses and automated file-based routing Invoices land in correct queues from the start
Permission Model Role-scoped visibility controls what users can see and process Maintains segregation of duties across entities
Workflow Impact Approval routing and reporting can vary by tray assignment Supports different governance models per business unit
Scalability Accommodates organizational changes without separate AP systems Grows with business complexity while preserving control

What Sources and Access Trays Cover

Sources and Access Trays establish the operational framework for invoice processing by creating named segments that correspond to how the business is organized. Each tray acts as a processing lane where invoices can be assigned, users can be granted access, and workflow rules can be applied. This segmentation extends across the entire procure-to-pay lifecycle, from initial invoice intake through final payment processing.

The system addresses the challenge faced by multi-entity organizations where invoices arrive through various channels but need to be processed by specific teams with appropriate visibility controls. Rather than forcing all work through a single global queue, trays create structured pathways that mirror real organizational boundaries while maintaining unified AP operations.

Tray Creation and Management

Tray creation establishes the organizational structure that will govern invoice processing. Administrators define tray names that correspond to business units, departments, entities, or operational segments. Each tray becomes a processing lane with its own access controls and workflow behaviors.

The system validates tray names to ensure consistency and prevents conflicts with reserved system values. When the first tray is created, the system automatically includes a special "N/A" option for invoices that should remain unassigned to any specific tray. Tray removal requires that no users are currently assigned to that tray, ensuring operational continuity.

Intake-Level Routing

Invoice routing begins at the point of entry through tray-specific email addresses and automated file processing. Each configured tray receives a unique email address that automatically assigns incoming invoices to the correct processing queue. This eliminates manual sorting and ensures invoices reach the appropriate team from the moment they enter the system.

For organizations using file-based intake, the system supports folder-based routing where invoice files placed in specifically named directories are automatically assigned to the corresponding tray. CSV batch uploads can include tray assignments in the data file, allowing high-volume processing with proper segmentation maintained throughout.

Role-Based Access Control

Access control operates through role-specific tray assignments that determine which invoices each user can see and process. The system distinguishes between different AP roles, applying separate tray restrictions for coders, processors, and payment handlers. This granular control ensures that users see only the work they are responsible for while maintaining the flexibility to assign different tray access across roles.

The "For My Attention" view intentionally bypasses tray restrictions to ensure users can always access tasks assigned directly to them, preventing workflow interruptions while maintaining overall segmentation. Payment approvers and users with full visibility roles can access broader data sets when their responsibilities require organization-wide oversight.

Processing Queue Segmentation

Daily invoice processing operates within tray-defined boundaries through automatic filtering on all major workflow tabs. The New Invoices tab shows only invoices in trays assigned to the user's coding role, while approval and payment processing tabs filter based on the corresponding role assignments. This ensures that each user's work queue contains only relevant invoices without manual filtering.

Search functionality respects the same tray boundaries, preventing users from finding invoices outside their assigned scope. Report generation applies identical filtering, ensuring that operational reporting reflects only the data users are authorized to see. Manual tray filters allow users to narrow their view further when focusing on specific segments within their assigned scope.

Approval Workflow Integration

Approval routing can incorporate tray assignments as workflow conditions, allowing different organizational segments to follow appropriate approval chains. Workflow rules can specify that invoices in certain trays route to designated approvers, supporting varied governance models across business units without requiring separate approval systems.

The system evaluates tray-based conditions alongside other workflow criteria such as amount thresholds and vendor relationships. This enables sophisticated routing logic where approval requirements can vary based on both the invoice characteristics and the organizational segment it represents.

Analytics and Reporting Segmentation

Analytics dashboards treat tray segmentation through a two-tier approach that balances organizational oversight with operational boundaries. Summary widgets and aggregated views display organization-wide data unless manually filtered, supporting executive visibility across all segments. Detailed drill-down views automatically apply tray restrictions based on user permissions, ensuring that individual invoice data respects operational boundaries.

Tray-specific widgets provide breakdowns that help managers understand workload distribution and performance across organizational segments. The manual tray filter allows users to focus analytics on their areas of responsibility while preserving the ability to see broader organizational patterns when appropriate.

Automated Assignment Systems

File-based intake systems support automated tray assignment through structured folder naming and CSV data mapping. Virtual drive uploads can encode tray information in folder names or data files, ensuring that high-volume automated processing maintains proper segmentation without manual intervention.

The system automatically creates new trays when referenced in automated uploads, supporting dynamic organizational structures while requiring administrative oversight to prevent unintended tray proliferation. Value lookup tables can translate external system codes into appropriate tray assignments, maintaining consistency across different source systems.

Common Misconceptions

Trays are not just financial reporting dimensions

Trays create operational workspaces that affect daily processing, not just reporting categories. They determine which invoices users can see, how approval routing behaves, and where work appears in processing queues.

Approval visibility is not restricted by tray assignments

Approvers can act on any invoice assigned to them regardless of tray. Tray restrictions primarily govern processors and coders, while approvers maintain the flexibility to handle assignments across organizational boundaries.

Analytics widgets do not automatically filter by user tray assignments

Summary charts and aggregated views show organization-wide data unless manually filtered. Only detailed drill-downs automatically apply tray restrictions, requiring users to apply tray filters when they want scoped summary views.

Tray removal does not reassign existing invoices

When a tray is deleted, invoices previously assigned to that tray retain their assignment. Users with appropriate permissions can still access these invoices, but new assignments to the removed tray are not possible.

Where This Fits in the P2P Workflow

Sources and Access Trays operate as the foundational organizational layer that affects every subsequent step in the procure-to-pay workflow. Invoice intake systems route documents into appropriate trays based on source channels, ensuring proper segmentation from the moment invoices enter the system. This early routing decision determines which users will see and process each invoice throughout its lifecycle.

The tray assignment influences approval routing, where workflow rules can direct invoices through different approval chains based on organizational segment. Payment processing respects the same boundaries, ensuring that payment handlers see only invoices within their assigned scope. Analytics and reporting maintain these operational boundaries while providing appropriate visibility for oversight roles.

Frequently Asked Questions

The user's role-specific tray assignments control queue visibility. Coders see invoices in their assigned trays on the New Invoices tab, while processors see invoices in their processor tray assignments on approval and payment tabs. Users with no tray restrictions see all invoices for their role.

Invoices can be assigned to trays through tray-specific email addresses, automated file processing with folder-based routing, CSV batch uploads with tray data, or manual assignment during processing. The system automatically creates new trays if referenced values do not exist.

Yes, approval workflows can include tray as a condition alongside other criteria like amount and vendor. This allows different organizational segments to follow appropriate approval chains while maintaining unified workflow management.

Summary widgets and charts show organization-wide data unless manually filtered using the tray filter. Only detailed drill-downs automatically apply tray restrictions based on user permissions, requiring manual filtering for scoped summary views.

If the user has permission to assign to the new tray, the system updates the assignment and may remove them as the current owner if they cannot access the new tray. The invoice then becomes available to users with access to the destination tray.

Yes, tray assignments are role-specific. A user who is both a coder and processor can have different tray assignments for each role, seeing different invoice sets depending on which processing tab they are using.

Search results and reports automatically filter to show only invoices in trays the user can access for their role. Manual tray filters allow further narrowing within the permitted scope, and exports respect the same restrictions.

Payment approvers and users with full visibility roles can access payments across all trays on certain processing tabs, bypassing normal tray restrictions to support organization-wide payment oversight responsibilities.