CherryMoney University Training: accounting, invoices, VAT, expenses and AI finance workflows
CherryMoney Training
Log in Open account

Module 15

Cherry Pay: Rewards, Subscriptions And Payment Automation

Review Cherry Pay payment requests, rewards, cashback, subscriptions, recurring billing and AutoPay controls in sandbox or provider-enabled environments.

Start module Simulator practice Sign in to take training

Learning Goals

By the end of this module, learners should be able to complete the workflow in CherryMoney and explain the accounting reason behind each important step.

  • Explain the lifecycle of a payment request, provider attempt and final payment status.
  • Review reward offers, cashback funding, refund protection and settlement controls.
  • Review subscription plans, renewals, dunning and recurring merchant billing.
  • Explain VRP or AutoPay consent, limits, provider readiness and fail-closed behaviour.

Lesson Plan

Use these lesson blocks for lecture delivery, live demo and class discussion.

Payment orchestration

Cherry Pay can coordinate payment requests and provider attempts while preserving explicit statuses, idempotency and audit evidence. Production execution depends on configured payment providers.

Rewards and cashback

Offers, reward claims, refunds, merchant-funded cashback and settlement require programme budgets, controls and auditable state transitions.

Subscriptions and AutoPay

Recurring billing combines plans, payer consent, renewals, failed-payment recovery, provider operations and admin controls.

Step-By-Step Lab

This is the student-facing sequence for the practical class. Complete the steps in order, then capture the evidence listed below.

  1. Confirm the exercise uses a sandbox or unavailable provider adapter and cannot move real money.
  2. Review the customer or merchant context before creating any payment or subscription record.
  3. Check amount, currency, reference, consent and provider status.
  4. For rewards, confirm offer terms, capacity, programme budget and refund behaviour.
  5. For subscriptions, review renewal date, collection state and any dunning or suspension action.
  6. For AutoPay, confirm mandate terms and limits before simulating an execution.
  7. Use admin controls and audit history to explain why a flow was allowed, paused or rejected.

Classroom Run Sheet

Use this structure to teach the module in a repeatable classroom or lab session.

Explain
Explain this module Introduce the accounting concept first: customer, invoice, VAT, expense, fund, role or audit trail.
Demonstrate
Demonstrate this module Trainer performs the workflow once in CherryMoney using a projected simulator account.
Practise
Practise this module Students complete the same workflow in their own VM tenant using seeded records.
Review
Review this module Students compare system outputs with expected accounting treatment and discuss errors.
Evidence
Evidence this module Students submit screenshots, exports, PDFs or short explanations for assessment.

Simulator Practice

These are the VM practice tasks for this module. They are written as student-facing tasks and can later be wired into a guided simulator checklist.

Practice Brief

  1. Create or inspect a sandbox Cherry Pay payment request and review its status lifecycle.
  2. Review a fictional reward offer and cashback settlement record.
  3. Create a fictional subscription and trigger a renewal scenario.
  4. Review a failed recurring collection and its retry or dunning state.
  5. Inspect a VRP or AutoPay mandate and identify consent, amount and frequency controls.

Knowledge Check

Use these questions for in-class review, a short quiz or a reflective workbook entry. Answers are hidden by default — open each one to check your work.

  1. Q1 What controls should be checked before a recurring payment attempt? Answer

    Provider readiness, payer consent, and the agreed amount and frequency limits on the mandate.

  2. Q2 Why are provider readiness, consent and idempotency important? Answer

    Without them, a recurring or automated payment could be attempted without authorisation, retried twice by mistake, or fail in a way nobody can trace — these controls keep every attempt deliberate and auditable.

  3. Q3 How should a failed collection or reward refund remain visible in the audit trail? Answer

    Its retry, dunning or refund state should stay visible and explained, not silently disappear from the record.

Assessment And Evidence

Students should submit proof that the workflow was completed and a short explanation of the decisions made.

Student Evidence

  • Submit one payment lifecycle diagram and one recurring-payment exception review.
  • Explain why production provider access and customer consent are mandatory before any real payment execution.

Trainer Notes

  • Do not use live bank details, production payment credentials or real mandates in training.

Continue The Course

Move through the modules in order for a complete accounting, invoicing, compliance and AI finance workflow.

Module 13 4 hours

Cherry Analytics, KPIs And Management Reporting

Use the Cherry Analytics companion workspace for deterministic reporting, KPI review, commentary and evidence where the organisation has Analytics access.
Module 14 5 hours

Forecasting, Scenarios And Group FP&A

Build deterministic forecasts from assumptions and dated events, then review scenario, multi-entity, elimination and FX effects at group level where enabled.
Module 16 6 hours

Capstone: Month-End And Quarter-End Simulation

Students complete a full finance cycle from setup to reporting using seeded simulator data.