Sign in with Microsoft Entra ID to access this training portal.
Signed in
Home > Progress
My Progress
Review the training sections and step-by-step cards you have covered.
Progress Tracker
Overall
0%
Not synced yet
Cards Reviewed
0 / 0
How-to cards marked or opened
Sections Viewed
0 / 0
Training sections visited
Covered Items
Home > Activity
User Activity
Recent sign-ins and navigation clicks captured for training audit review.
Loading activity...
📘 Interactive User Manual
ETG Pulses Canada MSD 365 & DMS
Your complete guide to transaction entry across the Deal Management System and Microsoft Dynamics 365 Finance & Operations.
26
Transaction modules
3
Legal entities
2
Purchase types
100+
Step-by-step actions
📂 Modules
Click any card or use the sidebar to navigate. Tick steps as you complete them to track progress.
🤝 DMS & Trading
🤝
Deal Management System
Opportunities, onboarding, MDM and approvals
📄 4 steps
📦 Procurement
🌾
Farm Purchases
Scale ticket, elevator receipt, GRN, PO and vendor payment flow
📄 Farm purchase process
📊 Progress Tracker
Overall
0%
💡Getting Started: Click any module card or use the sidebar. Each module has a Transaction Flow tab showing the end-to-end process and a How to Enter tab with step-by-step instructions. Use the search bar to jump to any topic instantly.
🏢Legal Entities: P009 = ETG Commodities Inc. (Trading/Parent). P012 = Dunnington Holdings Limited (Production). P027 = ETG Commodities Manitoba Inc. (Production). P009 retains legal ownership of all inventory throughout the production lifecycle.
Home › Deal Management System
Deal Management System
Foundation for all trading activities - opportunities, onboarding, MDM and deal approvals
🤝 DMS
🤝 Deal Management System — End-to-End Transaction Flow
Traders capture the initial opportunity in DMS after discussing commodity, grade, quantity, price, shipment period, origin, destination, and commercial terms with the counterparty.
System: Deal Management System (DMS)
Output: Opportunity record created and marked as Negotiated or Lost
2
👤
Step 2 — Counterparty Onboarding
Vendor or Customer KYC Completed
Documents · Compliance · Approval Workflow
🧾
Trigger Onboarding
New vendor or customer
→
📎
Upload KYC
Document Advisor checklist
→
🔐
Approve
Compliance verification
Step 2 — Counterparty Onboarding Summary
If the counterparty is new, DMS starts onboarding from the opportunity. Required KYC documents are captured and routed for compliance approval before the deal can move forward.
Control: Blocked or expired KYC must be revalidated
Output: Approved vendor or customer profile ready for MDM creation
MDM validates whether the customer, vendor, or item already exists. New records go through maker-checker approval and then sync to the required D365 legal entities.
Maker-checker: The creator cannot approve the same master record
Output: Approved master data available for deal processing
The deal is submitted for workflow approval. Once fully approved and confirmed, it integrates into D365 as a Purchase Agreement or Sales Agreement, and users receive notification of the created agreement.
Cost Sheet Engine: Applies to sales deals where cost elements are calculated
Output: D365 agreement created with DMS reference for traceability
💡Cost Sheet Engine API: For sales deals only, enter cost element inputs under the Cost Elements tab. The API returns applicable charges into the Other Charges tab as read-only values. These charges flow into D365 on deal confirmation.
⚠️Maker-Checker Control: The user who creates or modifies master data cannot approve the same record. Approval is managed through Microsoft Teams workflows.
Section Progress
0 / 0
1How to Create a Deal in DMS▼
1
Navigate to the Deal Management module
Select the Deal tab and click New Opportunity to begin.
2
Enter mandatory deal details
Fill in Deal Type, Counter Party, Trader, Trade Date, payment method, and payment terms.
3
Select delivery and destination details
Add amount and agreement declaration information as required.
4
Open the Items tab
Add item-related information, then review all details entered in the form.
5
Click Submit to create the deal
Save financial dimension details if prompted by the system.
2How to Onboard New Customers▼
1
Log in to DMS and open Customer Onboarding
Click Add New Customer to start creating a new customer profile.
2
Enter customer details
Fill in name, mobile, email, business info, and address (state, district, city, postal code).
3
Fill in tax and compliance information
Enter Tax Details, PAN, customer category, business type, and payment/account details.
4
Upload supporting documents
Navigate through each onboarding tab to complete and verify all sections.
5
Click Save or Submit
This creates the new customer record in DMS.
3How to Onboard a Vendor▼
1
Log in to DMS and navigate to Vendor Onboarding
Click Add New Vendor to begin the vendor registration process.
2
Enter vendor details
Fill in name, contact person, mobile, email, company name, business type, and address.
3
Fill in tax and compliance information
Enter Tax Details, PAN, vendor group/classification, and banking/payment details.
4
Upload supporting documents
Navigate through each onboarding tab to verify all sections are complete.
5
Click Save or Submit
This finalises the vendor record in DMS.
4How to Create an Item in DMS▼
1
Log in to DMS and navigate to Item Management
Click Create New Item to start adding a new product or inventory item.
2
Enter item details
Fill in name, code, SKU, description, category, brand, and product classification.
3
Configure unit of measurement and pricing
Set packaging, pricing (MRP, selling/purchase price), tax details (Tax Details/HSN), and stock settings.
4
Upload product images if applicable
Navigate through all tabs to validate the item configuration.
5
Click Save or Submit
This adds the new item to DMS.
Home › Procurement
Procurement
Manage farm purchases, back-to-back purchases, purchase agreements, receipts and procurement execution in D365 F&O
🛒 Procurement Module
🌾 Farm Purchase
End-to-end grain procurement flow — from deal origination through production, dispatch, and sales invoicing — managed across the Deal Management System (DMS), Microsoft Dynamics 365 F&O, and Puls-E.
🌾 Farm Purchase — End-to-End Transaction Flow
1
🤝
Step 1 — Deal Origination (DMS)
Opportunity Created & Deal Approved
Commodity · Qty · Price · Terms · Vendor KYC
🤝
Opportunity Created
Commodity · Qty · Price · Terms
→
🧑💼
Vendor Creation
KYC · Compliance check (if new)
→
✅
Deal Approved
Status: Negotiated → Confirmed
→
📋
Rate Card Applied
Estimated charges flow to opportunity
Step 1 — Deal Origination Summary
The GROUP Canada procurement process begins in the Deal Management System (DMS). Traders initiate an opportunity by negotiating with counterparties through various channels, capturing essential details such as commodity, quantity, price, and shipment terms.
Once the opportunity is created, the Cost Sheet Engine API estimates charges and flows them back to the opportunity. The opportunity status is updated to "Negotiated" or "Lost" and moves into an approval workflow.
If the vendor is new, the onboarding process is triggered to capture KYC documents and validate compliance before proceeding. The approved deal is then confirmed with a rate card applied for quality variations and discounts.
Master Data Management (MDM) ensures accurate creation and synchronization of customers, vendors, and item masters across DMS and D365. Auto-generation of codes, duplication checks, and additional attribute capture maintain data integrity.
The approved purchase deal transitions into a Purchase Agreement within D365. The agreement leverages rate card functionality to manage quality variations and discounts — critical for scenarios where the quality received differs from what is specified in the agreement.
The Purchase Agreement goes through a structured approval workflow with statuses: Draft → In Review → Approved → In Process → Completed. If rejected, it is marked Cancelled and synced back to DMS. The agreement number is also shared with the Puls-E system.
Rate Card: Contains sub-commodity items with applicable discounts for quality mismatches
Termination statuses: "Terminated" (no PO released) and "Force Closed" (partial PO released)
System: D365 Finance & Operations
D365 Path:Procurement and Sourcing → Purchase Agreements → + New
When physical goods are received at the production entity (P012 or P027), the weighing process begins. The system captures Gross Weight, Tare Weight, and Net Weight. Samples are inspected and quality is checked.
The Scale Ticket is the first document generated — created in D365 with reference to the Purchase Agreement number. Key fields include: Location, Branch Location, Scale Used, Producer, Carrier Info, Commodity, BIN, Operator, Inspected By, Graded As, Dockage, Moisture, Damage, Shrinkage, Splits, and Notes. It includes document upload as an attachment feature.
After scale ticket generation, the Elevator Receipt is created. It quantifies dockage and split items based on percentage, selects the actual grade, and confirms the final item from the rate card of the P009 purchase agreement.
Dockage formula: Weight of grain unloaded × Dockage %
Splits formula: Weight of grain unloaded × Splits %
Net weight: Weight of grain unloaded – Dockage – Splits
Note: One Scale Ticket can only be used once. Incorrect postings require restarting the entire process from scale ticket.
D365 Path:Inventory Management → Scale Ticket → + New
Purchase Order Auto-Generated & Grain Receipt Created
Rate Card · Levy Charges · Final Negotiated Price
📦
PO Auto-Generated
Qty & grades from elevator receipt via rate card
→
💰
PO Updated — Final Price
Negotiated price · Levy charges · Additional charges
→
🌽
Grain Receipt Generated
External cost + levy + additional charges captured
Step 4 — PO Update & Grain Receipt Summary
Once the Elevator Receipt is confirmed, the system automatically releases the Purchase Order (PO) in P009 with quantity and grades from the elevator receipt. If items differ from the agreement, rate card functionality amends the PO including dockage and split items.
Simultaneously, a Zero-value Purchase Order is auto-created in P012/P027 for the RM goods — allowing the production entity to receive goods without a financial value. Goods are received in Dirty BINs, which map to storage dimension Locations in D365.
The Grain Receipt Note (GRN) is generated once the PO is confirmed. It captures the final negotiated price along with additional charges (handling, freight) and automatically calculates levy charges based on predefined configurable logic:
Levy varies by warehouse and commodity (e.g., Saskatchewan Durum = 1 CAD/Net MT, Alberta Red Lentils = 7 CAD/Net MT)
Levy = Net Weight × Levy Rate
User can renegotiate the price based on actual item receipt via grain receipt
D365 Path:Purchase Order → Receive Tab → Grain Receipt Note
Once the Grain Receipt Note is created and the PO is confirmed, the system auto-posts the Product Receipt (GRN) for the entire quantity and all items at once. The product receipt is based on the quantity confirmed in the elevator receipt plus additional charges from the grain receipt.
The Purchase Invoice is then posted, recording the vendor liability in the accounts payable sub-ledger. The accounting impact is:
Debit: Inventory / Raw Material Account
Credit: Accounts Payable (Vendor)
Levy charges, handling, and freight are included as additional cost lines
For PTBF (Price To Be Fixed) contracts, the invoice may be posted at provisional price and updated post final price determination
D365 Path:Purchase Order → Invoice → Vendor Invoice → Post
6
💳
Step 6 — Vendor Payment (D365)
Payment Proposal & Payment Journal Posted
Due Invoices Pulled · Payment Method Selected · Bank Account Credited
📋
Open Invoice Reviewed
Payment terms & due date verified
→
📤
Payment Proposal Generated
Due invoices pulled · Method & bank selected
→
💳
Payment Journal Posted
Dr Accounts Payable / Cr Bank Account
Step 6 — Vendor Payment Summary
After the purchase invoice is posted, the accounts payable team reviews open invoices, verifying payment terms, due dates, and clearing any payment hold flags on the vendor account.
A Payment Proposal is generated in D365, which automatically pulls all due invoices for the selected vendor. The payment method (cheque, wire, EFT) and bank account are selected before the proposal is reviewed and approved.
The Vendor Payment Journal is posted, which records:
Debit: Accounts Payable (clears the vendor liability)
Credit: Bank Account (reduces cash balance)
Payment can cover multiple invoices in a single journal
The posted payment is settled against the vendor invoice using the Settle Transactions function in D365. Partial settlements are supported — a single payment can settle multiple invoices, or a single invoice can be partially settled by multiple payments.
The Vendor Balance Report is run to cross-check the outstanding balances against the vendor statement received from the supplier. Any debit notes for price disputes, quality deductions, or short deliveries are raised before period close.
Settlement status updates on the invoice: Open → Partially Settled → Settled
Vendor balance should be zero after complete settlement
GRN vouchers can be viewed under Purchase Order → Receive → Product Receipt → Vouchers
📌System Scope: The entire trading and production process is managed within the Deal Management System (DMS), Microsoft Dynamics 365 Finance & Operations, and Puls-E. DMS handles deal origination and sales deals; D365 manages all transactional accounting from purchase agreement through production, dispatch, vendor payment, and sales invoicing; Puls-E handles container stuffing and logistics with two-way integration to D365.
💡Rate Card: The rate card drives both charge estimation in DMS (for opportunities) and quality/discount variations in D365 purchase agreements. Keeping it current is critical to accurate costing across the entire flow.
🏭MTO vs MTS: In Make-to-Order, production orders are created with reference to a confirmed sales order. In Make-to-Stock, production orders are created to replenish inventory; any intercompany stock movement to another ETG entity is handled via intercompany sales. Both models auto-create mirrored production orders in the trading/parent entity (P009).
⚖️Scale Ticket: Generated from D365 when physical goods arrive at the production entity. Contains gross weight, tare weight, and net weight — the primary input for creating the Elevator Receipt.
🌾Elevator Receipt: Validates weight and quality — capturing grade bifurcation, dockage, and split percentages — before updating inventory records. Triggers automatic generation of the Purchase Order in D365 based on confirmed quantity and grades.
🌽Grain Receipt: Generated after final price negotiation post elevator receipt. Captures the final external cost, levy charges, and additional charges. Forms the basis for updating the Purchase Order and posting the Product Receipt.
💳Vendor Payment: Processed via the Vendor Payment Journal in D365 after the invoice is posted and payment terms are confirmed. A Payment Proposal pulls all due invoices for the vendor. On posting, D365 debits Accounts Payable and credits the Bank Account, clearing the AP liability.
✅Settlement & Reconciliation: The posted payment is matched against the vendor invoice using Settle Transactions. The Vendor Balance report is run to cross-check against the vendor statement. Any debit notes for price disputes, quality deductions, or short deliveries are raised before period close.
📄Bill of Lading: Generated by the production entity (P012/P027) for the trading/parent entity (P009) when finished goods are loaded into the rail car. Rail car loading is recorded in D365 and pushed to Puls-E as a transfer journal via integration.
🚢Container Stuffing: After rail car transfer, finished goods are moved into shipping containers. Container stuffing details are captured in Puls-E and flow back to D365 as a transfer order, updating inventory records for the trading entity.
📝 How to Enter — Farm Purchase Questions
Use these question cards to complete the Farm Purchase entry cycle after DMS setup, including purchase agreement, scale ticket, elevator receipt, grain receipt, purchase invoice and vendor settlement.
📋 Farm Purchase — Questions Completed:
0 / 0
1How to Enter an Elevator Receipt with Dockage and Split Details▼
1
Log in to D365 and open Elevator Receipt
Open the Elevator Receipt form and create a new entry.
2
Select receipt type, date, and scale ticket number
Select the corresponding scale ticket; one scale ticket can be used only once.
3
Finalize grain and quality details
Select final grain/item and enter grading details including dockage and split percentages.
4
Verify system-calculated values
Validate dockage, splits, and net weight calculations before confirmation.
5
Confirm and print elevator receipt
Confirm the transaction and print the elevator receipt for downstream GRN and PO processing.
2How to Convert a Farm Purchase Opportunity into a Deal▼
1
Search for the relevant opportunity
Select it from the opportunity list to open the details page.
2
Review the opportunity details
Check customer requirements, item details, and transaction information.
3
Click Create Response or Respond to Opportunity
Select the response — Negotiated or Lost.
4
Enter decision comments
Review the remaining credit and trade limit displayed by the system.
5
Verify all details and submit the response
The confirmed deal is now ready for further processing.
3How to Create and Print a Scale Ticket▼
1
Log in to D365 and navigate to Inventory Management → Scale Ticket
Click Create New Scale Ticket to begin.
2
Select the customer, vendor, or transporter
Enter ticket details: number, date, vehicle, and commodity information.
3
Record gross weight and tare weight
Confirm the auto-calculated net weight and select the warehouse or delivery point.
4
Add pricing, freight details, driver info, and remarks
Review all mandatory fields for accuracy.
5
Click Save, Submit, or Confirm
This completes the scale ticket entry in D365 and allows elevator receipt processing.
4How to Review GRN Entries▼
1
Log in to DMS and navigate to the GRN module
Open the GRN Entries or View GRN section to access receipt records.
2
Use search and filter options to locate records
Filter by GRN number, vendor/customer name, item, date, status, or warehouse.
3
Click Search or View to display results
Select a specific GRN entry to open its detailed information.
4
Verify item details and quantities
Check warehouse information, attached documents, and approval data within the record.
5
Use available options to edit, print, or export the GRN
Close the screen or return to the list when done.
5How to Create and Review a Movement Journal▼
1
Open Finance and Operations and confirm the correct legal entity
Locate the required journal (e.g., FG Consumption)
Open it to review the journal lines.
3
Check item number, product name, quantity, and unit of measure
Review line details including lot ID and inventory dimensions.
4
Click Validate to check for errors
If successful, select Post to post the movement journal.
5
Confirm the journal status shows as Posted
Verify it appears correctly in the journal list.
6How to Create a Rail Car Loading Entry▼
1
Open Finance and Operations and navigate to the Rail Car Loading workspace
Select the required rail car loading number from the list.
2
Review header details
Confirm the rail car number, warehouse, shipment info, and verify item details in the Sales Order Details section.
3
In Rail Car Loading Details, click New to add a loading line
Enter item number, rail load number, loaded quantity, and load location.
4
Validate quantity and batch/inventory dimension information
Save the transaction after completing all loading details.
5
Apply workflow actions (Validate/Confirm/Post) as required
Confirm the rail car loading status is updated successfully in the system.
7How to Update Inventory Transaction Status▼
1
Open Finance and Operations
Navigate to the Manage Inventory Transactions page.
2
Locate the required transaction
Use date, reference number, item number, or receipt/issue status to find it.
3
Select the transaction line
Click the current status value in the Status column.
4
Choose the required status from the dropdown
Apply the update to the selected transaction.
5
Verify the updated status appears correctly in the grid
Repeat for any additional transactions as needed.
8How to Update Production Order Status▼
1
Open Production Control > Production Orders in Finance and Operations
Search for the required production order.
2
Open the order and verify details
Check production order number, item, quantity, site, and warehouse.
3
From the Action Pane, select the appropriate status update option
Options include Created, Estimated, Scheduled, Released, Started, Reported as Finished, or Ended.
4
Review the update parameters and enter required quantity or posting details
Click OK or Post to apply.
5
Confirm the success message
Verify that the production order status has been updated correctly.
🔁 Back to Back Purchase
Manage a linked series of purchase and sales transactions between inter-group companies or third-party stakeholders. A purchase agreement can be created manually and the corresponding sales agreement can be generated automatically by selecting the customer, with details replicated from the purchase agreement. The reverse process is also supported.
🔁 Back-to-Back Purchase — DMS to D365 Transaction Flow
The Back-to-Back process begins in DMS. The trader manually creates a purchase opportunity capturing commodity, quantity, price, and shipment terms. The opportunity status is updated to "Negotiated" or "Lost", and moves into an approval workflow to be confirmed as the Purchase Deal.
If the vendor is new, the onboarding process is triggered to capture KYC documents and validate compliance before deal approval can proceed.
System: Deal Management System (DMS)
Output: Confirmed Purchase Deal in DMS
Once the purchase deal is confirmed, a Sales Opportunity is automatically created in DMS (see Step 2)
Cost Sheet Engine API · KYC · Sales Deal Confirmation
🔄
Sales Opportunity Auto-Created
Created after purchase deal confirmation
→
🧮
Cost Sheet Engine API
Estimated charges flow to opportunity
→
🧾
Sales Deal Approved
Post-approval confirmation
Step 2 — Sales Leg & Cost Sheet Summary
As soon as the purchase deal is confirmed, DMS automatically creates the sales opportunity. The Cost Sheet Engine API estimates charges and flows them back to the sales opportunity.
After review, the sales deal moves through the approval workflow and is confirmed. If the customer is new, customer onboarding and KYC validation must be completed before the sales deal can be approved.
System: Deal Management System (DMS)
Output: Both Purchase Deal and Sales Deal confirmed in DMS
⚠️ If a vendor or customer is new, onboarding is triggered to collect KYC documents and validate compliance before deal approval proceeds.
3
📑
Step 3 — Agreements & Order Release (D365 F&O)
Back-to-Back Purchase & Sales Agreements Created in D365
Purchase Agreement ↔ Sales Agreement · PO & SO Released
📑
Purchase Agreement Created
Back-to-back agreement in D365
↔
📄
Sales Agreement Created
Generated from purchase agreement
→
📦
PO & SO Released
Purchase order and sales order released
Step 3 — Agreements & Order Release Summary
Once both deals are confirmed, the system creates Back-to-Back Purchase and Sales Agreements in D365. The user manually creates the Purchase Agreement, and the corresponding Sales Agreement can be generated automatically by simply selecting the customer — with all details replicated from the purchase agreement. The reverse is also possible.
After agreements are in place, the Purchase Order (PO) and Sales Order (SO) are released from the respective agreements. Verify that vendor/customer details, item, quantity, price, shipment terms, and linked agreement references are correct before confirmation.
System: D365 Finance & Operations
D365 Path (Purchase):Procurement and Sourcing → Purchase Agreements → + New → Generate Sales Agreement
D365 Path (Release):Purchase Agreement → Release Order | Sales Agreement → Release Order
The physical goods are received using Product Receipt in D365 against the released Purchase Order. After receipt confirmation and matching, the Purchase Invoice is posted to record the vendor liability:
Debit: Inventory / Expense Account
Credit: Accounts Payable
The received material is then picked and packed for the designated customer already assigned to the Sales Order. The packing slip is posted if applicable, and the Sales Invoice is then posted to complete the B2B cycle:
Debit: Accounts Receivable
Credit: Sales Revenue
✅ The transaction is complete after material is received, vendor purchase invoice is posted, goods are picked/packed for the customer, and the customer sales invoice is posted.
D365 Path (Receipt):Purchase Order → Receive → Product Receipt → Post
D365 Path (Sales):Sales Order → Pick & Pack → Packing Slip → Sales Invoice → Post
🚧
Coming Soon
This section is currently being finalised. Step-by-step entry instructions will be available here shortly.
IN PROGRESS
Home › Production Orders
Production Orders
MTO/MTS production — P012/P027 operational orders sync to P009 financial orders
🏭 D365 · P009/P012/P027
🏭 Production Orders — End-to-End Flow (P012/P027 → P009)
1
🏭
Step 1 — Production Order Creation
Operational Order in P012/P027 · Financial Order Auto-Synced in P009
MTO or MTS · Shift-based · Formula includes RM only
🏭
Production Order Created (P012/P027)
MTO or MTS · created at shift start
→
🔄
Auto-Sync to P009
Financial production order generated
→
📋
Formula Assigned
RM items only · subcontracting service item in P009
Step 1 — Production Order Creation Summary
Production of finished goods follows either a Make-to-Order (MTO) or Make-to-Stock (MTS) approach. The production order must be created in P012 or P027 at the beginning of each shift. The formula includes RM only, and no inventory valuation occurs at the production entity level.
Each action in P012/P027 triggers a corresponding update in the P009 financial production order, which is auto-generated with reference to the P012/P027 production number. The P009 formula includes a subcontracting service item and links to the Sales Agreement and Sales Order.
MTO: Production order is directly linked to a Sales Order — demarking and re-marking required if SO changes
MTS: Production adds to inventory stock without a specific SO reference
D365 Path:Production Control → Production Orders → + New
2
⚙️
Step 2 — Estimate, Release & Start
Production Lifecycle Stages Executed in P012/P027
Estimate → Release → Start → synced to P009
📐
Estimate
BOM & route calculated
→
🚀
Release
Materials reserved · order released
→
▶️
Start
Production physically begins
→
🔄
Sync to P009
All stages auto-updated in P009
Step 2 — Production Lifecycle Summary
All production processes — Estimate, Release, Start, Picking List, Report as Finished, End — are executed in P012 or P027. Each action triggers a corresponding update in the P009 production order to maintain synchronization.
The route card journal is posted in production entities with zero values (zero financial impact) and is not synced to P009, as the P009 production order does not have a route.
Labor, machine, and overhead costs post to P012/P027 GL
Error logs are generated for any integration failures — key users must monitor and rectify
A Description field on the Production Order captures shift remarks
3
📋
Step 3 — Picking List & Report as Finished (RAF)
RM Consumed · FG/SFG Reported as Finished
Picking List Journal · RAF Journal · Auto-synced to P009
📋
Picking List Journal
RM consumed · posted in P012/P027
→
✅
Report as Finished
FG/SFG inventory inflated
→
🔄
Auto-Sync Journals to P009
Posted values replicated
Step 3 — Picking List & RAF Summary
The Picking List journal records raw material consumption in P012/P027 and is synced to P009 with actual posted values. Raw material is deducted at weighted average cost.
The Report as Finished (RAF) journal inflates SFG/FG inventory in P012/P027 and is also synced to P009. In P012/P027, the SFG stock value includes only route-related costs (not RM cost). In P009, RM cost + subcontracting cost = FG value.
If additional Picking List and RAF journals are posted in P012/P027, new journals are also created and posted in P009
The serial number for produced SFG is set to "NA"
GL (P009 — Picking List): Dr Production WIP / Cr Inventory RM
GL (P009 — RAF): Dr Inventory FG / Cr Production WIP
4
🏁
Step 4 — Production Order End & Cost Roll-Up
WIP Settled · FG Valued · Production Complete
Production End · WIP Absorption · FG = RM + Subcontracting
🏁
Production Order End
P012/P027 and P009
→
💰
Cost Roll-Up
WIP settled → FG valuation
→
📦
FG Value = RM + Subcontracting
Final inventory value confirmed
Step 4 — Production End & Cost Roll-Up Summary
When the production order is ended in P012/P027, the system performs a final cost roll-up and WIP settlement in both entities. The net financial impact ensures: Inventory FG = Inventory RM + Subcontracting Charge.
In P009, physical postings are reversed and financial postings are applied. In P012/P027, all overhead and resource costs are finalized and posted to respective GL accounts.
P012/P027 GL: Dr Production Expense / Cr Production Overhead Expense + Cr Production Resource Expense
Subcontracting charges are recognized once GROUP Commodity completes the sale of FG
🚧
Coming Soon
This section is currently being finalised. Step-by-step entry instructions will be available here shortly.
IN PROGRESS
Home › Rail Car Loading
Rail Car Loading
Record FG loading into rail cars and trigger transfer journal in P009
🚂 D365 · P012/P027
🚂 Rail Car Loading — End-to-End Flow
1
📦
Step 1 — FG Storage & Sales Order Reference
FG Stored in Clean BINs · Sales Order Selected
Production complete · BIN = storage location · SO dropdown from P009
📦
FG in Clean BINs
Post-production storage in P012/P027
→
📋
Sales Order Selected
Dropdown from P009 entity
→
🔄
SO Lines Populated
Item details auto-fetched from SO
Step 1 — FG Storage & SO Reference Summary
Once production is complete and FGs are stored in clean BINs (configured as storage locations in D365), the next operation is loading goods into rail cars. Physical loading takes place in P012 or P027.
The user selects the reference Sales Order number from the default entity mentioned on the inventory management parameter document data via a dropdown. Items from the Sales Order populate automatically along with all SO line information.
System: D365 P012 or P027
BINs: Configured as Dirty BINs (receipt) and Clean BINs (post-production)
2
🚂
Step 2 — Rail Car Details Entry
Rail Car Number · Loaded Quantity · Seal Number Captured
New entry per rail car · Quantity in MT · Seal & bag count
🚂
Rail Car Number Added
One row per rail car
→
⚖️
Loaded Qty & Unit
MT or applicable unit
→
🔒
Seal Number & Bags
Bags and seal number captured
Step 2 — Rail Car Details Entry Summary
Once item details are confirmed, the user clicks New to add rail car entries. Each row in the rail car form captures: Rail Car Number, Loaded Quantity, Unit, Number of Bags, and Seal Number.
Multiple rail cars can be added against a single Sales Order. All entries are captured in the P012/P027 rail car form before confirmation.
Serial number changes from "NA" to the respective rail car number via transfer journal
The transfer journal carries no cost implications — it only updates dimensions
3
🔄
Step 3 — Confirm & Auto Transfer Journal
Rail Car Form Confirmed → Transfer Journal Auto-Posted in P009
Serial number updated · Puls-E synced via D365 transfer journal
✅
Rail Car Form Confirmed
P012/P027
→
🔄
Transfer Journal Auto-Posted in P009
Serial: NA → Rail Car No.
→
📡
Puls-E Updated
Data from P009 TJ flows to Puls-E
Step 3 — Confirm & Transfer Journal Summary
When the user clicks Confirm on the rail car form, the system automatically creates and posts a Transfer Journal in P009. The transfer journal picks item and quantity from the rail car form and updates the serial number from "NA" to the respective rail car number.
For missing serial numbers in P009, the system automatically creates new serial number records. Batch information is added manually on the transfer journal form. Data from the P009 transfer journal subsequently flows to Puls-E for shipment tracking.
D365 Path:Inventory Management → Rail Car Loading Form → Confirm
No cost implications — transfer journal only updates storage/tracking dimensions
🚧
Coming Soon
This section is currently being finalised. Step-by-step entry instructions will be available here shortly.
IN PROGRESS
Home › Sales Order
Sales Order
Released from Sales Agreement — pick, pack, packing slip and sales invoice
🛒 D365 · P009
🧾 Sales Orders — End-to-End Flow
1
📑
Step 1 — Sales Agreement & SO Creation
Sales Contract Approved → Sales Order Created in D365
DMS deal → D365 Sales Agreement → SO approval workflow
📑
Sales Agreement Approved
DMS deal integrated to D365
→
🧾
Sales Order Created
Numbered to match Sales Contract
→
🔐
SO Approval Workflow
Value-based matrix approval
Step 1 — Sales Agreement & SO Creation Summary
Once the sales deal is confirmed in DMS, it is integrated into D365 to create a Sales Agreement (Sales Contract). The Sales Agreement goes through a value-based approval workflow: Draft → In Review → Approved → In Process → Completed. Rejection marks the agreement as Cancelled and syncs back to DMS.
Upon approval, a Sales Order (SO) is created. SO numbers align with the Sales Contract — e.g., Contract SC/001 generates SO numbers SC/001-01, SC/001-02, etc. The SO also goes through an approval process. Once approved, charges from the agreement are added to the SO.
Sales Agreement and released SO are shared with Puls-E via D365 integration
D365 Path:Sales and Marketing → Sales Agreements → + New
The pick and pack process involves picking goods from inventory and preparing them for shipment. When the packing slip is posted, inventory is deducted and the packing slip document is generated.
For GROUP Canada pulses entity, this transaction is carried in Puls-E and auto-posted back to D365. An alert is configured for un-invoiced packing slips, notifying a designated user group via email.
GL (Packing Slip): Dr System_COGS Delivered / Cr Inventory Account
Integration errors generate error logs — key users must monitor and rectify
Sales invoices are created in D365 and go through a configurable approval process based on invoice value. Post-approval, the invoice is posted and revenue is recognised.
A custom report displays variance between estimated and actual charges at the Sales Order level (customization of the GMR report with SO number added).
Payment Journal Created · Receipt Posted · AR Settled
Payment journal → approval → posting → DMS sync
💰
Payment Journal Created
Against invoice / customer
→
🔐
Approval
Journal reviewed and approved
→
✅
Receipt Posted
Bank Dr / Customer Cr · DMS synced
Step 4 — Customer Payment Summary
The user creates a payment journal to record receipt against an invoice or customer account and submits it for approval. Once approved, the receipt is posted and the customer balance is reduced.
Posted receipts are sent to batch execution where transaction details flow from D365 to DMS for activity logging.
This section is currently being finalised. Step-by-step entry instructions will be available here shortly.
IN PROGRESS
Home › Intercompany Orders
Intercompany Service Orders
IC sales/purchase orders between P012/P027 and P009 for subcontracting charges
🔄 D365 · P009/P012/P027
🔄 Intercompany Service Orders — End-to-End Flow (P012/P027 ↔ P009)
1
🏭
Step 1 — Auto-Creation of IC Orders
IC Sales Order (P012/P027) & IC Purchase Order (P009) Auto-Created
Triggered at production start · Draft stage · Estimated subcontracting price
🏭
Production Started in P012/P027
RAF journal posted
→
📤
IC Sales Order Auto-Created (P012/P027)
Draft — estimated subcontracting price
→
📥
IC Purchase Order Auto-Created (P009)
Auto-confirmed · no manual action needed
Step 1 — Auto-Creation of IC Orders Summary
D365 supports intercompany (IC) functionality for GROUP group entities, creating automatic linkages between transactions for smoother financial reconciliation. When production starts in P012 or P027, an IC Sales Order is automatically created in Draft stage at the estimated subcontracting price.
Simultaneously, an IC Purchase Order is auto-created and auto-confirmed in P009. No manual action is required in P009 at this stage. IC service orders apply only to GROUP entities present on D365 (P009, P012, P027).
For entities not on D365, standard purchase/sales orders are used
D365 Path:Sales and Marketing → Sales Orders (P012/P027) — auto-generated
After RAF is completed, the user performs the pick and pack process on the IC Sales Order in P012/P027 for the subcontracting service item. The packing slip is then posted, triggering two automatic actions:
A provisional sales invoice posts in P012/P027 to provisional GL accounts
A product receipt for the service item auto-posts in P009
⚠️ Required sequence: RAF → Packing Slip → Actual Invoice. Never post packing slip before RAF.
Provisional GL (P012/P027): Dr Provisional Receivable / Cr IC Revenue (Provisional)
GL (P009): Dr WIP / Subcontracting / Cr GR/IR Clearing
D365 Path:IC Sales Order → Pick and Pack → Post Packing Slip
3
🧾
Step 3 — Actual Invoicing & P009 Absorption
Actual Invoice Posted (P012/P027) · Purchase Invoice at P009 · WIP Absorbed into FG
The user manually posts the actual sales invoice on the IC Sales Order in P012/P027. The system automatically reverses the provisional invoice entry and posts to actual service revenue accounts.
In P009, the user manually locates the IC Purchase Order and posts the purchase invoice matching the actual invoice from P012/P027. The subcontracting cost is held in WIP. When the production order is ended, WIP is absorbed into FG valuation.
GL (P012/P027 Actual): Dr IC Receivable / Cr Service Revenue (provisional reversed)
GL (P009 PO Invoice): Dr GR/IR Clearing / Cr IC Payable
GL (P009 Production End): Dr Inventory FG / Cr WIP + RM consumed
Final FG value = RM cost + subcontracting service cost
D365 Path:IC Sales Order → Invoice → Invoice (P012/P027)
⚠️Provisional GL: The packing slip at P012/P027 auto-posts a provisional sales invoice to provisional GL accounts. When the actual invoice is posted, the provisional entry is automatically reversed. Monitor uncleared provisional balances before each period close.
🔄Scope: IC service orders only apply to GROUP entities present on D365 (P009, P012, P027). For any external entity or entity not on D365, standard purchase/sales orders are used instead.
🚧
Coming Soon
This section is currently being finalised. Step-by-step entry instructions will be available here shortly.
IN PROGRESS
GL Impact — Intercompany Service Orders
Transaction
Entity
Debit
Credit
Provisional Packing Slip
P012/P027
Provisional Receivable
IC Revenue (Provisional)
Product Receipt (auto)
P009
WIP / Subcontracting
GR/IR Clearing
Actual Invoice
P012/P027
IC Receivable
Service Revenue (provisional reversed)
IC Purchase Invoice
P009
GR/IR Clearing
IC Payable
Production Order End
P009
Inventory (FG)
WIP + RM consumed
Home › FG Adjustment
Finished Goods Adjustment
Movement journal in P012/P027 to consume FG stock after BOM journal is posted
📦 D365 · P012/P027
📦 Finished Goods Adjustment — Movement Journal Flow (P012/P027)
1
📋
Step 1 — BOM Journal Posted
BOM Journal Posted in P012/P027 & P009 · FG Received · SFG to be Consumed
SFG to FG conversion is carried out via a BOM journal. The user selects the FG item and mentions the quantity. Clicking Fetch Items auto-populates the corresponding SFG and packaging material from the Released Product master (1:1 relationship defined on product form).
Quantity calculations: SFG Qty = FG Qty × SFG Qty on product. Packaging Qty = FG Qty / unit conversion factor. Once posted in P012/P027, the BOM journal is auto-replicated in P009 — SFG is consumed and FG inventory inflates.
BOM Line tick = "Yes" for fetched items; "No" for FG item
Financial impact follows standard BOM journal posting
After the BOM journal is posted, the user clicks the Movement Journal button on the BOM journal form. The system auto-creates a movement journal with lines sourced from BOM journal lines where BOM Line = "No" (FG item lines).
The movement journal quantities are negative (to consume inventory). Users cannot manually add, delete, change quantity, or update dimensions on this journal. It is auto-posted immediately and the button is frozen to prevent re-use.
GL (P012/P027): Dr Production Expense Account / Cr System_Production_Clearing Account (Inventory FG)
No P009 impact — this movement journal is production entity only
BOM Journal reference appears in Movement Journal (hyperlink under General tab)
Movement Journal reference appears in BOM Journal form
🚧
Coming Soon
This section is currently being finalised. Step-by-step entry instructions will be available here shortly.
IN PROGRESS
Home › Bill of Lading
Bill of Lading
Generated in P012/P027 for P009 — references rail car loading and P009 sales order
📄 D365 · P012/P027
📄 Bill of Lading — Document Generation Flow
1
🚂
Step 1 — Rail Car Selection & Item Details Fetch
Rail Car Number Selected · Item & Quantity Auto-Fetched to BOL Form
Created in P012/P027 · SO numbers from P009 · Rail car details auto-populated
📄
New BOL Form Created
In P012 or P027 entity
→
🚂
Rail Car Number Selected
Item details + total qty auto-fetched
→
📋
SO Numbers Linked
P009 Sales Order numbers printed on BOL
Step 1 — Rail Car Selection Summary
The user generates Bill of Lading (BOL) documents from P012 or P027 entity for P009. A new form is created for the BOL document. The Sales Order numbers from P009 appear in a dropdown when creating the BOL in P012/P027.
The user selects the rail car number, and item details along with total quantity are automatically fetched into the BOL form.
Sales Order numbers are printed on the Bill of Lading document
D365 Path:P012/P027 → Bill of Lading Form → + New → Select Rail Car
2
🖨️
Step 2 — BOL Document Printed & Dispatched
Required Details Filled · BOL Document Printed from System
System-generated BOL · Attached to Sales Agreement · Dispatch documentation
📝
Required Details Filled
Carrier, consignee, commodity, quantity
→
🖨️
BOL Printed from System
Official BOL document generated
→
📎
Attached to Sales Agreement
Shipping documents linked to new SO
Step 2 — BOL Print & Dispatch Summary
Once all required fields are completed, the Bill of Lading document is printed directly from the D365 system. The BOL serves as the official dispatch document accompanying the rail car shipment.
For high-sea sale scenarios where goods are diverted, the relevant shipping documents (including the BOL) are subsequently attached to the newly created Sales Agreement for the new customer.
BOL documents are system-generated and traceable in D365
Sales Agreement number and Sales Order references are included on the BOL
🚧
Coming Soon
This section is currently being finalised. Step-by-step entry instructions will be available here shortly.
IN PROGRESS
Home › Transfer Journal
Transfer Journal Creation
Rail car to container serial number transfers via D365 auto-creation and Puls-E integration
🔁 D365 · P009 + Puls-E
📊 Transfer Journal — Rail Car to Container Flow
1
🔄
Step 1 — Auto Transfer Journal in P009 (Rail Car Confirm)
Rail Car Confirm → Transfer Journal Auto-Created in P009
Serial: NA → Rail Car No. · Missing serials auto-created · Batch added manually
✅
Rail Car Form Confirmed
Triggers auto TJ creation in P009
→
🔄
Transfer Journal Auto-Created
Item + qty from rail car form
→
🔢
Serial Numbers Updated
NA → Rail Car No. · new serials created if missing
Step 1 — Auto Transfer Journal Summary
When the user clicks Confirm on the rail car form in P012/P027, the system automatically creates a Transfer Journal in P009. The transfer journal picks item and quantity information directly from the rail car form.
The system compares rail car numbers with the serial number master of P009. For missing serial numbers, new serial numbers are automatically created. Batch information is added manually by the user on the transfer journal form.
No cost implications — only updates storage, product, and tracking dimensions
D365 Path:Inventory Management → Journals → Transfer (Auto from Rail Car Confirm)
2
🚢
Step 2 — Container Transfer via Puls-E → D365
Rail Car → Container · Serial Number Updated · Transfer Replicated in D365
Physical transfer in Puls-E · Rail Car serial → Container serial · Charges included
🚢
Physical Transfer (Puls-E)
Rail car goods moved to container
→
🔄
Serial Updated in Puls-E
Rail Car No. → Container serial no.
→
📡
Replicated to D365
Transfer journal with charges auto-posted
Step 2 — Container Transfer Summary
The physical transfer of goods from rail cars to containers happens in Puls-E. The serial number is updated in Puls-E from the Rail Car number to the respective Container serial number.
This transfer, along with any applicable charges, is replicated in D365 as a Transfer Journal. The D365 transfer journal reflects the updated container serial numbers and all relevant inventory dimensions.
Transfer is initiated and managed in Puls-E — D365 receives the replication
Charges associated with container stuffing are included in the replicated transfer
Stock is now tracked under container serial numbers in D365 and Puls-E
🚧
Coming Soon
This section is currently being finalised. Step-by-step entry instructions will be available here shortly.
IN PROGRESS
Home › Sales Agreement
Sales Agreement
Auto-created from DMS sales deal — approval workflow before sales order release
📋 D365 · P009
📑 Sales Agreement — DMS to D365 Flow
1
🤝
Step 1 — Sales Deal Confirmed in DMS
Counterparty Deal Agreed · Sales Deal Created & Approved in DMS
DMS deal negotiation · approval workflow · Confirmed status
🤝
Sales Deal Created in DMS
Commodity · Qty · Price · Terms
→
🔐
Approval Workflow
Deal reviewed and approved
→
✅
Deal Confirmed
Status: Negotiated → Confirmed
Step 1 — Sales Deal Confirmation Summary
Once the sales deal is agreed with the counterparty, it is created in the Deal Management System (DMS). The deal captures commodity, quantity, price, shipment terms, and counterparty details. It moves through an approval workflow before being confirmed.
System: Deal Management System (DMS)
Output: Confirmed Sales Deal in DMS, ready for D365 integration
2
📑
Step 2 — Sales Agreement Created in D365
Sales Contract Integrated from DMS → D365 · Approval Workflow
The confirmed DMS deal is integrated into D365 to create a Sales Agreement (Sales Contract), including any amendments. Delivery details are added to agreement line level via customization.
The Sales Agreement goes through an approval workflow: Draft → In Review → Approved → In Process → Completed. If rejected, it is marked Cancelled and synced back to DMS.
The created Sales Agreement and released SO are shared with Puls-E via D365 integration
D365 Path:Sales and Marketing → Sales Agreements → + New
3
🧾
Step 3 — Sales Order Released from Agreement
Sales Order Created & Released · Numbered to Agreement · Approval
Upon Sales Agreement approval, Sales Orders are created in D365. SO numbers align with the contract — e.g., SC/001 generates SC/001-01, SC/001-02. The user adds required charges per the agreement to the SO.
The SO goes through a value-based approval process. If rejected, amendments are made and re-submitted. Approved SOs proceed to the pick and pack stage.
Approval statuses: Draft → In Review → Approved → In Process → Completed → Cancelled
D365 Path:Sales and Marketing → Sales Orders → + New (from Sales Agreement)
🚧
Coming Soon
This section is currently being finalised. Step-by-step entry instructions will be available here shortly.
IN PROGRESS
Home › Customer Payment
Customer Payment
Record incoming customer payments and settle against outstanding sales invoices
💰 D365 · P009
💰 Customer Payment — End-to-End Flow
1
📋
Step 1 — Payment Journal Created
Receipt Journal Created Against Invoice / Customer · Submitted for Approval
The user creates a payment journal in D365 to record the receipt against an invoice or customer account. The journal is submitted for an approval process. Once reviewed and approved, the receipt is posted.
Posted receipts against invoice/customer are sent to a batch execution process where the posted transaction details flow from D365 to DMS for activity logging.
After posting, the payment is settled against the open customer invoice using the Settle Transactions function. The invoice status moves from Open → Settled once the full amount is applied.
Partial settlements are supported — a single payment can partially settle an invoice, or multiple payments can settle one invoice. The AR balance report is run to verify the outstanding customer balance.
Settlement status: Open → Partially Settled → Settled
Customer balance should reach zero after complete settlement
This section is currently being finalised. Step-by-step entry instructions will be available here shortly.
IN PROGRESS
Home › High-Sea Sale
High-Sea Sale
Transfer of goods ownership while in transit — original BOL endorsed to new buyer
🚢 DMS + D365 · P009
🚢 High-Sea Sale — Diversion & Re-Sale Flow
1
📦
Step 1 — Original Sale Posted (Packing Slip + Invoice)
First Dispatch: Packing Slip & Invoice Posted for Original Customer
IC or 3rd party sale · Packing slip posted · Invoice posted
📦
Packing Slip Posted
First dispatch for original customer
→
🧾
Invoice Posted
Revenue recognised for original customer
→
🚢
Goods in Transit
Container on high seas
Step 1 — Original Sale Posting Summary
GROUP posts the packing slip for the intercompany or 3rd party sale for the first dispatch. The packing slip records the deferred revenue and COGS delivered. The sales invoice is then posted, recognising revenue for the original customer.
Packing Slip GL: Dr System_COGS Delivered / Cr Inventory Account
Invoice GL: Dr Trade Receivables / Cr Export Sales + Dr COGS / Cr Inventory Account
2
🔄
Step 2 — Sales Return for Original Customer (Reversal)
Sales Return Created · Packing Slip & Invoice Reversed
Negative quantity equal to original SO · Return approval · Inventory reinstated
↩️
Sales Return Created
Against original sales order
→
📦
Packing Slip Reversed
Negative qty — inventory reinstated
→
🧾
Invoice Reversed
Customer balance reduced · revenue reversed
Step 2 — Sales Return (Reversal) Summary
When goods are to be diverted to a new customer, GROUP creates a sales return against the original sales invoice with a negative quantity equal to the original order. The sales return is submitted for approval, then packing slip and invoice reversals are posted.
Reversal Invoice GL: Dr Export Sales / Cr Trade Receivables + Dr Inventory / Cr COGS
Inventory is reinstated after the return process
3
🚢
Step 3 — New Sale to Diverted Customer
New Sales Agreement & SO Created · BOL Attached · New Customer Invoiced
Updated destination · New customer · BOL and shipping docs attached
📑
New Sales Agreement Created
For diverted/new customer
→
📦
Packing Slip + Invoice Posted
New customer sale completed
→
📎
BOL & Docs Attached
Shipping documents linked to new SA
Step 3 — New Customer Sale Summary
After completing the sales return, a new Sales Agreement and Sales Order are created for the new customer in D365, incorporating updated delivery and customer information. The relevant shipping documents — including the Bill of Lading — are attached to the new Sales Agreement.
The standard packing slip and sales invoice posting process is followed for the new customer sale.
New Invoice GL: Dr Trade Receivables (new customer) / Cr Export Sales + Dr COGS / Cr Inventory
D365 Path:Sales and Marketing → Sales Agreements → + New (new customer)
🚧
Coming Soon
This section is currently being finalised. Step-by-step entry instructions will be available here shortly.
IN PROGRESS
Home › Sales Return
Sales Return
Return sales order with credit note — restocks inventory and reverses original invoice
↩️ D365 · P009
↩️ Sales Return — End-to-End Flow
1
↩️
Step 1 — Sales Return Order Created
Return SO Created Against Original Order · Details Auto-Fetched
Original SO reference · Item, qty, rate auto-populated · Editable
↩️
Return SO Created
Against original sales order
→
📋
Details Auto-Fetched
Item · qty · rate from original SO
→
🔐
Return SO Approval
Submitted through workflow
Step 1 — Return Order Creation Summary
The sales return process is initiated when a customer wishes to return goods. In D365, the sales return is created against the original sales order. All details — item, quantity, rate — are automatically populated from the original SO. These details are editable to match business requirements.
The return SO header and lines are completed, then submitted through the approval workflow for the required authorities.
D365 Path:Sales and Marketing → Sales Orders → Return Order → Select Original SO
Standard packing process · Inventory increases · Customer balance reduced
📦
Pick & Pack Posted
Inventory reinstated (quantity increases)
→
🧾
Return Invoice Posted
Customer balance reduced
→
✅
Return Complete
Inventory updated · AR adjusted
Step 2 — Return Packing & Invoice Summary
Once the return SO is approved, the pick and pack process and invoicing are carried out as per the standard sales order process. However, the impact on inventory is reversed — inventory increases in the system (goods are returned to stock).
The customer balance is reduced by the posted return invoice value. A credit note may be raised for the customer if applicable.
GL (Return Invoice): Dr Export Sales / Cr Trade Receivables + Dr Inventory / Cr COGS