Construction is one of the pillars of the Panamanian economy: it accounts for roughly 14% of GDP, employs more than 130,000 people and drives both public works (bridges, hospitals, roads, schools) and an intense private market of residential towers and shopping centers. Despite the economic weight, most construction companies still run on generic accounting systems that do not understand project logic.
The result is predictable: project closeouts that take months to reconcile, margins eroded by costs that were not assigned correctly, subcontractor payments tangled in retention issues, and a financial trial balance that ties out but never answers the CFO question that actually matters: "is this project making money, and how much?".
The quick test: if your current system cannot show you the real margin (revenue vs direct costs vs prorated indirects) of any active project in under 5 minutes, you have outgrown what that tool can do for a construction company.
Why generic accounting is not enough in construction
A construction company has four dimensions that traditional financial accounting handles poorly:
- Multi-project: 15 active jobs at the same time, each with its own P&L, budget and physical progress.
- Cross-project costs: the same equipment (dump truck, formwork, foreman) works on several jobs at once and must be prorated correctly.
- Physical vs financial progress: cash arrives when progress claims are approved, not when invoices are issued, and costs accrue on a different rhythm.
- Retentions and warranty holdbacks: the client typically retains 5-10% as warranty until handover; that has to be booked as a restricted receivable, not as revenue lost.
A construction ERP must be designed around these four dimensions, not have them bolted on as optional modules.
The 12 must-have requirements
1. Multi-level project structure
Each project must be a primary object with a hierarchical code: project, work front, line item and sub-item. Every transaction (purchase, warehouse issue, labor hour, invoice) must attach to the correct level without manual rework.
2. Detailed budget by line items
The ERP must let you load the initial project budget (typically from Excel or estimating software like Presto) and then compare actual vs budget line by line. Without that view, there is no real cost control.
3. Project cost control
Four sources of cost must land on the right project: materials (via purchase orders), labor (via payroll), equipment (via depreciation or rental), and indirects (management, office, transport) prorated by progress percentage or direct cost. The ERP must automate all four flows.
4. Progress billing (valuations)
A construction invoice is not by product, it is by certified line-item progress. The ERP must generate progress claims (work-in-place statements) in the format clients accept - usually columns for line item, budgeted quantity, prior accumulated quantity, period quantity, period amount - and convert them into a DGI electronic invoice with CUFE.
5. Contractual warranty retention
Clients typically retain 5-10% of each invoice as warranty. The ERP must record that retention as a restricted receivable and release it when the contract condition is met (project completion, provisional acceptance, definitive acceptance). Treating it as an invoice discount is accounting-incorrect.
6. Subcontractors and statutory withholdings
In construction, subcontractors are central. The ERP must handle subcontract agreements, valuations by progress, 50% ITBMS withholding when the subcontractor is not a withholding agent, ISR withholding when applicable, and periodic reconciliation against the original contract.
7. Site warehouses and central warehouse
There is material in the central warehouse and material transferred to each site (which must be costed to the project at the moment of transfer, not at the moment of purchase). The ERP must keep inventory by site warehouse, with documented transfers and periodic counts.
8. Site petty cash
Every site has a petty cash float for small purchases and daily expenses (fuel, refreshments for crews, copies). The ERP must support controlled openings and replenishments, with expense reports by site and signed liquidations on close.
9. Equipment and usage-based depreciation
Construction companies hold heavy assets (dump trucks, mixers, formwork, scaffolding). The ERP must depreciate each asset and prorate that cost to the projects where it was actually used, instead of dumping it into a generic overhead bucket.
10. Payroll with two models: salaried staff and hourly labor
Technical staff (engineers, site managers, admin) are on monthly payroll. Laborers, foremen and skilled workers are on hourly payroll with hours tracked by project. The ERP must run both models and assign labor cost to the right project every pay cycle.
11. DGI compliance specific to construction
Construction has its own ITBMS rules (some civil works are exempt or have a special rate), special ISR treatment for public works, and electronic invoicing with CUFE for every progress claim. The ERP has to know these details cold.
12. Real-time margin report by project
The flagship report: invoiced revenue, assigned direct costs, prorated indirect costs, gross margin and net margin, all by project and compared against budget. If you cannot pull that for any active project in under 5 minutes, the ERP is not doing its job.
Common errors with generic systems in construction
- Booking costs to "general expenses": the cost gets diluted and you cannot tell which project is actually generating margin.
- Treating warranty retention as a discount: it reduces revenue when it should be a restricted receivable.
- No site warehouses: cement physically "on site A" is logged as central inventory, distorting that project cost.
- Subcontractors as one-shot expense: with no progress valuation, you cannot tell what is owed or what has been paid against the signed contract.
- Labor as one bucket: with no project distribution, you cannot tell what each project is really costing in labor.
- Equipment depreciation as overhead: a B/.150,000 machine depreciating against general accounts instead of being charged to the projects where it worked.
Petty cash and minor purchases: the most common leak
In most Panamanian construction companies, site petty cash is where control breaks down. The site manager gets B/.500 for daily expenses, spends it on a thousand small things, and at the end of the week hands the bookkeeper a stack of receipts to type in. Result: 30-50% of real "minor" site spend ends up miscategorized or with no project assigned.
A serious construction ERP must support:
- Petty cash openings per site with an authorized amount.
- Expense capture from the field (ideally with a mobile app, photo of the receipt).
- Categorization with a controlled list (fuel, refreshments, hardware, transport).
- Controlled replenishment with signed liquidation.
- Automatic posting to the project expense account.
This is exactly where the cifraHQ mobile app removes most of the pain: the site manager photographs the receipt, categorizes it on the spot, and it lands on the right project without going through the bookkeeper.
Multi-company: parent and joint-venture projects
Larger builders typically run as a parent that creates temporary entities (consortiums) by project, especially for public works. The ERP must handle these entities as separate legal persons with their own books, their own DGI compliance, and consolidate up to the parent.
More on this in our multi-company IFRS consolidation guide.
Typical implementation costs
| Builder size | Subscription | Initial implementation | Timeline |
|---|---|---|---|
| Small (1-3 active projects, 10-20 users) | B/.650 - B/.1,200 per month | B/.10,000 - B/.22,000 | 2 - 3 months |
| Mid-size (4-10 projects, 20-60 users) | B/.1,200 - B/.3,500 per month | B/.22,000 - B/.55,000 | 3 - 5 months |
| Large (10+ projects, 60+ users, multi-company) | B/.3,500 - B/.8,000 per month | B/.55,000 - B/.150,000 | 5 - 9 months |
The biggest cost driver is not user count, it is the number of simultaneous projects and the legal complexity (consortiums, joint ventures, multi-company).
Typical implementation plan (mid-size builder)
- Month 1: process discovery, standard line-item catalog, project structure, bank and PAC integration.
- Month 2: multi-company setup, chart of accounts, withholding parameterization, budgets for active projects.
- Month 3: pilot with 1-2 projects (purchases, warehouse, payroll, valuations), training for site teams and administration.
- Month 4: rollout to remaining projects, parallel run for one month, validation of period close and reports.
- Month 5: clean cut-over, ERP as single source. Old system kept read-only for historical lookup.