CEDX
Ecommerce / SaaS · United Kingdom
Meridian Commerce
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
- Industry
- Ecommerce / SaaS
- Region
- United Kingdom
- Footprint
- Multi-entity · subscription + commerce
- Products live
- Books, Revenue, Subscriptions, CRM, Tax
- Primary metric
- <24h month-end close
- Scenario type
- Illustrative reference
Executive summary
At a glance
- Multi-entity SaaS + commerce with ASC 606 in a private model.
- Pilot: Books + Revenue + Subscriptions linked to CRM.
- Target: sub-24h standard close; one audit export.
Finance finally sees the same customer the CRM sees — one record, one truth.
The challenge
What was broken
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
Before and after
What the team stopped using - and what runs on CEDX.
Before
- CRM ≠ books
- Side rev-rec model
- Three audit exports
After on CEDX
- Books + Revenue + Subs + Tax + CRM
- Live close checklists
- Single board pack export
The change
What CEDX replaced
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
What changed on the floor
Results used as pilot targets - the shape of success, not vanity dashboards.
- Month-end is same-day for standard periods.
- Auditors get one export, not three.
- Sales and finance stop debating who the customer is.
Team impact
Who feels the change
Controller
Close on live data.
Rev accountant
Schedules on real contracts.
CEO
One number in the board pack.
Why an estate
Why not another point tool
One customer graph
Sales, service, and finance stop arguing about whose record is authoritative.
One login
Operators do not maintain six passwords and six partial truths.
Live product demos
What you evaluate on the website is the build you implement.
Wave-ready architecture
Start with one motion; add products without a second platform.
Rollout
How they got live
Typical shape - your pilot may compress or expand by product footprint.
Phase 1
Books + entities
Multi-entity chart and open periods.
Phase 2
Revenue + Subs
ASC 606 schedules on live contracts.
Phase 3
CRM link
Customer graph unified.
Phase 4
Tax + audit pack
Scheduled truth for the board.
Risks
What this design avoids
- Shadow spreadsheets reappear when systems disagree — the estate is designed so the live number is the board number.
- Tool sprawl after the pilot — success criteria and hypercare keep the team on one stack.
- Training debt — enablement uses the live product, not a parallel slide deck of screenshots.
Your next 90 days
Playbook you can copy
Same skeleton Harbor, Northline, and Atlas-shaped programs use.
Days 1–14
Estate map
Sponsor, operators, systems list, retire list, pilot metrics.
Days 15–45
Pilot live
One pod or region on production-shaped config.
Days 46–75
Expand wave
Second region or adjacent product family.
Days 76–90
Hypercare exit
Metrics review, owner map, BAU support path.
In the room
Software that respects the people running it
Meridian Commerce runs day-to-day work in CEDX - the same apps you can open from every product page.
FAQ
About this scenario
Is this a named public case study?
It is an illustrative composite on live demo tenants. Named case studies publish with customer approval.
Can we pilot the same products?
Yes. Products in this scenario: Books, Revenue, Subscriptions, CRM, Tax.
Who implements?
CEDX, a consulting partner, or both - decided in the estate map.
Architecture notes
What sits under the pilot
Identity
One login for operators in scope. Entitlements follow the product graph.
Data
Customer graph ownership is written in the estate map before imports.
Integrations
Prefer estate events and first-party connectors over brittle nightly CSV.
Commercial shape
How programs are usually bought
Pilot SKU
Products in the first motion, seats for the pod, success metrics, hypercare window.
Expansion
Wave-two products and regions after metrics clear - written in the original map when possible.
Related scenarios
More operators on the estate
Harbor Retail Group
Harbor put POS, CRM, inventory, and desk on one login so store close and support share the same customer.
B2B servicesNorthline Systems
Northline collapsed six tools into one estate so new reps quote, sign, and bill on the same customer graph.
LogisticsAtlas Cold Logistics
Atlas put field jobs, parts, and contact-center voice on one desk record across three provinces.
Map a ecommerce / saas program like Meridian Commerce
Thirty minutes. Products, retire list, and pilot metrics - before anyone configures.