Progress Billing Software: 7-Step Excel Migration (2026)

Why Are We Still Doing Progress Billing in Excel?

Across the Turkish construction sector — regardless of company size — the vast majority of firms still prepare progress billing reports in Microsoft Excel. The reasons are obvious: Excel is cheap, ubiquitous, everyone can use it at some level, and it's been the company's habit since day one. A first project starts with a single billing template, then it gets copied for every new project, then a tab is added for each deduction type, and a few years later you end up with a 25-tab monster that no single person fully understands.

The problem is that progress billing has direct financial consequences that flow to the client, the subcontractor and the government. A formula error, a misaligned cell, or a wrong deduction percentage breaks both the current period payment and the subsequent cash flow. In multi-year projects these small errors compound; year-end reconciliations surface the differences and create tension with subcontractors, clients or financing banks.

The barrier to digital migration is not technological. It is behavioral: the team is used to Excel, the transition period looks inefficient, software costs appear upfront while benefits are diffuse and invisible. The goal of this article is exactly to break that barrier — to quantify the real cost of Excel-based billing and to provide a concrete 7-step migration plan.

The 7 Dangers of Excel-Based Billing

Saying Excel is dangerous for progress billing is not hyperbole; because it is not a structured financial tool, risk accumulates with every use. Here are the 7 most common dangers we see in the field.

1. Formula error risk: A typical billing workbook contains 200 to 400 formulas. A misdragged cell reference, a VLOOKUP pointing to the wrong column, or a rounding rule that differs across tabs instantly translates into thousands of liras of error.

2. Version chaos: File names like "Billing_v3_final_DONE_FINAL.xlsx" have become an industry joke. Which version was sent to the client, which was approved, which was forwarded to the subcontractor — these questions usually get answered by searching email archives.

3. No audit trail: Excel cells don't record who changed what, when, or from which value. In an audit or dispute scenario, the question "who changed it and when" simply cannot be answered.

4. Weak permissions: Once the file is shared, everyone can change every cell. Sheet protection is insufficient; someone takes a copy, edits it, sends it back, and which version is canonical becomes unclear.

5. No e-signature or approval flow: A progress bill is typically signed by the site foreman, the supervising engineer, the project manager and finance. In Excel this flow happens by email forwarding; delays, lost messages and out-of-order approvals are inevitable.

6. Disconnected from field data: Site progress percentages, actual quantities, photographic evidence and QC forms are manually entered into the Excel sheet. Data duplication, transcription errors and delays follow.

7. Annual reporting difficulty: Consolidating billing data from dozens of projects at year-end takes days. Each file's structure is slightly different; bulk analysis, profitability comparison and trend reporting become nearly impossible.

Each of these 7 dangers stems from Excel's nature; user skill alone cannot solve them. Our progress billing digital methods article approaches the technical side from a different angle.

What the Carnegie Mellon Excel Study Says

The most credible academic source documenting that spreadsheet errors are systemic rather than isolated is the Carnegie Mellon University research compiled by Professor Raymond R. Panko. According to his literature synthesis, 88 percent of enterprise spreadsheets contain at least one formula or reference error. Even more striking, most of these errors remain unnoticed even under audit; reviewers don't know what to look for, and the errors live in the file for a long time.

Other repeatedly validated findings: the error rate grows exponentially (not linearly) with sheet count; as formulas get more complex the chance of catching errors drops; and people struggle significantly to spot errors in their own formulas.

Now apply these findings to progress billing: a typical mid-sized construction project has 30-80 pay items per monthly bill, 4-7 deduction types, and including subcontractor billings amounts to 200-400 formulas. With an 88 percent error probability, a file of this size effectively means "there are errors, the only question is how big, how late they are discovered, and how much they cost to fix."

The 8 Non-Negotiables of Digital Billing Software

When migrating from Excel, which features the chosen software has directly determines migration success. An incomplete tool brings Excel's problems back in another form. The following 8 features are non-negotiable in our experience.

