Sales
S00128Lim & Co · confirmed
Open quotations14
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
Partner in Singapore · teams in Taguig City & Ho Chi Minh City
We implement Odoo 20 around how your company runs: Accounting, Sales and Inventory first, your data migrated, each team trained, and dedicated support on your team after go-live. You don't need to hire your own ERP team.
One Odoo databaseyour-company (sample)
Sample dataS00128Lim & Co · confirmed
Open quotations14
WH/OUT/0042Reserved · ready to ship
Products below reorder3
INV/2026/0107Posted · VAT 12% · 2307 on payment
LedgerDr = Cr
BIR reports (sample)
Discovery, configuration on a staging copy of your database, data migration, training, integrations and support after go-live. Most companies start with Accounting, Sales and Inventory, then add apps on the same database. Scope is written down in a quotation after discovery.
Order to cash, procure to pay, plan to produce, record to report and hire to reimburse all run on the same customers, vendors, products, employees and chart of accounts. Every step posts to one ledger that always balances. Pick a process, run all five, or hover a master record to see every document that uses it.
One set of master records
P&L
GST
Cash
Order to cash: quotation, sales order, delivery, invoice, payment matched from the bank feed.
Procure to pay: reorder rule, request for quotation, purchase order, receipt, vendor bill with a 3-way match, batch payment.
Plan to produce: manufacturing order from the bill of materials, work order, quality check, finished goods valued in stock.
Record to report: bank statement lines, reconciliation, accruals, the GST report and the P&L.
Hire to reimburse: employee record, time off, expense claim, reimbursement.
Sample data. The postings are illustrative: your chart of accounts, taxes and stock valuation are set up in discovery.
A full implementation is more than switching apps on. It is the configuration, the data, the custom pieces, the training and the support that come after, delivered as one project.
Chart of accounts, taxes, warehouses, pricelists, approval rules and document templates, set once, in Odoo's standard features wherever possible.
Customers, vendors, products, opening balances and open items imported and reconciled against your current books before cut-over.
When a standard feature can't match a real requirement, we build a focused module on Odoo.sh instead of bending your process to the software.
Bank feeds, payment gateways, e-commerce and existing systems connected through standard connectors or the Odoo API.
Role-based sessions for finance, sales and warehouse teams, on your own data, with written steps they keep.
A controlled cut-over, the first month-end done together, then dedicated support on your team for fixes, upgrades and small changes.
Every implementation follows the same four phases. What changes is the scope inside them, agreed with you in discovery and never assumed.
We map how your company runs today (the flows, the documents, the reports you can't live without, and the BIR or IRAS filings you owe) and agree which apps Odoo covers first.
We configure the apps, build any custom module on a staging branch, and load your master data and opening balances for you to check.
Each team runs its own process on real data in staging, signs off on it, and keeps written steps ready for day one.
We cut over on an agreed date, close the first period together, then move you onto support for changes and upgrades.
These three share products, partners and journals. Implemented as one project they remove the re-keying between quotes, stock movements and the ledger. Purchase and CRM follow on the same database.
The ledger, bank feeds, tax and reporting, configured for how you actually close the month, and for the filings you owe: GST or VAT in Singapore, BIR in the Philippines.
Quotations, confirmation and invoicing that follow your pricing and approval rules. Confirming an order reserves the stock.
Real stock across warehouses, barcode operations and replenishment that raises purchase orders before you run out.
RFQs to vendors, orders, and bills matched to what was actually received.
Leads, pipeline and activities. A won deal opens the quotation with customer and pricelist already set.
If you file with the BIR, the implementation starts from the reports you must produce and works back to how invoices, bills and payments are recorded. E-invoicing is due by 31 December 2026 for covered taxpayer groups. On the discovery call we talk through whether you are likely to be in the first group, and your accountant confirms it.
What Odoo's Philippine set-up produces Sample data
Odoo's own cloud. Standard apps, automatic upgrades, fastest to start. Best when no custom modules are needed.
Odoo's platform for custom development, with staging branches, backups and version control included. Best when you need tailored modules.
Your servers or your cloud account. Best when data residency or existing infrastructure decides it.
Everything configured, migrated and handed over, with the people who use it able to run it without us in the room.
What is delivered 12 items, one database
Yes, with the Philippine localisation set up for your company. Odoo produces the 2307 per payee, the SLSP, SAWT and QAP as DAT files for the BIR's tools, and the 2550Q VAT summary, from the invoices and bills you post, and it can serve as your computerised books. Which reports you file is scoped in discovery. Odoo has no built-in connection to the BIR's EIS, and TechNext has not built one. If you are covered, we assess the options with you and quote any connection separately.
No software is BIR-accredited in that sense. The BIR registers your books and issues your Permit to Issue for the system you use, and its 14 September 2026 advisory says it has not accredited any e-invoicing provider. We set Odoo up for BIR requirements; your business registers it as its books. See BIR rules for your accounting system.
It depends on scope: how many apps, how much data has to be migrated, how many entities, branches and integrations, and whether any custom module is needed. We set the timeline in discovery and write it into the quotation, so you plan against an agreed schedule rather than a guess.
Usually the ones causing the most manual work today. For many companies that is Accounting, Sales and Inventory, because they share the same products, partners and journals. We confirm the order in discovery.
Yes. If a system works and your team likes it, we connect it through a standard connector or the Odoo API instead of replacing it.
Master data (customers, vendors, products) comes across in full. For transactions we usually bring opening balances and open items, and keep the old system available for history. We agree the exact scope in discovery.
Only when a real requirement can't be met by a standard feature. Custom work is built as a module on Odoo.sh, so it survives upgrades and stays version-controlled.
On Odoo Online, Odoo.sh or your own infrastructure. It is a scoping decision driven by whether you need custom modules and any data-residency rules, not a default.
Every implementation is scoped to the apps, data and integrations you need, so pricing is on quotation. Tell us what is manual today and we will come back with a plan.
Tell us what is manual today. An adviser will say which apps to switch on first, what your BIR or GST filings need, and what it takes.