Discovery
We walk through the real operation and the accounting position: how the company buys, sells, invoices and closes today, and which systems and spreadsheets hold it together. Deliverable: scope, risks and assumptions.

Tech Jungle · Peru
Odoo implementation in Peru from process review and configuration to migration, training and go-live, with technology and accounting expertise.
We walk through the real operation and the accounting position: how the company buys, sells, invoices and closes today, and which systems and spreadsheets hold it together. Deliverable: scope, risks and assumptions.
Flows, documents, taxes, price lists, approvals and roles, written down. Deliverable: an approved design document that governs every later change.
Companies, chart of accounts, journals, taxes, warehouses, products, document sequences and permissions. Deliverable: a configured environment.
Customers, suppliers, products, accounting balances, receivables, payables and valued inventory. Deliverable: reconciliations signed off against the source system.
Real company cases end to end, including returns, credit notes, advances and exceptions, verified down to the journal entry. Deliverable: test log and fixes.
Role-based training on the company's own data, with reference material. Deliverable: users who can operate unassisted.
We stay through the first week and the first monthly close, where everything testing could not predict shows up. Deliverable: a stable operation and an improvement plan.
Projects rarely slip because of software. They slip because nobody defined who decides and who validates.
| Open deliverable | Status |
|---|---|
| Valued inventory reconciliationOwner: client | Under review |
| Test set by areaOwner: shared | In progress |
| Manual by roleOwner: Tech Jungle | Draft |
A baseline implementation with one legal entity and the commercial and accounting modules typically starts from around 30 days depending on scope. Multiple warehouses, manufacturing, historical data migration, SUNAT and bank integrations, or limited availability from key users extend that. We commit to a date after discovery, with scope in writing.
The hard part is usually not Odoo: it is translating Peruvian statutory requirements into a model that headquarters can read. Electronic invoicing (CPE), the local chart of accounts (PCGE), the SPOT withholding system known locally as detracciones, withholdings and perception regimes all have to coexist with group reporting. We configure both views on the same database instead of maintaining two accounting truths.
FAQ
Yes, and for companies under tax pressure it is a reasonable starting point. Decide where documents will come from: if sales and purchasing stay outside the ERP, someone will keep entering them manually.
It stays live until the agreed cut-off date. We define the cut-off, how pending documents are handled, and which history is migrated versus consulted in the old system.
Not to run Odoo Online or Odoo.sh. You do need an internal project owner with authority to decide and time allocated.
It is a frequent case. We start with a review of the existing functional and accounting configuration, decide what to keep and what to rebuild, and re-plan from there.
Yes, as an explicit part of scope: document types, series, credit and debit notes, dispatch guides and the integration with the transmission service.
We review operations, accounting and current systems before discussing scope or price.