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

Connect collections, proofs, receipts and approvals to the school account.

Record or process configured school payment activity, review payment proofs, issue receipts and support controlled refund, approval and payment-link workflows.

See It in a Demo →Explore Capabilities
Built for Finance Teams • Cashiers • Approvers
Payment HubPayment ProofsReceiptsPayment LinksRefundsApprovals
Global Payments
BL TECHNO Global Payments illustrative product mockupILLUSTRATIVE • DEMO DATA
PART OFBL TECHNO FinanceExplore product →
FeaturePayments
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 or process configured school payment activity, review payment proofs, issue receipts and support controlled refund, approval and payment-link workflows.

See BL TECHNO Finance →
01Configured school currency
02Student/account context
03Approvals & evidence
04Role-aware finance access
HOW PAYMENTS 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 Global Payments illustrative mockupSTEP 01
FINANCE WORKFLOW

Receive

School payment / configured rail

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

Match

Learner or account

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

Verify

Proof / transaction context

Transactions Dashboard
BL TECHNO Student Platform illustrative mockupSTEP 04
FINANCE WORKFLOW

Receipt

Record collection

Student Platform
BL TECHNO School Command Dashboard illustrative mockupSTEP 05
FINANCE WORKFLOW

Control

Approval, refund or reconciliation

School Command Dashboard
OPERATIONAL OUTCOMES

What Payments is designed to improve.

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

01

Clear collection record

Connect money received back to the relevant learner or school account.

02

Controlled exceptions

Keep proofs, refunds and approvals inside an auditable finance workflow.

03

Flexible collection architecture

Prepare for school-counter, link and configured provider-based collection methods.

CAPABILITY MAP

Go inside Payments.

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

PH

Payment Hub

Centralise configured payment activity and account matching.

School paymentLearner accountCollection recordPayment method
PP

Payment Proofs

Review supporting proof where the school accepts proof-based workflows.

Proof upload/reviewAccount matchStatusFinance follow-up
RC

Receipts

Record and surface receipts against collected amounts.

Receipt recordPrint/emailStudent accountCollection history
PL

Payment Links

Support controlled payment-link workflows where configured.

Payment linkAccount contextProvider handoffStatus
RF

Refunds & Credits

Handle approved exceptions without losing the original finance trail.

Refund requestCreditReason/contextControlled action
AP

Finance Approvals

Separate sensitive finance actions from ordinary capture where configured.

Approval queueAuthorised approverException handlingAudit context
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.

CollectedPayment activity
ProofsVerification queue
ReceiptsIssued record
LinksPayment requests
RefundsException workflow
ApprovalsControlled actions
BL TECHNO Global Payments mockupGlobal Payments
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

Payments does not have to become another isolated tool.

Move into the neighbouring workflows that share relevant school context.

PYPaymentsCurrent feature
BIBillingCharges & invoicesTRTransactionsMoney movementUSUser ManagementFinance permissionsSTStudent ManagementLearner account
CONNECTED PLATFORM STORY

See Payments 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 Payments 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 Payments 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 Payments to work cleanly from day one.

04

Train

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

05

Launch

Introduce Payments 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.

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

✓Sensitive payment permissions
✓Approval separation
✓School/centre finance scope
✓No public exposure of payment credentials
Explore Security →
IDENTITYWho is signed in?
↓
ROLEWhat is their responsibility?
↓
SCOPEWhich school / centre / class?
↓
FEATUREPayments
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 Payments fits by school need and responsibility.

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

Continue through the connected workflow.

BL
Billing

Charges & invoices

→TX
Transactions

Money movement

→US
User Management

Finance permissions

→SM
Student Management

Learner account

→
FEATURE FAQ

Questions about Payments.

The current finance interface includes Payment Proofs and Receipts as dedicated finance areas.

Yes. The current Billing environment includes Refunds & Credits and Finance Approvals.

Gateway availability depends on the configured provider, country, commercial setup and production integration. The public site should not promise universal availability.

SEE PAYMENTS 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