| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Discuss (mail)
• Invoicing (account) |
| Community Apps Dependencies | Show |
| Lines of code | 2977 |
| Technical Name |
l10n_ge_rs_waybill |
| License | OPL-1 |
| Website | https://gencbaris.com/odoo_plugins/ |
| Versions | 18.0 19.0 |
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Discuss (mail)
• Invoicing (account) |
| Community Apps Dependencies | Show |
| Lines of code | 2977 |
| Technical Name |
l10n_ge_rs_waybill |
| License | OPL-1 |
| Website | https://gencbaris.com/odoo_plugins/ |
| Versions | 18.0 19.0 |
Georgia RS.ge Waybill + e-Invoice
Revenue Service of Georgia electronic waybills for Odoo — save, activate & close with the waybill number & QR on every document
Connect Odoo to the Revenue Service of Georgia (RS.ge) mandatory electronic waybill system. Customer invoices and credit notes are turned into RS.ge waybills, saved as drafts, activated before the goods move and closed on delivery — with the returned waybill id, number and verification QR code stored on the move.
Full waybill lifecycle
Save (draft), activate (begin transport), close (delivery) and cancel over the documented RS.ge waybill service, plus counterparty-name and unit lookups. Test and production endpoints are editable; requests retry with exponential backoff and every call is logged.
Waybill number + QR
The waybill id, number and status are captured after RS.ge registers the document. An RS.ge public verification QR is generated and rendered to a PNG for the printed waybill.
Georgian VAT & goods list
VAT-type bucketing for the 18% standard rate, 0% zero-rated and exempt supplies. Each goods line carries quantity, unit code, unit price, bar code and VAT, with return-waybill referencing of the original waybill.
Real identifier validation
A genuine RS.ge identification-number validator (9-digit legal entity, 11-digit individual) on company and partner, with taxpayer-class detection and a business-rule check layered on an EN 16931-style core (seller/buyer identifier, VAT types, GEL currency, transport).
Bring-your-own-key credentials
Your RS.ge service user name and password are stored only on your own database and are transmitted solely to the RS.ge endpoint you configure. Nothing is bundled with the module and no data is sent anywhere else. A guided onboarding wizard, a connection model and an optional batch-submission cron complete the setup.
Compatible with Odoo 18 & 19
Built on the shared e-Invoice Core Engine (canonical JSON builder, validation framework, BYOK REST transport and the e-Invoicing document model). This connector adds only the Georgia-specific profile and generator hook — no engine functionality is duplicated.
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