Feature	Why It Matters
Pay item library	Unit price and description consistency; re-entered pay items are a source of error
Automated deductions	Withholding tax, VAT, VAT reverse charge, retainage, advance offset eliminate formula error risk
E-signature workflow	Site foreman → supervising engineer → PM → finance sequential signatures; no email forwarding
Mobile field app	Progress percentage, actual quantity, photo evidence go from the field directly into the system
Audit trail	Who, when, why for every change; insurance against audits and disputes
Version control	End of "v3_final_DONE" files; every billing version is preserved in the system
Role-based permissions	Who can edit which field; site staff and finance have different permission levels
Excel/CSV export	Standardized export for accountants, clients, banks

Pay special attention to the last row: no progress billing software in Turkey currently offers direct API integration with accounting systems like Logo, Mikro, Netsis or ETA. Instead, reports generated by the software are exported as Excel/CSV and handed to the accounting team. Keep this in mind when deciding; if a vendor claims otherwise, demand a live integration demo before signing.

Step 1: Document Your Current Billing Process

The first step of migration is not setting up something new, but writing down the existing process as it really is. Skipping this leads to misconfigured software; the team complains that "a feature we used to have is missing."

What to document: who prepares the bill, what data they start with (contract, BoQ, site report), which deductions are computed and in what order, who approves, how many days approval takes, how it's sent to the client, how subcontractor billings are linked, and what format goes to accounting. One or two paragraphs per topic is enough.

This documentation later lets you ask the vendor concretely: "we do it this way, how is it reflected in your system?" It also clarifies internal ownership of each step; most firms only discover this lack of clarity during the migration itself.

Step 2: Extract Pay Items and Contract Templates

Step two is library preparation. List the pay items you use in your existing Excel bills, the unit prices you apply, and which deduction percentages apply to which contract types.

Turkish construction billings commonly use standard pay items from the Ministry of Public Works, Highways, and DSI. Their codes and unit prices are updated annually. When moving to software, asking "is there a structure where we can add pay items manually" is critical; no software automatically maintains current ministry pay items — the user must add them according to their own version.

For contract templates, remember that each contract type (lump sum, unit price, cost-plus) has its own billing rules. Headings that vary by contract type: advance offset method, retainage percentage, late delivery penalty, price adjustment. Our construction contract types article looks at contract type selection in depth.

Step 3: Pilot Project Selection

Migrating all projects to new software simultaneously is a guaranteed failure path. Instead, pick a single pilot project. The properties of a good pilot: not too small (1-2 months) nor too large (3-5 years); a site supervisor open to new things; a reasonable, flexible client.

Ideally it's a newly contracted project where the first bill hasn't been issued yet. Mid-project migration creates data carryover cost; starting from the first bill is cleaner and lets the team learn the software from the ground up.

An ideal pilot duration is 3-4 months. In that time at least 3-4 billing cycles complete; the team uses the software both theoretically and practically. The data gathered at pilot end becomes the concrete foundation of the full-rollout decision.

Step 4: Software Selection — Criteria and Decision

Choosing the right software at this step determines the success of every subsequent step. Beyond the 8 non-negotiables above, you need software selection criteria. Our construction software selection criteria article covers this deeply; we'll summarize the billing-specific essentials.

• KVKK compliance and data location: Billing data is sensitive financial data and should be stored in Turkey. Overseas data centers introduce risk.
• Multi-user concurrent access: Site, office and finance should be able to work in different modules at the same time.
• Mobile field support: Site staff must be able to enter progress via iPhone/Android; web-only is insufficient.
• Turkish-language support and training: The vendor must have a Turkish-speaking team; email or phone support should be contractual.
• Pricing model: Calculate the 3-year total cost of per-user or per-project license models.
• Demo and trial period: Always run the demo with your own real data; the vendor's standard demo data is insufficient.
• Roadmap: How many updates the vendor ships per year and which features are planned matters.

Where does AECKraft fit these criteria? It's a Turkey-based, KVKK-compliant SaaS solution with a mobile field app, Turkish support and a 60-day free trial. The billing module includes a pay item library, automated deduction calculations, audit trail and Excel/CSV export. It does NOT offer direct API integration with Logo, Mikro or Netsis; instead, reports are exported via Excel/CSV and handed manually to the accounting team. The healthiest approach is to compare AECKraft on the same criteria set against your alternatives.

