Map and Validate ERP Order-to-Cash

Map and validate an ERP order-to-cash flow with live Business Central evidence.

Introduction

30 Second Summary

An emailed customer order can pass through several spreadsheets before anyone knows whether it shipped or was invoiced. One missed update leaves teams acting on different versions of the truth.

In this project, you will expose that manual failure before redesigning the order-to-cash flow through an ERP case study. Your final case study will connect standard Dynamics 365 Business Central capabilities to a live posted transaction with test evidence.

What You'll Build

You will present a five-slide transformation story that traces SO-002 from a manual status contradiction to a posted Business Central invoice backed by UAT evidence.

By the end of this project, you'll have:

A manual-process diagnosis that exposes conflicting order and invoice statuses for SO-002. Your as-is map pinpoints the duplicate entry behind the failure.
A fit-to-standard blueprint that classifies requirements as Fit, Configuration, or Needs Validation. Your to-be map shows how standard ERP capabilities control the order-to-cash flow.
A live ERP proof showing a sample sales order posted through shipment and invoicing. Your UAT case study connects the transaction evidence to requirements and recommendations.
Secret Mission: Post part of a sales order and prove that standard partial-shipment fields handle the remaining quantity without a custom workaround.

Are there any prerequisites?

No previous ERP access is required because the Business Central free trial provides sample data.

You need a Mac with an up-to-date Safari browser, a Google account with access to Google Sheets and Google Slides, plus a work or school email associated with a Microsoft 365 tenant.

Before We Start

Before the hands-on work begins, commit to the business problem your case study will prove. Your evidence will connect duplicate order tracking to conflicting statuses and show why a controlled ERP order-to-cash flow matters.

Set Up the Trial and Portfolio Workspace

You have defined the control failure that your case study needs to solve. The next task is to create a safe place for testing the replacement process.

A demonstration environment lets you test an ERP design without touching real company data. Named evidence files keep every finding connected to your final case study.

Microsoft Dynamics 365 Business Central provides the demonstration company. Google Sheets stores your analysis. Google Slides holds the presentation.

In this step, get ready to:

Confirm Safari can reach the Business Central trial page.
Start the free trial in a demonstration company with sample data.
Create the named workbook and presentation for your evidence.

Check Safari and reach the trial page

Safari receives later versions through compatible macOS updates. Loading the official product page confirms that your browser can reach the trial entry point.

Press Command-Space bar to open Spotlight.
Type Safari in the search field.
Press Return to open Safari.
Open the official Dynamics 365 Business Central product page.

You should see the Business Central product page with the Dynamics 365 Business Central free trial available.

Start the Business Central trial

The demonstration company keeps your work separate from real business records. Its sample data gives your later sales order test a safe starting point.

This project stays on the free trial throughout, so you do not need to choose a paid plan. The sign-up requires a work or school email.

The trial flow asks you to sign in with your organization account. Consumer addresses from outlook.com, hotmail.com, or gmail.com are not accepted.

Select the Dynamics 365 Business Central free trial from the product page.
Enter your confirmed work or school email.
Complete the sign-in prompts for your organization account.
Choose the demonstration company that contains sample data.
Leave the Business Central Role Center open in its Safari tab.

You should see the Role Center for the demonstration company. The Get Started card confirms that you are in the demo experience with sample data.

Can't Reach the Role Center?

Open System Settings from macOS search if Safari is reported as outdated.
Select General in the sidebar.
Select Software Update.
Install the latest compatible macOS update offered for your Mac.
Return to the free trial page after the update finishes.
Retry the sign-up with a work or school email if your personal email is rejected.
Still stuck? Help me reach the Business Central demonstration company in Safari.

Create the named portfolio files

Your workbook captures process evidence. Your presentation turns that evidence into a case study someone else can follow.

Google may ask you to sign in before it creates the first file. Use the Google account that provides your Sheets and Slides access.

Click the plus button in Safari's tab bar to create a new tab.
Enter sheets.google.com/create in the Smart Search field.
Press Return to create the spreadsheet.
Complete the Google sign-in flow if it appears.
Select the file title area in the upper-left corner.
Enter ERP Transformation Workbook as the workbook name.

You should see a blank Google Sheets workbook named ERP Transformation Workbook.

