Financial Services covers the commercial and operational lifecycle of asset finance. It handles origination, structuring a deal for a specific product and country, running the calculation that prices it, and capturing the parties, asset and terms. A pipeline tracks each contract through its states: draft, submitted, credit approved, activated, performing, and then matured, terminated, defaulted or restructured. Once a contract is live, portfolio management takes over: schedules generate the expected cash flows, receipts are allocated back, arrears are detected and bucketed, and provisions are calculated.

The fourth pillar is analytics. Outstandings, arrears, balances and exposure are visible at every abstraction level: the individual contract, the customer aggregating all their agreements, the dealer with its flooring lines and inventory ageing, the product, the legal entity, the country and the whole portfolio. That multi-level visibility is computed at query time from the underlying contract, cash-flow and arrears data rather than held in a parallel reporting store, so a customer exposure figure and a portfolio NPL ratio are always drawn from the same source.

The contract is the atom of the module. Every cash flow, document and analytics query traces back to a single agreement, which carries its parties (lessee, lessor, guarantor, dealer or co-signer, each with a role and a share) and its subject asset, holding make, model, serial number, purchase price, residual value and condition. Point-in-time valuations record the asset's market, book and forecast residual value over the life of the deal, so loan-to-value is monitored rather than assumed.

Product behaviour is configured rather than hard-coded. Each of the four products is defined by its own base calculation parameters, and country-specific variants overlay local regulation, tax and documentation, so a Netherlands financial lease can treat VAT differently from a German one without becoming a separate product. Rate tables hold base rates and margin tiers by amount band and risk tier, effective-dated so a contract is always priced on the rules that applied when it was written. The flooring side adds a dealer record with its credit limit, facility limit and audit schedule, and jurisdiction rules hold the regulatory and tax logic per country. Reference and master data sit apart from the transactional record of schedules, arrears, curtailments and credit decisions, and every state change is written to an immutable audit log, so exposure can be trusted at contract, customer, dealer and product level alike.

A contract enters through origination and credit. A credit application captures the requested amount, term and applicant; a scorecard produces a score, risk grade and the PD, LGD and EAD used downstream; and a credit decision records approve, decline, refer or conditional, with approved amount, rate and term. Only on a credit-approved contract does activation occur, at which point the relevant engine generates the payment or amortisation schedule and the first financial events are pushed to Accounting & Control.

From there the contract runs its servicing cycle. Invoice requests are raised on the schedule and sent to A&C for AR creation; receipts matched in A&C are allocated back and reduce the outstanding balance; interest accrues and, for dealer flooring, does so daily per unit. The arrears engine detects past-due amounts, assigns them to ageing buckets and escalates, while the provisioning engine stages exposures under IFRS 9 and books expected credit loss. Product-specific workflows sit alongside: operational lease captures usage readings, service events and end-of-lease return conditions; dealer flooring processes unit sales through a repayment waterfall, applies curtailments on ageing stock, and reconciles physical inventory audits. Early termination and restructuring are first-class events, each producing its own settlement calculation and posting.

The four calculation models are genuinely different, which is why each has its own engine over a shared financial-math library of present value, annuity factors and day-count conventions. Financial lease is an amortising-debt model: payments split into interest on the outstanding balance and principal, by annuity or linear method, optionally reduced by a residual, and the module produces the IFRS 16 right-of-use asset and lease liability as the present value of lease payments at the implicit or incremental borrowing rate. Operational lease is a total-cost-of-ownership build-up: the rental is assembled from economic depreciation, residual value risk, maintenance, insurance, road tax, cost of capital at WACC and a profit margin, with over and under-usage settled against contracted volumes.

Equipment financing is asset-backed credit, where loan-to-value and debt-service-coverage drive both underwriting and ongoing monitoring: an LTV breach triggers a margin call or additional collateral, and residual value is stress-tested across base, low and stressed recovery scenarios. Dealer flooring is a revolving facility with no amortisation schedule at all: availability is the limit less outstanding unit advances, interest accrues daily from floorplan date to sale, and mandatory curtailments step up with inventory age until full repayment is demanded. Across all products, provisioning follows IFRS 9 expected credit loss with stage 1, 2 and 3 classification computed as PD times LGD times EAD, and portfolio metrics such as NPL ratio, provision coverage, average yield and collection rate roll up consistently from the same contract-level data.

Financial Services is an integrated specialist, not an island. Its most important relationship is with Accounting & Control, reached through an event bridge rather than duplicated ledger logic. Contract activation recognises a lease receivable or, for a lessor-owned operational lease, a fixed asset; periodic invoices become AR invoices with journal entries; interest accruals, depreciation, residual revaluations, impairments, settlements and write-offs each map to a defined posting. Receipts flow the other way, matched in A&C and allocated back to the originating contract, and flagged arrears are handed to the A&C Collections capability for recovery.

Document Management is the home for the paperwork a finance book accumulates: signed contracts, asset inspection reports, insurance certificates, credit assessments, correspondence and amendments, linked through the suite's polymorphic attachment model against the contract. Financial Services also bridges to the Product & Service Catalog, linking its own product definitions and financed assets to catalogue products so that a configured, quoted item can be carried into financing and reported on across the commercial and finance sides. Permissions run on the suite-wide model, with a coarse module subject gating visibility and fine-grained subjects per product and per function, including a dedicated credit-decision right.

The suite treats AI Workers as first-class users, and in a finance book that is where much of the leverage sits. Workers query the module conversationally, answering questions such as total exposure for a customer, the arrears distribution for a dealer, or the LTV spread across the equipment book, resolving them against the same multi-level analytics that the dashboards use, and bounded by the same permission subjects a human holds. They execute actions within those bounds: running a TCO or amortisation calculation, generating a schedule, raising an invoice request, or recording a usage reading.

Because the book is event-driven, Workers are effective at anomaly and exception alerting: an LTV breach, a DSCR deterioration, a dealer unit crossing a curtailment threshold, an ageing bucket shift or a contract sliding into a worse IFRS 9 stage can each be surfaced the moment the underlying data moves. They perform document and data extraction, reading a signed contract, an insurance certificate or a financial statement held in Document Management and lifting the structured terms back onto the contract or credit application. And they act as a decision-support and review node in workflows, pre-scoring a credit application, drafting a recommendation with its rationale, or sitting as a named approval or review step in the credit and restructuring flows, with every action they take written to the same audit trail as any other user.