Skip to main content

Customer/Vendor Statement

Purpose​

Customer/Vendor Statement adds a Partner Statement PDF action to contacts. Its report lists posted journal items on receivable and payable accounts for the exact selected partner and the current user's company, with debit, credit and accumulated balance columns.

The report uses the company's existing journal entries. It does not create invoices, record payments, reconcile entries or send a statement automatically.

Before you start​

Install eis_partner_statement for Odoo 18.0 with Accounting (account). The manifest declares no Enterprise-only dependency. The package uses Odoo's native PDF reporting and external layout, so the normal report-rendering setup and company branding must work.

This guide is based on source review. No PDF was generated in this review. Verify the report cutoff in your environment before relying on the output: the report also uses its displayed date in the journal-item search. This source detail does not by itself establish a generation failure.

Access and roles​

The addon creates no new role and its report action has no extra group restriction. Users still need native permission to read the contact and the accounting entries used by the report. The query runs in the user's environment; the module does not give a contact-only user accounting access.

Use an appropriately authorized accounting user. Entries are selected using the company stored on the printing user. Confirm that it is the company whose statement you intend to produce; the report does not aggregate every company available in the session.

Setup and menu​

There is no separate Statement application or configuration wizard. Open a contact and locate Partner Statement among its native print/report actions. The action is also bound to the contact model for selected records in a list.

The reviewed implementation has no date-range selector, opening-balance wizard, overdue-only filter or per-currency selector. Those options should not be inferred from the general description of the app.

Workflow​

  1. Open the exact customer or vendor contact whose entries you need. Check whether postings use this record or another commercial/contact record.
  2. Confirm the company on the printing user and that the relevant invoices, bills or payments are posted.
  3. Choose Partner Statement from the contact's report actions. For several contacts, select the intended records in the list before choosing the report.
  4. Inspect the generated document for the partner, report cutoff, currency label, reference, debit, credit and balance. The source wraps multiple selected contacts into the report output; it does not implement a separate file download per partner.
  5. Compare the totals with the relevant posted receivable/payable journal items before sharing the document through your organization's normal process.

Practice scenario​

In an authorized test database, use fictional contact “Harbor Supplies” with one posted receivable invoice and a posted payment. Print the contact's statement and compare the debit/credit totals with its ledger entries. Repeat with a contact that has no qualifying items and inspect the empty result. This is a source-derived practice case, not a successful PDF test.

Troubleshooting and limitations​

Entries are missing: the search includes only posted receivable/payable items for the exact partner, the printing user's company and report cutoff. Draft entries, other companies and child-contact entries are not automatically consolidated.

The balance sequence looks unusual: rows are newest first, and accumulation starts at zero in that display order. Intermediate balances are not a conventional oldest-first chronological running balance. The final total is the displayed debit sum minus the displayed credit sum.

Currency label or vendor wording looks wrong: debit and credit come from entries in the printing user's company. The displayed currency instead comes from the contact's company when one is set, and otherwise from the user's company. Confirm that the currency label matches the company of the selected entries before sharing; the template does not convert amounts to a different label currency. Its summary wording is generic and customer-oriented, so also review vendor wording.

The cutoff is unexpected: compare the displayed report date and included journal-item dates in the target environment. Ask the administrator to inspect the report's date handling if they differ from the intended cutoff.

Only Odoo 18.0 is present and qualified in the supplied inventory. No other major version or runtime report result is established by this guide.