An ERP cut-over that doesn't land on month-end close.
ERP projects fail at the edges, in the interface to CRM, the vendor master nobody cleaned, or the approval that lived in someone's inbox. We implement Dynamics 365 Finance and Business Central, integrate SAP, and plan migrations around the finance calendar.
CRMSalesforce · Dynamics 365 SalesBanks and supplierspayments · statements · EDI
02 · ERP
ERPD365 Finance · Business Central · SAPMaster datacustomers · vendors · items
03 · Controls
Roles and SoD rulescreate vendor ≠ approve paymentIdentity governanceSailPoint · Entra ID Governance
04 · Reporting
Finance warehouseGL · subledgers · Snowflake
Microsoft Dynamics 365Microsoft Power PlatformSalesforceSnowflake
in short·15-second read
ERP systems run finance, procurement, inventory and operations.
Cohash implements Microsoft Dynamics 365 Finance, Supply Chain Management and Business Central, integrates SAP and other ERPs with CRM and data platforms, and migrates master and transactional data. For SAP ECC customers, mainstream maintenance ends at the end of 2027, so we also help plan what comes next.
you probably need this if
The go-live date your vendor proposed lands in the week of quarter-end close.
The vendor master holds three records for the same supplier with different bank details.
One person can create a vendor and approve its payment without anyone noticing.
terms on this pageSegregation of dutiesdefinitionA rule that no one person should hold two powers that together allow fraud, such as creating a vendor and approving payment to it.explained in a field note →
From the first call to a setup your own team can run.
Here's what usually prompts a call about your ERP Systems, what we do about it and in which order, and where you end up.
01 · where it hurts02 · what we change03 · how it runs04 · where you end up
incident board · erp systems3 open
openThe go-live date your vendor proposed lands in the week of quarter-end close.
recurringThe vendor master holds three records for the same supplier with different bank details.
blockedOne person can create a vendor and approve its payment without anyone noticing.
exposure
Dynamics 365 Finance and…Master data clean-upERP and CRM integrationSAP ECC planningSegregation of duties in ERPFinance data for reporting
startrehearsehandover
Discovery
Design
Build and rehearse
Cut-over and hypercare
we are here
ready to hand over
The decision rests on how much custom code is really in use and which interfaces have to…
The new ERP starts with one record per supplier and bank details someone has verified.
The first close starts from reconciled opening balances.
Fit-gap analysis and target process designs
chapter 01 · where it hurts
Why teams reach out
The go-live date your vendor proposed lands in the week of quarter-end close.
The vendor master holds three records for the same supplier with different bank details.
One person can create a vendor and approve its payment without anyone noticing.
chapter 02 · what we change
How we solve it
Dynamics 365 Finance and Business Central
Master data clean-up
ERP and CRM integration
SAP ECC planning
Segregation of duties in ERP
Finance data for reporting
chapter 03 · how it runs
Our approach
Discovery
Design
Build and rehearse
Cut-over and hypercare
chapter 04 · where you end up
What changes
The decision rests on how much custom code is really in use and which interfaces have to survive.
The new ERP starts with one record per supplier and bank details someone has verified.
The first close starts from reconciled opening balances.
Fit-gap analysis and target process designs
what we do
Where we spend the hours
6 areas of work, each one done by an engineer who has run it in production.
Chart of accounts, dimensions, posting setup and approval workflows, set up around how your finance team actually closes the books.
Before migration we profile and deduplicate customers, vendors, items and the chart of accounts. Every domain gets an owner.
We sync quotes, orders, invoices and credit status between ERP and Salesforce or Dynamics 365 Sales. One system owns each field.
An inventory of custom code, interfaces and reports to inform the choice between S/4HANA, another ERP or extended maintenance, which SAP offers through 2030.
Security roles designed so the person who creates a vendor can't also approve its payment, tied to identity governance where you have it.
General ledger, subledger and operational data landed in the warehouse with conformed dimensions for finance reporting.
capability 01 / 06in production
Dynamics 365 Finance and Business Central
Chart of accounts, dimensions, posting setup and approval workflows, set up around how your finance team actually closes the books.
An inventory of custom code, interfaces and reports to inform the choice between S/4HANA, another ERP or extended maintenance, which SAP offers through 2030.
We pieced these together from ERP Systems situations that come up a lot. They're patterns. You won't find a specific client in them.
case file 01
SAP ECC, thousands of custom ABAP objects and a 2027 date
composite · not a client story
Beforethe situation
An SAP ECC system carries thousands of custom ABAP objects and a dozen interfaces to banks and warehouses. Finance also has reports it refuses to give up. Mainstream maintenance ends at the end of 2027, and the board wants a decision this year.
What we dothe work
Usage data shows which custom objects actually run. Interfaces are cataloged with owners, and we check which of finance's reports a standard S/4HANA or alternative ERP report would cover. Then we price the options: S/4HANA, a different ERP, or extended maintenance to 2030 while you prepare.
Afterwhere you end up
The decision rests on how much custom code is really in use and which interfaces have to survive. Leadership compares the paths side by side instead of reacting to one vendor's proposal.
case file 02
Duplicate suppliers with different bank details before go-live
composite · not a client story
Beforethe situation
We profile the vendor master ahead of a Business Central go-live and find suppliers entered several times under different names. Some of those duplicates have different bank account numbers. Finance thinks fraud first.
What we dothe work
We match vendors on tax ID, address and bank details, and procurement picks the survivor. Any changed bank details get checked by phoning a known contact before migration. From then on, bank changes need approval, and the person who creates a vendor can't approve its payments.
Afterwhere you end up
The new ERP starts with one record per supplier and bank details someone has verified. A bank account change needs a second person, so one compromised login can't redirect payments.
case file 03
Finance go-live proposed for the last week of a quarter
composite · not a client story
Beforethe situation
The integrator wants Dynamics 365 Finance live in the final week of a fiscal quarter. Three legal entities move at once, with intercompany postings and open purchase orders in flight.
What we dothe work
Cut-over moves to the start of a period, and we plan backward from there with full-volume mock loads, trial balance and open-item reconciliation per entity, and a posting freeze agreed with finance. Close support for the first period on the new system is planned as well.
Afterwhere you end up
The first close starts from reconciled opening balances. Go-live and quarter-end reporting no longer compete for the same people.
Where the ERP sits between CRM, finance controls and reporting
Orders and customers flow from CRM into the ERP, which posts them to the ledger and syncs invoices and credit status back. Identity governance enforces separation of duties on ERP roles, and finance data lands in the warehouse.
Identity governanceSailPoint · Entra ID Governance → Roles and SoD rules · role assignments
04 · Reporting
Finance warehouseGL · subledgers · Snowflake
Read the diagram as text
CRM → ERP: orders and customers
ERP → CRM: invoices and credit
Banks and suppliers → ERP: payments and statements
Master data → ERP: clean master data
Identity governance → Roles and SoD rules: role assignments
Roles and SoD rules → ERP: security roles
ERP → Finance warehouse: ledger extracts
how it runs
A typical engagement
We don't start a step until the last one has produced something you can check.
step 01
Discovery
No estimate until we've mapped processes, interfaces, data volumes and the fiscal calendar.
step 02
Design
We run the fit-gap, design target processes and security roles, and agree a migration approach. Finance and operations sign it off.
step 03
Build and rehearse
Configuration, integrations and migration scripts built, then rehearsed with full data loads until balances reconcile.
step 04
Cut-over and hypercare
Go-live timed away from close, followed by close support and handover.
you keep
What you're left with
We write these for your ERP Systems setup, and they're working documents. Your team should be able to keep things running from them long after we've gone.
design01
Fit-gap analysis and target process designs
yours to keep
inventory02
Data migration mapping and reconciliation reports
yours to keep
document03
Integration specifications for CRM, banking and data platforms
Some clients want a project team, some want a couple of engineers on theirs. Either works. Onsite, nearshore or offshore, with handovers across time zones that keep things moving.
Put these to anyone bidding on your ERP Systems work. The ones who've done it answer differently from the ones who've read about it.
Q1
How many full mock cut-overs will we run, and what must reconcile before go-live?
Trial balances and open items that reconcile in rehearsal are the best sign of a clean go-live. Agree the reconciliation criteria, and who signs them, before the first mock load.
Q2
How will you find out which of our custom code is actually used?
ECC systems often carry custom objects nobody runs. Usage data cuts a S/4HANA or replacement estimate down to the code that matters.
Q3
Which segregation-of-duties conflicts will the role design prevent, and how is that tested?
Creating a vendor and approving its payment in one role is the classic ERP fraud path. Roles should be tested against a conflict matrix before go-live, not after the first audit.
Q4
When does SAP maintenance end under our specific contract?
SAP's end-2027 mainstream date and 2030 extended option are for Business Suite 7 in general. What applies to you comes down to your enhancement pack and your contract terms.
Q5
Who owns the CRM integration after go-live, and how is it monitored?
Quotes, orders and credit status cross the CRM and ERP boundary daily. Without a named owner and alerting, sync failures show up as customer complaints.
01When does SAP ECC support end?
SAP has said core SAP Business Suite 7 applications, which include ECC, receive mainstream maintenance until the end of 2027, with optional extended maintenance until the end of 2030. Check your own contract and enhancement-pack level with SAP.
02Business Central or Dynamics 365 Finance?
Business Central suits smaller and mid-sized companies with simpler structures. Finance and Supply Chain Management suits multi-entity, multi-currency operations with heavier supply chain needs. We compare your entities, volumes and processes before recommending one.
03How long does an ERP implementation take?
It depends on the number of legal entities, modules, integrations and the quality of the data you're moving. We estimate after discovery, and we schedule cut-over around your close calendar.
04Do you also handle the reporting after go-live?
Yes. We land ERP data in your warehouse and build finance models and reports, or connect embedded reporting inside the ERP.
05Can you connect an ERP we're keeping to a new CRM?
Yes. That's common when finance isn't ready to move. We define which system owns customers, products, prices and credit status, then build the sync through APIs or the middleware you already run.
related
Often paired with
Projects on ERP Systems usually end up touching one of these, so they're worth a look.
