Finance · F3

Accounts Receivable

8
Processes
349
Details worked out
44
Execution steps
8
Diagrams
F3.01

Customer Invoice Creation (Instant / Manual)

Creation of customer invoices directly in Accounts Receivable via Instant Invoice or Manual Customer Invoice, outside the order-to-cash sales flow. Covers header and line entry, tax handling, postings and credit check at invoice creation.

IFS Financials / Accounts Receivable
43 details
diagram
F3.02

Customer Payments & Matching (Mixed Payment)

Entry and matching of incoming customer payments using Mixed Payment, including payments on file, offsets, payments on account and cancellations. Payments match to open customer ledger items and generate vouchers to the general ledger.

IFS Financials / Accounts Receivable
43 details
diagram
F3.03

Reminders / Dunning & Collections

Creation and printing of customer reminders (dunning) on overdue balances using reminder proposals and multi-level reminder templates, plus follow-up on invoices that reach collection level. Reminder proposals load due open items and can calculate accrued interest.

IFS Financials / Accounts Receivable
41 details
diagram
F3.04

Interest Invoices & Write-offs

Creation and printing of interest invoices on customer invoices due or paid late, and management of write-offs and write-off notices for uncollectible amounts. Each customer is linked to an interest template; write-offs within tolerance are handled automatically at payment entry.

IFS Financials / Accounts Receivable
41 details
diagram
F3.05

AR Aging & Credit Management

Monitoring of customer credit activity and receivables aging: assignment of credit analysts, credit limits and credit checks, Customer Ledger Age Analysis reporting and DSO analysis. Supports proactive control of exposure and follow-up on outstanding balances.

IFS Financials / Accounts Receivable
41 details
diagram
F3.AM22

Service Contract Billing (Recurring, Usage & Outcome)

Turns aftermarket service agreements into cash across three commercial models: fixed recurring fees, usage-rated charges driven by meter readings, and outcome or availability-based charges with bonus and service-credit mechanics. In IFS Cloud the Service Contract carries the billing structure, periodic invoicing draws on contract calendars, Measurement readings and completed Work Order lines, and the resulting Invoice feeds revenue recognition and contract margin analysis. It is the process that makes servitization financially controllable rather than merely aspirational.

FinancialsManufacturing Aftermarket
47 details
diagram
F3.C42

Progress Valuation & Applications for Payment

Governs the periodic valuation of works in progress and the issue and certification of applications for payment (AFP) in IFS Cloud, covering both upstream client applications and downstream subcontractor applications. Progress measured against the IFS Cloud Project and Project Activity structure drives the gross valuation, from which retention, previous payments and contra charges are deducted to produce the net sum applied for. The process is aligned to the UK statutory payment regime of payment notices, notified sums and pay less notices.

Project ManagementConstruction
46 details
diagram
F3.R28

Rental Cycle Billing

Bills the recurring hire charge across the life of the rental in IFS Cloud. The customer invoice for rentals is based on rental transactions rather than deliveries, so the Generate Rental Transactions job must run before invoicing and a single rental order line can be invoiced many times throughout the hire. The transaction generation schedule on the order line drives the transaction end date and the planned invoice date, and rental lines can be consolidated onto the same invoice as other order lines.

FinancialsEquipment Dealers & Rental
47 details
diagram
What a license opens

Everything you can see here is real and current, the names, the structure and the counts come straight out of the ModelIFS library and change as it grows. What sits behind the license is the worked-out content itself: the execution steps, the data each one needs, the configuration decisions, the KPIs, the integration points, the workshop questions and the diagrams. That is the part you would otherwise spend a program building from nothing.

Sign in to open it