Admin Configuration

Everything on this page lives under the Admin menu and is Admin-only. Admin is your institution's control panel: it holds every setting that applies to the whole institution, including the templates and rules staff use every day when creating and approving loans. (Settings that are just about you — your own profile, for instance — are under Settings instead; see Settings.)

Open Admin from the side menu and click a card, or type in the search box at the top to find one. The cards are grouped like this:

Branches, Team & Access, Cash Accounts, and Subscription & Billing open pages that are documented elsewhere — see Branches, Team Management, Accounting, and Billing. Everything else is covered below.

Loan Products

A Loan Product is a pre-configured loan template — set it up once, and staff can build new loans from it in seconds instead of entering every term by hand (see Loans).

Go to Admin → Loan Products → Create Loan Product:

• Loan Product Name and Status (Active/Inactive)
• Branches — which branch(es) can use this product
• Applicant Portal Visibility — whether the product is available for self-service applications through the customer portal

Principal Settings: whether staff/applicants can edit the loan amount, and the minimum, default, and maximum Principal.

Interest Settings: Interest Method (Flat, Reducing Balance – Equal Installments or Equal Principal, Interest-Only, or Compound Interest – Accrued or Equal Installments — each shows a plain-language explanation as you select it), Interest Type (Percentage or Fixed Amount), Interest Period, whether the rate is editable, and minimum/default/maximum Interest.

Duration Settings: whether duration is editable, the duration period (Days/Weeks/Months/Years), and minimum/default/maximum Duration.

Repayment Settings: Repayment Frequency (Daily through Yearly, or Lump Sum), and a Repayment Order you can drag into any sequence — this controls how an incoming payment gets split when it doesn't cover everything owed. For example, with the default order (Penalty → Fees → Interest → Principal), a payment first clears any penalty, then fees, then interest, and whatever's left reduces the principal.

Loan Maturity Settings: whether the loan should keep accruing under different terms after its maturity date, and if so, what rate and basis to use.

Fees & Charges: attach any of your institution's Loan Fees (set up separately, below) that apply to this product — only fees available to the product's selected branch(es) can be attached.

A couple of things this form doesn't include, in case you go looking: there's no description field and no duplicate-name check, so double-check the name you choose since two products can currently share the same name.

Loan Fees

Go to Admin → Loan Fees → Create Loan Fee. Fields:

• Name and Description
• Category — this determines how the fee interacts with the loan:

• Calculation — a Fixed Amount, or a Percentage of the Principal, Interest, or Principal + Interest
• Amount / Rate
• Branches — which branch(es) this fee is available to

Once created, a fee is available to be attached to any Loan Product on a matching branch, or added directly to an individual loan. Editing an existing fee also lets you set it to Inactive.

For a fee that applies to one loan only, a loan officer can instead choose Enter a Custom Fee on the loan form (see Loans) and give it a name, an amount and how it is settled. Either way, the fees received are reported fee by fee on Reports → Fees Report (see Reports).

Penalty Types

Go to Admin → Penalty Types. Create and manage the penalty types that can be applied to overdue or defaulted loans.

Custom Fields Manager

Go to Admin → Custom Fields. This lets you add extra fields onto forms without needing a code change — useful for institution-specific information the standard fields don't cover.

Creating a field: choose the Form it belongs to (Borrower, Team Member, Loan, or Collateral), a Field Label, and a Field Type:

• Text — free text
• Number — numbers only
• Dropdown — pick from a list you define (add options one at a time)
• Date — a date picker
• Textarea — a multi-line text box

Check Set this as a Required Field if it should be mandatory. New fields show up in a Custom Fields section on the relevant create form (Create Borrower, Create Loan, Add Team Member, Add Collateral) and on a Custom Fields tab on each existing record, where they can be filled in or changed later. A required field must be filled in before a new record can be saved, and before that tab's changes can be saved.

Editing or removing a field: use the Modify tab — select the form, load its fields, and you can edit a field's label or required setting, or delete it outright (you'll be asked to confirm). A dropdown's options and a field's type can't be changed after it's created — to change them, delete the field and create it again, which discards the values already entered for it.

Custom fields apply to your whole institution — staff on every branch see the same fields, and you can edit or delete any of them from the Modify tab whichever branch you're on.

Contract Templates

Go to Admin → Contract Templates (a Branch Manager opens it from Loans → Contract Templates in the side menu). This is where you write the loan agreements your officers draft from. A loan officer never edits the wording: they press Draft Contract on a loan, and the loan's own terms (borrower, amount, amount in words, interest, dates, repayment schedule, fees, guarantors and collateral) are filled in for you.

