Closing a Government Contract in Panama: Why Delivered Is Not Done.

You delivered. You invoiced. You were paid. Your finance team booked the project as complete two years ago and your bonding capacity moved on to the next job.

Under Panamanian law, that contract is still open, and so is your exposure.

This is the single most common gap between how foreign contractors read a public contract and how Panama's procurement statute actually works. It is not a technicality that surfaces in litigation. It surfaces in due diligence, in an auditor's file review, in a bonding renewal, and in the prequalification stage of the next tender you want to bid.

Note: general information current as of the date, under the consolidated text of Law 22 of 2006 as ordered by Law 153 of 2020. Every file turns on its own record.

The concept that does not translate

Panamanian procurement recognizes three separate acts that English-language contract practice tends to compress into one.

The trap sits in that third row. Resolución looks like "resolution" and reads like a neutral word for winding something up. It is not. It is administrative termination for cause, its grounds are closed and exhaustively listed, and it carries debarment of the contractor for anywhere from three months to three years.

If an entity proposes to resolver a contract you completed, that is not housekeeping. It is a sanction, and it needs a statutory ground that a finished contract does not supply.

What closes a performed contract is the liquidación: the settlement.

Three clocks that start on their own

None of these needs anyone to trigger it. They run from the calendar, and they run whether or not either party is paying attention.

Five business days to issue the receipt document. Entities are obliged to receive the goods, services or works and to issue the receipt document within five business days. Where they do not, they must state the reasons in writing. That second duty is a freestanding obligation, breached by silence, and it is honored far less often than it is owed.

Two months to settle. The statute defers first to whatever period the tender documents set. Check yours before assuming, because in practice most set none, and the statutory default then applies: two months from expiry of the performance period.

One or three years of defects cover after settlement. The performance bond's statutory life is the performance period plus the settlement term plus one further year for latent defects, extended to three years for construction defects in works or immovable property. Note the ordering. The defects year does not begin at delivery. It begins after settlement, which means that in an unsettled contract nobody can yet calculate when your bond is finally released.

The bond problem, and whose problem it is

Here is the part that reverses the intuition most foreign contractors bring with them.

In Panama, keeping the performance bond alive is the contracting entity's legal duty, not yours and not the surety's. The statute is explicit: it is the responsibility of the contracting entity to require that the performance bond remain in force through completion and through the additional statutory period.

What happens in practice is mechanical. The bond gets endorsed forward each time the performance period is extended, extension by extension, and the endorsements stop when the performance period stops. Nobody endorses it to cover the settlement term or the defects year, because settlement has not happened and the defects year has therefore not begun.

Then someone opens the file three years later and finds a bond that lapsed on the day the performance period ended, a contract that is still legally in force, and a surety being asked to endorse backwards over a period that has already elapsed. Sureties generally cannot do that.

The default is the entity's. Your problem is different and still real: a guarantee sitting unreleased against your name, a file your compliance function cannot close, and a counterparty with an incentive to leave things exactly as they are.

The advance payment reports that gate everything

If your contract carried an advance payment, and in Panama it can reach 20 percent of the contract value, there is a statutory precondition that is easy to miss and hard to cure afterwards.

The contractor is required to render a monthly, itemized and substantiated report on the use of the advance, prior to issuance of the final acceptance certificate.

"Prior to" is doing real work in that sentence. These are not reports you can produce later or regularize once the certificate is signed. They are a legal precondition of the certificate itself. A final acceptance certificate issued without them was issued against an express statutory requirement, and that is precisely the kind of defect an auditor finds years afterwards, by which point the advance payment bond, whose statutory life is the principal period plus thirty calendar days, expired long ago.

If you took an advance and never filed monthly reports on it, that is worth resolving before you ask anyone to close the file.

If you are still bidding: the awards are decided on paper, not on price

This is the section worth reading twice, because the pattern is consistent and it costs foreign bidders contracts they had already won on the numbers.

In a 2018 award file we reviewed, the losing consortium had bid roughly USD 121,000 below the winner on a contract of about USD 2.8 million. It was excluded before its price was ever compared, on six documented failures. Half of them were legalization failures:

