ExamFinch.com My Study

Study guide

15.3 Budget Transfer Rules & Processing Budget Transfers

Practice this exam

Microsoft Certified: Dynamics 365 Finance Functional Consultant Associate MB-310

Track your progress as you read

Finished sections get a check mark.

1 Chapter 1: MB-310 Exam Overview & Financial Architecture

1.1 MB-310 Exam Structure, Skills Measured & Consultant Role 1.2 Dynamics 365 Finance Architecture, Legal Entities & Global Address Book 1.3 Hands-on Lab Strategy & Preparation Framework

2 Chapter 2: Chart of Accounts & Main Accounts

2.1 Designing Chart of Accounts & Main Account Types 2.2 Main Account Categories & Ledger Account Aliases 2.3 Balance Control Accounts & Year-End Opening Account Setup 2.4 Legal Entity Overrides for Main Accounts & Dimensions

3 Chapter 3: Financial Dimensions & Account Structures

3.1 Custom & Entity-Backed Financial Dimensions 3.2 Financial Tags: Limits, Storage & Ledger Settlement Use 3.3 Account Structures, Segment Criteria & Activation 3.4 Advanced Rules & Advanced Rule Structures 3.5 Derived Dimensions & Dimension Default Templates

4 Chapter 4: Ledgers, Calendars & Currencies

4.1 Fiscal Calendars, Period Statuses & Module Access Control 4.2 Posting Layers, Multi-GAAP Reporting & the Ledger Form 4.3 Currency Exchange Types, Rate Providers & Triangulation 4.4 Accounting & Reporting Currencies (Dual-Currency Architecture) 4.5 Foreign Currency Revaluation & Revaluation Posting Profiles

5 Chapter 5: General Ledger Journals & Allocations

5.1 Journal Names & Voucher Number Sequences 5.2 Journal Control & Posting Restriction Rules 5.3 Journal Entry, the One-Voucher Rule, Validation & Posting 5.4 Reversals, Storno Corrections & Excel Integration 5.5 Ledger Allocation Rules & the Four Allocation Methods 5.6 Allocation Processing & Periodic (Recurring) Journals

6 Chapter 6: Intercompany Accounting & Settlements

6.1 Intercompany Accounting Setup & Due-To / Due-From Postings 6.2 Intercompany Journal Processing & Multi-Company Vouchers 6.3 Ledger Settlements Configuration & Processing

7 Chapter 7: Cash and Bank Management

7.1 Bank Groups, Bank Accounts & Ledger Integration 7.2 Payment Formats, Bank FX Revaluation & Shared Payment Setup 7.3 Manual vs. Advanced Bank Reconciliation & Statement Formats 7.4 Matching Rule Sets, Reconciliation Execution & Reversals 7.5 Cash Flow Forecasting Setup & Automation 7.6 Customer and Vendor Netting

8 Chapter 8: Periodic Closing & Financial Consolidations

8.1 Financial Period Close Workspace, Closing Roles & Schedules 8.2 Year-End Close Configuration & General Ledger Balance Carryforward 8.3 Consolidations Online: Legal Entity Setup, COA Mapping & Currency Translation 8.4 Import Consolidations & Intercompany Elimination Rules

9 Chapter 9: Sales Tax & Withholding Tax

9.1 Sales Tax Engine Hierarchy, Authorities & Settlement Periods 9.2 Ledger Posting Groups, Sales Tax Codes & Calculation Methods 9.3 Sales Tax Groups, Item Sales Tax Groups & Tax Exemptions 9.4 Sales Tax Adjustments and Settle and Post Sales Tax 9.5 Withholding Tax & US 1099 Vendor Reporting

10 Chapter 10: Accounts Receivable Setup & Invoicing

10.1 Customer Master, Customer Groups & Shared Customers 10.2 Customer Posting Profiles & Account Code Precedence 10.3 Free Text Invoices, Recurring Invoice Templates & AR Charges 10.4 Sales Order Invoicing, Billing Classifications & Prepayments 10.5 Customer Payment Methods, Payment Processing & Customer Bank Accounts

