MS Dynamics 365 Business Central - Company Setup New Entity Set up

Cliente Freelancer · Remoto · Remoto · freelance · mid · 30–250 AUD

Publicada el 2026-07-28

Descripción de la oferta

Appendix A – Work Order Template WORK ORDER Microsoft Dynamics 365 Business Central — New Entity Setup (3 Companies) 1. Work Order Details Work Order Number: [WO-1256] Project Name: New Company Setup – ARO Investments, Noru NZ & Noru SG (Existing Daleys Business Central Tenant) Client: Daley’s Group 2. Project Period Start Date: [28-07-2026] Indicative End Date: [] (Indicative duration: 2–3 weeks across Sandbox, UAT and Production go-live) Note: The indicative end date is based on current planning assumptions and may be adjusted upon mutual agreement, particularly around client data-readiness and go-live cut-off timing. 4. Description of Activities The Vendor shall perform the following activities to set up three (3) new companies — ARO Investments, Noru NZ and Noru SG — within the Client's existing Microsoft Dynamics 365 Business Central tenant. All three entities will share a common Chart of Accounts framework, with entity-specific customer and vendor master data, tax/statutory setup, and opening balances. 4.1 Scope of Activities Phase 1 – Sandbox Build (New Companies in Existing BC Tenant) ● Create three new company records (ARO Investments, Noru NZ, Noru SG) within the existing Sandbox environment of the Daleys Business Central tenant. ● Configure Company Information for each entity: legal name, registered address, tax/GST registration numbers, fiscal year and accounting periods. ● Design and build the shared Chart of Accounts once, then replicate across all three companies via Configuration Packages, adjusting G/L account categories and posting groups where local statutory reporting requires it. ● Configure General Ledger setup common to all entities: General Posting Setup, General Business/Product Posting Groups, Source Codes, Number Series, and Global/Shortcut Dimensions — kept consistent across entities to enable group-level consolidated reporting. ● Configure jurisdiction-specific GST/VAT posting setup and statutory tax reporting (New Zealand GST, Singapore GST/IRAS requirements). ● Set up multi-currency (NZD, SGD and group reporting currency), including exchange rate tables/services. ● Configure bank accounts and bank/GL reconciliation setup for each entity. ● Inventory module setup: Item Templates, Item Categories, Units of Measure, Locations, Inventory Posting Setup/Groups and Item Journal templates — configured structurally for all three entities regardless of current item volume. ● Accounts Payable (AP) setup: Vendor Posting Groups, Payment Terms, Payment Methods, Vendor Templates, Vendor Bank Accounts, and purchase approval workflows. ● Accounts Receivable (AR) setup: Customer Posting Groups, Payment Terms, Payment Methods, Customer Templates, Finance Charge Terms, and sales approval workflows. ● Master data build and migration – ARO Investments: cleanse, map and import the full customer and vendor master base (names, addresses, tax IDs, payment terms, bank details) using Configuration Packages / RapidStart. ● Master data build and migration – Noru NZ & Noru SG: import the smaller customer and vendor master lists for each entity, validated to the same data-quality standard applied to ARO Investments. ● User security setup: permission sets, user-to-company assignment, and approval workflow configuration per entity. ● Intercompany setup where trading occurs between the three entities: Intercompany Chart of Accounts mapping and IC partner setup. ● Load indicative opening balances into Sandbox for test purposes: GL trial balance journal, AP/AR opening transactions, opening inventory quantities/values, and opening bank balances — used to validate the configuration end-to-end. Phase 2 – User Acceptance Testing (UAT) ● Refresh/copy the validated Sandbox configuration into a dedicated UAT environment. ● Prepare and execute UAT test scripts covering: GL posting and financial reporting, AP invoice-to-payment cycle, AR order-to-cash cycle, inventory transactions, opening balance reconciliation, GST/VAT return generation, and financial statement outputs (Trial Balance, Balance Sheet, P&L) for each of the three entities. ● Log, triage and resolve UAT defects; re-test as required. ● Obtain formal Client UAT sign-off, per entity, before proceeding to Production. Phase 3 – Production Environment & Go-Live ● Provision a new Production environment and create the three companies in Production, replicating the UAT-validated configuration (Chart of Accounts, posting groups, dimensions, tax setup, templates, security). ● Execute the cutover plan: freeze legacy-system transactions and extract final opening balances as at the agreed go-live cut-off date. ● Load final opening balances into Production for all three entities: GL trial balance, AP/AR subledger opening balances (open invoices/credit notes), opening inventory quantities and values, and opening bank balances. ● Reconcile the opening Trial Balance against legacy/source records prior to go-live sign-off. ● Execute go-live cutover across ARO Investments, Noru NZ and Noru SG. ● Provide post go-live hypercare support: first month-end close, first GST/VAT return cycle, and issue resolution. 4.2 Deliverables ● Three (3) new companies live in Business Central (ARO Investments, Noru NZ, Noru SG) on a shared Chart of Accounts framework. ● Configured Inventory, Accounts Payable and Accounts Receivable modules for each entity. ● Migrated and validated customer/vendor master data for all three entities. ● Opening balances loaded, tested and reconciled — Sandbox test load, UAT-validated load, and final Production go-live load. ● UAT test scripts and sign-off documentation. ● Cutover and go-live checklist. ● Post go-live hypercare support log and closure summary. 4.3 Exclusions / Out of Scope ● Migration of historical transaction-level detail beyond opening balances (no full transaction-history import). ● Custom report or Power BI development beyond standard Business Central financial reports (to be scoped and quoted separately if required). ● Integration with third-party systems (e-commerce, CRM, payroll, etc.) not currently in use by the new entities. ● Cleansing of source data prior to handover — Client to provide validated customer/vendor master files in the agreed template. ● Custom AL code/extension development beyond standard configuration. ● Additional Business Central user licensing for the new companies (licensing is a separate commercial matter with Microsoft/the Client's licensing partner). 5. Assumptions and Dependencies ● Client will provide cleansed and validated customer and vendor master data files, in the agreed template format, for all three entities prior to migration. ● Existing Business Central licensing on the Daleys tenant already accommodates the three additional companies; any incremental Microsoft licensing cost is out of scope of this Work Order. ● The Chart of Accounts and dimension framework designed for ARO Investments will be adopted as the group standard, with only jurisdiction-specific tax/statutory adjustments made for Noru NZ and Noru SG. ● Client will confirm the final go-live cut-off date at least two (2) weeks in advance, to allow time for opening balance extraction and reconciliation. ● Client will provide timely access to existing legacy/source systems for the three entities for opening balance extraction. ● Any custom AL code, extension development, or third-party integration identified during the project is out of scope and will be quoted separately. ● Key client stakeholders will be available for UAT testing and sign-off within the agreed project timeline.

Skills

Fuente original: freelancer