Click the plus button in Safari's tab bar to create another new tab.
Enter https://slides.google.com/create in the Smart Search field.
Press Return to create the presentation.
Select the file title area in the upper-left corner.
Enter ERP Transformation Case Study as the presentation name.

You should see a blank Google Slides presentation named ERP Transformation Case Study.

Before you check the full workspace, which three tabs do you expect to find?

Switch through the three Safari tabs to verify the complete workspace.

You should see the Business Central Role Center with sample company data. You should also see the blank workbook and blank presentation under their assigned names.

Your safe ERP workspace is ready. Next, you'll build a manual tracker that exposes the status mismatch your transformation needs to solve.

Expose the Manual Process Failure

Your safe workspace is ready. A credible ERP transformation needs evidence that the current process loses control when separate trackers rely on a manual handoff.

Google Sheets will represent the order log plus the invoice log. Google Slides will capture every handoff in an as-is process map.

You will deliberately stress the manual process. The result will expose its duplicate-entry risk before you introduce an ERP solution.

In this step, get ready to:

Build a matching pair of manual trackers.
Map the current order-to-cash handoffs.
Stress-test the status handoff to expose a contradiction.

Build the duplicate trackers

Separate trackers can look reliable while every row matches. This baseline gives you a fair test of what happens after the process starts moving.

The sheet tab menu is easy to miss. You will find it beside the sheet name at the bottom of the workbook.

Switch back to the ERP Transformation Workbook tab from earlier.
Use the first sheet tab's menu to rename it Order Log.
Enter Order ID, Customer, Amount, Owner, Status, plus Last Update across row 1.

You should see six headers across the first row of Order Log.

Baseline Records

Use SO-001 for Northwind School. Set the amount to $1,250. Set the owner to Jordan. Set the status to Open. Set the last update to 2026-11-09.
Use SO-002 for Alpine Outfitters. Set the amount to $2,380. Set the owner to Casey. Set the status to Open. Set the last update to 2026-11-09.
Use SO-003 for Harbor Retail. Set the amount to $975. Set the owner to Morgan. Set the status to Open. Set the last update to 2026-11-09.

Enter the three baseline records into rows 2 through 4.

You should see SO-001, SO-002, plus SO-003 with an Open status.

Use the Order Log sheet tab menu to make a copy of the tab.
Rename the copied tab Invoice Log.

You should now see matching Order Log plus Invoice Log tabs. Each tab should contain the same three fictional orders.

Map the as-is handoffs

The map shows how an order moves through the current process. Red re-entry points reveal where someone must copy information into another record.

Switch back to the ERP Transformation Case Study tab from earlier.
Click Insert in the top menu.
Choose Shape.
Add six shapes to the blank slide.
Label the shapes from left to right as Customer Email, Re-key Order, Order Log, Fulfillment Update, Invoice Log, plus Manual Payment Update.

You should see the six stages of the manual process laid out across the slide.

Click Insert in the top menu.
Choose Line.
Connect the six shapes from left to right.

You should see one continuous flow from the customer email to the manual payment update.

Select the Re-key Order shape.
Use the toolbar color control to make the shape red.

The first manual re-entry point should now stand out from the rest of the process.

Select the Invoice Log shape.
Use the toolbar color control to make the shape red.

Why Mark These Points Red?

The Re-key Order step copies customer information into the order tracker. The Invoice Log step copies fulfillment information into another tracker.

Each re-entry point depends on a person completing the next handoff. The red shapes show where the process can lose control.

Stress-test the manual handoff

The logs currently agree because they share the same baseline. The real test begins when fulfillment changes only one record.

Before you run the stress test, do you think two manually maintained logs will stay aligned after only one receives a fulfillment update?

Switch back to the ERP Transformation Workbook tab.
Select the Order Log tab.
Find the row for SO-002.
Change its Status from Open to Shipped.
Leave the Invoice Log unchanged.
Select the Invoice Log tab to inspect SO-002.

You should see SO-002 as Shipped in Order Log while it remains Open in Invoice Log. The designed contradiction proves that the manual process has no reliable status handoff.

You have caught the failure in action. SO-002 now carries two conflicting operational statuses.

Evidence becomes useful implementation material when it connects the visible symptom to the missing control.

Return to the ERP Transformation Case Study tab.
Click Insert in the top menu.
Choose Text box.
Add a text box that states the SO-002 status mismatch as the business problem.
Add a second text box that identifies the missing fulfillment-to-invoice handoff.