Step 5: Train Your Team (Typically 16-24 Hours)

The most-skipped critical step after software selection is training. "We'll learn as we go" is often the leading cause of migration failure. In our experience, average training hours by role:

• Field staff (4-6 hours): Progress entry, photo upload, mobile usage, simple pay item entry
• Bill preparation staff (12-16 hours): Contract linking, pay item library, deduction setup, billing approval, e-signature flow, reporting
• Managers / project managers (4-6 hours): Approval flow, reporting, dashboard, user permissions
• Finance / accounting (6-8 hours): Billing output analysis, Excel/CSV export, manual transfer to accounting system

Total training investment is 16-24 hours per person. View this time not as "lost time" but as "investment for years of productive use." Live training (classroom or video conference) is much more effective than self-service videos; the interactive format addresses the team's specific questions and produces lasting learning.

Step 6: Parallel Operation Period (1-2 Months)

Throwing away Excel and running only on the new software the moment training ends is risky. Instead, plan a 1-2 month parallel operation period. During this time every bill is prepared in both Excel and the software; the two results are compared.

Purpose of the parallel period: verify that the software runs correctly, build the team's confidence in it, catch missing configurations early, and concretely identify which one is right when results differ. When differences appear, Excel is usually the one that's wrong — and this observation dramatically increases the team's trust in the new tool.

The period adds extra workload; for the team to accept it, the message "this is temporary, there's an end" must be clear. The date when Excel will be fully retired should be communicated in advance; otherwise the parallel period becomes permanent and benefits never materialize.

Step 7: Full Cutover and Archiving Excel

The seventh and final step is the official retirement of Excel. What this step entails:

• All historical Excel billing files are archived as PDFs for reference; removed from active use
• Excel is banned as a billing template; all new bills are prepared in the software
• Active projects beyond the pilot are migrated to the software gradually (typically 2-3 projects per month)
• Clients and subcontractors are notified about the new format
• Internal software champions (1-2 people) are appointed; day-to-day support routes to them

The success of full cutover is usually measured at the 6-month mark: has error rate dropped, has approval time shortened, has year-end reporting become easier, is anyone in the team asking to return to Excel? In our experience, by month 6 of a successful migration "going back to Excel" is no longer a discussion topic.

Payback Period and Annual Savings

The most frequent question is when the software investment pays back. For a typical mid-sized construction firm (10-50M TL annual revenue, 3-8 active projects):

Savings Item	Annual Impact (TL)	Note
Formula error prevention	80,000 - 400,000	0.5-2 percent of revenue is a typical error cost
Faster approvals	60,000 - 250,000	Cash arrives 15-25 days earlier; financing cost saved
Administrative workload	40,000 - 200,000	Bill preparation time halved; staff freed for other work
Dispute prevention	20,000 - 350,000	Audit trail reduces sub and client disputes
Total savings	200,000 - 1,200,000	Varies by firm size and project count

Annual software cost is typically 30,000 - 120,000 TL (depending on user count). Payback: smallest firms 5 months, mid-sized 3-4 months, larger firms 2-3 months. First-year training adds a one-time 50,000-150,000 TL; it doesn't repeat in year two. Our Excel to AECKraft migration guide covers broader migration scenarios.

Accounting Integration — Plain Talk

A frequently asked question deserves a direct answer: does digital billing software integrate directly via API with your accounting system (Logo, Mikro, Netsis, ETA)?

Answer: nearly no solution in the Turkish market provides this. Even when marketing materials claim integration, demanding a live integration demo usually reveals the actual mechanism: manual Excel/CSV export. The same holds for AECKraft: the bill is generated in the software, results are exported via Excel/CSV to the accounting team, then entered manually into Logo/Mikro/Netsis.

This should not block the migration decision; the main savings already occur in the bill preparation phase, not the accounting transfer phase. A monthly manual CSV transfer takes 15-30 minutes; eliminating it is not the big prize. The big prize is bill preparation moving from days to hours, error rate dropping from 12 percent to below 1 percent, and disputes shrinking thanks to audit trail.

