BL TECHNO Global School Management Platform • Local-currency pricing Explore the platform
← Feature LibraryFINANCE FEATURE
TX
BL TECHNO FEATURETransactions

Keep money in and money out visible in one school cashbook.

Record income and expenditure across configured currencies, categories, centres and payment methods, then review cashflow trends and produce cashbook statements.

See It in a Demo →Explore Capabilities
Built for Finance Teams • Management • Authorised Administrators
Money In / OutCashbookCashflow TrendCategoriesCentresCurrency Summary
Transactions Dashboard
BL TECHNO Transactions Dashboard illustrative product mockupILLUSTRATIVE • DEMO DATA
PART OFBL TECHNO FinanceExplore product →
FeatureTransactions
Operating areaFinance
Product familyBL TECHNO Finance
Access modelRole + scope aware
ExperienceResponsive
WHY THIS FEATURE MATTERS

Move school money workflows from isolated records into controlled financial context.

Record income and expenditure across configured currencies, categories, centres and payment methods, then review cashflow trends and produce cashbook statements.

See BL TECHNO Finance →
01Configured school currency
02Student/account context
03Approvals & evidence
04Role-aware finance access
HOW TRANSACTIONS WORKS

Follow the workflow from first action to review.

Tap a step to change the visual. Each stage comes directly from the feature workflow defined for BL TECHNO.

BL TECHNO Transactions Dashboard illustrative mockupSTEP 01
FINANCE WORKFLOW

Record

Money in / money out

Transactions Dashboard
BL TECHNO Global Billing Command illustrative mockupSTEP 02
FINANCE WORKFLOW

Classify

Category & method

Global Billing Command
BL TECHNO Global Payments illustrative mockupSTEP 03
FINANCE WORKFLOW

Scope

School / centre

Global Payments
BL TECHNO School Command Centre illustrative mockupSTEP 04
FINANCE WORKFLOW

Review

Cashflow & summaries

School Command Centre
BL TECHNO School Command Dashboard illustrative mockupSTEP 05
FINANCE WORKFLOW

Report

Cashbook statement

School Command Dashboard
OPERATIONAL OUTCOMES

What Transactions is designed to improve.

These outcomes describe the operating purpose of the feature without inventing customer statistics.

01

Reliable cash record

Keep school income and expenditure in a structured transaction register.

02

Better management view

Review cashflow, categories, centre performance and payment methods.

03

International context

Record activity using the school’s configured currency context rather than assuming one currency worldwide.

CAPABILITY MAP

Go inside Transactions.

Six capability areas show what the feature organises and how the workflow becomes operational.

IO

Income & Expense

Record money entering and leaving the school.

Credit/incomeDebit/expenseDate/contextNarrative
CB

Cashbook

Maintain a searchable transaction history.

FiltersRecent transactionsStatementExport/print context
CF

Cashflow Trend

Review movement over time.

Trend viewIncome vs expensePeriod contextManagement signal
CT

Categories

Understand where money is coming from and going.

Top categoriesClassificationOperational spendIncome sources
CP

Centre Performance

Review transactions in centre context.

Centre summarySchool group viewComparative contextAuthorised scope
CR

Currency & Methods

Summarise configured currencies and payment methods.

Currency summaryPayment methodsLocal contextGlobal readiness
OPERATIONAL SIGNALS

Bring the information that matters closer to action.

The exact records shown depend on the signed-in user, school configuration and current school data. These labels show the kinds of context this feature organises.

Money InIncome
Money OutExpense
CashflowMovement trend
CategoriesSpend/income mix
CentresPerformance context
CurrencyConfigured school money
BL TECHNO Transactions Dashboard mockupTransactions Dashboard
WHO USES IT

One feature. Different responsibilities.

Switch roles to see how the same feature serves different authorised users without giving everyone the same view.

CONNECTED WORK

Transactions does not have to become another isolated tool.

Move into the neighbouring workflows that share relevant school context.

TXTransactionsCurrent feature
BIBillingStudent chargesPAPaymentsCollectionsPAPayrollStaff payoutsSCSchool CommandManagement visibility
CONNECTED PLATFORM STORY

See Transactions as part of the wider BL TECHNO environment.

This public-safe motion teaser uses illustrative marketing visuals and demo interface language. It is designed to communicate the connected platform story without exposing production school data.

Open Product Tour →Book a Demo
IMPLEMENTATION PATH

Introduce Transactions as an operating process, not just another screen.

The exact implementation depends on school size, plan and scope. This path shows the practical sequence for introducing the feature responsibly.

01

Discover

Identify where Transactions fits into the school’s current operating process and what should improve.

02

Configure

Confirm school currency, account context, permissions and the finance workflow that will use the feature.

03

Prepare

Check the records, settings and authorised users needed for Transactions to work cleanly from day one.

04

Train

Walk the responsible teams through the Transactions workflow using their real roles and school scope.

05

Launch

Introduce Transactions into the agreed school process with controlled access and clear ownership.

06

Review

Review usage, exceptions and operating quality, then refine the school process where needed.

SECURITY & GOVERNANCE

Access follows responsibility.

Transactions inherits BL TECHNO’s role, scope and permission principles. Public marketing shows the controls; authenticated product access remains authoritative.

✓Finance-only action rights
✓School/centre transaction scope
✓Controlled exports
✓Protected financial records
Explore Security →
IDENTITYWho is signed in?
↓
ROLEWhat is their responsibility?
↓
SCOPEWhich school / centre / class?
↓
FEATURETransactions
RESPONSIVE EXPERIENCE

Fit the feature to where the role works.

Responsive finance summariesPhone-ready payment/family touchpoints where enabledTouch-friendly review actionsReadable transaction context
Explore Mobile Experience →
GLOBAL CONTEXT

Keep local school context configurable.

Configured school currencyCountry-specific payment availabilityLocal timezone for transaction contextMarket-specific tax and commercial review
Explore Global Platform →
RELATED SOLUTIONS

See where Transactions fits by school need and responsibility.

SOLUTIONSchool OwnersExplore →SOLUTIONPrincipalsExplore →SOLUTIONAdministratorsExplore →SOLUTIONFinance TeamsExplore →
RELATED FEATURES

Continue through the connected workflow.

BL
Billing

Student charges

→PY
Payments

Collections

→PR
Payroll

Staff payouts

→SC
School Command

Management visibility

→
FEATURE FAQ

Questions about Transactions.

Yes. The current Transactions Dashboard is built around recording money in and money out.

The current interface describes recording rand, dollar, pound or other local currency and includes a Currency Summary.

Yes. The current module includes printing, emailing or WhatsApp-oriented cashbook statement workflows.

SEE TRANSACTIONS IN CONTEXT

Bring this workflow into your tailored BL TECHNO demo.

Inspect the feature in detail, then see how it connects to the product family and wider school operation.

Book a DemoExplore BL TECHNO Finance