Your slide should now connect the red re-entry points to the visible status contradiction.

Before your final check, which two values should now disagree for SO-002?

Switch to the Order Log tab.
Confirm that SO-002 shows Shipped.
Switch to the Invoice Log tab.
Confirm that SO-002 shows Open.
Return to the ERP Transformation Case Study tab.
Confirm that the slide records the mismatch plus the missing handoff.

The workbook shows SO-002 as Shipped in Order Log. The same order remains Open in Invoice Log.

Your slide shows the six-step map with both re-entry points in red. The business problem identifies the SO-002 contradiction plus the missing handoff.

Do Both Logs Show the Same Status?

Return the Invoice Log value for SO-002 to Open if you changed it during the test.
Check that each tab contains one row for SO-002.
Still stuck? Help me create the intended SO-002 status contradiction in Google Sheets..

Your case study now has a visible control failure backed by evidence. Next, you will turn that evidence into a controlled ERP blueprint.

Design the Fit-to-Standard Blueprint

Your manual tracker now proves that one order can hold two statuses at the same time. The next goal is to turn that failure into a controlled Dynamics 365 Business Central design.

Recreating those spreadsheet handoffs inside Business Central would preserve the same waste. Fit-to-standard analysis starts with standard capabilities. It isolates items that need configuration or more evidence.

In this step, get ready to:

Build a decision matrix that connects requirements to Business Central capabilities.
Classify each requirement as Fit, Configuration, or Needs Validation.
Draw the to-be process with Adopt, Configure, and Validate recommendations.

Build the decision matrix

The Google Sheets matrix creates traceability between each business requirement and its design decision. Each row connects a process step to supporting evidence.

Switch back to ERP Transformation Workbook from earlier.
Use the add-sheet control at the bottom of the workbook to create one sheet.

You should see a new blank sheet beside the existing Order Log and Invoice Log tabs.

Double-click the new sheet tab.
Enter Fit-to-Standard as the tab name.

You should now see Fit-to-Standard on the workbook tab.

Enter these headers across row 1 in order: Process Step, Business Requirement, Business Central Capability, Decision, Resolution, Evidence, Risk, Test Status.

You should see eight populated header cells across row 1. The last header should be Test Status.

Classify the standard capabilities

A Fit decision needs evidence that the standard capability covers the requirement. Your demonstration company can provide the first piece of that evidence.

Switch back to the Business Central Role Center in Safari.
Select Search.
Enter Sales Orders.
Choose the related Sales Orders link.
Review the existing sample orders to confirm that the demonstration company holds orders on the standard page.

You should see sample sales orders listed on the standard page. Good work. That confirmation gives your first Fit row direct demonstration evidence.

Can't find Sales Orders?

Return to the Role Center before using Search.
Enter the full page name Sales Orders in the search field.
Still stuck? Help me find the Sales Orders page in my Business Central demonstration company. You can also ask the NextWork community with a screenshot that hides account details.

How do the decisions work?

A Fit means the observed standard behavior covers the requirement.
A Configuration means the standard capability needs business-specific setup.
A Needs Validation means the available evidence does not yet prove the requirement in this trial environment.

Use one row for each process point. The reference below follows the workbook's column order.

Use These Matrix Rows

Process Step: Order Entry. Business Requirement: Capture each customer request once. Business Central Capability: Sales Orders. Decision: Fit. Resolution: Adopt standard sales order entry. Evidence: Existing sample sales orders. Risk: Users continue duplicate tracking. Test Status: Observed.
Process Step: Fulfillment and Invoicing. Business Requirement: Ship and invoice from the same order. Business Central Capability: Post. Decision: Needs Validation. Resolution: Validate posting in the live trial. Evidence: Microsoft posting guidance. Risk: Posting remains unproven until the live test. Test Status: Planned.
Process Step: Receivables. Business Requirement: Trace the posted customer balance. Business Central Capability: Cust. Ledger Entries. Decision: Needs Validation. Resolution: Confirm the customer entry after posting. Evidence: Microsoft posting guidance. Risk: Ledger impact remains unproven. Test Status: Planned.
Process Step: Payment Application. Business Requirement: Apply a customer payment to an invoice. Business Central Capability: Cash Receipt Journals. Decision: Needs Validation. Resolution: Verify localization-specific journal and bank setup. Evidence: Microsoft receivables guidance. Risk: Local setup could block the test. Test Status: Not Run.
Process Step: Approval Controls. Business Requirement: Route sales orders for approval. Business Central Capability: built-in workflow configuration. Decision: Configuration. Resolution: Define approvers and approval limits. Evidence: Built-in workflow guidance. Risk: Missing user setup blocks approvals. Test Status: Planned.