11 Chapter 11: Credit Management & Collections

11.1 Credit Management Architecture & Customer Credit Groups 11.2 Risk Scoring, Credit Limits, Blocking Rules & Credit Holds 11.3 Aging Definitions, Collections Workspace & Customer Pools 11.4 Collection Letter Sequences & Interest Notes 11.5 Customer Write-Offs, Bad Debt & Write-Off Reversals

12 Chapter 12: Subscription Billing & Revenue Deferrals

12.1 Recurring Contract Billing, Billing Schedules & Milestones 12.2 Deferral Principles, Deferral Defaults & Schedule Calculation Methods 12.3 Recognition Processing, Expense Deferrals & Modifying Schedules 12.4 Multiple Element Revenue Allocation (MEA / ASC 606)

13 Chapter 13: Accounts Payable & Invoice Processing

13.1 Shared Vendors, Global Address Book & Vendor Groups 13.2 Vendor Posting Profiles, AP Parameters & Vendor Bank Accounts 13.3 Invoice Matching Setup (2-Way, 3-Way), Tolerances & Exceptions 13.4 Vendor Invoicing Methods, Journals & Invoice Automation

14 Chapter 14: Vendor Payments & Expense Management

14.1 Methods of Payment & the Vendor Payment Proposal Engine 14.2 Generating Payments, Centralized Payments & Check Lifecycle 14.3 Expense Management Configuration, Categories & Policies 14.4 Expense Reports Processing, Mobile Receipts & Intercompany Expenses

15 Chapter 15: Budgeting & Budget Control

15.1 Budget Models, Budget Codes & Allocation Terms 15.2 Budget Register Entries, Workflows & Budget vs. Actual 15.3 Budget Transfer Rules & Processing Budget Transfers 15.4 Budget Control Configuration, Cycles, Rules & Budget Groups 15.5 Budget Funds Available, Over-Budget Permissions & Document Budget Check 15.6 Budget Planning Framework, Organization Hierarchies & Planning Processes 15.7 Budget Plans, Scenarios, Allocations & Generating Register Entries

16 Chapter 16: Fixed Assets Configuration & Transactions

16.1 Fixed Asset Groups, Asset Records & Group/Book Mapping 16.2 Depreciation Profiles: Methods & Conventions 16.3 Fixed Asset Books, Derived Books & Posting Profiles 16.4 Fixed Asset Acquisition Pathways 16.5 Depreciation Proposals, Multi-Company Runs & Fixed Asset Budgets 16.6 Fixed Asset Disposals: Sale, Scrap & Disposal Accounting 16.7 Fixed Asset Splits, Transfers & Reclassification 16.8 Asset Leasing (IFRS 16 / ASC 842)

15.3 Budget Transfer Rules & Processing Budget Transfers

Key Takeaways Explain This Topic AI

Budget transfer rules only take effect after Use rules for budget transfers is selected on the Budgeting parameters page.

A transfer that violates the rules does not update budget balances and can be completed only through Budgeting workflow approval.

A budget transfer is an ordinary budget register entry on a Transfer budget code, with a negative source line and offsetting positive destination lines.

A budget register entry becomes Completed once balances are updated and can never be reopened; corrections require a new entry.

Transfers move existing budget sideways, whereas revisions change the total authorized budget amount.

Last updated: August 2026

15.3 Budget Transfer Rules & Processing Budget Transfers

Quick Summary: A revision changes how much budget an organization has. A transfer does not — it moves existing budget sideways between financial dimension values, leaving the total authorization untouched. Because transfers are the easiest way for a department to quietly fund something the board never approved, Dynamics 365 Finance provides budget transfer rules to say which moves are allowed without approval and which must go through a workflow. The MB-310 blueprint names transfer rules explicitly in "Configure budgeting components, including budget models, codes, allocation terms, and transfer rules."

1. Turning the feature on

Budget transfer rules are off by default . Enable them with a single parameter:

