Payments When Moving from OSM

This one is for reference — nothing imports#

Payments are different from your other data. There is nothing to export and import here, because payment arrangements do not transfer between platforms. This article is simply to explain what to expect, and what to do instead.

Direct Debits and history do not move#

Two things in particular stay behind in OSM:

• Direct Debit mandates — the authority a parent gives to collect payments — cannot be transferred to another platform. Each provider sets these up under its own arrangement.
• Payment history — past transactions and receipts stay in OSM.

This is normal and expected when moving between any two systems. The practical upshot is that you set collection up fresh in Scoutworks rather than migrating it.

What to do before you switch#

A little preparation makes the transition painless:

• Note your subscription amounts — what each family pays, and how often (for example, termly or monthly). You will use these when you set up payments in Scoutworks.
• Keep a copy of recent payment history from OSM for your own records before you close the account.
• Run both systems in parallel, then make a clean cut-over. The natural point is the start of a new term, or whenever your subscriptions are due to be set up again anyway. Collect that first cycle in Scoutworks rather than OSM, and time it around your OSM renewal so you are not paying for two systems for long.

Setting payments up in Scoutworks#

Once you are in Scoutworks, you can set up your group's bank details and start collecting. New Direct Debit mandates are created within Scoutworks, so parents authorise collection once and you are away.

• First steps after signup — the early setup, including getting your group ready.
• Moving from OSM to Scoutworks — the full migration checklist.

What's next#

• Moving from OSM to Scoutworks
• Are you ready to switch? — the printable one-page summary.