ERPNext Consultant in Glasgow

Why ERPNext comes up in Glasgow's screen sector

Pacific Quay, on the south bank of the Clyde, is home to BBC Scotland and STV, and a cluster of independent production companies, post-production houses and facilities firms has grown up across the city to serve them and other broadcasters and streaming services. Film and drama productions also come to Glasgow for its streets, studios and crews. Funding can involve Screen Scotland, broadcaster commissions and private finance, each with its own reporting expectations.

Many of these businesses are small at the center and large at the edges. A company with a handful of permanent staff may run several productions in a year, each with its own budget, crew and bank account, often inside a separate company. That pattern explains the interest in ERPNext: additional companies do not need additional licenses, custom reports can be built to match the industry's cost report formats, and the data stays under the company's own control.

ERPNext is not the industry's default tool, and that matters. Production accountants are used to specialist production accounting systems, and some financiers expect reports in familiar formats. A realistic design often uses ERPNext for the parent company, development spending and smaller productions, while larger productions keep a specialist system and bring summarized results across. The ERPNext platform page covers the product itself.

A company for every production

Creating a separate company for each production is common practice in British television and film, partly for financial control and partly because the UK's creative sector tax reliefs are claimed through the company responsible for each production. Your accountant decides the structure; the ERP has to make it quick and cheap to repeat. In ERPNext, each production can be a company in the same system, sharing a chart of accounts template, cost center structure, tax settings and user roles set up by the parent.

The design questions are practical. How is a new production company opened, and by whom? Which suppliers and crew records are shared across companies, and which belong to one production? How are production overheads and staff time recharged from the parent, and how are those intercompany entries matched on both sides? What happens when a production wraps, the final cost report is signed off and the company goes quiet?

I write a production template that answers those questions, then test it by loading a past production and comparing the results with its original cost report. A consolidated view across the slate lets the company see total commitments, cash needs and overhead recovery in one place, without waiting for each production accountant's spreadsheet. The multi-company ERP solution page describes the general pattern.

Budgets, cost reports and estimated final cost

The cost report is the heartbeat of a production. Producers and financiers want to see, for each budget line, the original budget, spending to date, committed spending and the estimated final cost, often broken down by episode or block for drama and factual series. Variances need an explanation before they become overspends.

ERPNext provides budgets against cost centers and accounting dimensions, purchase orders that record commitments, and a report framework flexible enough to produce a cost report in the layout your team expects. I design the budget structure first, mirroring the top sheet and detailed lines your budgets already use, then add dimensions such as episode or shooting block so the same transaction can be reported in several ways without duplicate entries.

Commitment control is the weak point in many cost reports. A crew deal or a location agreement commits money weeks before an invoice arrives, and if only invoices are recorded, the report looks healthier than reality. Purchase orders and approval rules close that gap, and I define who can approve what, at which level, and how changes to the budget itself are approved and recorded. The project costing page covers similar controls in other industries.

Crew, kit and the evidence trail for relief claims

A production pays a shifting cast of suppliers: freelance crew invoicing for their services, kit and vehicle hire, locations, catering, post-production and music clearances. Some crew are employed through payroll for the length of the shoot, and the employment status of each role is a question for your accountant and payroll provider, not something the ERP should decide.

ERPNext can hold supplier records, purchase invoices, expense claims and petty cash floats for each production, with approvals before payment and batches of approved invoices prepared for payment through your bank. Payroll for employed crew is better run by a specialist entertainment or general UK payroll provider, with journals posted back to the production company by department or budget line. That keeps the cost report complete without stretching ERPNext's payroll into territory it was not designed for.

Relief claims and funder audits depend on tracing spending back to source. I organize records so each cost can be followed from budget line to purchase order, invoice, approval and payment, with the place where money was spent recorded wherever a funder or relief rule cares about it. What qualifies, and how claims are prepared, is for your accountant or tax advisor; the system's job is to make their evidence easy to assemble. The Glasgow ERP business analyst page covers documenting requirements like these in depth.

Hosting, support and a realistic first phase

Owning an open-source system means deciding who runs it. ERPNext can be hosted on Frappe Cloud, with a managed hosting provider or on your own cloud account, and each option changes who applies updates, takes backups and answers when something breaks. For a small company with no IT staff, a managed service with a clear support agreement is the sensible starting point.

A first phase for a Glasgow production company might cover the parent company and the next production to start, with budgets, purchasing, supplier invoices and the cost report, leaving development tracking, deeper integrations and historic productions for later. Custom reports and any custom fields are documented and kept in a separate app, so upgrades remain manageable and another developer could pick up the work.

I work remotely as an independent consultant and earn nothing from your choice of host or support provider. Workshops run over video with the production accountant and a producer, design decisions are recorded, and configuration is done by me or by an implementer you select, with anything beyond configuration built by a developer under my review. A visit to your premises in Glasgow can be arranged when a working session in person would help. If you are still weighing ERPNext against other platforms, the UK ERPNext page covers tax and payroll considerations, and my Glasgow ERP consultant page covers the wider city.