Every non-standard loan repayment becomes a manual workaround
Most loan systems are built around the simple case, a single drawdown at the start, a single repayment at maturity, interest on a regular frequency. Real loan agreements are rarely that tidy. There might be a stub interest period at the start because the deal was signed part way through a period. There might be several drawdowns followed by a stepped series of repayments. There might be a term negotiated by the lender that simply does not match any standard template.
When the system cannot represent the actual agreement, the treasury operations team ends up rebuilding the schedule by hand, usually in a spreadsheet, cross-checking every capital and interest line against the signed contract to make sure nothing has drifted from what was actually agreed.
It works, but it means the schedule the team relies on day to day is not the same one the system generated. It is a manual patch sitting alongside it.
Rebuilding schedules by hand eats the hours treasury does not have
The hours add up quickly. A schedule that takes minutes to generate for a standard bullet loan can take an afternoon to rebuild correctly for a loan with an irregular first period, multiple drawdowns, or a repayment profile that changes partway through the term.
Worse, if a single term changes later, a new drawdown date, an amended rate, an early partial repayment, the whole manual schedule often needs reworking rather than a single line being adjusted. Capital and interest can drift out of sync, and errors typically surface only when a payment does not match what the bank expects, which is the worst possible time to find one.
None of this is a skills problem. It is what happens when the tool assumes every loan looks the same, and the operations team is left to handle every loan that does not.
The schedule is not the problem, the rigidity of the schedule is
The instinct is often to look for a system with more built-in loan templates, hoping the next one covers the specific structure at hand. That misses the actual requirement. No fixed set of templates will ever cover every negotiated term, because the whole point of a negotiated loan is that it can differ from the standard case.
What treasury operations actually needs is not a longer list of templates. It needs a scheduler that builds the standard case automatically when the loan is standard, and can then be edited freely, transaction by transaction, when it is not, without losing the link between the capital schedule and the interest calculated on it.
Inside Salmon Treasurer’s custom loan scheduler
Salmon Treasurer generates the initial schedule automatically using the Schedule Wizard, which produces a bullet capital schedule, one drawdown at the start and one repayment at maturity, along with an interest schedule based on the frequency defined at deal level. Any stub period is placed at the end of the deal by default.
Where the agreed terms differ from that standard shape, the Custom Schedule function allows the wizard-generated schedule to be edited directly, or a schedule to be built from nothing. Capital transactions can be added individually, a single drawdown and a single repayment, or as a series, for example a monthly repayment amount repeated for a defined number of movements starting from a chosen date. A capital schedule can also be imported from another deal that follows the same repayment pattern, or uploaded directly from a csv file matching the agreed schedule.
The interest schedule can be adjusted with the same flexibility. An existing interest schedule can be removed entirely and rebuilt, starting with a single irregular period to capture a stub, followed by the remaining periods generated at the agreed frequency, for example annually. Every capital and interest transaction remains linked to the underlying deal, so nothing is calculated in isolation from the loan it belongs to.
Additional functions sit alongside the scheduler rather than requiring separate tracking. Interest rate fixing can be actioned in bulk across multiple deals on a fixing date, or within a single deal, with clear flags showing which rates are ready, missing, or not yet due. Capitalisation allows accrued interest to be converted into additional principal, recorded as a memorandum transaction so it does not appear as a cash movement, with all subsequent interest recalculated on the updated balance. Fees and charges unrelated to the capital and interest schedule, such as arrangement or facility fees, are recorded separately under their own defined fee types, so they never distort the underlying repayment schedule.
What a flexible scheduler frees the team to do instead
With a scheduler that can represent the loan as it was actually agreed, the operations team builds the schedule once, checks it against the signed agreement, and moves on. A change to one term means editing one transaction, not reworking a spreadsheet from scratch.
Capital and interest stay linked throughout, so a change to the repayment profile is reflected automatically in the interest calculated on the outstanding balance. That removes the drift that manual rebuilding tends to introduce, and it means the schedule the team relies on day to day is the same one the system is holding, not a parallel version kept just to make the numbers work.
Try building a schedule in Salmon Treasurer
If your team is still rebuilding non-standard repayment schedules by hand, we would like to show you how the custom scheduler in Salmon Treasurer handles it instead. Request a demo and bring one of your trickier loan agreements, we will build the schedule together.