BIR noticeCAS and CBA users register their 2026 computerised books online through ORUS by 30 January 2027 (calendar-year taxpayers).Computerised books: register in ORUS by 30 Jan 2027.

CAS set-up in Odoo
TechNext

Odoo Ready PartnerPartner in Singapore · teams in Taguig City & Ho Chi Minh City

Your Odoo team after go-live.

You don't need to hire your own Odoo team. We stay on for fixes, month-end help, upgrades (such as moving to Odoo 20) and the small changes a growing business keeps needing, with the people who configured your system.

  1. 1Discovery
  2. 2Training
  3. 3Integration
  4. 4Support
Support deskSample data

Example plan · one tracked channel

Dedicated support on your teamThe people who configured your system

  • ALConsultant
  • RIDeveloper
  • KELead
  • T-1042 UrgentBank feed stopped syncingIn progress00:41:20
  • T-1043 HighMonth-end close: check 2307 and SLSP before filingTriage02:10:05
  • T-1040 NormalAdd a PO approval stepWaiting on youPaused
  • T-1039 NormalUpgrade to Odoo 20 on a staging copyTesting on staging12:30:00
  • T-1038 LowHow do I split a delivery?ClosedTarget met
Open tickets
4
Closed this month
27
Escalated to lead
1
  1. T-1038 closed after your test
  2. T-1043 picked up by your consultant
  3. T-1039 staging copy ready for your test

Example plan and sample tickets. Your response targets are agreed in your support plan.

At a glance

Phase
Step 4 of 4
Covers
Fixes · month-end · upgrades · changes
Response
Targets agreed in your plan
Channel
Single tracked channel, named team
Team
Singapore HQ · Philippines · Vietnam

In one paragraph

Odoo support from TechNext continues after go-live with the same people who configured your system: fixes, month-end help, version upgrades and the small changes a growing business keeps needing. Requests run through one tracked channel, with response targets agreed in your support plan.

Every Odoo support ticket, tracked from new to closed.

Bugs, how-to questions, change requests and upgrade tasks each take their own path through TechNext's support desk: triage, a fix on a staging copy, your test, then a batched release to production on Odoo.sh or your own hosting. Timers run against an example plan's response targets and pause while a ticket waits on you. Filter by priority, or report an urgent issue and watch it jump the queue.

Support deskExample plan · sample tickets · business hours

