| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Expenses (hr_expense)
• Invoicing (account) • Employees (hr) • Discuss (mail) |
| Lines of code | 577 |
| Technical Name |
hdk_ramp_integration |
| License | OPL-1 |
| Website | https://www.hamdek.com |
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Expenses (hr_expense)
• Invoicing (account) • Employees (hr) • Discuss (mail) |
| Lines of code | 577 |
| Technical Name |
hdk_ramp_integration |
| License | OPL-1 |
| Website | https://www.hamdek.com |
Hamdek Ramp Integration
Integrate Ramp with Odoo: sync Ramp bills as vendor payments, create expenses from Ramp transactions with receipts and journal entries, and run scheduled fetches for bills and transactions.
Ramp and Odoo in Sync
This module connects Ramp to Odoo so you can fetch bills into vendor payments, turn Ramp transactions into HR expenses (with receipts and moves), and use scheduled actions to keep data up to date.
Ramp Bills → Payments
From Accounting → Payments, use Fetch Ramp Journal to pull Ramp bills and create vendor payments in Odoo (with optional auto-validate).
Transactions → Expenses
Fetched Ramp transactions create HR expenses in Odoo; receipts are attached and journal entries (and reconciliation) are created in the configured journals.
Scheduled Actions
Two crons run (e.g. monthly): one to create expenses from Ramp transactions, one to fetch Ramp bills. Configure and activate them in Settings → Automation.
Key Features
Ramp Integration Settings
Configure Client Id, Secret Key, generate token, and set expense journal, vendor payment journal, debit account, product, and date range. Under Expense → Configuration.
Receipts & Moves
Transaction receipts from Ramp are attached to the created expenses. Journal entries and bank statement lines are created in the configured journals for reconciliation.
Manual & Scheduled Fetch
Fetch from Ramp Integration Settings (full or date-range wizard) or let scheduled actions run. Ramp Transaction list under Expense → Configuration shows fetched data.
Requirements
Depends on account and hr_expense. You need valid Ramp API credentials (client id and secret) and a generated token.
How to Get Started
- Install Hamdek Ramp Integration (and ensure account and hr_expense are installed).
- Go to Expense → Configuration → Ramp Integration Settings and create a record. Enter Client Id and Secret Key, then click Generate Token.
- Set Expense Journal, Vendor Payment Journal, Debit Account, Product, Start/End Date, and default Ramp Employee. Save.
- Ensure employees and GL accounts (matching Ramp codes where needed) exist. Use Fetch Ramp Transaction or Fetch Specific Ramp Transactions to pull data, or configure the two Ramp scheduled actions in Settings → Technical → Automation.
Use Cases
Expense Management
Sync card transactions from Ramp into Odoo expenses with receipts and proper accounting moves.
Vendor Bills & Payments
Fetch Ramp bills and create vendor payments in Odoo, with optional automatic validation.
Workflow
Follow the steps below to use the module.
Ramp Integration Settings
Go to Expense → Configuration → Ramp Integration Settings. Create a record, enter Client Id and Secret Key, click Generate Token, then set journals, accounts, product, dates, and default employee.
Fetch Ramp Transactions
From Ramp Integration Settings use Fetch Ramp Transactions or Fetch Specific Ramp Transactions (wizard with date range). Transactions appear under Expense → Configuration → Ramp Transaction.
Ramp Transaction list and created expenses
Fetched transactions are processed (via cron or manually) into HR expenses. View the Ramp Transaction list and the resulting expenses and sheets in Odoo.
Scheduled actions (Ramp cron jobs)
In Settings → Technical → Automation → Scheduled Actions, search for Ramp. Configure the two actions: create expenses from Ramp transactions and fetch Ramp bills. In Accounting → Vendors → Payments, use Fetch Ramp Journal to pull bills manually.
Support & Expert Services
sales@hamdek.com
www.hamdek.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