Return to the Fit-to-Standard tab in ERP Transformation Workbook.
Enter the five mappings into rows 2 through 6.

You should now see Sales Orders, Post, Cust. Ledger Entries, Cash Receipt Journals, and built-in workflow configuration in the capability column.

The Decision column should contain Fit, Configuration, and Needs Validation.

Map the to-be process

The Google Slides to-be map turns the matrix into a process people can follow. It replaces duplicate re-entry with one connected order-to-cash flow.

Switch back to ERP Transformation Case Study from earlier.
Add one blank slide after the as-is process map.

You should see a blank slide after the slide that records the SO-002 mismatch.

Enter To-Be Order-to-Cash Process as the slide title.
Select Insert from the top menu.
Choose Shape.
Create five process boxes in a left-to-right row.

You should see five empty boxes beneath the to-be slide title.

Label the boxes from left to right as Customer Request, Sales Order, Shipment and Invoice Posting, Customer Ledger Entry, and Cash Receipt Journal.
Select Insert from the top menu.
Choose Line.
Connect each neighboring pair of process boxes.

You should see one continuous flow from Customer Request to Cash Receipt Journal.

The recommendation labels turn the process design into an implementation plan. Each label corresponds to one decision type in the matrix.

Select Insert from the top menu.
Choose Text box.
Add three text boxes below the process flow.
Populate the text boxes with Adopt: Use Sales Orders and Post as the standard flow, Configure: Set approvers and approval limits before enabling workflow, and Validate: Prove ledger and payment behavior in the trial.

You should now see the complete to-be flow with Adopt, Configure, and Validate recommendations beneath it.

Before you filter the matrix, do you expect every requirement to carry the same decision?

Return to the Fit-to-Standard tab.
Select the completed table.
Apply a filter with the spreadsheet's filter control.
Open the filter menu in the Decision column.
Select only Fit.

You should see the Order Entry row. Its Evidence cell should show Existing sample sales orders.

Change the Decision filter to Configuration.

You should see the Approval Controls row linked to built-in workflow configuration.

Change the Decision filter to Needs Validation.

You should see the fulfillment, receivables, and payment rows. Each row should contain a process step plus an evidence source.

Restore the filter to show all decision values.

You should see all five mappings with at least one Fit, one Configuration, and one Needs Validation decision. You have turned the manual failure into an evidence-backed ERP blueprint.

Decision Categories Missing?

Check that row 1 contains the exact header Decision.
Confirm that the filter includes rows 1 through 6.
Check the spelling of Fit, Configuration, and Needs Validation.
Still stuck? Help me troubleshoot the Decision filter in my Fit-to-Standard Google Sheets matrix.

Your blueprint now separates adopted standards from setup work and unproven assumptions. Next, you will test the core order flow in Business Central to replace those assumptions with posted evidence.

Validate the Core Sales Flow

Your fit-to-standard blueprint has replaced the broken spreadsheet handoffs with a controlled order-to-cash design. You have mapped each requirement to a standard capability or an honest validation boundary.

That blueprint remains a hypothesis until a real transaction produces evidence. In this step, you will create a sample order in Dynamics 365 Business Central and follow it through shipment and invoicing.

In this step, get ready to:

Create a sales order for an existing demonstration customer and inventory item.
Post the order as both shipped and invoiced.
Confirm the resulting shipment and invoice with credential-safe screenshots.

Create a demonstration sales order

Sales order processing keeps the customer request and item quantity together before anything reaches the ledgers. This creates a controlled source transaction for the live test.

Return to the Business Central Role Center from earlier.
Use Search to enter Sales Orders.
Choose the related link for Sales Orders.
Choose New on the Sales Orders page.
Select an existing demonstration customer in Customer Name.
Select an existing inventory item in No. on the Lines FastTab.
Enter 1 in Quantity.

