Module 4 · Configure financials · 165 min estimate
Journals, receivables, payables and fixed-asset controls
By the end, you can
- Configure bank accounts, journal templates, number series, batches and recurring journal templates.
- Set up customer/vendor accounts, related banking records, sales/purchase setup and payment/receipt workspaces.
- Explain master records, ledger entries, detailed entries and G/L relationships, and configure fixed asset books/classes/components/methods.
Follow the customer balance from invoice to application
- Customer cardDefaults and control-account mapping.
- Invoice ledger entryOriginal obligation: 1,200.
- Receipt ledger entryPayment: 900.
- Detailed applicationLinks payment to invoice and reduces remaining amount.
- ReconciliationOpen balance 300 agrees with G/L control under the test assumptions.
Create safe journal workspaces
A journal template establishes a journal’s purpose and behaviour. A batch provides a working subdivision within the template, often with its own numbering and balancing settings. Northstar’s two finance clerks should not accidentally edit the same working lines. Give them appropriate batches and permission scope, then test numbering, balancing account, source context and posting preview. Separate workspaces reduce mistakes; they do not provide independent authorisation by themselves.
Recurring journals add a repetition model. Select the recurring method according to whether the amount stays, is cleared, or needs a reversing pattern. Configure frequency and dates deliberately. A monthly expense journal that remains available after posting is useful only when its dates and amounts are reviewed before the next run. An allocation can distribute an amount across accounts or dimensions. Record the allocation basis so another person can reproduce the total rather than trusting the journal because it balanced.
Configure the bank subledger
Create a bank account card with the intended currency, identifiers, posting group and supported statement import/export configuration. The bank account ledger records bank transactions; the G/L account records their financial effect. A direct entry to the bank’s G/L control account does not automatically create a matching bank ledger entry. This is why a plausible G/L opening balance can still fail the first reconciliation.
Test supported file formats with a harmless sample and validate references, signs and dates. Exporting a payment file, posting the payment journal and receiving settlement confirmation are distinct events. A test should never send a real payment instruction. Use an approved simulation or isolated test workflow and ensure fictitious account details cannot be mistaken for real beneficiary instructions.
Build customer and vendor controls around their ledgers
A customer or vendor card holds master settings: posting group, currency, payment terms, method and relevant bank/address records. The ledger entry represents a posted commercial or settlement transaction, such as an invoice or payment. Detailed ledger entries track subsequent applications and related adjustments. G/L entries record the accounting effect. When an ageing balance is wrong, investigate remaining amounts and applications rather than editing the master record’s name or payment term.
Example: customer invoice INV-100 is 1,200. A receipt of 900 is applied to it with no discounts or exchange differences. The invoice’s original amount remains 1,200 while its remaining amount becomes 300. The customer’s net open balance is 300. Application evidence explains the change. Posting the same receipt without application can leave an open invoice and an open payment even though the net customer balance is 300. An ageing report and a simple net balance therefore answer different questions.
Configure Sales & Receivables Setup and Purchases & Payables Setup with the number series, defaults and controls needed for the business. Create cash receipt and payment journal batches with appropriate bank balancing and numbering. Payment Registration is a supported workspace for registering incoming customer payments; it is not a substitute for defining the customer’s payment terms. Validate a partial payment, a credit memo and an unapplied amount before accepting the design.
Use fixed assets as a maintained subledger
A fixed asset card identifies an asset and its classifications. A depreciation book defines depreciation and G/L integration choices for the relevant accounting purpose. Classes and subclasses organise reporting; a main asset and components represent a related asset structure. These classifications do not by themselves determine every posting account. Inspect the fixed-asset posting setup and integration settings.
Compare methods conceptually before calculating. Straight-line spreads depreciable cost over useful life under the selected settings. Declining-balance methods accelerate recognition by applying a rate to a reducing basis. A user-defined method follows an agreed pattern. Do not confuse book value with market value, or assume that one method satisfies every accounting and tax requirement. In a simplified straight-line example, an asset cost of 24,000 and residual value of 4,000 over five years gives a 20,000 depreciable basis and 4,000 per full year. Business Central’s actual schedule also depends on dates, method settings and depreciation-day conventions.
Plan a test that acquires a small asset, calculates depreciation into a journal, previews it and inspects the fixed-asset ledger alongside G/L. If a depreciation book is intentionally not integrated with G/L, the absence of a G/L entry is not automatically a defect. Explain the selected book’s purpose before deciding whether the result is correct.
Sandbox lab: Design settlement workspaces and a depreciation book
Use synthetic records in your authorised sandbox. Record the company and work date before posting. Never run this exercise in a customer’s production company.
- Create separate test journal batches and a bank card in a disposable company. Review number series and balancing fields.
- Configure one synthetic customer and vendor with terms, method, posting groups and related bank/address records.
- Inspect or post authorised small invoice and receipt examples. Apply a 900 receipt against a 1,200 invoice and compare original versus remaining amounts.
- Create a recurring-journal example, select its method and explain what should remain after posting. Do not schedule unattended posting.
- Create a fixed asset, classification and depreciation book. Specify whether G/L integration is intended.
- Calculate the simple 24,000 cost, 4,000 residual, five-year example independently. Compare it with the configured method and dates using posting preview.
Expected observations
- Each batch is identifiable and uses the intended numbering and balancing settings.
- Application leaves 300 on the customer invoice under the no-tax/no-discount assumptions.
- The depreciation-book design and expected ledger effects are documented before posting.
Evidence to retain
- Journal template/batch design
- Customer/vendor-to-ledger trace
- Partial payment application evidence
- Fixed-asset method comparison and preview
Cleanup
Remove unposted training lines and fictitious banking records. Reverse authorised posted entries using supported actions. Revoke temporary permissions and retain no real beneficiary data.
Common pitfalls
- Treating bank G/L postings as a complete bank-subledger implementation.
- Mistaking a net customer balance for proof that invoices and payments are applied.
- Assuming all depreciation books are integrated with G/L or that classifications select all posting accounts.
Check your understanding
1. A 1,200 invoice receives an applied 900 payment with no other adjustments. What are original and remaining amounts?
Original amount 1,200; remaining amount 300.
Application changes the amount still open. It does not rewrite the original invoice amount.
2. Two clerks need distinct journal working lines within the same journal type. What is appropriate?
Separate batches within a suitable journal template, with appropriate permissions.
The template defines the journal context; batches organise working lines and settings.
3. A fixed asset has no G/L depreciation entry. What must be checked before declaring an error?
Whether the selected depreciation book is configured for G/L integration.
A deliberately nonintegrated book serves a different reporting purpose.