Mobile Money Invoicing (Request-to-Pay + Reconcile)
by AminiTech Solutions https://aminitechsolutions.com$ 26.99
Mobile Money Invoicing
Collect the invoice from the invoice. Hit Pay with Mobile Money on any posted customer invoice and a request-to-pay lands on the customer's phone. They approve with their PIN — the payment is created, posted and reconciled for you. No copying receipt codes into a payment form.
Button on the posted invoice — pick the rail, confirm the phone, send. The amount defaults to what is still owed.
The engine re-queries every pending request once a minute until it resolves. Callbacks are never trusted on their own.
MTN MoMo, Airtel Money, M-Pesa — the same button, the same ledger. Buy the rail once and this app speaks it.
Real screens from a real Odoo Accounting
Every screenshot below is a working Odoo 18 invoice collecting genuine mobile money. No mockups, no renders.
Collect an invoice from the invoice form
A green Pay with Mobile Money button sits in the header of every posted customer invoice that is not yet fully paid. It opens this wizard with the amount already filled from the balance still due and the customer’s phone pulled off their contact record. Type nothing, hit Send Payment Prompt, and a request-to-pay lands on the payer’s handset.
Pick the rail in the same dropdown
The wizard collects through whichever Mobile Money providers you have set up — MTN MoMo, Airtel Money, M-Pesa. Choose the provider and the Rail field tells you exactly which network the prompt goes out on. Your billing team learns one button, not one screen per network.
Every collection, every rail, one list
Invoice collections land in the shared Mobile Money ledger with the invoice number carried as the reference — see INV/2026/0031–0033 here, Airtel and MTN sitting in the same list. Rail, phone, amount, receipt and state in one place. A stat button on the invoice opens this list filtered to that invoice alone.
Confirm a receipt — but only a real one
When a customer pays out of band, Confirm Mobile Money Receipt takes the code they read you. We only accept it if a genuinely successful, unclaimed inflow matching that code and amount exists in this ledger — a guessed code is rejected outright. An atomic single-use claim means one receipt can never settle two documents.
The provider your invoices collect through
This is the provider record the invoice wizard sends through — this screen ships in the Mobile Money Base engine, not in this app. Set the rail, sandbox or live, shortcode and keys once. Secrets stay manager-only, and every invoice collection reuses that same configuration.
Live on today's invoices, not next quarter
Install Mobile Money Base plus at least one paid rail app (MTN MoMo or Airtel Money), then this app. Open the provider record, pick the rail, choose Sandbox or Live, and paste your shortcode and keys.
Open any posted customer invoice and hit Pay with Mobile Money → the prompt goes to the payer’s phone. The instant the rail confirms, a customer payment is created, posted and reconciled against that invoice — no one touches Register Payment.
We don’t just sell the app — we get you live on mobile money.
Buying Mobile Money Invoicing includes hands-on implementation by our engineers: installed on your Odoo, connected to your mobile-money account, configured for your business, and proven with a real payment before we hand it over. No hourly fees, no “figure it out yourself.”
We install it on your Odoo and set it up for your business — nothing for you to work out.
We help you get your MTN, Airtel or Safaricom credentials and switch you from sandbox to live.
We run a real mobile-money payment with you, end to end, so you watch it work before launch.
A short session so your cashiers and admins know exactly what to do.
Real people on call for 90 days after you go live — included.
The complete Mobile Money family for Odoo
Every app below shares one engine, one configuration and one set of security roles. Pick the rails your customers use and the channels you sell through — enter your credentials once. All of them are covered by one documentation portal.
Other Odoo services we offer
Common questions
What else do I have to buy to actually collect money?
I already own a rail app for POS or my website. Do I buy it again?
What happens if the customer never approves the prompt?
Can a fake callback mark my invoice as paid?
Someone could type a receipt code they made up. Doesn't that just confirm the invoice?
Which invoices does the button appear on?
Do I need a mobile money account before I install?
Talk to us today
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Invoicing (account)
• Discuss (mail) |
| Community Apps Dependencies | Show |
| Lines of code | 1105 |
| Technical Name |
aminitech_momo_invoice |
| License | OPL-1 |
| Website | https://aminitechsolutions.com |
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