You should see the selected customer in the order header. The line should show one inventory item with quantity 1 plus a calculated order total.

This screenshot becomes part of your case study evidence. Account credentials stay outside the image so the result is safe to keep or share.

Arrange the order page so the header and item line are visible with the total.
Capture a credential-safe screenshot of the order before posting.

Can't create the sales order?

Reselect an existing demonstration customer if the header fields remain blank.
Click inside the Lines FastTab if the item fields are unavailable.
Use the No. lookup to choose a different existing inventory item if your first selection is unavailable.

Still stuck? Help me create a demonstration sales order in Business Central.

Post the order as shipped and invoiced

Posting turns the editable order into recorded transaction evidence. The posting dialog lets you choose which parts of the transaction Business Central records.

Before you post, predict whether one posting action should create one posted document or two.

Open the Posting menu on the sales order.
Choose Post.
Select the posting option that covers both shipment and invoicing.
Confirm the posting action.

Business Central posts the order as a shipment and an invoice. The original transaction now has two linked pieces of operational evidence.

What does posting update?

Posting the completed order creates a shipment and invoice. It also updates the customer account.

The transaction reaches the general ledger and item ledger entries. One posting action keeps the operational documents connected to their accounting impact.

Posting blocked?

Return to the order if Business Central highlights a required field.
Complete the highlighted field with demonstration data.
Choose a different existing sample item if the page reports an inventory-related problem.

Need another set of eyes? Help me troubleshoot this Business Central posting problem.

Verify the posted documents

Posted documents provide the audit trail that the manual trackers could not maintain. You will trace the transaction through its shipment record and invoice record.

Use Search to enter Posted Sales Shipments.
Choose the related link for Posted Sales Shipments.
Open the newest shipment for the customer you selected.

You should see the selected customer and inventory item on the posted shipment. The shipped quantity should be 1.

Capture a credential-safe screenshot of the posted shipment.
Use Search to enter Posted Sales Invoices.
Choose the related link for Posted Sales Invoices.

Before you open the newest invoice, predict which values should match the sales order you created.

Open the newest invoice for the customer you selected.

You should see the same customer and inventory item on the posted invoice. The document should also show quantity 1 plus the posted total from your transaction.

That proves the blueprint with live ERP evidence. Your sample order has moved through shipment and invoicing without a duplicate tracker.

Capture a credential-safe screenshot of the posted invoice.

Can't find the posted documents?

Check the customer name when several posted documents have similar dates.
Match the inventory item and quantity 1 to your original order.
Return to the sales order list if no matching documents appear.

Still missing the transaction? Help me trace my posted Business Central sales order.

Your core sales flow is now backed by posted ERP evidence. Next, you will connect that evidence to requirements and package it as a UAT case study.

Package the UAT Case Study

Your ERP blueprint now has live evidence from Dynamics 365 Business Central. The posted shipment plus invoice prove that the standard order flow works for a quantity of 1.

Screenshots alone cannot prove implementation skill. They need a clear link to the requirement being tested.

A user acceptance testing record connects each requirement to an expected result. It also records the observed result plus decision.

In this step, get ready to:

Record the posted-order test as Passed.
Document the payment-application test as Not Run.
Package the evidence into a five-slide portfolio story.

Build the UAT record

A UAT table creates traceability from a requirement to its evidence. Clear columns make each test decision reproducible.

How does the UAT table work?

Each column answers one audit question about the test.

Use Test ID as the unique reference for the test.
Use Requirement for the business behavior being validated.
Use Preconditions for the required starting state.
Use Test Actions for the steps performed by the tester.
Use Expected Result for the intended system behavior.
Use Actual Result for the observed system behavior.
Use Status for the evidence-backed outcome.
Use Evidence Link for the location of supporting proof.
Use Follow-up Decision for the next implementation decision.

Switch back to the ERP Transformation Workbook tab from earlier.
Click the plus icon beside the existing sheet tabs to add a blank sheet.
Rename the new sheet UAT.

You should see a blank UAT tab beside the existing workbook tabs.

Enter the nine callout headers across row 1 from A1 through I1.

Use this field map for the posted-order test

