What came in, matched to what was owed
Card payments through Stripe, bank transfers through an open-banking feed, cash and cheques recorded at the desk — all landing against the family's charges rather than in a separate list to reconcile later.
Reconciliation is the part that takes the afternoon, so it is the part that is automated: a transfer with a reference is matched to the family and the charge without anyone reading a statement. What cannot be matched stays in a short list, and matching it teaches the next one.
For the office
What a secretary, a bursar or a head of year can do with it.
- Card payments from the parent portal, with the receipt sent automatically
- Bank feeds from GoCardless, Ponto or TrueLayer, imported nightly
- Automatic matching by reference and amount; the rest in one short list
- Cash, cheque and standing orders recorded at the desk, with an undeposited-funds account
- Receipts in Hebrew and English, per payment or per year
For whoever has to approve it
Where the data sits, who can read it, and what it connects to.
- Bank credentials are held by the provider, never by us; the feed is read-only
- Every payment carries its allocation history — nothing is silently re-pointed
- Stripe accounts are per organization, so a school with two entities keeps two payouts
Questions we are asked
- Which banks are supported?
- Anything reachable through GoCardless Bank Account Data, Ponto or TrueLayer, which between them cover most EU and UK banks.
- Can we take payments without a bank feed?
- Yes. Card payments and manual entry work on their own; the feed only saves the reconciliation.
See it with your own school's data
Sixty days free, no card up front — or open a ready-made demo school and click around it first.