Ecommerce / SaaS · United Kingdom
Meridian put Books, Revenue, and CRM on one identity so ASC 606 and the board pack stop living in a private spreadsheet.
Multi-entity · subscription + commerce
Executive summary
Finance finally sees the same customer the CRM sees — one record, one truth.
The challenge
Rev rec and CRM were different truths. Board packs took a week of reconciling.
Subscriptions drifted from invoices. Tax was a third system.
Auditors asked for three exports and a narrative bridge.
Stack change
What the team stopped using - and what runs on CEDX.
The change
Books, Revenue, Subscriptions, and Tax share identity with CRM.
Close checklists run on live data — not a rebuilt model.
Board pack is a scheduled export with a single customer key.
Outcomes
Results used as pilot targets - the shape of success, not vanity dashboards.
Team impact
Close on live data.
Schedules on real contracts.
One number in the board pack.
Why an estate
Sales, service, and finance stop arguing about whose record is authoritative.
Operators do not maintain six passwords and six partial truths.
What you evaluate on the website is the build you implement.
Start with one motion; add products without a second platform.
Rollout
Typical shape - your pilot may compress or expand by product footprint.
Books + entities
Multi-entity chart and open periods.
Revenue + Subs
ASC 606 schedules on live contracts.
CRM link
Customer graph unified.
Tax + audit pack
Scheduled truth for the board.
Risks
Your next 90 days
Same skeleton Harbor, Northline, and Atlas-shaped programs use.
Estate map
Sponsor, operators, systems list, retire list, pilot metrics.
Pilot live
One pod or region on production-shaped config.
Expand wave
Second region or adjacent product family.
Hypercare exit
Metrics review, owner map, BAU support path.
In the room
Meridian Commerce runs day-to-day work in CEDX - the same apps you can open from every product page.
FAQ
It is an illustrative composite on live demo tenants. Named case studies publish with customer approval.
Yes. Products in this scenario: Books, Revenue, Subscriptions, CRM, Tax.
CEDX, a consulting partner, or both - decided in the estate map.
Architecture notes
One login for operators in scope. Entitlements follow the product graph.
Customer graph ownership is written in the estate map before imports.
Prefer estate events and first-party connectors over brittle nightly CSV.
Commercial shape
Products in the first motion, seats for the pod, success metrics, hypercare window.
Wave-two products and regions after metrics clear - written in the original map when possible.
Related scenarios
Harbor put POS, CRM, inventory, and desk on one login so store close and support share the same customer.
B2B servicesNorthline collapsed six tools into one estate so new reps quote, sign, and bill on the same customer graph.
LogisticsAtlas put field jobs, parts, and contact-center voice on one desk record across three provinces.
Thirty minutes. Products, retire list, and pilot metrics - before anyone configures.