Budgeting > Setup > Budgeting parameters → select Use rules for budget transfers .

While you are on that page, note the other fields the exam likes to test:

  • Field What it does
  • Allocation key Determines how a budget account entry amount is allocated in the cash flow forecast
  • Use rules for budget transfers Enables budget transfer rules
  • Display legacy budget analysis inquiry Shows the older budget analysis inquiry page

Default account structure Auto-populates the account structure on the budget register from the main account (requires the Default the account structure in the budget register entry feature)

Budget journal The journal name used for budget appropriations; visible only when Enable budget appropriation is set on General ledger parameters

2. What a transfer rule actually controls

A transfer rule is a statement about which source and destination financial dimension values may exchange budget without an approval step . Microsoft's own worked example is the clearest model to memorize:

Allowed without approval: expense budget transferred between main accounts inside the Sales and Marketing department.

Blocked without approval: budget transferred into or out of the Sales and Marketing department.

So the rule set draws a boundary. Inside the boundary, money can slosh around freely. Crossing the boundary demands governance. +------------------------------------------------------------------+

  • | Sales & Marketing department (Dept 030) |
  • | |
  • | 600100 Travel <----- allowed, no workflow -----> 600200 Ads |
  • | |
  • +---------------------------|--------------------------------------+
  • |
  • crossing the department boundary
  • |
  • v
  • +------------------------------------------------------------------+
  • | Operations department (Dept 020) |
  • | 600300 Maintenance -- requires Budgeting workflow approval -- |
  • +------------------------------------------------------------------+
  • The enforcement mechanic — know this precisely

When budget transfer rules are in use and a user creates a document with a budget code of the Transfer type, budget balances are not updated if the transfer rules are violated . The entry is not silently discarded and it is not hard-blocked at data entry either: the transfer can still be completed, but only if it is approved through a Budgeting workflow .

That is the distinction candidates lose marks on. Transfer rules are not a hard prohibition — they are a routing decision that determines whether a transfer settles straight away or has to earn an approval.

3. Processing a budget transfer, step by step

A transfer is not a separate document type. It is an ordinary budget register entry whose budget code happens to carry the Transfer budget type.

Go to Budgeting > Budget register entry and create an entry.

On the Budget register entry FastTab, select a budget model and a budget code that is associated with the Transfer budget type .

In the Budget account entries grid, select Add line for the account structure and dimension values you are transferring from , and enter a negative amount — for example -1,000.00 .

Select Add line again for the dimension values you are transferring to , and enter the offsetting positive amount, 1,000.00 . Multiple receiving lines are fine as long as the entry nets to zero.

Select Update budget balances .

If a workflow is activated for that budget code, the transfer request is submitted to the workflow. If no workflow is activated, select OK or enter batch criteria and the balances update immediately.

Once balances are updated the entry status becomes Completed , and a completed budget register entry cannot be reopened for edits . Correcting a bad transfer means creating a new budget register entry, not editing the old one.

4. How transfers interact with budget control

Under budget control, the budget funds available figure is what blocks or warns on a purchase order or journal. Transfers and revisions are the two sanctioned ways to change that figure mid-cycle:

  • Situation Correct instrument
  • Department has money, but in the wrong account Transfer budget code
  • Department genuinely needs more total budget Revision budget code
  • User just needs to exceed the limit once Over-budget permission, not a budget change
  • Prior-year money must fund this year Carry-forward budget code

Two boundary conditions worth remembering: transactions — including budget register entries — posted before budget control was turned on are not considered for budget control , so beginning-balance entries must be updated after budget control is switched on; and allocation terms are not supported when budget control is enabled , because budget control needs to know every accounting distribution before the document posts.

Exam traps in this section

Transfer rules do nothing until Use rules for budget transfers is selected on Budgeting parameters .

A violated transfer rule stops the balance update , not the data entry; workflow approval is the escape hatch.

A transfer entry must net to zero — negative source line(s), offsetting positive destination line(s).

A Completed budget register entry can never be edited; issue a new entry instead.