Safe navigation

Before entering information, confirm company, user, date, and period. Available actions depend on permissions and document state.

Learning objectives

• Use saved searches for repeatable work. When finished, verify the result with a test record and document ownership.
• Review required fields and messages before confirmation. When finished, verify the result with a test record and document ownership.
• Do not confuse save, validate, post, pay, and reconcile. When finished, verify the result with a test record and document ownership.
• Never correct posted fiscal documents directly in the database. When finished, verify the result with a test record and document ownership.

Concepts to master

• Use saved searches for repeatable work.
• Review required fields and messages before confirmation.
• Do not confuse save, validate, post, pay, and reconcile.
• Never correct posted fiscal documents directly in the database.

Guided practice

1. Activity 1. Use saved searches for repeatable work. Perform it in staging first, record preconditions, and compare expected and actual results.

2. Activity 2. Review required fields and messages before confirmation. Perform it in staging first, record preconditions, and compare expected and actual results.

3. Activity 3. Do not confuse save, validate, post, pay, and reconcile. Perform it in staging first, record preconditions, and compare expected and actual results.

4. Activity 4. Never correct posted fiscal documents directly in the database. Perform it in staging first, record preconditions, and compare expected and actual results.

How to verify the result

• Company, user, language, time zone, and date match the scenario.
• Permissions allow only operations assigned to the responsibility.
• Changes are traceable and related documents remain consistent.
• The procedure is repeatable and has a documented correction path.
• A restored backup can reproduce the process without relying on production.

Common mistakes

• Confusing save with confirm, post, pay, or close.
• Testing only as administrator and assuming access rights work.
• Changing states or totals with SQL to bypass validation.
• Upgrading without inventory, restorable backup, and post-upgrade reconciliation.
• Documenting only the happy path while omitting cancellation, correction, and exceptions.

Developer perspective

Identify the models, fields, buttons, domains, and access rules involved. Before extending the process, locate the module that owns the rule, review its tests, and preserve invariants through super(). A correct customization must work across companies, languages, permissions, and states.

Production checklist

• Company, user, language, time zone, and date match the scenario.
• Permissions allow only operations assigned to the responsibility.
• Changes are traceable and related documents remain consistent.
• The procedure is repeatable and has a documented correction path.
• A restored backup can reproduce the process without relying on production.