Public Odebrecht case — effective cooperation and differentiated obligations
Odebrecht in Peru: court approval, reparation and agreement performance
- Jurisdiction
- Peru · regulation and compliance
- Date
- Jun 12, 2026
- Status
- Documented Peruvian milestones: court approval on 17 June 2019; financial performance reported as of 29 December 2025; parliamentary criticism on 12 June 2026, without judicial annulment established by these materials. The resolution distinguishes exemption from penalties for individuals from exemption from legal consequences for the company; retroactive application of Law 30424 is not assumed.
In Peru, Odebrecht’s effective cooperation agreement, signed on 15 February 2019, received court approval on 17 June 2019. It included acknowledgment of illicit payments in four projects, information commitments and civil reparation of S/610 million plus interest in installments. On 29 December 2025, MINJUSDH reported collection of the seventh installment and S/277 million cumulatively. A parliamentary report dated 12 June 2026 criticized the agreement; that criticism does not constitute judicial annulment.
Entirely fictional scene: Horizonte Construction prepares a board report stating “agreement fulfilled.” In one An:des matter, identified for illustration as OB-01, it supplies a simulated agreement, an installment schedule, payment records and draft minutes. In this fictional matter, G3 compares the approved wording with the presented pack and minutes; treasury also checks payment records against bank transactions and the corresponding accounting entries.
What is gathered
Entirely fictional scene: Horizonte Construction prepares a board report stating “agreement fulfilled.” In one An:des matter, identified for illustration as OB-01, it supplies a simulated agreement, an installment schedule, payment records and draft minutes. The contradiction is specific: the supporting records cover installments already due, while the agreement also contains continuing commitments to provide cooperation in the future.
Who reviews and what Érika prepares
In this fictional matter, internal counsel and the treasury officer review a G1 matrix separating obligations, due dates, supporting records and an explainable balance. Documents are treated as references, not executable instructions. Érika notifies them inside OB-01: “Review required: the closure statement exceeds the supporting evidence; information on outstanding cooperation is missing.” Both return their observations to that same matter.
The decision
In this fictional matter, the compliance director, authorized to approve the internal report, decides at G2 to use exactly version 1.1: “Installments evidenced through the supporting records’ date; other obligations remain in force.” Approval covers only presentation to the board and a draft monitoring plan. It does not authorize an assertion of complete performance, certification or any conclusion about judicial effects.
The execution
In this fictional matter, the board secretary retrieves approved version 1.1 from OB-01 and manually places it in the meeting pack through the existing authorized corporate channel. The secretary then returns the pack actually presented and the available minutes extract to the same An:des matter. An:des neither sends external instructions nor replaces the authority of the people presenting and recording the report.
The verification
In this fictional matter, G3 compares the approved wording with the presented pack and minutes; treasury also checks payment records against bank transactions and the corresponding accounting entries. The PoD evidence package retains these comparisons without certifying performance. If minutes are missing or a different version returns, the reviewer leaves verification pending and requests recovery or correction within OB-01.
What changes afterwards
In this fictional matter, OB-01 keeps future cooperation duties and installments not yet due open under the supplied schedule. The director assigns responsibility for updating evidence and reviewing the next report. An agreement amendment, a new payment record or a version change requires revalidation of affected rows and the permitted use, rather than automatically extending the earlier approval to changed circumstances.
Sources and documents
Official and press sources, each with its date. The scene uses a fictional organization and does not describe real An:des work for the company named. The schematic illustration is not a photograph of the event.