Tue 10:00simulated business hours

    Release train fixes are batched: staging first, then production

    Fix readyDevelopment branch
    StagingStaging branch, a copy of your database
    ProductionMerged to the production branch

    Response targets example plan

    PriorityRespondResolveOpenAt risk

    The clock pauses while a ticket waits on you or is being tested by you. At 75% of a target the ticket escalates to the lead consultant.

    Monthly report sample

    • Bug
    • How-to
    • Change
    • Upgrade

    Desk log

      States: new, triage, in progress, waiting on you, testing on staging, deployed, closed.

      Paths: a bug is reproduced and fixed on staging, tested by you, then released to production; a how-to is answered and confirmed; a change request is sized and approved before it is built; an upgrade task is migrated and tested on a staging copy, then released on a date you choose.

      Timers: each priority has a response and a resolution target in the support plan. The clock pauses while a ticket waits on you, and a ticket close to its target escalates to the lead consultant. Fixes are batched into deploys: staging first, then production, on Odoo.sh or your own hosting. A monthly summary shows what was closed and what is pending.

      Example plan and sample tickets. The targets shown are for illustration, not TechNext commitments: your response targets are agreed in your support plan.

      The help a live system needs.

      Six kinds of request, and how each one is handled.

      RequestWhat we doHow it is handled
      Fixes

      Something doesn't post, a report is wrong, a user is stuck: a named channel and a response target agreed in your plan.

      In your plan
      Month-end help

      Reconciliations, tax returns and closing entries, worked alongside your finance team for the first cycles until it is routine.

      Closing cycles
      Version upgrades

      Odoo releases new major versions on a regular cadence. We test, migrate your customisations and upgrade on a schedule you choose.

      On your schedule
      Small changes

      A new report, an extra field, an approval step, another warehouse: handled within the plan, not treated as a fresh project.

      Within the plan
      New requests

      Larger additions, such as a new app or a new integration, scoped and quoted first, then built when you are ready.

      Scoped and quoted
      Health checks

      Periodic review of performance, access rights and housekeeping, so problems are caught before users feel them.

      Periodic review

      In the Philippines, month-end help includes the BIR side.

      We work alongside your finance team through the close and the BIR filing cycle: reconciliations, the reports Odoo produces for the BIR (2307, SLSP, SAWT, QAP and 2550Q) and the checks before you file, until it is routine.

      Month-end support before you file Philippines

      • Month-end closeReconciliations, tax returns and closing entries, worked with your finance team.
      • BIR filing cycle2307 certificates, SLSP, SAWT and QAP files and the 2550Q checked against your Odoo books before you file.
      • Same teamThe people who configured your system answer the ticket, in one tracked channel.

      One channel, tracked, reviewed.

      1. 1Setup review

        Confirm the apps, users and customisations we support, and agree your response targets.

      2. 2Single channel

        One place to raise requests, each tracked as a ticket from open to done.

      3. 3Triage and fix

        We reproduce on a staging database, fix, and release once you have checked it.

      4. 4Review and plan

        A regular summary of what was done and what's pending, including the upgrade path.

      A plan sized to your team.

      Plans are based on the number of users and apps in use. Effort rolls into fixes, changes and upgrade work; anything larger gets its own scope and quotation first.

      Channel
      One tracked channel
      Crew
      The people who configured your system
      Targets
      Agreed in your plan
      Based in
      Singapore HQ · Taguig City · Ho Chi Minh City
      Support plan checklist12 / 12
      • A named team who already know your setup
      • A single channel with tracked tickets
      • Response targets agreed in your plan
      • Bug fixes and issue investigation
      • Month-end and closing support
      • Version upgrade testing and migration
      • Small changes handled within the plan
      • New requests scoped and quoted before build
      • A staging database for testing before go-live
      • A regular summary of work done and pending
      • Support for systems we didn't implement, after a review
      • Resize or cancel with agreed notice

      You don't need to hire your own team.

      TechNext Care is support that goes past Odoo: your website and improvements from the same team, every month. Three levels, sized to your users and apps, each one including the one before.

      Essentials

      Odoo fixes, month-end help and tested version upgrades, plus website updates and small edits.

      Everything in Essentials, plus

      Growth

      New reports, automations, website pages, SEO checks and an AI chatbot on your site or WhatsApp.

      Everything in Growth, plus

      Full team

      A quarterly roadmap review with your adviser.

      Support, answered.

      Do you support Odoo you didn't build?

      Yes. A short review of the current setup comes first, so we know what we are taking on before we commit to a plan.

      What are your response times?

      Response targets are agreed in your plan and tracked against every ticket. We keep them realistic to your setup rather than quoting a headline number that doesn't fit.

      How do we raise requests?

      Through a single channel, where each request becomes a tracked ticket from open to done, so nothing gets lost in an inbox.

      Will an upgrade break our customisations?

      We test on a staging database, migrate your customisations and upgrade on a schedule you choose, never a forced cut-over.

      Where is the support team based?

      Support is led from our Singapore HQ, with consultants and developers at our main development and consulting hub in Taguig City, and AI engineers in Ho Chi Minh City for AI features. We serve clients globally.

      What is TechNext Care?

      Our monthly plan after go-live, in three levels. Essentials covers Odoo support, upgrades and website updates; Growth adds improvements, new pages and an AI chatbot; Full team adds a quarterly roadmap review. It means you don't need to hire your own team for any of it.

      Keep the system healthy after go-live.

      Already on Odoo, or about to be? Tell us the apps and team size and we will size a support plan.

      Set up meeting Ask Nexi
      Services catalogue