Walkthrough · Skye Split Engine Ops

Full walkthrough tutorial

Go from blank install to protected money-ops workflow without guessing what page does what.

This tutorial walks through the real order of operations: set the shell, add payout people, build the split math, schedule recurring runs, track deals, issue receipts, and export backups. Mark steps done as you move. The app remembers tutorial progress locally.

Jump into split engine Open backup vault

Tutorial progress

0 / 7

Interactive checklist progress

Recommended next move

Start

Open the first unfinished lane.

Current data readiness

Based on your saved records

Last backup activity

Never

Create a vault recovery point after setup.

What each lane is actually for

Settings

Brand the shell, choose currency, set glass/background, and decide how often auto snapshots should happen.

Open

Contacts

Store recipients, vendors, contractors, founders, or internal payout people so later forms are faster.

Open

Split Engine

Build the payout math itself. Gross in, deductions out, participants defined, and a reusable plan saved.

Open

Money Ops

Turn split plans into recurring payout templates and track actual deal ledger rows with status and due dates.

Open

Receipts

Issue settlement receipts tied to a deal or split, then print or export the proof file.

Open

Backup Vault

Create local restore points and export plain or encrypted full backups outside the browser.

Open

Fastest clean setup order

Do not start in Receipts. The clean order is Settings → Contacts → Split Engine → Money Ops → Receipts → Backup Vault. That gives you reusable math first, then actual operating records, then proof, then protection.

15-minute practice run

A. Add one contact

Example: Founder payout, Contractor payout, or Vendor reserve recipient.

B. Build one saved split plan

Example: gross 10000, fees 300, reserve 500, two people at 60/40.

C. Convert it into a monthly recurring template

Set next run date and default gross if you want the template to stamp out similar runs.

D. Create one deal ledger row

Use the same numbers and link the template or split so the record chain stays clear.

E. Issue one settlement receipt

Tie it back to the deal, then print or export as proof.

F. Export one encrypted backup

That turns your local workflow into something recoverable after browser/device issues.

CSV batch movement, without confusion

Export first

Always export a CSV from the live app before editing batches. That gives you the right column layout.

Edit outside the app

Use your spreadsheet tool, keep the same headers, then import the cleaned file back in through Money Ops or Receipts.

Import by lane

Deals, templates, contacts, and split plans import through Money Ops. Receipts import through the Receipts page.

Snapshot before big imports

Make a vault snapshot first so a bad batch can be rolled back fast.

Recent local activity

What success looks like

Saved contacts

People are ready to be reused in later records.

Saved split plans

Your payout logic is reusable and not trapped in one calculation.

Recurring templates

You can stamp out repeat payout runs instead of rebuilding math every time.

Deal ledger rows

Money movement is tracked as actual operating records.

Settlement receipts

You have printable proof tied to the underlying work.

Vault backup

You can survive browser wipes or device changes.