Refused invoices in Odoo
You invoice from Odoo and a customer refuses an invoice. RIGA connects to your Odoo and opens the case where the two of you settle the disagreement.
Request a demoUnder French e-invoicing, your customer’s refusal reaches your Odoo with a code and a reason. Odoo then lets you issue a credit note or a corrected invoice. Everything in between, documents, questions and answers, goes back to email. RIGA gives it a case.
Fictional example: a €4,800 invoice refused because the price did not match the quote, settled with a partial credit note. The panels show what you see at each stage.
From your RIGA account, enter your Odoo address and an API key created in Odoo with read access to invoicing. RIGA checks the key and shows your company.
Your customer refuses the invoice on their own platform. The “Refused” status and its reason reach your Odoo. RIGA reads them every two hours, or at once if you add one automation rule in Odoo.
RIGA opens the case with the invoice exactly as Odoo issued it, the reason for refusal and the customer’s email read from their record. Your customer receives an invitation and joins with their own access.
The RIGA mediator, a neutral assistant, asks the first question from the stated reason. Each party adds documents and answers. You propose a resolution, your customer accepts or discusses it, and each side consents in its own name.
You issue the credit note in Odoo as you always do. RIGA recognises it as the agreed outcome and closes the case. Each signatory receives the closing record and can verify their copy without a RIGA account.
RIGA changes neither the invoice nor the parties’ accounting. Resolution depends on their agreement and does not guarantee payment.
The invoice, the status, the reason and the customer come from your Odoo.
RIGA reads your Odoo and never writes to it. Credit notes and corrected invoices remain your acts, in your own tool.
At closing, each party keeps the complete case and can verify it independently.
RIGA reads your Odoo through its external API, which Odoo Online’s Standard plan does not include. You keep the key you created, with the rights you gave it, and can revoke it at any time. We are onboarding the first Odoo connections now.
Odoo 17, 18 and 19 with the France e-invoicing module. Your Odoo must be reachable at a public address: on your own server, on Odoo.sh, or on Odoo Online with the Custom plan. Odoo Online’s Standard plan does not include the external API.
No. The API key you create is read only. RIGA reads your invoices’ statuses, reasons and documents; credit notes and corrected invoices are yours to issue in Odoo.
No. Their refusal comes from their own platform and reaches your Odoo through the e-invoicing circuit. They take part in the case with a simple access, nothing to install.
Two hours at most, until the next read. With one automation rule in your Odoo, described in your RIGA account, the case opens within a minute.
Give each dispute a shared workspace for documents, questions and decisions, whether you run the business yourself or with a small team.
Let your assistant review authorised documents and prepare responses. You decide which resolution to propose to your customer.
Retain the agreed terms and their history after the dispute. Each signatory keeps a copy they can verify independently of RIGA.
The demo walks through a disputed invoice: gathering supporting documents, preparing a response with an AI assistant and recording an agreement with the customer.
Request a demoThe complete workflow, including both parties’ agreement and delivery of the closing record, was demonstrated in a development environment with test identities.