Payment requests, governed from submission to reconciled payment
One unified pipeline for customer collections and vendor/employee payments — multi-stage approval, portal submission for unlicensed staff, and automatic payment posting, all in a single Odoo app.
The problem
Odoo's accounting handles the mechanics of a payment, but there is no governed request layer in front of it. Approvals happen over email and chat, requesters have no visibility into where their request stands, and collections staff manually email invoice links one at a time with no tracking of who has been reminded or who has paid.
The solution
A single request object covers both directions with a documented multi-stage approval workflow, a portal so non-accounting staff can submit without a paid seat, and automatic payment creation and reconciliation once a request is approved — backed by a triage dashboard and scheduled reminders.
Everything a governed request needs
Every capability below is implemented in the module.
Unified Two-Way Requests
One payment.request model handles both inbound customer-collection requests and outbound vendor or employee payment requests, tracked in a single pipeline instead of two separate apps.
Multi-Stage Approval Workflow
Requests move through Draft, Submitted, Manager Approved, Approved, In Payment, and Paid, with a documented reject-to-draft path so a rejected request can be corrected and resubmitted instead of restarted.
Portal Submission, No Seat Required
Managers, project leads, and field staff submit new requests and track their status from the customer portal, with no accounting license required to raise or follow a request.
Automatic Payment Posting
Once fully approved, the request creates and reconciles the account.payment automatically against its linked invoice or bill, after the account and journal have been captured up front.
Invoice-Integrated Requests
A Request Payment button and a live Payment Requests smart button on the customer invoice link every request straight back to the document it belongs to.
Kanban Triage Dashboard
Requests are grouped by stage on a kanban board with an overdue/stuck badge and requester avatar, so accountants see exactly what needs attention first.
One-Click Bulk Approval
Approve a whole batch of pending requests in a single action straight from the list view's Actions menu, instead of opening each one individually.
Automated Reminders
A scheduled cron sends configurable email reminders on unpaid or stuck requests using editable mail templates, so nobody has to chase a payment by hand.
Pivot & Graph Reporting
Built-in pivot and graph views break down request volume, aging, and status so finance can report on collection and payment effectiveness without exporting data.
How it works
Submit
A requester creates a request, with or without a linked invoice or bill, adds lines, and submits it for approval from the backend or the portal.
Approve
Manager and accounts review the request, approving each stage or rejecting it back to draft with a documented reason.
Post & Pay
Once approved, the app creates the payment and reconciles it automatically against the linked invoice or bill.
Track
Requesters and finance follow the exact stage on the kanban dashboard, portal status page, or a scheduled reminder, right through to Paid.
Frequently asked
No sales fog. If your question isn't here, email us and we'll answer it the same way.
Yes. A single payment.request model covers both inbound customer-collection requests, linked to invoices, and outbound vendor bill or employee reimbursement requests, so finance manages everything from one pipeline.
Buy it on the Odoo App Store
Purchase, download and install directly from the official Odoo Apps Store — you'll always get the latest supported build.
Payment Requests
Inbound and outbound payment requests in one multi-stage approval workflow — submitted from the portal without a seat, triaged on a kanban, approved in bulk and closed out by automatic payment posting.
Buy on Odoo App Store