• Which contract a loan gets. The default contract for the loan's product, if it has one; otherwise your standard contract; otherwise the built-in agreement that every institution starts with, so Draft Contract works before you write anything. The built-in agreement is a general starting point, not legal advice: have your own counsel review the wording before you rely on it.
• Start a template with New template, or Create contract beside a loan product. Start from the built-in agreement, a copy of one of your own, or a blank page. Open a template to edit it, Set as default to make it the one used for its loans (a scope has one default), Duplicate, Archive (loans stop using it; Show archived brings it back to restore), and, for an Admin only, Delete.
• The editor builds a contract from blocks: title, headings, paragraphs (optionally numbered 1., 1.1…), bullet lists, a key-terms table, the repayment schedule (choose its columns), a fees table, guarantors, collateral, signature lines (the borrower, the lender, a line for each guarantor, a witness), spacing, a divider and page breaks. Move blocks with the arrows, duplicate or delete them, and show a block only when the loan has guarantors, collateral or fees.
• Insert field puts the loan's details into your wording, for example {{borrower.fullName}}, {{loan.principal}}, {{loan.principalWords}}, {{loan.interestRate}}, {{loan.term}}, {{loan.startDate}}, {{loan.maturityDate}}, {{loan.installmentAmount}}, {{loan.totalPayable}}, {{institution.name}}, {{branch.address}}, {{officer.name}} and {{contract.number}}. Use B and I (or **bold** and _italic_) for emphasis. A field that isn't in the list is an error, and the template can't be saved.
• Page settings set the paper (A4 or US Letter), typeface, text size, justified text, whether your Document Header letterhead opens the contract, a footer line, and the DRAFT watermark.
• Preview shows the template as a PDF filled with a sample loan. History lists every earlier version, who saved it and when; Restore loads one into the editor, and saving makes it the newest. If someone else saves the same template while you are editing it, your save is refused and you are offered their version, so nobody's work is overwritten.

On the loan side, see Loans. Who may write templates, and who may draft, issue or void a loan's contract, is set under User Permissions (the Loan contracts group).

Loan Approval Rules

Go to Admin → Loan Approval. This is where you decide who has to sign off on a loan before it disburses, and it's configured separately for each branch — pick the branch you want to configure at the top of the page.

A few rules always apply, regardless of configuration:

• Admin can always approve any loan and never needs to be added explicitly.
• Branch Manager is always a required approver once the branch has an active one on staff — this can't be turned off.

