Contribution by title
Development, print and royalty cost against net sales shows which titles pay for themselves and which do not.
A practical look at what an ERP does for a publishing business, where the value sits, and how to choose a platform that reports title profitability and handles royalties and returns properly.
Publishing economics are decided title by title. Development cost, print run, discount structure, returns and royalties all sit between the cover price and the profit.
An ERP (enterprise resource planning system) brings those together so contribution by title, imprint and channel is known during the life of a title, not after it goes out of print.
Editorial and rights systems keep their specialist role. The ERP governs cost, stock, revenue and royalties.
For most publishers, an ERP is where the following live:
The value is title level truth. Knowing what each title earns after cost, discount, returns and royalties.
Development, print and royalty cost against net sales shows which titles pay for themselves and which do not.
Sales history and stock position inform reprint decisions, reducing both stockouts and pulping.
Escalating rates, advances and earn-out handled by the system rather than a fragile spreadsheet.
Discount, freight and returns by channel show what each route to market really contributes.
Provisions and actual returns tracked against the title keep reported revenue honest.
Ebook, audio, subscription and print revenue reported together rather than in separate systems.
Data taken from a survey we commissioned in December 2024. Click here to view
of businesses are utilising an ERP
businesses are dissatisfied with their current ERP
of businesses say using an ERP has contributed to achieving business outcomes
Six everyday situations where one connected system changes the outcome.
Advance, development budget and expected print cost are set so the P&L can be tested before committing.
Publishing has requirements generic systems don't cover. These are the questions worth asking before you shortlist.
Finance, purchasing, stock, projects and reporting should sit in one system. Anything left in a spreadsheet quickly becomes the version everybody argues about at month end.
A system designed for a different sector rarely suits publishers. The platform should reflect your real processes, approvals and cost structures rather than forcing a rewrite of how you operate.
Consolidation, reconciliation and management reporting should be routine rather than a fortnight of manual work. Ask to see a month end demonstrated, not described.
Role-based permissions, approval workflows and a complete audit trail should be built in, so compliance is a by-product of daily work rather than a separate exercise.
Cloud platforms with standard processes go live in weeks rather than years. A long implementation is usually a sign the system is being bent into shape.
New sites, entities, currencies or product lines shouldn't need a replacement system. Check licensing and functionality for where you expect to be in five years.
Once you know what an ERP should do, the question becomes which platform fits how your teams already work. Microsoft Dynamics 365 Business Central brings finance, purchasing, stock, projects and reporting into one cloud system connected to the Microsoft tools you already use.
For publishers that means title level cost and revenue tracking, stock and warehouse control including returns, project accounting for development cost, deferred revenue for subscriptions, and Power BI dashboards for title and channel performance.
Industry extensions add royalty and rights handling, and standard APIs connect distribution and ecommerce platforms so sales data reaches finance automatically.
It isn't just an accounting package. These are the capabilities teams tell us make the biggest difference day to day.
Ledgers, budgets, cash flow and management reporting run from the same data, with Power BI dashboards leadership can open themselves rather than waiting for a pack.
AI drafts descriptions, reconciles bank entries, chases anomalies and answers questions about your data, taking a chunk of routine admin off the finance team.
Approvals, quotes and reports work inside Outlook, Teams and Excel, so people use the tools they already know instead of learning another interface.
Approvals, alerts and handovers can be automated with Power Automate using low-code tools your own team can maintain.
Role-based access, approval limits and full traceability protect the financial and operational data publishing businesses are accountable for.
Start with finance and operations, then add supply chain, projects, service or Dynamics 365 CRM as you grow - without another migration.
No. Editorial workflow and rights management stay where they are. The ERP handles cost, stock, revenue and reporting.
Base functionality plus publishing extensions support rate bands, advances and earn-out, producing statements from sales data.
Returns are recorded against the title and channel with provisions maintained, so net sales and royalty positions stay accurate.
Yes. Recurring billing with deferred revenue recognition spreads income across the subscription term.
Yes. Per user per month licensing suits a small finance team while still supporting title level reporting.
Tell us how title costs, royalties and returns are handled today and we'll talk through what an ERP would change, which capabilities matter most and where to start. No obligation, just a straight conversation.