• A sworn declaration signed by only one of the four consortium members, when the requirement bound all of them, and with signatures that were never notarized.
• A manufacturer's authorization letter from a European supplier that arrived without an apostille.
• Type-approval certificates from two foreign regulators, submitted without apostille, and in one case with the apostille affixed to the translation rather than to the original document.
• A certificate of the wrong kind substituted for the one the tender named, and unlegalized as well.

The evaluation record also noted a proponent registration certificate that had expired, and two consortium members holding only an application for registration rather than the registration itself.

None of that is about capability. Every one of those companies could do the work. The tender was lost in the document room.

Four practical rules follow from it, and they cost almost nothing to apply:

1. Apostille the original, never the translation. This single error appears again and again.
2. Every consortium member satisfies every threshold requirement. Lead-member compliance is not consortium compliance.
3. Register before you bid, not while you bid. An application on file is not a registration.
4. Read the certificate name literally. A type-examination certificate is not a software security certificate, however similar the subject matter.

Build your document timeline backwards from the bid date with apostille turnaround in it. In most jurisdictions that is weeks, not days, and it is the schedule item that most often fails.

One more thing about your consortium

Two provisions of the statute deal with consortium membership, and they cut in opposite directions.

At bid stage, a threshold requirement generally binds every member. At performance stage, dissolution of the contractor or of any company forming part of a consortium is a ground for administrative termination, unless the remaining members can perform the contract.

If your Panamanian project vehicle has been restructured, wound down or merged since award, and the contract has never been settled, that ground is theoretically live on a contract you consider finished. It is a five-minute check and worth making.

Two statutes with the same name

A practical detail that costs hours. Two consolidated texts of Law 22 of 2006 coexist: the one ordered by Law 61 of 2017 and the one ordered by Law 153 of 2020, which is the version in force. The numbering shifted between them, by roughly eight articles.

Contracts, resolutions and amendments signed between 2017 and 2020 cite the older numbering. Reading them against the current text produces genuine confusion: the article your contract cites for termination grounds may today govern something else entirely. Before arguing about what a provision says, establish which consolidated text the drafter had in front of them.

What to do, in order

The sequence matters, because each step sets up the next.

1. Establish the real status of the bonds, in writing, from the surety and from the comptroller. This determines everything else.
2. Obtain the payment certification, by budget line and by date. Internal resolutions rarely agree with one another on the numbers, and settlement needs an arithmetic base that holds.
3. Inventory the deliverables one by one against what the tender documents required at each phase. Manuals, training sessions and periodic reports are usually what is missing, and they almost never appear in progress reports.
4. Put what is outstanding in writing, with a deadline. Silence from either side helps neither.
5. Insist on a formal settlement convocation. Unilateral settlement is only available to the entity after it has formally convened the contractor. Until it does, it cannot settle alone.
6. Check who signs. Every settlement requires the signature of the entity's legal representative or delegate together with the public servant authorized by the comptroller. Without that second signature, what was signed is not a settlement.

One point of leverage worth knowing: in a settlement by mutual agreement the contractor has an express statutory right to record reservations. Use it. A subsequent unilateral settlement can only cover matters that were not agreed, so a well-drafted reservation defines the ground the entity is later free to decide on its own.

Why this sits unattended for years

A performed contract generates no urgency. Nobody complains, nothing fails, no loss is visible. The file gets closed mentally while remaining open legally, and the issue surfaces only when someone has a reason to look: an audit, a change of administration, a contractor who needs the closeout to prequalify elsewhere, or a surety asking why a guarantee from 2023 is still on its books.

By then the two-month deadline is years past, the bond has been unendorsed for just as long, and what should have been a closing formality has become a file with liability on both sides of it.

Related: suing the State in Panama.

Legal basis: consolidated text of Law 22 of 2006 on Public Procurement, as ordered by Law 153 of 2020, articles 98, 102, 104, 106, 113, 123, 124 and 136. Informational content; not legal advice.