Contact Info
What does an ERP business analyst capture for an Edinburgh organization?
An ERP business analyst turns the rules hidden in an Edinburgh organization's contracts and statements into requirements a system must meet. For a publisher that means advances, royalty rates and returns reserves; for an independent school, termly fees, sibling discounts and means-tested bursaries; for a professional body, membership grades, exam entries and deferrals. The analysis runs remotely, and you receive process maps, a rules catalog, a requirements document and acceptance tests.
Last reviewed by Vikas Saroj
Some of the hardest ERP requirements in Edinburgh are not in anyone's process diagram. They sit in documents: an author's contract with royalty rates by format and territory, a school's terms and conditions for fees and deposits, or a royal college's regulations for membership grades, exam entries and refunds. If nobody reads those documents and translates them, no software demonstration will reveal the gap.
I do that translation as a remote business analyst. I read the documents with the people who administer them, map how the work flows today, and write requirements precise enough that a vendor has to respond to each one and a tester can verify it. The engagement runs in English, and the output belongs to you whichever platform you choose.
Each output is written so that a vendor can price it, an implementer can build it and your own staff can test it.
For publishers, I turn author and translator contracts into a structured catalog of royalty rates, escalators, advance recoupment, reserves against returns and subsidiary rights splits, so candidate systems are tested against your real deals.
I define what each royalty statement, agent report and rights income summary must show, how often it is produced and which figures must reconcile to the ledger, before anyone designs a template.
For independent schools, I document how termly fees, sibling and staff discounts, boarding charges, extras, deposits and invoices sent to sponsors are billed, and how changes in the middle of a term are handled.
I map how means-tested bursaries and scholarships are applied for, assessed, approved and shown on invoices, keeping sensitive family finances visible only to the people who genuinely need them.
For professional bodies and royal colleges, I capture membership grades, subscription rates, exam entries, deferrals and refunds as rules with worked examples, including members and candidates who pay in other currencies.
The final pack combines a business requirements document, a fit-gap matrix scoring each shortlisted platform, and acceptance tests drawn from your own contracts, fee schedules and membership regulations.
Business first, technology second. You can hire me for one step - a BRD, a gap analysis, a vendor shortlist - or for the whole journey.
Contracts, terms and current reports
Rules, flows and data
Tests your own staff can run
Business analysis is often described as mapping processes. In many Edinburgh organizations the process is the easy part; the difficulty is the set of rules behind it. Edinburgh is a UNESCO City of Literature and home to a cluster of publishers and literary agencies. It has a large independent school sector, and it hosts several long-established professional bodies and royal colleges whose members and exam candidates live around the world. In each case, money moves according to rules written in contracts, terms and conditions or formal regulations.
Those rules rarely survive a standard requirements template. A generic list says that the system must produce invoices or report on contracts. It does not say that a paperback royalty steps up once sales pass an agreed level, that a sibling discount applies only while an older child remains enrolled, or that a candidate who defers an exam keeps part of the fee only under certain conditions.
My approach is to read the documents with the people who administer them, turn each rule into a requirement with a worked example, and then test candidate systems against those examples. UK-wide topics, such as VAT treatments and Making Tax Digital, are covered on the UK ERP business analyst page, and the broader city picture is on the Edinburgh ERP consultant page. The sections below stay with the Edinburgh situations.
A publishing house holds contracts with authors, illustrators and translators, and almost every contract differs. Royalties may be calculated on the recommended price or on net receipts, with different rates for hardback, paperback, ebook and audio, for home and export sales, and with escalators once sales pass agreed levels. Advances must be recouped before royalties are paid, and a reserve against returns is often held back for a period. Subsidiary rights, such as translation, serial and film rights, bring income that is split between author and publisher in proportions each contract sets.
Many smaller publishers manage this in a specialist royalty system, or in spreadsheets maintained by one person, beside an accounting package. When the business considers an ERP, the first question is whether royalties move into it, stay in a specialist tool linked to it, or remain separate with a clean interface. That decision cannot be made without a full picture of the rules.
I build a royalty rules catalog from a sample of real contracts, covering every variation that appears, then write requirements for sales and returns data from distributors, reserves, statement production and author payments. Each requirement carries a worked example, so a vendor demonstration either calculates the right figure or visibly fails to. The tax and accounting treatment of advances and rights income stays with your accountant.
Edinburgh has a large independent school sector for a city of its size, with day and boarding schools, many of them registered charities. Their bursar's offices handle billing that looks simple from outside and rarely is. Fees are charged termly in advance at different rates by stage and boarding status. Discounts apply for siblings and staff children, extras such as music lessons, trips and exam entries are added during term, and deposits are taken on acceptance and credited when a pupil leaves. Invoices may go to parents, to an employer or to a relative who pays on the family's behalf.
Means-tested bursaries add another layer. Applications include sensitive financial information, awards are reviewed regularly, and the bursary must appear correctly on the invoice without exposing details to staff who do not need them.
Schools also run a management information system for pupils and admissions, so the requirements must say which system is the record for each pupil, family and fee, and how changes pass between them. I map the fee cycle from acceptance to leaving, write requirements for billing, credit control, bursaries and deposits, and define that interface. Charity reporting, Gift Aid on donations and the tax treatment of fees remain with your accountant and auditor; the requirements make sure the data they need exists. The education ERP page covers the wider sector.
Edinburgh is home to several long-established professional bodies and royal colleges, some with members and exam candidates in many countries. Their membership and finance teams apply rules that a generic membership module rarely covers in full: grades with different subscription rates, reduced rates for particular career stages or for members in certain countries, joining fees, part-year subscriptions for people who join after renewals, and lapsed members who later rejoin.
Examinations add another layer. Candidates book sittings at centers at home and abroad, pay in several currencies, and may defer or withdraw under published regulations with partial refunds or credits. Examiners claim fees and expenses. Courses, events and continuing professional development bring their own bookings and charges, and journal or publishing income may sit alongside. When these rules live partly in a membership database, partly in finance and partly in staff memory, renewal and exam seasons become the busiest and most error-prone weeks of the year.
I document each rule with a worked example, from a member changing grade during the year to a candidate deferring a sitting, and write requirements for the membership system, the finance system and the interface between them. Subscriptions, exam fees and events may each have a different VAT treatment, which your advisor confirms; the requirements make sure every charge is classified so that treatment can be applied. The multi-currency ERP page covers the currency side.
In these organizations the knowledge sits with very few people: a royalties manager, a bursar and fees assistant, a membership or examinations manager. They are busy at predictable times, such as royalty statement runs, the start of each school term or the annual renewal season, so I plan workshops around those peaks rather than through them.
Sessions are short and focused, held over video with shared screens so we can walk through real contracts, invoices and reports together. Between sessions I write up rules and examples for review, so the specialist's time goes on checking rather than explaining from scratch. Confidential material, such as bursary applications or member records, is handled through redacted samples agreed with you in advance.
At the end you hold process maps by role, the rules catalog, the requirements document, a platform-by-platform fit-gap matrix and acceptance test scripts. You own all of it, so any vendor or implementer can work from it. The BRD consulting service explains the document structure, and the Edinburgh freelance ERP consultant page covers what happens once a platform is chosen. A visit to Edinburgh is possible by arrangement, though nothing in the analysis requires one.
Tell me about your business and current systems. I’ll suggest the most sensible first step.
Book a Consultation
Not sure which ERP you need?
Share your business requirements with me and I will help you understand the right process, architecture and platform before implementation.
It depends on how varied your contracts are and how often statements run. A specialist royalty tool linked to the ERP may handle unusual terms better, while simpler contract terms can sit inside a general platform with some configuration. I document your rules first, then test both routes against the same worked examples, so the choice rests on evidence rather than on a vendor's preference.
That is rarely the right aim. The pupil system holds admissions, timetables, attendance and reports, while the finance side handles billing, bursaries and the ledger. The requirements define which system owns each piece of data and how fee changes pass between them, so the bursar's office stops rekeying information that already exists elsewhere.
Often, but the requirements must spell out how. Each charge needs a currency, a price list by grade or country where rates differ, and rules for exchange differences, deferrals and refunds. I document those rules with worked examples, then test whether the shortlisted membership and finance systems apply them correctly, including when a candidate defers or withdraws from a sitting.
We agree at the start which documents I see in full and which are redacted. A small set of anonymized examples is normally enough to capture the rules, and access to live records is not needed for requirements work. The requirements then specify who in your organization may see sensitive fields once the system is running.
No. The documents, systems and people can all be reached over video and shared folders, and short sessions fit around statement runs, term starts and renewal periods. If one workshop would clearly work better in person, a visit can be arranged for it.
Every business is different. Share where you are today and what you want to fix, and I’ll tell you honestly whether and how I can help.
Book a Consultation
Book a consultation to talk through your processes, systems and goals. I’ll reply with practical next steps - no obligation.