Managing ready-for-payment priorities
How payment officers see urgent, medium, low, and unset queues after approvals are complete.
Ready for payment has hard prerequisites
Backend queries for payment-ready documents require the business match, `is_ready_payment = true`, both approval levels completed, and no rejection markers.
Priority is a dedicated operational queue
The product exposes four payment priority routes: urgent, medium, low, and unset. The dashboard cards summarize each queue separately so payment teams can work by urgency rather than by document family alone.
This stage belongs after document correction, not before
Because the payment-ready queue only includes fully approved items, any knowledge article should point users back to detail correction or approval resolution when a record is missing from payment lists.
Continue with adjacent workflows
Approval levels and rejection logic
The real two-step approval model in Datamonster, including role separation, counts, pending queues, and reject officer visibility.
Reviewing document detail and line items
How detail view is structured, which accounting and payment fields matter, and how operators correct OCR output.
Dashboard views by role
What each role sees on the main dashboard and why the dashboard is really a routing layer into operational queues.