Skip to content
Qentak — The Education Operating System

Finance & Administration

Online Payments

Connect a payment to the account it belongs to.

Connect payment records with student balances and reconciliation, subject to the payment providers agreed for deployment.

Try the workflow
Finance adviser in emerald discussing a fee plan with a parent
THE PEOPLEPayment references

Associate each request with the intended student account and invoice.

01 / 03

START WITH THE ACTUAL WORK

Why connect online payments?

A payment confirmation is useful only when finance can trace it to an invoice and reconcile it with the provider’s settlement.

WHAT THIS CAPABILITY BRINGS TOGETHER

Online Payments: records, decisions, and handovers.

01

Payment references

Associate each request with the intended student account and invoice.

02

Provider confirmation

Record verified payment events from the agreed payment integration.

03

Reconciliation exceptions

Separate confirmed payments from unmatched, reversed, or disputed transactions.

FOLLOW THE WORK FROM START TO FINISH

Explore the online payments workflow.

This interactive illustration explains the operating model. It contains no live institutional records.

Finance review workspaceIllustrative preview
CONTROLLED FINANCIAL PROCESSSource. Review. Reconcile.
Review areaControl contextStage
Payment referencesSupported provider and payment methodsReview
Provider confirmationCurrencies and allocation prioritiesReview
Reconciliation exceptionsSettlement and refund-review responsibilitiesReview
Illustrative review only · No financial transactions
STEP 1 OF 4

Present a payment reference

Present the approved provider flow with the invoice reference.

A WORKED EXAMPLE · ILLUSTRATIVE SCENARIO

A provider notification can arrive twice

A payment service repeats a success event while a family refreshes the payment page. Counting each event as a new payment would overstate collection.

The decision and its context

Use provider and transaction references to identify the event and its status. Distinguish initiated, confirmed, settled, failed and reversed payments as required by the chosen provider, with a finance-owned reconciliation process.

What a complete outcome looks like

Trace an accepted payment to the correct invoice and settlement evidence. Duplicate notifications should not create duplicate credits.

FOLLOW THE HANDOVERIntegrations & APIsThe payment connection needs an explicit event contract, duplicate handling and failure ownership.

A CAPABILITY, NOT AN ISLAND

Connect online payments with the next workflow.

The same institutional context should support the next responsible team’s action. Explore the connected capabilities.

YOUR INSTITUTION’S RULES

Set the rules for online payments.

  • Supported provider and payment methods
  • Currencies and allocation priorities
  • Settlement and refund-review responsibilities
Explore configuration and flexibility

WHEN THE DAY DOESN’T FOLLOW THE DEFAULT

A payment arrives without a reliable match

Hold it in an exception queue until finance confirms the correct account.

A clear exception keeps the reason, owner, and next decision visible.
School board members discussing a campus plan in a timber meeting roomOnline PaymentsPayment references → Reconciliation exceptions

SEE HOW THE WORK CONNECTS

Online Payments

Finance teams · Billing contacts. Associate each request with the intended student account and invoice.

  1. 01

    Payment references

    Associate each request with the intended student account and invoice.

  2. 02

    Provider confirmation

    Record verified payment events from the agreed payment integration.

  3. 03

    Reconciliation exceptions

    Separate confirmed payments from unmatched, reversed, or disputed transactions.

Illustrative workflow · Shape the details around your institution.

AUTOMATION WITH A PURPOSE

When a verified provider event arrives.

Use an agreed trigger and response while keeping the responsible person in the decision.

WHEN

A verified provider event arrives

THEN

Check for an existing event before recording and allocating the payment.

How connected workflows work

APPROPRIATE CONTROL

Who can act on online payments?

Payment processing belongs to the agreed provider. Access to transaction references, refunds, and reconciliation must follow finance responsibilities.

Explore security and institutional control

KNOW WHETHER THE CHANGE IS HELPING

Payments properly accounted for

Review unmatched transactions and the time between provider confirmation and account reconciliation.

Agree the baseline, reporting period, and owner before comparing results.Connect evidence to decisions

SEE IT IN YOUR CONTEXT

Different institutions. Specific responsibilities.

A practical introduction

Bring a representative workflow, one recurring exception, and the people who own the handoffs.

Plan your implementation

BEFORE THE CONVERSATION

Useful questions about online payments.

Which payment gateways are included?

Gateway availability is determined for the deployment, country, currency, and payment methods. A provider connection is not implied by this illustrative page.

What makes finance implementation successful?

Bring the approved account and fee structures, opening balances, authorizations, and representative exceptions. Reconcile the agreed sample with the finance team before rollout.

PUT YOUR PROCESS IN THE PICTURE

Explore online payments in your institution.

Start with your current workflow, the decisions that take time, and the handoffs you want to improve.

This public page presents Qentak’s capability model and an illustrative workflow. Available modules, integrations, operating rules, and rollout scope are established in your implementation plan.

Explore all 69 capabilities