Beyond that, click Edit and check any additional roles you want to require: Loan Officer, Credit Committee, Accountant, Auditor, Collections Officer, or Risk Analyst. (Cashier isn't offered, so the person handling cash never also signs off the loan it pays out. A Cashier requirement saved before this change still shows, and can be removed.) A role only appears as an option if someone with that role is actually on staff at the branch — there's no point requiring a signature from a role nobody holds.

If a branch only has Admin users on staff, this page tells you there's nothing to configure — approvals happen automatically. See Loans for how the approval process plays out day to day once it's configured.

User Permissions

Go to Admin → User Permissions. This is a grid of every permission against every role — Branch Manager, Loan Officer, Credit Committee, Accountant, Cashier, Collections Officer, Auditor, Risk Analyst, IT Support and Viewer — with the number of people holding each role under its name. Tick a box to give a role a permission, untick it to take it away, then Save Changes. It applies to everyone with that role within a few seconds, with no sign-out needed.

• Admin is always on and can't be turned off, so you can't lock yourself out.
• Boxes that differ from the standard are shaded, and an unsaved change is shaded differently. Reset next to a permission, under a role, or at the bottom puts them back to the standard. Customised only shows just what you've changed, and the search box finds a permission by name.
• Some permissions can't be changed, and say why when you point at them: basic reading every staff member needs (such as seeing borrowers and loans), a few Admin-only actions (deleting a payment, adding team members, the Admin area itself), and anything another part of the system enforces for itself.
• Linked permissions move together. Collecting group meeting repayments needs recording payments, and posting journals needs the ledger and reports; turning one on turns on what it needs, and the page says so under the grid.
• The page asks before taking a permission away from a role that has people in it, or giving a role a permission that moves money, deletes records, or shows balances or the team directory.
• Last changed by… and Show recent changes list who changed which permission, and when.
• If two Admins edit at once, the second to save is told the permissions changed and offered the latest version, rather than overwriting the first.

A few things are not set here: which borrowers and loans a person sees (a Loan Officer sees their own; everyone else sees their branch), and who must approve loans, which is Loan Approval above. See Roles & Permissions for what each role can do by default.

Day Control

Go to Admin → Day Control. This lets you stop back-dated entries, branch by branch. It is off by default — nothing changes for a branch until you switch it on.

With the Day lock on for a branch, that branch has one open day at a time. Everyone at the branch except Admins — Branch Managers included — can only save records dated that day: loans (start and disbursement date), repayments, penalties, expenses, other income, and deposits and withdrawals. The date fields are fixed to the open day, and a record dated any other day can't be edited, reversed or voided. Closing a loan or writing one off is dated the open day too. Admins are never restricted.

• Switch the lock on (the switch on the branch's row): today is opened straight away.
• Close day: nobody except Admins can save anything dated until a day is opened again.
• Open day: an Admin can open today or any earlier date — for example, yesterday, to let the team catch up on a day that was missed — but never a day that hasn't started yet. A Branch Manager can open today and close the day for their own branch from the Day open / Day closed badge at the top of the screen; they can't open an earlier date.
• Closes by itself: an open day closes automatically at midnight, in the time zone of the Admin who switched the lock on (shown under each branch's status). The next morning someone has to open the new day before anything dated can be saved. If an Admin opens an earlier date to catch up, it stays open until the day they opened it on ends, then closes the same way. The badge and the Day Control page show Closed (automatic) when this has happened.
• Switch the lock off and past dates can be entered again.

Things to know:

• A loan draft saved on an earlier day has to be re-dated to the open day (edit the draft) before it can be approved or activated by anyone but an Admin. When you open such a draft's Approval tab, a warning tells you so before you reach the final approval, and says who can fix it (a Branch Manager or an Admin can edit the draft; saving moves it onto the open day). Copying or cloning a loan starts the copy on the open day.
• Attribute dates — a borrower's date of birth, an insurance expiry date, a "promise to pay" date — aren't affected. Neither are SACCO postings or manual journals, which have their own rules. Stopping and resuming interest on a loan is not affected by the open or closed day either.
• Staff who already have the app open see a change within a few minutes (and an automatic close at the moment midnight passes), and always before their next save: the lock is checked again at the moment someone saves.
• The lock is enforced by the app. It stops everything done through the screens and the AI assistant, but it isn't a substitute for access controls on who can sign in.

Institution Profile

Go to Admin → Institution Profile. Your institution's basic profile: Institution Name, Institution ID (visible to Admins), Branch, Country, and Currency. Only Admins can open this page; click Edit to change the profile and save.

Document Header

Go to Admin → Document Header. Upload an image to appear at the top of exported documents like loan statements. This page is Admin-only. Recommended image size is 2480 × 350 px, JPG or PNG, up to 2MB, with a transparent or white background so it fits documents cleanly. Note that this only controls the header image — it doesn't currently offer a way to add custom header text or address details separately.

Reporting Policy

Go to Admin → Reporting Policy (the same form is also behind the Reporting Policy button on the Reports page). It holds the institution-wide rules the reports and the general ledger read, so every report uses the same definitions:

• Income basis (cash or accrual) for Profit / Loss and the general ledger, and how loan losses are expensed
• Stop accruing after a number of days past due
• PAR thresholds (in days) — PAR N counts loans more than N days late
• Provision on (principal outstanding, or principal plus interest receivable) and a provision % for each aging bucket
• Dropout grace period — how long a repaid borrower can go without a new loan before counting as a dropout
• High-value disbursement and single-borrower limit — optional thresholds used to flag exceptions; leave blank for no flag

Only Admins can change the policy. See Reports for where each setting shows up.

Email Notifications

Go to Admin → Email Notifications. Email notifications are included in the free trial and the Corporate and Enterprise plans; they are not included in Pro. When they become available to you, a banner at the top of the page tells every admin so — click Click here to activate to open this page (the banner can be closed). Turn on email updates about loan and payment activity for your staff and, optionally, your borrowers — sent from no-reply@notice.loantabs.com on your institution's behalf. Set a Reply-To address (replies fall back to an institution admin's email if left blank) and an optional footer note appended to every notification email.

Below that, a grid lets you choose exactly who is notified for each event — loan submitted for approval, taken (disbursed/active), rejected, closed, or written off; payment received; penalty applied; payment due soon; and payment overdue — across four audiences: Admins, Branch managers, the Loan officer, and the Borrower. Every box starts unchecked, and turning on a Borrower box asks you to confirm first, since it means borrowers with an email address on file start receiving emails. Two reminder-timing fields control how many days before the due date a "due soon" email goes out, and how often an "overdue" email repeats once a payment is late.

Your own wording. Below the grid, Borrower email wording lists the emails borrowers can get: loan approved and disbursed, application rejected, loan closed, payment received, penalty applied, payment due soon and payment overdue. Each starts with the standard wording. Open one and switch on Use my own wording to write your own subject and message in plain text. Click a field — the borrower's name or first name, your institution's name, the loan number, the loan amount, and, where the email has them, the amount paid or charged, the payment date, the due date and the amount in arrears — to put it where your cursor is; it is filled in for each borrower. A blank line starts a new paragraph, and a web address starting with https:// becomes a link. The preview shows the email with example values, and Send test to me emails one copy to your own address only (a few a day at most). Wording that can't be sent as written — a field the email doesn't have, or an empty subject — is marked and stops you saving until it is fixed; Reset to standard wording goes back to the standard email. Only emails to borrowers can be changed; staff emails always use the standard wording, and your footer note is added to both.

PDF receipts and statements. Under an email's wording you can tick Receipt for the payment (on the payment-received email) and Loan statement (on any borrower email except a rejected application). The PDF is attached automatically to that email and sent to the address on the borrower's record; ticking one asks you to confirm because a statement lists the loan's payment history. They are the same receipt and statement the app prints with Export PDF, drawn with your institution's name and, if you have uploaded one under Admin → Document header, your letterhead. Nothing is attached until you tick it. If a PDF can't be made, or is too large to email, the email still goes without it, and the borrower's Messages tab says so. Send test to me attaches a sample receipt or statement, drawn from an invented loan, so you can see what borrowers will get.

A borrower can opt out. Open the borrower and go to the Messages tab: the Automatic emails switch at the top stops LoanTabs emailing that borrower — notifications, reminders and any PDF attached to them. It does not affect emails to your staff, or SMS and WhatsApp messages. Changing it needs permission to update borrowers, and the tab shows who changed it and when.

Payments and penalties dated more than a week ago are never emailed, so importing or back-filling history doesn't send anything. The due-soon and overdue reminders go to the borrower only, once a day (early morning UTC, about 09:00 in East Africa). There is nothing else to switch on: they start with the next daily run after you save with the Borrower box ticked for those events. A borrower with no email address on file is skipped, and each installment (or each overdue window) is reminded about only once.

Who is told, and when. Once an admin turns emails on, branch managers and loan officers who are ticked in the grid see a banner saying email notifications have been turned on and to check their inbox for notices (they can close it). Roles that the emails never go to — an accountant or cashier, for example — see nothing.

Plans. On Pro emails are switched off automatically: nothing is sent, the Email Notifications page shows a note that your plan doesn't include them, and everything you had saved is kept. Upgrade to Corporate or Enterprise and the emails start again with your settings as they were. The free trial comes with a limited free email allowance. When it is used up, admins see a banner at the top saying so and prompting an upgrade to a plan that includes email notifications; emails stay paused until you upgrade. The Billing page's plan comparison shows which plans include email notifications.

SMS Notifications

Go to Admin → SMS Notifications. Send SMS updates through your own SMS aggregator account, using the same event/audience grid as Email Notifications to choose who gets texted for what. The aggregator bills your institution directly for each message — LoanTabs doesn't see or charge for the messages themselves.

Pick an aggregator (Africa's Talking, Termii, or Twilio, which can also send WhatsApp), enter its API credentials (an expandable "how to get your API key" panel walks through each provider's setup), and optionally set a Sender ID, then Connect. Once connected, set a default country (used to interpret phone numbers stored without a country code) and a monthly segment cap — sending stops for the rest of the month once the cap is reached — plus an optional signature appended to every message, space permitting. A Send test SMS button (limited to 5 per hour, and counted against your monthly cap) lets you confirm the connection works before turning notifications on for real. Remove disconnects the provider and stops all SMS sending immediately; you can reconnect the same or a different provider at any time.

WhatsApp (Twilio only). Once Twilio is connected, Send via lets you choose SMS, WhatsApp or both, and Send test WhatsApp checks it. Two limits come from WhatsApp and Twilio, not from LoanTabs: free-form WhatsApp messages are delivered only through Twilio's shared Sandbox (each phone must first send the sandbox "join" message) or to a customer who messaged you within the last 24 hours; messaging other customers needs approved message templates, which LoanTabs does not send yet. A Twilio trial account can message only numbers you have verified. A WhatsApp message counts as one unit against the monthly cap.

Payment reminders. The grid includes Payment due soon and Payment overdue, sent to the borrower only, with the timing set under the grid (how many days before a due date, and how often to repeat once overdue). Reminders are switched on for an institution by LoanTabs (ask support); when they are, a Payment reminders card lets you preview who would be texted and send the reminders that are due now. Each installment is reminded at most once, every message counts against the monthly cap, and it all appears on the borrower's Messages tab.

SACCO

Go to Admin → SACCO, or open SACCO in the menu. SACCO is an add-on for running a savings and credit cooperative — member savings and share accounts, interest, dividends, meetings and loans against savings — in its own workspace. It is included in the free trial and the Corporate and Enterprise plans; it is not included in Pro, where this page says so and offers View plans.

On a plan that includes it, SACCO is on by default, so there is nothing to activate and a new institution has it from day one. The page has one switch. Turning it Off hides the SACCO link and screens and stops new SACCO entries; everything already recorded is kept exactly as it is, and your books keep including it. Turn it back on at any time. Moving down to Pro does the same, and upgrading brings it all back; a payment or plan change never switches it on or off by itself. The first time you open SACCO, a Start Here guide for your role walks you through setting it up, and its own guides appear in Help & Support once SACCO is available to you.

Webhooks

Go to Admin → Webhooks. LoanTabs can post a signed JSON message to a URL of yours whenever a loan or payment event happens — a loan submitted, disbursed, rejected, closed or written off, a payment received, a penalty applied — so a CRM, spreadsheet or automation tool (Zapier, Make, your own service) can react.

Paste the URL (it must start with https://; private and internal addresses are refused), choose the events, and save. A signing secret is generated and shown once — copy it into the receiving system, which uses it to check each message really came from LoanTabs (the page includes Node and Python examples). Send a test event checks the endpoint is reachable, and the page shows whether the last delivery worked. New signing secret replaces the secret (the old one stops working immediately) and Remove deletes the webhook.

Each event is sent once. Failed deliveries are not retried in this version, so treat the webhook as a convenient feed rather than a guaranteed queue. Messages include the borrower's name, phone and email so a CRM can match them.

LoanTabs AI

Go to Admin → LoanTabs AI. A single switch (Admin-only) to turn the conversational portfolio assistant on or off for your institution. It can answer questions about your portfolio and propose creating or updating records, but every proposed change still needs a person to review it and click Confirm before anything is saved — nothing happens automatically. What it can and can't do, who can use which part, and how its monthly budget works are in Using LoanTabs AI. A "Bring your own API key" option is shown but marked Coming soon; it isn't usable yet, and nothing you type there is stored or sent anywhere in the meantime.

Import from Old LoanTabs

Go to Admin → Import from Old LoanTabs. If your institution used the Old LoanTabs before moving to the New LoanTabs AI, an Admin can bring across the old business's borrowers, loans (with their payments, penalties and fees), accounts and their transactions, team members, guarantors, collateral, contracts, expenses, and other income from here. This is a one-time migration from the Old LoanTabs (also known as LoanTabs Classic), not an ongoing sync — once it completes, anything entered into the Old LoanTabs afterward will never come across.

Before you start

• You must be signed in to the New LoanTabs AI with the same, verified email address you used in the Old LoanTabs — that's how the system finds your old account. If you set up your New LoanTabs AI business with a different email, this won't find anything.
• Only the original business owner's Old LoanTabs account can be imported — a staff login from the old system won't work, and you'll be told so if you try.
• This can only be run once per institution. If you need to redo it, contact support rather than trying again.
• Only an institution Admin can open this page and run an import.

Running it

1. Click Preview import. This previews what would be imported — how many borrowers, loans, payments, accounts (and the deposits and withdrawals recorded on them), team members, guarantors, collateral items, contracts, expenses, and other-income records — along with any notes worth reading first (for example, a loan or payment linked to more than one account in the old system, which gets simplified to just the first account). Nothing is written to either system at this stage.
2. If the preview looks right, click Confirm import to run it for real. A large business can take a few minutes; you can leave the tab open or check back later, and the status updates as it goes.

What the import changes

• Everything is imported into your institution's existing default branch, which is renamed to match your Old LoanTabs business name (no new branch is created). Your institution's currency is also set to the Old LoanTabs' currency (UGX if the old business never set one) — the confirmation prompt tells you which. These are the only two existing records the import changes; nothing else you've already entered in the New LoanTabs AI is overwritten or deleted. If the currency can't be set automatically, you'll be told to set it yourself in Admin → Institution Profile.
• Old LoanTabs securities come across as Collateral. Each loan is given an imported loan product named Imported (legacy), one for each combination of loan type and interest/duration period the old loans used, so migrated loans calculate the way they did before. Migrated loan numbers start with IMPORT-.
• Each borrower keeps their assigned loan officer where the old system recorded one; otherwise the borrower and their loans are attributed to the Admin running the import.
• Files attached in the Old LoanTabs (borrower documents, and documents on guarantors, collateral and contracts) are not copied. They appear in the Files tabs as links to the original files, marked as added by "Old LoanTabs import", and open the same way any other link does.
• Team members who had a login in the Old LoanTabs are given a New LoanTabs AI login and emailed a temporary password.
• Imported loans are calculated by the Old LoanTabs' own rules — the same instalment amounts and dates, interest method (reducing balance, flat, or lump sum), and late-payment interest after the end date — so each loan's schedule, interest and balance read the way they did there. (Loans you create in the New LoanTabs AI keep using the New LoanTabs AI's own calculation.)
• A loan that was fully repaid, but was never manually marked closed or cleared in the Old LoanTabs, is imported as Closed rather than Active — the same way it would end up if it were a native New LoanTabs AI loan that reached a zero balance. A loan that still owes money stays open, and once it passes its end date it is Overdue, with the late-payment interest the Old LoanTabs added. A loan you had set to _override to cleared_ is imported as Closed, with interest stopped on the day you set it.
• Everything recorded on an Old LoanTabs account's own page comes across onto that account: deposits and withdrawals as account transactions, expenses on the Expenses page and other income on the Other Income page, each still tied to its account. Each loan's disbursement and any loan fees collected are posted to the account they went through in the Old LoanTabs, exactly as the New LoanTabs AI records them for a new loan.
• Your New LoanTabs AI subscription and plan limits are not affected by the import.

What doesn't come across

Where the old system linked one item to several accounts or several borrowers (a payment, loan fee, expense or other-income record with more than one account; a contract with more than one borrower), only the first is kept. Any row that couldn't be imported — for example a loan whose borrower wasn't found — is skipped and listed under Things worth knowing rather than stopping the import.

Investors, investments, and reports aren't migrated into the New LoanTabs AI — they're preserved for your records in the downloadable file below, but not written anywhere you'll see in the app. Old billing history (Pesapal payment records) is dropped entirely, since it's specific to the old system and has nowhere to go in the new one.

After it finishes

You'll see a summary of everything migrated, Things worth knowing (each team member who was emailed a temporary password, and any skipped rows), a reconciliation of each account's balance (what the New LoanTabs AI computed from the imported transactions), and a Download full import details (JSON) link with the complete import record for your own reference. The Old LoanTabs left anything dated before an account was created out of that account's balance; the New LoanTabs AI counts every entry, so where an account had such entries the reconciliation says how many and by how much the balance differs.

If an import stops part-way (for example on a very large business), the page offers Retry import after a few minutes; retrying removes whatever the stopped attempt had written before starting again.

Repair import (imports made before loans were calculated the Old LoanTabs way)

Earlier versions of the import didn't carry over how each loan is calculated — its interest method, how often it is repaid, lump-sum terms, and the late interest the Old LoanTabs added after the end date — so some imported loans showed different schedules and balances than they did in the Old LoanTabs. If you imported before 03-Oct-2026, you'll see a banner on the dashboard (until you start a repair) and a Repair import button on this page. Institutions that never completed an import, or that signed up after 03-Oct-2026, don't see either.

• Repair import re-applies the Old LoanTabs' rules to every imported loan so its statement matches again. It doesn't import anything again and never touches the Old LoanTabs. A loan that was closed as "fully paid" although it still owes money is reopened; a loan that is fully paid is closed.
• It overwrites any changes you've made to imported loans so far (such as their repayment settings and status), but keeps all payments and penalties, including the ones you've added since.
• It runs in the background and shows its progress; if it stops part-way, run it again — loans already repaired are skipped. It is only offered once per import, and never for an import made after 03-Oct-2026.