Table of contents5 sections
  1. Event cost settlement: how to close a project when some invoices arrive after it ends
  2. Why invoices arriving after the event distort project profitability
  3. How to run event cost settlement properly
  4. How did we solve this problem at Administy?
  5. An event is over operationally long before it is fully settled

Event cost settlement: how to close a project when some invoices arrive after it ends

The event ended as planned. The client accepted the delivery, the team logged its hours, and the Project Manager prepared the financial summary. The report shows the expected margin, so the project is treated as closed.

A few days later an invoice arrives for transport. Then a subcontractor sends the settlement for the technical crew’s overtime. An additional cost appears for accommodation, materials used and services ordered right before the event.

Every further document changes the result of the project.

A margin that initially looked safe starts to fall. In an extreme case it turns out that the project was closed with a profit only because some of the costs were not yet visible.

We know what it is like when all the work is finished but the project is still open financially. The team remembers that an additional service was ordered, but the invoice has not arrived yet. The supplier has not given the final amount, and some of the costs exist only in messages or in phone arrangements.

That is why event cost settlement should not rest solely on the invoices that arrived by the day the event ended. It must also take into account planned liabilities, services that have been ordered, and costs for which the company is still waiting for documents.

The event ended as planned. The client accepted the delivery, the team logged its hours, and the Project Manager prepared the financial summary. The report shows the expected margin, so the project is treated as closed. A few days later an invoice arrives for transport, the technical crew’s overtime, and extra costs for accommodation and materials.

Why invoices arriving after the event distort project profitability

In the events industry, the moment a service is performed, the moment the invoice is issued and the moment of payment often fall on completely different days.

A subcontractor may do the work before the event, settle overtime after it ends, and send the invoice only several or a dozen or so days later. In the meantime the agency may already have prepared the final report for the client and treated the project as closed.

The report includes documents, not all liabilities

If only invoices that have been received go into the settlement, the result of the project is incomplete.

In reality the agency may already have liabilities arising from:

  • a confirmed order,
  • an accepted subcontractor quote,
  • hours worked,
  • a service performed,
  • a signed contract,
  • arrangements made during set-up,
  • additional work commissioned on the day of the event.

The absence of a document does not mean the cost does not exist.

If a service has been performed, the agency should include it in the project, even if it does not yet know the final invoice number or payment date.

The final amount differs from the original order

In event projects the final cost can change in the last hours of delivery.

This most often concerns:

  • crew overtime,
  • additional transport,
  • a larger number of attendees,
  • extended catering,
  • missing materials,
  • accommodation,
  • changes to the set design,
  • additional security,
  • longer equipment hire,
  • dismantling costs.

If the project budget contained only the initial quote and was not updated after the change, the final report can significantly understate the real cost.

The team forgets about costs after the event ends

Right after the event, the people involved remember which services were extended and what additional purchases were made.

After a few weeks, reconstructing this information is much harder.

The Project Manager starts the next project, subcontractors send documents to different people, and information about costs stays in:

  • e-mails,
  • messaging apps,
  • notes,
  • phones,
  • paper confirmations,
  • private spreadsheets.

When the invoice finally arrives, it can be hard to establish whether the amount matches what was agreed and which project it belongs to.

The project is closed with an inflated margin

An example:

  • project revenue: 180,000 PLN,
  • cost invoices received: 125,000 PLN,
  • team labour cost: 15,000 PLN,
  • initial margin: 40,000 PLN.

After the event ends, however, additional costs appear:

  • technical crew overtime: 8,000 PLN,
  • transport: 4,500 PLN,
  • additional materials: 3,500 PLN,
  • accommodation: 2,000 PLN.

The real margin falls from 40,000 PLN to 22,000 PLN.

If a company analyses results on the basis of the first report, it may make wrong decisions about quotes, bonuses and client profitability.

How to run event cost settlement properly

The key is to separate two pieces of information:

  • the document has not arrived yet,
  • the cost does not exist yet.

These are not the same thing.

The cost should be visible from the moment the commitment is made, and the invoice should later confirm its final value.

1. Record the cost at the moment the service is ordered

Every order should go into the project budget before the invoice is received.

