Topic
Core systems under load
How we replace core systems during live operation.
03.3Success story · Financial services
Financial Service Plus
A core system that grows with the business.
We rebuilt the core system for Financial Service Plus's factoring business as a multi-tenant platform and replaced the legacy system during live operation.
Core system
One model
Processes, roles and reporting in one model instead of copies per client.
Operation
No standstill
Replacement in stages, with real process volume in daily business.
Recreated views · all figures illustrative
01Fact sheet
Financial Service Plus at a glance.
Scope details from our own project communication.
- Client
- Financial Service Plus
- Industry
- Financial services · Factoring
- Role
- Architecture · Engineering · Evolution
- Services
- Modernisation & software architecture · Digital products & platforms · Operation and evolution
- Platform
- Multi-tenant process platform
- Replacement
- First the process chain, then reporting, then the tenants; every stage live before the next
02Starting point & goal
Rebuild without stopping.
Financial Service Plus runs factoring: buying receivables, checking them, paying out, monitoring. The previous core system had grown over years and worked, but extending it for new products and tenants took considerable effort. Booking day, audit trail and payout had to keep running while the platform underneath was exchanged.
- Take on new tenants without special cases
- Map the factoring chain close to the process
- Bring reporting into the core instead of calculating beside it
03Tenant model
One model instead of copies per client.
In the legacy system every tenant was a separate variant in the code, so each change had to be implemented and tested several times. In the new platform a tenant is a record with parameters: process variant, assignment type, payout rule, dunning levels.
Difference
Configuration
What separates tenants is a parameter, not a branch of its own in the code.
Recreated views · all figures illustrative
Limits and usage in the core
Purchase limits per debtor, their usage and any breaches live in the core system instead of a separately maintained side calculation.
core system · debtor portfolio · limit approval
Limit was edited successfully.
Limit processing
Customer:Lipsia Digital, Reichsstraße 1–9, DE 04109 Leipzig Customer no.: 2700021Debtor:Musterlogistik, Grassistraße 12, DE 04107 Leipzig
CDR ID: 75, System ID: 2, ERP ID: 1080000
CDR ID: 75, System ID: 2, ERP ID: 1080000
Active? ✔Factoring type: Full-service factoringRisk class: 2 - Risk customerDamage level 0Head officeAddress verification
Contract start: 04.08.2019Factoring procedure: open procedureFollow-ups 0Country risk: 0 - no riskBalance confirmation:Create
Limit approval
Requested limit35.000Credit score-Maximum credit/credit limit-
Insurance limit10.000Risk class-pos. payment experience-
Additional limit-Grade/rating-
The data of the currently active policy is shown.Financing typeFactoring
Change| ID↑↓ | Type↑↓ | Subtype↑↓ | Credit limit↑↓ | Valid from (internal)↑↓ | valid from↑↓ | valid until↑↓ | Created on↑↓ | Created by↑↓ | Actions↑↓ | Attach note↑↓ |
|---|---|---|---|---|---|---|---|---|---|---|
| 5 | Credit limit | named | 10.000 | 19.10.2026 | 19.10.2026 | 19.10.2026 | Lars Busch | Deactivate |
Note
Add limitReject limitApprove limitCancel
Approvals
| Limit IDs↑↓ | Approved on↑↓ | Approved by↑↓ | Limit↑↓ | Role↑↓ | Pending approval↑↓ |
|---|---|---|---|---|---|
Check
One state
Limit check and reporting calculate on the same basis.
Reporting without a second system
Volume, balances and due dates per tenant are reported directly from the core system. The detour through exports and spreadsheets is gone.
core system · reports · s8 debtor master data
Master dataStatusDebtor analysis
25entriesDownload ExcelCalculate totals
| Σ | Σ | |||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| CDR ID↑↓ | System ID↑↓ | Master↑↓ | Customer no.↑↓ | Customer↑↓ | Branch / CC↑↓ | Old debtor no.↑↓ | Debtor↑↓ | Street↑↓ | Country↑↓ | ZIP↑↓ | City↑↓ | Legal form↑↓ | Open items↑↓ | Purchased balance↑↓ | Financing type↑↓ | Payment term↑↓ |
| 3 | 3 | 2019001 | Musterlicht Gruppe | EX-679-16-6142 | Beispielreifen | Hermann-von-Helmholtz-Str. 683 | DE | 61067 | Saschaberg | Credit check | ||||||
| 4 | 4 | 2019001 | Musterlicht Gruppe | EX-439-15-5187 | Beispielreifen | Dürerstr. 905 | DE | 42154 | Andreasdorf | Credit check | ||||||
| 5 | 5 | 2019001 | Musterlicht Gruppe | EX-887-80-0377 | Beispielreifen | Warnowstr. 448 | DE | 83222 | Neu Jimmyhagen | Credit check | ||||||
| 9 | 9 | 2019003 | Beispiel Handels AG | EX-571-04-2493 | Beispiel Heimwerker | Feuerdornweg 652 | DE | 53556 | Bad Sandyhagen | Credit check | ||||||
| 10 | 10 | 2019003 | Musterbau Gruppe | EX-789-07-3281 | Beispiel Heimwerker | Lötzener Str. 692 | DE | 43432 | Marisaheim | Credit check | ||||||
| 11 | 11 | 2019016 | Beispiel Metall KG | EX-796-44-5782 | Beispiel Heimwerker | Speestr. 271 | DE | 82299 | Groß Julinascheid | Credit check | ||||||
| 125 | 6 | 6 | 2019022 | Muster Backwaren GmbH | EX-430-28-8947 | Beispielwerke | Hans-Gerhard-Str. 278 | DE | 31081 | West Darleen | Credit check | |||||
| 125 | 7 | 7 | 2019025 | Beispiel Schuh AG | EX-624-59-5155 | Beispielwerke | Sanddornstr. 109 | DE | 09116 | Sackheim | Credit check | |||||
| 125 | 8 | 8 | 2019040 | Muster Spielwaren KG | EX-418-34-1518 | Beispielwerke | Niederblecher 138 | DE | 81595 | Wesselscheid | Credit check | |||||
| 75 | 2 | 2 | 2700021 | Lipsia Digital | EX-113-99-0388 | Musterlogistik | Springerstr. 17 | DE | 04105 | Leipzig | Factoring | |||||
| 75 | 1 | 1 | 2700022 | Beispiel Systeme GmbH | EX-836-28-7224 | Musterlogistik | Grassistraße 12 | DE | 04107 | Leipzig | Factoring |
1 to 11 of 11 entries1
Source
1
One data base for processing and reporting.
Recreated views · all figures illustrative
04Purchase and review
The chain as the department counts it.
Purchase, review, payout, collection: the platform maps the stages the way back office works with them, with balances, rules and a log for every step.
Batch
126 items
An invoice batch with a status per item. Review cases are visible at once.
Rules
5
Rules per item: master data, duplicate, limit, assignment, release.
Recreated views · all figures illustrative
Rules are part of the process
Every item passes the same rules, and the rule that applies is shown on the case. A rule does not have to be renegotiated for every case.
core system · invoice processing · post-processing
Post-processing - Invoice M1675 (Rechnungsvorlage.pdf)
1Document informationError messageDocument check (upstream)1
Document address/debtor assignmentAssign debtor
Old debtor no.???
Debtor no. (ERP)
NameMuster & Söhne
Addition
StreetSchnurlos-Straße 81
ZIP34131
CityKassel
CountryGermany
Document information
Credit note procedure
Document typeInvoice
Document date19.10.2026
Document numberM1675
CurrencyEUR - Euro
Net 1186,99
Tax rate 119,0 %
Tax amount 135,53
Muster GmbH
Muster GmbH Lange Str. 2 | 10245 Berlin
Muster & SöhneSchnurlos-Straße 8134131 Kassel
Muster GmbHLange Str. 210245 Berlin+49 (0) 30 2121356mail@muster.dewww.muster.de
Invoice
| Pos. | Item no. | Description | Qty | Unit | Price/unit (€) | Total (€) |
|---|---|---|---|---|---|---|
| 1 | B-3025-078 | B-3025, color greenSample item | 1,00 | pcs. | 47,00 | 47,00 |
| 2 | B-0050-050 | B-0050, color blueSample item ABC | 2,00 | pcs. | 36,00 | 72,00 |
| 3 | A-0086-007 | A-0086, antique lookSample item | 1,00 | pcs. | 56,00 | 56,00 |
| 4 | V-13kg | Shipping and packaging | 1,00 | pcs. | 11,99 | 11,99 |
Subtotal net€ 186,9919,00% VAT on 186,99 €€ 35,53Total€ 222,51
Delivery terms: free deliveryPayable within 14 days with 3 % discount or within 30 days netBoundary
1 check flag
The rule stops the item, back office decides on the release.
A log instead of reconstruction
Receipt, master data match, triggered rule, submission for release: the history sits on the document and stays traceable, even for questions months later.
Audit trailRE-104 222
Received from client system14 Mar · 06:02 · interface
Master data match14 Mar · 06:02 · automatic
Limit check triggered14 Mar · 06:03 · rule L-12
Submitted for release14 Mar · 08:44 · back office
Every step is traceable — a precondition for audit and revision.
Evidence
Every step
Time, trigger and rule stay with the case.
Recreated views · all figures illustrative
05Outcome
A platform for new product modules.
Further product modules are planned; the business side sets the order.
6months
Project duration
//Next story
Rapidobject
A shop system more than ten years old, replaced by a modern storefront built with AI-assisted development.
//Read on
Service
Digital products & platforms
The approach behind this project, in five stages.
Let's talk about your project.
A free initial call: your situation, your plans and mutual fit clarified. You decide on the next step afterwards.