NextERP Documentation
ROEN

Start here · Article 06

Testing the flows before going live

Applies to Odoo 19 · 20

Before going live, every person who will work in Odoo goes through their own flows on the company's real data: an order, a delivery, an invoice, a receipt. The test is done on a copy of the database, so that the test documents reach neither the accounting nor ANAF (the Romanian tax administration). The goal is to discover the missing settings before the start: a wrong account on a category, a wrong tax on a product, a missing access right.

When to use

  • Setup and data import are done and go-live is approaching.
  • A new flow has been added (a cash register, a warehouse, a new activity).
  • The Odoo version changes.

Before you start

  • Your consultant has provided a test copy of the database, with the imported data. Check by the database name or by the message on screen that you are working on the test copy.
  • Each user has their own account, with the rights they will have after go-live.

Steps in Odoo

1. Choose the flows to test

List the operations the company does every month: sales, purchases, receipts, deliveries, customer receipts, payments, manufacturing, cash register. For each, choose a recent real case (a customer, a product, an invoice from last month).

2. Go through each flow end to end

Each user goes through their flow following the guide in the right chapter: for example the order, the delivery and the invoice from the Sales and invoicing chapter, then the receipt from the Receipts, payments and bank chapter.

3. Check the printed documents

Check the invoice, the delivery note, the receipt: the company data, the series, the bank accounts, the mandatory mentions.

4. Check the journal entries

The accountant opens the journal entries of the test documents and checks the accounts and taxes against the tables in the For the accountant blocks of the guides.

5. Check the returns on the test data

Generate the monthly returns for the test period (D300, the VAT return; D394, the domestic sales and purchases informative return) and check that the operations appear on the expected lines. Do not file them.

6. Correct the settings and repeat

For each problem found, correct the setting (account, tax, access right) in the production database, not only in the copy, and repeat the flow.

Variants

Testing the ANAF connection

e-Factura and e-Transport (the Romanian e-invoicing and goods-transport reporting systems) have a test environment at ANAF. On the test copy, check that the company is connected to the test environment, not the real one, before sending documents: see the e-Factura, e-Transport and SPV chapter.

Testing the cash register

The fiscal cash register issues real receipts. Test it only with the procedure indicated by the register's supplier.

Common mistakes

  • Test done only by the consultant. Users discover the problems only after go-live. Each person tests their own flows.
  • Corrections made only in the test copy. At go-live, the problem comes back. Correct in the production database.
  • Test documents sent to ANAF. A test invoice sent to the real e-Factura becomes an issued invoice. Check the environment before sending.
  • Testing only the simple case. Also test the company's special cases: returns, down payments, foreign currency, EU customers.
For the accountant: what to check during the test

Accounting checks

What to check Where
Income, expense and stock accounts the entries of invoices and stock moves
The tax and the D300 line the invoice and the return generated for the test period
Partners in D394 the CIF and the operation type
Stock write-off on delivery the delivery entry (expense = stock)
Opening balances the trial balance at the start date
Documentation by the NextERP team.