If a vendor claims "we integrate directly with Logo," ask: which Logo version, which module, which fields synchronize, one-way or two-way, what happens on errors. Most of the time these questions don't receive clear answers and the claim turns out to be promotional.

AECKraft and Your Billing Migration

Concrete features AECKraft brings to this process (real features only):

• Pay item library structure in the billing module (where users can manually add ministry and their own pay items)
• Automated deduction calculations (withholding tax, VAT, VAT reverse charge, advance offset, retainage)
• Audit trail and version control (every billing version and change history is preserved)
• Role-based permissions (site, office, finance have different permission levels)
• Mobile field app (iOS + Android, progress and photo entry)
• Excel/CSV export to the accounting team (NO API integration with Logo/Mikro/Netsis)
• 60-day free trial (no credit card required)
• KVKK-compliant Turkey-based data storage
• Turkish UI and Turkish support

Visit the contact page for a demo, the pricing page for package details. You can run a 14-day parallel test using your existing Excel billing templates; experience with real data is far more reliable than brochures for a decision.

Conclusion

Excel-based progress billing is a deep-rooted but dangerous habit in Turkish construction. The 88 percent error rate, version chaos, missing audit trail and absent approval flow have crossed below acceptable risk thresholds. Digital migration is not technologically hard; it is behaviorally hard. The 7 steps in this article (process documentation, pay item extraction, pilot project, software selection, training, parallel operation, full cutover) are a battle-tested method.

Payback is 3-5 months; annual savings range from 200,000 to 1,200,000 TL. The cost of not investing far exceeds the cost of investing. The real question is not "should we migrate to software" but "when should we migrate." Our recommendation: start the pilot this quarter; full cutover can complete by year-end.

Related resources: Construction progress billing digital methods, Excel to AECKraft migration guide, Quantity takeoff software comparison 2026, Construction software selection criteria 2026.

Frequently Asked Questions

Is Excel-based billing always wrong, should we never use it?

Excel is acceptable for small projects (1-2 months, single billing cycle) and simple calculations. But for mid-sized and larger projects with multi-cycle billing, subcontractor bills, or audit obligations, Excel carries unacceptable risk. As size grows, risk grows exponentially.

Is the Carnegie Mellon research current or outdated?

Professor Panko's literature synthesis covers 1995-2015 publications; its findings have been confirmed by newer research. The human-psychology aspects of spreadsheet errors (missing your own mistakes, error rate rising with complexity) are time-invariant findings.

During parallel operation, which is treated as correct when Excel and software differ?

Analyze both results when a difference appears. In our experience, the great majority of cases Excel is wrong; but the software's configuration may also be incorrect. Request a configuration review from your vendor during the first 2-3 cycles to confirm correct setup.

Does the billing software integrate directly with our accounting system (Logo, Mikro, Netsis)?

No. Practically no Turkish market solution offers live integration. AECKraft included, software generates Excel/CSV reports that are handed to the accounting team and entered manually into Logo/Mikro/Netsis. This "lack of integration" should not block the migration decision because the main savings are upstream in bill preparation.

Is a 60-day trial enough, or do I need longer?

14 days suffices for the preparation phase (user creation, project setup, pay item entry) and testing at least one billing cycle. For deeper evaluation, request in writing a 1-2 month paid usage with cancellation rights; most vendors accept reasonable requests.

Should the pilot project be small or large?

Neither too small (won't exercise all features) nor too large (failure cost high). An ideal pilot is an 8-18 month project budgeted 3-7M TL, run by a team open to new methods. A reasonable and flexible client is also key.

What if our team resists the software?

Resistance is usually not "difficulty learning something new" but "the psychology of letting go of Excel habits." Solution: in the parallel period, demonstrate concretely that the software is correct when differences appear; communicate clearly the long-term gains (annual reporting, audit readiness, fewer late hours); and show that management itself uses the software.

Do ministry pay items come pre-loaded in the software?

No. No Turkish billing software (AECKraft included) maintains current Ministry of Public Works, Highways or DSI pay items automatically. Software provides a "pay item library" structure; users add the pay items relevant to their own version. So when evaluating software, the right question isn't "is there a pay item library" but "how practical is adding pay items."