Set Test ID to UAT-001.
Set Requirement to posting a sales order with 1 in Quantity as shipped plus invoiced.
Set Preconditions to an existing demonstration customer plus an existing inventory item.
Set Test Actions to creating the sales order with 1 in Quantity. Record posting it as shipped plus invoiced. Record opening Posted Sales Shipment. Record opening Posted Sales Invoice.
Set Expected Result to a posted shipment plus invoice showing the selected customer. Include the item. Include quantity 1. Include the posted total.
Set Actual Result to the confirmed customer. Include the item. Include quantity 1. Include the posted total from both posted documents.
Set Status to Passed.
Set Evidence Link to ERP Transformation Case Study slide 5.
Set Follow-up Decision to adopting the standard sales order posting flow.

Enter the field map from the callout across row 2.
Review row 2 from left to right for a complete requirement-to-decision trail.

You should see UAT-001 with a Passed status. The row now explains why the screenshots count as test evidence.

Having trouble with the UAT row?

Check that row 1 contains all nine headers in the same order as the callout.
Check that the Passed status belongs to the posted-order test in row 2.
Still stuck? Help me check the traceability of my posted-order UAT row.

Define the untested payment boundary

A credible UAT record shows where live testing stopped. The payment-application test stays unexecuted until the trial's localization-specific bank plus journal setup is verified.

Use this field map for the payment test

Set Test ID to UAT-002.
Set Requirement to applying a customer payment through Cash Receipt Journals.
Set Preconditions to verified localization-specific bank plus journal setup.
Set Test Actions to using Search to open Cash Receipt Journal. Record choosing Edit Journal. Record setting Document Type to Payment. Record setting Account Type to Customer. Record setting Bal. Account Type to Bank Account. Record selecting Applies-to Doc. No..
Set Expected Result to a posted application that closes the customer ledger entries. The Open field should clear.
Set Actual Result to the test remaining unexecuted because the required setup has not been verified.
Set Status to Not Run.
Set Evidence Link to no live evidence because the test was not run.
Set Follow-up Decision to validating the localized setup before executing the test.

Enter the payment test from the callout across row 3.
Compare the Status cells in rows 2 plus 3.

You should see Passed for the posted-order test. You should see Not Run for the payment-application test.

Why record a test you did not run?

The Not Run status preserves the boundary between demonstrated behavior plus planned validation. It prevents an unverified environment assumption from becoming a false success claim.

Complete the five-slide story

Your Google Slides deck should move from business pain to evidence-backed recommendation. Each slide advances one part of that story.

What belongs on each slide?

Slide 1 is Business Problem. Use the commitment statement about conflicting statuses plus weak controls.
Slide 2 is As-Is Failure. Show the red-marked duplicate-entry points plus the SO-002 mismatch.
Slide 3 is Fit-to-Standard Decisions. Show examples classified as Fit. Show one Configuration example. Show one Needs Validation example.
Slide 4 is To-Be Process. Show the ERP flow plus the Adopt, Configure, plus Validate recommendations.
Slide 5 is UAT Evidence and Recommendation. Show both UAT statuses. Recommend the standard posting flow. Preserve payment application as a follow-up test.

Switch back to ERP Transformation Case Study from earlier.
Add blank slides until the left filmstrip shows exactly five slides.

You should see five slide thumbnails in the filmstrip.

Build slide 1 as Business Problem with your one-sentence problem statement.
Place the existing as-is map on slide 2 under the title As-Is Failure.

Slides 1 plus 2 should now establish the control problem before any ERP recommendation appears.

Build slide 3 as Fit-to-Standard Decisions with one example for each decision category.
Place the existing to-be map on slide 4 under the title To-Be Process.

Slides 3 plus 4 should now connect the fit-to-standard decisions to the redesigned process.

Build slide 5 as UAT Evidence and Recommendation with the two UAT statuses plus the follow-up decision.

Slide 5 should distinguish the validated posting flow from the untested payment-application boundary.

Click Insert in the Google Slides menu.
Select Image.

You should see the available image source options.

Choose the image source that lets you select files from your Mac.
Select the credential-safe order screenshot plus the posted shipment screenshot plus the posted invoice screenshot.

You should see all three Business Central screenshots on slide 5 without any account credentials.

Switch back to the ERP Transformation Workbook browser tab.
Copy the workbook URL from Safari's Smart Search field.

The workbook address is now ready to attach to the final slide.

Return to the ERP Transformation Case Study browser tab.
Select the text ERP Transformation Workbook on slide 5.

