An event agency does not sell a product. It sells a project that exists only once: a three-day conference, a product launch, a trade show. Every event has its own quote, its own suppliers, its own deposits, a deadline that cannot move and, in the end, its own margin. When the event closes, there is still invoicing to finish, suppliers to settle and a question to answer: what did this event really earn?
This is exactly what spreadsheets handle badly once an agency runs more than a handful of events in parallel. This article explains how to structure an event management ERP around the event lifecycle, which invoicing and VAT rules to know, where an ERP stops for a trade show organizer, and how to choose between a project ERP, a PSA and a specialist tool.
One Event, One Short-Lived Project: Why Excel Breaks Down
The economics of an event agency rest on three particularities.
- Margin per project, not per product. The selling price is built from dozens of lines (venue hire, sound and lighting, catering, set design, hosts and hostesses, transport, internal time). Margin is won or lost in the gap between estimate and actual, line by line.
- A large share of external costs. Most of the delivery is often subcontracted: revenue flows through suppliers, freelancers and temporary crew. Controlling commitments matters more than tracking internal hours.
- Staggered cash flows. The client pays deposits, the agency pays suppliers before the event, and the client balance only arrives afterwards. An event’s cash position can be negative for weeks.
Excel holds up while the agency runs three or four events. Beyond that, the symptoms are always the same: several quote versions in circulation, purchase orders keyed in by hand with no link to the budget, supplier invoices arriving after closing, and an “estimated” margin that only reveals itself at the final review. The problem is not the spreadsheet itself, it is the missing chain between quote, commitments, invoices and accounting.
An ERP (or a PSA, see the last section) provides that chain: the event becomes a single record (project, job or internal order, depending on the vendor) to which everything attaches. The logic is the same as the one described for IT services firms and progress billing, with one major difference: the dominant cost is not internal time but subcontracting.
From Quote to Event Budget: Cost Lines, Target Margin, Revisions
The quote is the reference budget
In a well-configured ERP, the quote accepted by the client is not a Word document: it is the budget baseline of the event. Each sales line is linked to one or more cost lines (planned supplier, quantity, estimated purchase price). The gap between selling price and cumulative cost gives the target margin, line by line and overall.
Three configuration rules prevent most overruns:
- A shared catalogue of cost categories (venue, technical, catering, set design, communication, transport, accommodation, staff, miscellaneous). Without it, no comparison between events is possible. It is built like analytical dimensions, as explained in our guide to analytical accounting and ERP dimensions.
- A target margin per event type (seminar, trade show, product launch, internal event), rather than one margin for the whole agency. Risk and subcontracting ratios differ.
- A valued internal cost: the time of project managers and stage managers must be charged to the event, otherwise the margin shown is flattering.
Quote revisions and versions
An event changes until the last day: attendee numbers, a change of room, an extra technical option. The ERP must handle quote versions that keep the history (v1 signed, amendment 1, amendment 2) rather than overwrite the previous one. Two points to watch:
- only the version accepted by the client feeds the reference budget, the others stay available for consultation;
- each amendment recalculates the target margin, so a last-minute request can be refused or repriced with full knowledge of the impact.
An amendment that was never formalized is, in practice, the number one cause of lost margin: the supplier delivers, the agency pays, but the client was never invoiced.
Suppliers and Subcontracting: Purchase Orders, Temporary Crew, Commitments
The purchase order is the control pivot
For an event, spending is born at the order, not at the invoice. When the agency signs a catering quote or an equipment rental contract, it commits itself, sometimes three months before the invoice arrives. The ERP must therefore track three levels, all attached to the event:
| Level | Source | Question it answers |
|---|---|---|
| Budgeted | Approved client quote | How much the agency planned to spend |
| Committed | Purchase orders and contracts | How much it has already obliged itself to pay |
| Actual | Matched supplier invoices | How much it has actually paid or owes |
The main gain comes from the “Committed” column: it lets you see an overrun before the invoice. Without a purchase order linked to the event, margin only deteriorates when invoices are received, which is too late.
Freelancers, temporary crew and extra staff
Events mobilize a lot of one-off staff: technicians, hosts, stage managers. Depending on status, treatment differs: a freelancer’s invoice, a service from an umbrella or payroll company, or direct employment of entertainment-industry temporary workers by the agency itself. The latter falls under payroll and social security filings, which are country-specific (in France, for example, the GUSO one-stop service for occasional performance-industry employers applies in some cases: check its applicability on guso.fr for your situation). On the ERP side, the challenge is to attach the full cost (salary and charges, or invoice) to the event, whichever route it takes: purchasing, payroll or expense claims.
Controlling overruns
Four automatic controls cover most overruns:
- overrun alert when the commitments on a cost category exceed its budget, with mandatory managerial approval of any purchase order above budget;
- blocking or double approval of orders placed without a linked event;
- three-way matching (order, goods or service receipt, invoice) to avoid paying twice or paying for a service not delivered;
- tracking of last-minute spending (on-site purchases, taxis, replacement equipment) through the expense management built into the ERP, which must charge every expense to the event at the moment of entry.
Deposits, Staged Invoicing, VAT and Pass-Through Costs
An invoicing schedule tied to the event
Most events are invoiced in milestones: a deposit at signature, an interim instalment before the event, the balance afterwards. The ERP must generate these instalments from the quote, track deposits and apply them to the final invoice. Two effects deserve attention:
- cash flow: as long as deposits do not cover the commitments to suppliers, the agency is financing the event. A cash table per event (expected receipts against expected payments) is a decision tool, not a luxury;
- VAT: the rules vary by country. Under French rules, for example, VAT on services is in principle due when payment is received, with an option for the invoice-date basis. Deposits received trigger VAT liability without waiting for the final invoice, and the invoice-date option cannot postpone VAT beyond receipt of the price or of a deposit. See the French tax authority’s guidance at bofip.impots.gouv.fr. An ERP must therefore manage VAT liability per instalment, not just at the final invoice. Validate with your accountant for your jurisdiction and regime.
Pass-through costs or re-invoicing: a distinction not to miss
In an event, the agency often advances expenses on behalf of the client. There are two very different treatments:
- Re-invoicing with a margin: the agency buys a service (catering, rental) and resells it to its client. It is a sale by the agency, subject to VAT, and the margin is revenue.
- Disbursements (pass-through costs): under French rules (article 267, II-2° of the French tax code), sums reimbursed by the client are excluded from the agency’s VAT base only if four cumulative conditions are met. According to the BOFiP, the intermediary must act under a prior, explicit mandate, in the name and on behalf of the principal, account precisely for the expenses, record them in clearing accounts and be able to prove their nature and exact amount. Other EU countries apply comparable but not identical tests.
In practice, a true disbursement is rarer than people think in the events industry: if the agency contracts with the supplier in its own name, it is generally a case of re-invoicing, not disbursement. This qualification must be settled before configuration: the ERP must distinguish “re-invoiced” items from “disbursements” (dedicated clearing accounts) so that the client invoice is correct. If in doubt, have the qualification validated by your tax adviser.
E-invoicing
The French timetable provides that all VAT-registered businesses must be able to receive electronic invoices from 1 September 2026, with large companies and mid-sized firms required to issue them from that date, and SMEs and micro-businesses from 1 September 2027 (detailed timetable, Cegid). For an agency, two consequences follow: receiving suppliers’ invoices through an approved platform (high volume, often in batches), and preparing issuance with compliant invoice lines, deposits included. Our review of the first month of e-invoicing details the first feedback from the field.
Margin per Event and Real-Time Tracking
What you actually track
An event’s margin is read at three moments: forecast (quote), to date (committed and actual during preparation) and final (after all invoices are in and the event is closed). The gap between the three is the real indicator of how well the agency is in control.
Sample dashboard
The following table is purely illustrative: the figures are fictitious and come from no study.
| Cost category | Budget (quote) | Committed | Actual to date | Committed vs budget |
|---|---|---|---|---|
| Venue and logistics | €40,000 | €41,500 | €12,000 | +€1,500 |
| Sound, lighting, video | €35,000 | €33,000 | €0 | −€2,000 |
| Catering | €25,000 | €27,000 | €0 | +€2,000 |
| Staff and temporary crew | €20,000 | €20,500 | €0 | +€500 |
| Miscellaneous | €5,000 | €3,000 | €1,200 | −€2,000 |
| Total costs | €125,000 | €125,000 | €13,200 | €0 |
| Selling price | €150,000 | |||
| Forecast margin | €25,000 (16.7%) |
Reading: the event looks under control overall, but catering is drifting by €2,000 while the technical line leaves some room. This category-level view, before the event, makes trade-offs possible. A spreadsheet only provides it after the fact.
Closing each event
Closing day is often neglected. It should be a process: check that all supplier invoices have arrived (otherwise accrue for invoices not yet received), invoice the balance and any extras, record the final margin, then lock the record. Without a formal close, late invoices keep being charged months afterwards and distort the comparison between events. The financial year must also correctly reflect events that straddle two periods.
For Trade Shows: Stands, Exhibitors, Ticketing, Subscriptions
A trade show organizer has a different model from an agency: it sells floor space and services to exhibitors (stands, furniture, options, visibility) and tickets to visitors, and repeats the event every year. The needs go beyond the core of an ERP:
| Need | ERP / PSA | Specialist trade show tool |
|---|---|---|
| Invoicing, accounting, VAT | Very well covered | Sometimes limited |
| Budget and margin per edition | Well covered (project) | Varies |
| Floor plan, stand allocation | Rarely native | Core of the product |
| Exhibitor portal (booking options, documents) | Limited | Core of the product |
| Ticketing, access control, badges | No | Core of the product |
| Reminders and recurring subscriptions (annual editions) | Depends on vendor | Depends on vendor |
The practical conclusion: the ERP remains the financial system of record (customers, invoicing, accounting, budget per edition), while the show-specific commercial side (floor plan, exhibitors, ticketing) belongs to a dedicated tool that feeds the ERP. Trying to do everything in the ERP leads to costly custom development. Trying to do everything in the trade show tool exposes you to fragile accounting. What matters is the interface between the two.
Integrations: CRM, Scheduling, Expenses, Ticketing
Four integrations determine how smoothly the process runs.
- CRM to ERP: the won opportunity creates the event record with client, quote and terms. Without this, re-keying introduces amount errors. Our article on native versus dedicated CRM helps with this choice.
- Scheduling and production: planning tools (teams, equipment, stage management) must feed hours and requirements back to the event record.
- Expense claims: an expense incurred in the field must be charged to the event as soon as it is entered or the receipt is photographed.
- Ticketing and registration: ticket and registration sales must reach the ERP as aggregated sales entries, with VAT and a split by edition, rather than thousands of individual lines.
Before any decision, list the flows in and out of the ERP, and check for each whether the vendor offers a standard connector, a documented API or custom development.
Choosing: Project ERP, PSA or Specialist Tool
The three families are positioned differently.
| Option | Strengths | Limits | Suitable profile |
|---|---|---|---|
| PSA / project tool (e.g. Productive, Teamleader, Harvest) | Fast to deploy, time and budget tracking, moderate entry cost | Accounting must be connected, supplier commitment management sometimes limited | Small agency, a few people to a few dozen |
| Project ERP (Dynamics 365, Odoo, Sage X3, NetSuite, depending on configuration) | Purchasing, commitments, accounting and analytics in one system, multi-entity | Needs configuration and an integrator, change management effort | Structured agency, group, multi-activity organizer |
| Specialist event software | Industry functions (floor plans, exhibitors, ticketing, registration) | Shallower finance and accounting, interface to build | Trade show organizer, highly specialized agency |
Our comparisons of PSA tools for creative agencies and of ERP for service companies detail the generic offerings. Features and pricing change: check them with each vendor before deciding.
Recommendation by size, to be adapted to your context:
- Small agency (up to about twenty people): start with a PSA or project tool coupled to your accounting software. The goal is margin per event, not completeness.
- Growing agency (several dozen people, several simultaneous events): aim for a project ERP or a PSA with a solid purchasing module. Control of supplier commitments becomes the main criterion.
- Trade show organizer: ERP for finance and per-edition management, a specialist tool for exhibitors and ticketing, with a carefully built integration.
- Multi-entity or international group: ERP with consolidation, multi-currency and intercompany re-invoicing.
Whatever the choice, what sets successful projects apart is upfront scoping: define what an “event” is in the tool, which cost categories, which invoicing milestones and which closing rule, before choosing the vendor.
Going Further
To see how to structure your profitability dimensions, read our guide to analytical accounting in the ERP. If you run an agency or an organizing company and want to scope your project, get in touch to discuss your event cycle, your suppliers and the right level of tooling.