It is worth recording:

  • the supplier,
  • the type of service,
  • the planned amount,
  • the delivery date,
  • the expected date of the document,
  • the payment due date,
  • the person who placed the order,
  • the delivery status,
  • the project the cost relates to.

This way the report shows the liability even though the accounting document has not arrived yet.

2. Separate planned, ordered and invoiced costs

Not all values carry the same level of certainty.

It is worth using three basic statuses:

Planned cost — The item is in the budget, but the service has not been ordered yet.

Ordered cost — The company has made a commitment and the supplier has confirmed delivery, but the invoice has not arrived yet.

Invoiced cost — The document has been received and can be verified and scheduled for payment.

This distinction lets you control the budget and assess the certainty of the data at the same time.

3. Update the cost forecast after every change

If the scope grows during delivery, the planned cost should be updated immediately.

For example, the company ordered technical equipment and crew for 20,000 PLN, but the event ran a few hours over. The Project Manager was told that an overtime cost will appear.

There is no need to wait for the invoice to include it in the forecast.

You can enter an estimated item and, once the document arrives:

  • approve the amount,
  • update it,
  • explain the variance,
  • link the planned cost to the invoice.

This way the forecast margin changes together with the project.

4. Do not close the project without a list of expected documents

Before closing an event financially, it is worth running a completeness check.

The list should cover:

  • all subcontractors,
  • services ordered,
  • costs incurred,
  • invoices already received,
  • documents still expected,
  • advance payments to be settled,
  • additional costs,
  • refunds and corrections.

The project does not have to stay fully open until the last invoice is received. It should, however, have a status indicating that the result is forecast, not final.

5. Compare planned cost with actual cost

Once the invoice is received, it is worth checking:

  • what amount was planned,
  • what amount was ordered,
  • what value appears on the document,
  • what the difference results from,
  • whether the change was approved,
  • how it affects the final margin.

This kind of analysis helps not only to close a particular event, but also to improve the quotes for future projects.

If transport regularly costs more than assumed, the problem is not a single invoice. It is the way budgets are set.

Case study

How did we solve this problem at Administy?

In our own agency projects, too, a subcontractor’s invoice sometimes appeared only after the work was finished.

The project had already been delivered, the client had received the invoice, and the team had prepared the summary. A few days later a cost document arrived that changed the margin calculated earlier.

The mistake was that the report relied primarily on documents already received.

We knew that a certain cost would appear in the future, but until the invoice arrived it was not always visible in the project statement.

This caused several problems:

  • the margin looked better than it should have,
  • it was hard to assess the full cost at completion,
  • the project owner did not know which documents we were still waiting for,
  • an invoice could be assigned only after the context had been reconstructed by hand,
  • the report changed after the project had been formally closed.

That is why at Administy we take into account not only invoices received, but also planned costs and liabilities whose documents have not yet arrived.

Each item can contain:

  • the supplier,
  • the project,
  • the cost category,
  • the planned amount,
  • the person responsible,
  • the expected date of the document,
  • the payment due date,
  • the delivery status,
  • the invoice status.

In practice this lets you separate:

  • planned cost,
  • cost already ordered,
  • invoiced cost,
  • paid cost.

When a document arrives, we link it to the item created earlier. This way a second, independent cost is not created, and the report shows the difference between plan and actual.

If we expected a spend of 12,000 PLN and the invoice is for 14,500 PLN, we can check:

  • whether the scope grew,
  • whether overtime appeared,
  • whether the cost was approved,
  • how the difference affects the margin.

This approach lets you see:

  • costs already incurred,
  • invoices awaited,
  • planned liabilities,
  • the amount needed to complete the project financially,
  • the current margin,
  • the forecast final margin.

The most important change is that a missing invoice does not mean a missing cost in the analysis.

This way the Project Manager can close the operational stage but still see that the project is financially waiting for documents from specific suppliers.

Conclusions

An event is over operationally long before it is fully settled

The end of an event does not automatically mean the end of all financial liabilities.

Reliable event cost settlement requires taking into account invoices received, ordered costs and planned items for which the company is still waiting for documents.

This way the project margin does not suddenly change a few weeks after the report was prepared, and the agency owner knows the expected result even before the last document arrives.

Check the full cost of the event before closing it financially

Administy helps combine the budget, planned costs, invoices received, payments and forecast margin in a single project view.