The workbook text should now be selected on the final slide.

Apply the copied workbook URL with the link control in the toolbar.

You should see the workbook text displayed as a link on slide 5.

Before you present the deck, which slide should make the boundary between validated behavior plus untested behavior easiest to see?

Return to slide 1 in the left filmstrip.
Start presentation mode from the top-right toolbar.

You should see five slides in the planned order. The story moves from Business Problem to As-Is Failure.

Next you should see Fit-to-Standard Decisions followed by To-Be Process. The final UAT Evidence and Recommendation slide should show both test statuses.

You should also see the workbook link plus the three Business Central evidence screenshots.

Missing evidence from the final slide?

Check that the workbook text was selected before you applied the copied URL.
Return to Insert if an image is missing. Choose Image to add the missing screenshot.
Still stuck? Help me check the evidence slide in my ERP transformation case study.

That is the portfolio package complete. Your case study now separates proven ERP behavior from the next environment-specific test.

Secret mission

Prove the Partial-Shipment Exception

A complete order proves the happy path. This challenge tests staged fulfillment by posting one unit from an order of three while keeping two units available for later fulfillment.

Clean Up Your Resources

This project uses a Dynamics 365 Business Central free trial alongside your existing Google access at no additional cost. Decide whether to keep the evidence available, pause your work, or delete the resources entirely.

Resources you used:

Business Central trial tenant containing the original posted sales transaction plus the partial-shipment order and its posted evidence.
Google Sheets workbook named ERP Transformation Workbook.
Google Slides presentation named ERP Transformation Case Study.
Credential-safe order and posting screenshots saved in Google Drive.

Keep everything running

No action is needed. Choose this option if you want to continue testing the demonstration company or presenting the finished case study.

Keep using the Business Central demonstration company while the trial remains active.
Retain ERP Transformation Workbook in Google Drive as your requirements and UAT record.
Retain ERP Transformation Case Study in Google Drive as your presentation-ready portfolio deck.
Keep the credential-safe screenshots with the workbook and presentation.

Microsoft considers a Business Central trial expired after 45 unused days. Microsoft then deletes its tenant.

Pause - I'll come back to this later

Preserve your portfolio evidence while you step away from the live trial. Your Google files remain available when you return.

Save local copies of ERP Transformation Workbook through the file's download option.
Save a local copy of ERP Transformation Case Study through the file's download option.
Save local copies of the credential-safe screenshots on your Mac.
Keep the online originals in Google Drive.
Stop using the Business Central trial after saving the evidence you need.

A Business Central trial left unused for 45 days is considered expired. Its tenant is deleted.

Delete - I don't want to use this again

This option removes the online project resources. It suits you when you have finished using the tenant and portfolio files.

Save local copies of ERP Transformation Workbook if you want an offline archive.
Save a local copy of ERP Transformation Case Study if you want an offline archive.
Save the credential-safe screenshots on your Mac if you want to preserve the transaction evidence.
Ask your Microsoft 365 administrator to cancel the Business Central trial subscription in the Microsoft 365 admin center.
Move the Google Sheets file named ERP Transformation Workbook to trash in Google Drive.
Move the Google Slides file named ERP Transformation Case Study to trash in Google Drive.
Move the core sales-order screenshot plus the posted-document and partial-shipment screenshots to trash in Google Drive.
Empty Google Drive trash after confirming that it contains only files you want to delete.

Nice Work!

That is a substantial transformation project complete. You built an evidence-backed ERP case study that traces a broken manual process through a validated order-to-cash design.

You've learned how to:

Build an as-is diagnosis by exposing contradictory statuses across the Order Log and Invoice Log. You mapped the duplicate-entry points that created the control failure.
Apply fit-to-standard analysis to classify requirements as Fit, Configuration, or Needs Validation. You translated those decisions into a to-be process mapped to standard Dynamics 365 Business Central capabilities.
Produce live ERP evidence by posting a demonstration sales order through shipment and invoicing. You packaged the results into a five-slide UAT case study with traceable evidence and honest testing boundaries.
Complete the optional Secret Mission by posting 1 unit from an order quantity of 3 with Qty. to Ship and Qty. to Invoice. You proved that two units could remain open for later fulfillment without a custom workaround.

Ready to quiz yourself?