Reconciliation, Allocations & FX Adjustments
Bank reconciliation ensures your books match the bank. GL allocations distribute costs across dimensions. Exchange rate adjustments revalue foreign currency balances. Three essential month-end processes.
Month-end: Making the numbers match
Month-end is like balancing your spending notebook against your bank app.
You check every transaction on your bank statement and tick it off in your notebook. Some things are in the notebook but not the bank yet (that cheque you posted on Friday). Some things are on the bank but not in your notebook (a direct debit you forgot about). You sort out the differences until both sides agree.
At Coastal Traders, Olivia does this every month β plus she splits shared costs across departments and adjusts for currency swings on their overseas invoices. Three jobs, one goal: accurate financial statements.
Bank account reconciliation
Bank reconciliation is the process of matching your Business Central bank ledger entries against the actual bank statement. The goal is to confirm that every transaction BC knows about also appears on the bank statement, and vice versa.
The reconciliation process
Olivia reconciles the operating account at the end of each month:
- Open Bank Account Reconciliations (Tell Me > βBank Account Reconciliationβ)
- Select the bank account, enter the Statement Date and the Statement Ending Balance from the bank statement
- Import the bank statement file (CAMT, CSV) or enter lines manually
- Suggest Lines Matching β BC auto-matches by amount, date, and description
- Match Manually β pair remaining lines by selecting a statement line and one or more BC entries
- Transfer Difference to GL Account β for bank fees or interest not yet recorded in BC, post directly from the reconciliation
- Review outstanding items β cheques not yet cleared, deposits in transit. These are normal and will match next period.
- When the Difference is zero, click Post to finalise
Exam tip: Outstanding items are normal
The exam may present a scenario where cheques written in the last few days have not cleared the bank. This does NOT mean the reconciliation is wrong. Outstanding cheques and deposits in transit are expected β they simply have not reached the bank by the statement date. They should appear on next monthβs statement.
Payment reconciliation journal vs bank account reconciliation
These two features sound similar but do very different things.
| Feature | Payment Recon Journal | Bank Account Reconciliation |
|---|---|---|
| Purpose | Create and post payments from bank data | Match existing BC entries against the bank statement |
| Creates entries? | Yes β posts customer/vendor ledger entries | No β only matches what already exists |
| When to use | Processing incoming payments from the bank | Verifying BC and the bank agree at month-end |
| Matching | Matches bank lines to open customer/vendor entries | Matches bank lines to existing bank ledger entries |
| After posting | New payment entries created and applied | Existing entries marked as reconciled |
Think of it this way: Payment Reconciliation Journal = incoming work (turning bank data into BC entries). Bank Account Reconciliation = checking work (confirming BC and the bank agree).
Olivia imports a bank statement into BC and notices several customer payments that were deposited but never recorded. Which feature should she use?
Recurring journals β operational context
We covered recurring journal setup in Domain 2. Here, we focus on how they fit into month-end operations.
Olivia has these recurring journals posting each month:
| Recurring Entry | Method | Why |
|---|---|---|
| Office rent ($4,500) | Fixed | Same amount, split across departments |
| Depreciation | Variable | Changes as assets are added or disposed |
| Insurance accrual ($1,000) | Fixed | Annual policy spread over 12 months |
| Reversing accruals | Reversing Variable | Estimated expenses that auto-reverse next period |
Recurring methods quick reference
| Method | Behaviour |
|---|---|
| Fixed | Same amount every period |
| Variable | You update the amount before each posting |
| Balance | Posts whatever is needed to reach a target balance |
| Reversing Fixed | Posts a fixed amount, then auto-reverses on the next posting date |
| Reversing Variable | Posts a variable amount, then auto-reverses |
| Reversing Balance | Posts to reach a target balance, then auto-reverses |
Why reversing journals matter
Olivia estimates $3,200 electricity for March, but the invoice will not arrive until April. She posts a Reversing Variable entry on March 31. On April 1, it auto-reverses. When the real invoice arrives at $3,150, she posts it normally β both months are clean. The exam loves reversing scenarios: the reversal happens on the NEXT posting date automatically.
GL allocations
Some costs benefit multiple departments but arrive as a single invoice. GL allocations let you distribute those costs across dimensions automatically.
How allocations work
Olivia pays $4,500 in rent each month. The office space is shared:
- Sales department uses 40% of the floor space
- Operations uses 30%
- Administration uses 30%
Instead of manually splitting every rent entry, she sets up an allocation account that distributes the cost automatically.
Setting up allocation accounts
- Open GL Allocation Accounts (Tell Me > βGL Allocation Accountβ)
- Create an account (e.g., ALLOC-RENT β βRent Allocationβ)
- Define the distribution β where the cost goes:
| Share | Account | Department | Percentage |
|---|---|---|---|
| 1 | 6100 (Rent Expense) | SALES | 40% |
| 2 | 6100 (Rent Expense) | OPERATIONS | 30% |
| 3 | 6100 (Rent Expense) | ADMIN | 30% |
Fixed percentage allocation means you define the split manually (40/30/30). Variable percentage recalculates the split from actual data like headcount or revenue per department.
Running allocations
Olivia posts the full rent to a holding account, then runs the allocation:
- Post $4,500 to account 6099 (Rent β Unallocated)
- Run the allocation β BC creates entries that debit 6100 per department (SALES $1,800, OPERATIONS $1,350, ADMIN $1,350) and credit 6099 for $4,500
- The holding account zeros out and each department carries its fair share
Exam tip: Allocation accounts
BC has two allocation mechanisms: GL Allocation Accounts (distribute from one GL account to multiple accounts/dimensions) and Allocation keys on journal lines (split a journal line across dimensions during posting). The exam typically tests GL Allocation Accounts. Allocation happens AFTER the initial posting β the source entry must exist first.
Coastal Traders pays a $6,000 monthly IT support bill. The cost should be split based on headcount: Sales has 20 employees, Operations has 15, and Admin has 10. What type of allocation should Olivia use?
Adjust currency exchange rates
Coastal Traders is an import/export business β they buy in USD and EUR but report in NZD. When exchange rates move between recording and paying an invoice, the NZD value of open entries changes.
Why exchange rate adjustments matter
Marcus entered a USD $10,000 purchase invoice on March 5 when the rate was 1 USD = 1.62 NZD. BC recorded it as NZ$16,200.
By March 31 (month-end), the rate has moved to 1 USD = 1.67 NZD. The same invoice is now worth NZ$16,700 in todayβs money. That is a NZ$500 difference β and since Coastal Traders has not paid it yet, their liability is understated.
The Adjust Exchange Rates batch job fixes this by revaluing all open foreign currency entries to the current rate.
What gets adjusted
The batch job revalues open vendor entries (unpaid purchase invoices), open customer entries (unpaid sales invoices), foreign currency bank account balances, and GL accounts if you use an Additional Reporting Currency.
Running the adjustment
- Open Adjust Exchange Rates (Tell Me > βAdjust Exchange Ratesβ)
- Set the period (Starting/Ending Date), Posting Date, and Document No. (e.g., FX-MAR2026)
- Filter by currency if needed (USD, EUR, or blank for all)
- Select which entry types to revalue (Customer, Vendor, Bank)
- Click OK β BC calculates the difference between the original rate and current rate for every open entry and posts to unrealised gains/losses accounts
Unrealised vs realised β the lifecycle
Here is what happens to Marcusβs $10,000 invoice:
- March 5 (posted): USD $10,000 at 1.62 = NZ$16,200
- March 31 (adjustment): Rate now 1.67 = NZ$16,700. Unrealised loss of NZ$500 posted (liability increased)
- April 15 (paid): Rate is 1.64 = NZ$16,400. BC reverses the unrealised entry and posts a realised loss of NZ$200 (the actual difference between invoice rate and payment rate)
Update rates BEFORE adjusting
The batch job uses rates from the Currency Exchange Rate table. If you forget to update rates first, BC uses old rates and the adjustment is wrong. Always enter current rates (manually or via the automatic exchange rate service) BEFORE running the batch job.
Marcus runs the Adjust Exchange Rates batch job at March month-end. An open EUR customer invoice was posted at 1 EUR = 1.75 NZD. The March 31 rate is 1 EUR = 1.70 NZD. What adjustment is posted?
Month-end checklist
| Step | Task | Why This Order |
|---|---|---|
| 1 | Post recurring journals | Standard monthly entries into the ledger first |
| 2 | Run GL allocations | Distributes shared costs β needs recurring entries posted |
| 3 | Update exchange rates | Current rates needed before revaluation |
| 4 | Run Adjust Exchange Rates | Revalues open foreign currency entries |
| 5 | Reconcile bank accounts | Done last β earlier steps may create bank-affecting entries |
| 6 | Review and close | Trial balance, P and L review, close the period |
Why order matters
Bank reconciliation comes last because exchange rate adjustments on foreign currency bank accounts change the LCY balance. If you reconcile first, you would need to reconcile again. The exam may ask about correct sequence: post first, adjust second, reconcile last.
Knowledge check
During bank reconciliation, Olivia finds a $45 bank fee on the statement that was never recorded in BC. What should she do?
π¬ Video coming soon
Next up: The final module β fixed asset transactions. Youβll learn how to acquire assets, depreciate them over time, and dispose of them when theyβre no longer needed. The complete asset lifecycle with GL entries at every stage.