Commissa

Penny-exact commission statements — flat, tiered, per-category or on quota attainment — owned outright.

The problem it solves

Anywhere reps earn commission, someone owns The Spreadsheet — and every pay period it produces a dispute. Tiered schemes are where it breaks: a deal that straddles a band gets rounded twice, the statement doesn't reconcile to the total, and the argument costs more goodwill than the pennies involved. Commission SaaS fixes the math but charges per seat, per month, forever, for what is a calculator plus a ledger.

• Tier-boundary math that's subtly wrong in a spreadsheet
• Statements that don't reconcile, and reps who notice
• Per-seat SaaS pricing for a pay-period calculation you could own

Every feature

• Email a rep their own statement. One button on the period sends a rep their statement — their deals, their tiers, their total, nobody else's — through your own SMTP, off until you enable it, every send recorded.
• CRM exports import without re-heading. Deal exports from your CRM import as the file your CRM already writes — columns recognized, reps matched by name, and anything unmatched reported rather than guessed.
• Commission schemes. Flat rate, progressive tiered bands (like tax brackets), per-product-category rates, or a quota scheme that pays a higher rate past quota, defined globally or per rep.
• Penny-exact tier math. Money is integer cents and rates are integer basis points; a deal that straddles a tier is split across bands to the cent, and statement lines always sum exactly to the period total.
• Effective-dated rules. Commission rules carry effective dates, a rep-specific rule overrides the global one, and a pay period you close keeps its statements as paid — so a mid-year plan change is a new dated rule, and a later correction is carried into the next open period.
• Deals and pay periods. Record deals with won/pending status — only won deals earn — and compute payouts for monthly, biweekly, or custom periods with inclusive date ranges.
• Per-rep payout statements. Each statement shows every deal, the applied rate or tier breakdown, the commission, and a running total — exported as a dependency-free PDF and hardened CSV.
• Bonuses & clawbacks. Add positive or negative adjustments in exact integer cents, itemized on the statement.
• Installable mobile app (PWA). Add it to a phone or tablet home screen straight from the browser — a full-screen app served from your own server, with no app store involved. Business data is not stored offline on the device; what you see is read live.
• Disputes with an outcome. Raise a dispute against a deal, decide it, and settle it with an adjustment that lands on the statement; every step is in the audit trail.
• Reps see their own statements. Send each rep a private link to their statement for the period: every deal, the rate applied to it, adjustments and net, with no login. A rep can question any line, and it lands on your Disputes screen.
• A closed period stays what was paid. Close a paid period and its statements freeze, with a fingerprint printed on each. A correction found later is carried into the next open period as one adjustment that names where it came from.
• Quotas and accelerators. Set each rep's quota for the period and see attainment on every statement. A quota scheme pays a higher rate past quota (8% up to quota, 12% above, or a stepped plan), on the same to-the-cent engine as the tiers.
• Approve payouts, then hand them to payroll. Optionally, an administrator approves each period's payouts before it can close, and a changed payout needs approving again. A closed period gives a payroll CSV: one row per rep with their payroll employee ID and the amount.
• A change log for the plan. Every change to a commission rule is kept: who made it, when, what changed in plain words (a rate, a band, a category, who it applies to: before → after) and the reason typed with it.
• Commission that waits for the customer's money. Switch it on and a won deal earns in the period its customer paid; until then it is listed on the rep's statement as held and earns nothing. Enter the payment date on the deal, in a CSV import or through the API.
• Updates from inside the app. The Updates page installs a new release with your license key: Ownware's signature is checked, a backup is taken first, and the app puts the previous version back by itself if the update is interrupted or the database step or start-up check of the new version fails. It never checks by itself.
• Backups by themselves. Automatic backups, an optional copy to S3-compatible storage you own, and a weekly check that the latest backup reads back. The Health page names anything that needs attention.
• Own It 4.0.1 — fixes and an up-to-date manual. For Commissa, 4.0.1 fixes an installer that had lost its styling, a rollback that a page opened during an update could stop and a command-line update that ended in an error after putting the previous version back. Its manual, FAQ and QUICKSTART now cover everything 4.0 added, including two Nginx rules that keep the data folder private. Your license covers it: press Check for updates on the Updates page, or download it from your order page.
• Own It 4.0.2 — the installer opens on every host. For Commissa, 4.0.2 fixes a fresh install on an Apache host: the one-page setup at /install/ looped back to itself and never opened, and now it opens. Your license covers it: press Check for updates on the Updates page, or download it from your order page.

Release notes in full

• Own It 4.1: client installations and your other tools. For Commissa, 4.1 makes two changes that every app gets. An Extended license bought from October 4, 2026 covers up to ten client installations, one per client project: hand each one over to the client or host it for them, with the client's logo and colors from the app's branding settings. The API reference now shows how to connect Commissa to Zapier, Make or n8n, using its own webhooks and API key. Your license covers the update: press Check for updates on the Updates page, or download it from your order page.
• Own It 4.0: it updates and backs itself up. For Commissa, 4.0 means updates from inside the app: the Updates page checks for a new release with your license key, verifies Ownware's signature, takes a backup and puts the previous version back by itself if the update is interrupted or the database step or start-up check of the new version fails. A new install can start with a sample business and remove it in one click; backups run by themselves, with an optional offsite copy and a weekly check that the latest one reads back; and the Health page says whether the install is looking after itself.
• Own It 3.3: paid when the customer pays, with the plan's history kept. This release tied commission to the customer's money and kept the plan's history. Switch it on and a won deal earns in the period its customer paid, and until then it is listed as held on the rep's statement. Every change to a commission rule is kept: who made it, when, what changed and why.
• Own It 3.2: reps see what they are paid. This release opened the statement to the rep: each rep gets a private link to their own statement, with no login, and can question any line. A closed period stays what was paid, and quotas and accelerators pay a higher rate past quota. Payouts can be approved before a period closes and handed to payroll as a CSV.
• Own It 3.1: it writes to the people you serve. The 3.1 wave gave the catalog a way to reach the other side of the transaction: counterparty email through your own SMTP server, calendar feeds your own calendar subscribes to, attachments filed where the paperwork belongs, and export presets other people's software imports. Each outbound feature ships switched off and runs on your own credentials; a failed send is recorded, and the action that triggered it stands. What this app gained is listed at the top of this section.
• Own It 3.0: works for your AI, not just for you. Six MCP tools cover reps (with the rule that applies to each), deals, statements, period rollups and disputes — and every money figure comes out of the same payout engine the screen, the CSV, the PDF and the REST API use, so an agent and an accountant cannot be shown different numbers.
• Own It 2.0: API, 2FA, backups, dark mode. Commissa 2.0 adds the 2.0 owner layer. Upgrade by replacing the files — the database migrates itself, and it is still the same one-time purchase.