Partner statement - portal
Customer portal for account statements: browse and download generated statements, request new ones, view a live statement with aging summary and Excel export, and manage automatic statement schedules.
What you get
- Statement archive on the portal -
/my/statementslists the statement documents generated in the backend (with search, filters, grouping, per-partner pages and a pager); each statement has its own portal page with PDF preview and download - Self-service statement requests - on
/my/statements/newa customer picks a partner and a period (max one year) and the statement PDF is generated on the spot - Live statement page -
/my/statementshows posted receivable journal items for the customer's commercial entity across the configured statement accounts, with opt-in date range and open/overdue filters, and an optional per-partner aging-bucket summary (not due / 0-30 / 31-60 / 61-90 / 90+) - Excel export -
/my/statement/exportstreams the full statement as .xlsx without the on-screen row limit, honouring the same filters - Automatic statement rules - on
/my/statement-rulesportal users can view, create, edit and pause their own schedules (statement or open-invoices export, interval, next send date, recipient emails), backed by a portal record rule limited to their own published customer rules - Backend preview - a Customer Preview button on the statement form opens the record as the customer will see it
Configuration and use
Statement accounts come from the company's customer_statement_account_ids (from the rlbooks statement module); if none are set, all receivable accounts are used as fallback.
Two settings live in Settings under the rlbooks statements block: a checkbox that installs the companion published module (restricting the portal to explicitly published statements), and Show aging summary on /my/statement (system parameter partner_statement_portal.ws_show_aging_summary, off by default).
Portal users see the new entries on their My Account page; statement documents are the rlbooks_statement.report.print records your team generates or that customers request themselves.
Technical note
Requires the openpyxl Python package for the Excel export. Built on the rlbooks statement modules (rlbooks_statement, rlbooks_imp_portal, rlbooks_imp_purchase).
Requires the Python package(s) openpyxl on the server. On Odoo.sh, add them to your requirements.txt.
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Contacts (contacts)
• Discuss (mail) • Invoicing (account) • Inventory (stock) • Purchase (purchase) • Sales (sale_management) |
| Community Apps Dependencies | Show |
| Lines of code | 20658 |
| Technical Name |
partner_statement_portal |
| License | OPL-1 |
| Website | https://www.rlsd.dk/ |
Odoo Proprietary License v1.0 This software and associated files (the "Software") may only be used (executed, modified, executed after modifications) if you have purchased a valid license from the authors, typically via Odoo Apps, or if you have received a written agreement from the authors of the Software (see the COPYRIGHT file). You may develop Odoo modules that use the Software as a library (typically by depending on it, importing it and using its resources), but without copying any source code or material from the Software. You may distribute those modules under the license of your choice, provided that this license is compatible with the terms of the Odoo Proprietary License (For example: LGPL, MIT, or proprietary licenses similar to this one). It is forbidden to publish, distribute, sublicense, or sell copies of the Software or modified copies of the Software. The above copyright notice and this permission notice must be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Please log in to comment on this module