How Unit4's requisition-to-pay and contract-based billing map to D365's purchase and sales frameworks — and why the migration must deliberately assign each revenue stream to Sales and marketing, Project management and accounting, or Subscription billing.
Unit4's commercial operations model is tailored to the organisations it serves: public-sector procurement with approval workflows and budget encumbrances, professional-services billing from project and timesheet activity, and subscription or retainer revenues for ongoing advisory arrangements.
Unit4's procurement cycle runs: Requisition → Purchase Order → Goods Receipt → Supplier Invoice → Match-and-Approve → Payment. The Account + Attribute coding on each PO line carries through the entire cycle, posting to the GL at goods receipt (accrued-not-invoiced) and then reversing at invoice match.
Unit4's revenue comes from three primary sources in most organisations: project-based billing (time-and-materials, milestones, fixed-fee), recurring contract billing (retainers, subscriptions, maintenance fees), and occasional product or service sales not tied to a specific project. D365 has a dedicated module for each.
Unit4's pricing model is typically a single default price per article or charge code, sometimes overridden on a PO or SO line. D365's trade agreement framework is a structured pricing layer that sits above the released product and is evaluated at order entry:
Charges in D365 are the mechanism for adding non-item costs to purchase orders or sales orders — freight, insurance, customs, handling fees. Charges can be added at header or line level, can be debited to inventory or expensed directly, and can be allocated across lines by value, weight or quantity.
Multi-entity Unit4 customers using intercompany billing between Companies find that D365 automates much of what they currently do manually. D365 intercompany trade works as follows: a selling legal entity creates a sales order for an intercompany customer (the buying entity).
D365's trade capability covers Unit4's procurement and billing patterns and adds considerable structure around pricing, matching, subscription revenue and intercompany automation. The migration is broadly close for procurement; the primary design work is in assigning each revenue stream to the right D365 module.