Ledgerlinefor Pell & Ward Bank

Move the core over one weekend nobody notices.

A core banking migration proposal for Pell & Ward Bank, from Ledgerline.

1.4Maccounts moved
31 hcutover window
$18.5Mfixed price
CUTOVER  SAT 23:00 TO MON 06:00LIVE
100.00%
0 minutes offline for customers
SAT 23:00SUN 06:00SUN 18:00MON 06:00
Ledgerline for Pell & Ward Bank. Proposal issued October 2026.A Closewell Studio example. Companies and figures are fictional.
L.01

Four sentences from September, reconciled.

Each of you gave us one line in the discovery sessions. We've set our answer against each one the way your finance team closes a month. Nothing on this page is left unmatched.

LINEYOU SAIDWE COMMIT TOSTATUS
01
If a customer notices, we've failed. If the press notices, I've failed.Helen, Chief Executive

Zero minutes offline. Cards, the app and ATMs stay up all weekend, and 35 percent of our fee is only paid when we call go.

Matched
02
My team has kept this core alive for 26 years. They need to be in the room, running it.Tobias, Chief Information Officer

31 of your people hold named roles on the weekend rota. They run all four rehearsals with us first, so by May they've done the weekend four times.

Matched
03
I want to be able to stop it at any point and know where we'd be.Priya, Chief Risk Officer

Seven checkpoints. You can call a hold at any of them without giving a reason, and the rollback point is printed beside each one.

Matched
04
Sunday afternoon is when people check their balance before the week. That screen has to look like every other Sunday.Marcus, Head of Customer

The app reads from a live mirror of your current core until Monday morning. Sunday's balance is the same number in the same place.

Matched
4 lines4 matched, 0 open
L.02

Run the weekend before you sign.

This is the cutover plan for Saturday 22 May 2027, hour by hour. Drag the clock and watch 1.4M accounts move in five waves, each one reconciled to the cent before the next starts. Then break it on purpose.

SAT 23:00T+0h 00m
0.00%0 of 1,400,000 accounts

RUNNING NOW

Freeze the old core and seal the snapshot.

Wave 0 of 5

WHAT CUSTOMERS SEE

  • Card paymentsOld core
  • App and onlineOld core
  • ATMsOld core
  • Approved so far0

MINUTES OFFLINE

0Buffer at go or no-go, 5h 00m

Rehearse a hold. Pick a checkpoint and its reconciliation fails. One hold costs 75 minutes and we still go. A second hold in the same weekend means no-go, whatever the clock says, and the old core is back serving before branches open.

Clean run. Go called Monday 01:00 with five hours to spare.
L.03

By May, your team has done this four times.

Each dress rehearsal runs the whole weekend on a full copy of your data, against the clock, with the same people on the same shifts. These are the run times we plan each one to hit, from our last nine migrations.

26 h

Four rehearsals bring the run to go or no-go down to 26 hours. That leaves five hours of buffer inside the window, almost twice what a full rollback needs.

Rehearsal results go to Priya and your regulator the Monday after each one, with every mismatch we found and who fixed it.

CH.1

Will anyone outside this building know it happened?

HEFor Helen, Chief Executive, and the board paper she takes to December's meeting.
$18.5MFixed price for the plan as written. Five-year licence included.
0 minCustomers offline across the 31 hours. Cards, app and ATMs stay up.
22 MayCutover Saturday, 2027. Standby weekend held for 5 June.
3 hThe smallest buffer we'll accept at go or no-go. Plan carries five.
$6,475,000

That's the share of our fee Ledgerline is only paid when we call go at the end of the weekend. If we call no-go, it waits, and the next attempt costs Pell & Ward nothing.

Banks moved on Ledgerline9
Accounts moved11.2M
Customer minutes offline0
Weekends we called no-go1

The worst weekend, played out.

Two reconciliations fail. We call no-go on Sunday, switch every channel back to your current core and finish by Monday 05:40, before a single branch opens. Customers bank as usual. The papers have nothing to write.

Then we go again on 5 June at our cost. The one weekend we've ever called no-go went this way, and that bank went live a fortnight later.

CH.2

How does it run, and what do my people do that weekend?

TOFor Tobias, Chief Information Officer, and the team that has run the 1998 core since it went in.

Every channel keeps a home all weekend. Pick a moment and see where each one is served from.

Your current coreLive mirror, read onlyLedgerline

The weekend rota

SHIFTYOURSOURS
NightSat 22:00 to Sun 08:001116
DaySun 08:00 to 18:00914
Switch-overSun 18:00 to Mon 07:001116
Total on the rota3146

Your engineers own the old core's freeze, the snapshot and the rollback switch. Nobody on our side touches them. Every checkpoint has one of yours and one of ours signing it off together.

CH.3

What must be true at each checkpoint, and who can stop it?

PRFor Priya, Chief Risk Officer, and the regulator she reports to.
T1Every balance matches to the cent+
All 1.4M account balances compared, old core against Ledgerline, after every wave. One cent out on one account is a fail.Fails at 1 mismatch
T2General ledger totals match by product+
The 212 product codes are totalled on both sides and compared line by line, so a balance can't move between products and still pass T1.Fails at $0.01 difference on any product
T3Accrued interest matches+
Interest accrued to Saturday 23:00 is recalculated on Ledgerline and compared per account. Rounding rules were agreed with your finance team in March.Fails at 1 mismatch
T4Card holds and pending items carried+
Every open card authorisation and pending payment on the old core appears on Ledgerline with the same amount and expiry.Fails at 1 missing item
T5No rejected record without an owner+
Any record Ledgerline refuses is listed with a named person fixing it before the next wave starts. Rehearsal four carried zero.Fails at 1 unowned record
T6Weekend payments replay cleanly+
Card payments approved by stand-in during the weekend are replayed onto Ledgerline and matched against the card network's own file.Fails at 1 unmatched payment

