Odoo Projects Consultant, Kenya

Billing models for Kenyan project work

In Odoo, the invoicing behavior comes from how each service product is configured. Milestone products create milestones on the project; timesheet-based products turn approved hours into invoice lines; fixed-fee products bill an agreed amount. Once contract types are defined, the setup is straightforward.

Patterns I map with Kenyan teams:

• Solar and water installations for schools, clinics, farms and businesses: deposit, equipment delivery, installation, commissioning and handover.
• ICT and network projects for banks, county offices and corporates: fixed-fee implementation with change requests billed on hours.
• Engineering and electromechanical works for factories and buildings: milestones with variations agreed in writing.
• Managed services combining a monthly fee with extra hours above scope.

Donor-funded and grant work, where time must be split across funding sources, is a different profile; my Zoho Projects Kenya page covers it. Pay-as-you-go solar businesses that collect small payments from many households usually rely on specialist platforms, with Odoo, if used, covering stock and finance. For a general tour of the product, see the Odoo Projects page.

Field service far from Nairobi

For a Kenyan installer, a job may mean a long drive, a night away and limited signal on site. Field Service, which recent versions place in Enterprise, assigns visits to technicians, shows them on a schedule and lets technicians record time, parts used and a customer signature on their phones.

Design decisions I work through:

• Trip planning. Grouping visits in the same region into one trip, so planners see which jobs can share travel.
• Travel costs. Fuel, accommodation and per diems captured as expenses linked to the project, so margin includes them.
• Parts on the job. Technicians carrying stock in a vehicle, recorded as a location, or parts issued per job from a warehouse.
• Weak signal. I test how the app behaves when sites have little or no connectivity, and agree how work reports are completed once technicians are back in range.
• Evidence for clients. Photos and signed reports attached to the task, since institutional clients may require them before paying a milestone.

Equipment serials recorded on delivery make later service and warranty claims far easier. Stock and serial design is covered on my Odoo Inventory Kenya page, and adjacent patterns on field service.

Timesheets, approvals and travel days

Hourly billing and accurate margins depend on complete, approved timesheets. Odoo records time against tasks from the browser or mobile app; in recent versions, manager approval of timesheets has been an Enterprise feature, so Community deployments need another control.

Rules I agree with project leads:

• Travel time. Whether hours spent driving to an upcountry site are billable, depending on the contract, and decided per task in advance, not by the technician on the day.
• Crew entry. A site lead entering time for a crew daily, or each person entering their own; mixing both without a rule creates duplicates.
• Approval before billing. A weekly approval so month-end invoicing does not wait on missing time.
• Casual and subcontracted labor. Casual workers hired locally for a job are often paid outside the main payroll; their cost reaches the project through expenses or vendor bills.

Finance sets the hourly cost rates used for margin. Kenya's Data Protection Act is another reason to restrict who sees timesheets and cost figures; your HR lead and legal advisor decide which roles qualify. Payroll itself, including statutory deductions, usually runs in a local payroll system rather than in Odoo.

Invoices through eTIMS, withholding and M-Pesa

Every project invoice is posted in Odoo Accounting and must pass through eTIMS. Which route applies depends on version and edition; options range from localization features in newer releases to third-party modules and middleware. Once the route is known, I test it on milestone, timesheet and recurring invoices, credit notes included. Your tax advisor confirms invoice content and treatment.

Points I check on the project side:

• Service items carrying the product data the eTIMS route requires, so milestone and service lines are not rejected.
• Client withholding. Government bodies and some large companies may withhold VAT or income tax when paying; how those deductions are booked is explained on my Odoo Accounting Kenya page.
• Deposits and how they appear on later invoices.
• Dollar-priced contracts, where finance chooses the exchange rate source.

Smaller clients may pay milestones by M-Pesa. Receipts matched to invoices in accounting let project leads see what is paid before scheduling the next phase. How receipts enter Odoo is discussed on my Odoo consultant Kenya page.

Where Odoo Projects falls short in Kenya

Odoo Projects is a sound base once the eTIMS route is proven and you want delivery and finance on one record. Look elsewhere, or budget for add-ons, if:

• Building contracts with interim certificates, retention and remeasurement are the core of the business. These usually call for construction software or heavy customization, as the construction industry page explains.
• Grant and donor accounting is the main requirement, which needs fund-based reporting beyond standard project tools.
• Pay-as-you-go collections from many households, which belong in a specialist platform.
• A Community-only plan that still depends on field visits, approved timesheets and recurring billing, all Enterprise apps in recent versions.
• No confirmed eTIMS route for your version, which leaves invoicing risk with finance.

I am an independent consultant, not an Odoo partner, and take no commissions. For system selection, start with the Kenya ERP consultant page; to see how bids and quotes feed projects, read Odoo CRM Kenya. The Kenya hub gives wider market background. Delivery is remote, and the engagement is conducted in English.