Three people can call a hold.

  • PRPriya, Chief Risk Officer
  • TOTobias, Chief Information Officer
  • JOJoanna, Ledgerline cutover lead

Any one of them can stop the weekend with one word. Nobody needs to explain why until Monday. A hold freezes the current wave, backs out its last batch and reruns it. Every checkpoint card in the console shows the point we'd roll back to.

Your regulator gets 60 days' notice of the date, the evidence pack from each rehearsal, and a call from Priya at go or no-go.

CH.4

What do customers see, and what do my teams say?

MAFor Marcus, Head of Customer, and the 86 branches and contact centre behind him.

What stays the same for every customer

  • Account and routing numbersUnchanged
  • Debit cards and PINsUnchanged
  • Saved payees and transfersUnchanged
  • Direct deposits and autopayUnchanged
  • App login and face IDUnchanged
  • Statement layoutUnchanged until you choose
+40 percent

Contact centre staffing on Sunday 08:00 to 20:00 and Monday 08:00 to 12:00, with one script your team writes and we rehearse with them in April.

We don't email customers in advance. Nothing they use changes, and a warning creates the calls it's meant to prevent. Branch staff get a one-page brief on Friday 21 May and a Monday 07:00 huddle.

L.05

One fixed price, line by line.

The licence and the migration are the same in every version of this. Everything below them can come down on its own, and each line says what you'd give up.

LINEAMOUNT

Ledgerline core licence, five years

The core for 1.4M accounts and 212 products, hosted in two regions, upgrades included.

In every version
$9,400,000

Migration and the cutover weekend

Data mapping, the five waves, the 46-person rota, the stand-in for cards and the live mirror for the app.

In every version
$5,850,000

Dress rehearsals

$310,000 each. A full weekend on a copy of your data with the live rota.

4
$1,240,000

Parallel run

$185,000 a week. Both cores process every day after go, and we reconcile them each night.

6 wks
$1,110,000

Extended hypercare

Our cutover team stays on your floor for 90 days after go instead of 30.

$640,000

Cutover command on site

Our 46 people work the weekend from your operations centre on Harbour Street.

$260,000

We'd sign it as it opens. Four rehearsals is what gets the run to 26 hours, and six weeks of parallel run is the shortest that carries your first quarter-end on both cores. If something has to come out, take the on-site command first. It's the line that costs you least in risk.

L.06

December to August, with one weekend in the middle.

The plan moves with the price above. Change the parallel run or hypercare and the bars here follow.

DECJANFEBMARAPRMAYJUNJULAUG
    L.07

    The four people in the room that weekend.

    They lead the rehearsals, the weekend and the parallel run. None of them hands over to anyone else once you've signed.

    JO

    Joanna

    Cutover lead

    Runs the clock and calls go with Priya and Tobias. Ran the no-go weekend in 2024 and the clean one a fortnight later.

    7 cutovers led

    DV

    Dev

    Data migration lead

    Owns the mapping of your 212 products and the five waves. Starts with your data team on 11 January.

    9 migrations, 11.2M accounts

    RU

    Ruth

    Risk and controls lead

    Writes the six tests with Priya's team and builds the evidence pack your regulator receives after each rehearsal.

    Former bank examiner, 12 years

    SA

    Sam

    Customer operations lead

    Works with Marcus on the contact centre script, the branch brief and the Monday 07:00 huddle.

    4 cutovers, 0 complaint spikes

    The terms, plainly.

    What can change the fixed price
    Only two things. More than 1.55M accounts at cutover, or a product we haven't mapped by the end of rehearsal two. Either one comes to you as a written change before any work starts.
    If we call no-go
    The 35 percent go payment waits. We run the standby weekend on 5 June, or a date you choose, at no cost to you. If a third attempt is ever needed, you can leave the contract and keep everything we've built.
    Your data
    It stays yours. If you ever leave Ledgerline we hand back a full export in an open format within 30 days, at no charge.
    The licence after year five
    Renewal is capped at a 4 percent rise a year. You'll have the renewal price in writing twelve months before it's due.
    Your current core
    It stays installed, read only, for 12 months after go, so the rollback switch exists long after anyone expects to need it.

    What we don't know yet.

    1. Will your examiner want 90 days' notice?We've planned on 60. At 90, signing needs to move to 20 November or the cutover moves to 5 June.
    2. What stand-in limit will your card network allow?We've assumed $2,500 a day per card over the weekend. A lower limit means a lower ATM cash limit that Sunday, and Marcus's script would need to say so.
    3. Who cleans the 3,140 addresses we couldn't parse?They showed up in the sample you shared. They need an owner on your side before rehearsal two.
    4. Is 22 May clear of your own calendar?We've checked for month-ends and holidays. We haven't seen your marketing or rate-change plans.

    Sign by 4 December and rehearsal one is 13 March.

    After that date the March slot goes to another bank and every date on this page moves back three weeks, including the cutover.

    Ask Joanna a question

    1. 4 DecSignatures from Helen, Tobias, Priya and Marcus
    2. 11 JanDev and your data team start mapping
    3. 13 MarRehearsal one, the full weekend on a copy
    4. 22 MayCutover, Saturday 23:00