For finance and marketplace teams

Every payout, booked and checked. No settlement spreadsheet.

Payouts post to the ledger on their own. Only a payout over a limit you set waits for finance, and anything that doesn't add up is flagged.

Free sandboxTemplate ready to runSwap in your own apps

Watch it run: Supplier and marketplace payoutsThe workflow running in Nexra, from the first app to the record it leaves behind.
The problem

Every payout, split by hand.

The settlement report is downloaded, split into fees, refunds and chargebacks in a spreadsheet, then keyed into the ledger. When a payout doesn't match, nobody knows which line broke.

  • Stripe
  • QuickBooks Online
  • Microsoft Teams

Today

Settlement reports are downloaded and split into a spreadsheet, then keyed into the ledger line by line.

With Nexra

Each Stripe payout posts to QuickBooks Online as one balanced journal on its own, and anything that doesn't add up is flagged in Teams.

How it runs

Connect. Govern. Prove.

These are the exact steps the sandbox template runs. Routine runs go through on their own; only the exceptions you set wait for a person.

Connected

Apps, APIs, providers, and workflows.

Stripe to the ledger, payout by payout.

Each new payout starts the flow. Nexra reads the charges, fees and refunds behind it and posts one journal with every deduction on its own line.

  1. Stripe · Read the payout and its feesbalance_transactions.listRuns on its own
  2. QuickBooks Online · Post the balanced journaljournal_entries.createException: Payouts over $25,000 wait for financeRuns on its own
  3. Microsoft Teams · Flag payouts that don't balancechannel_messages.sendException: Only payouts that don't balance are flaggedRuns on its own

Approved

Permissions, approvals, limits, and secure credentials.

Payouts post on their own. Large ones wait.

Payouts post to the ledger on their own. Only a payout over a limit you set waits for finance. A journal that doesn't balance is never booked; it goes to Teams with the lines that broke.

  • Payout po_2041$12,480.00 · posted on its ownRuns on its own
  • Payout po_2077$31,800.00 · over $25,000, waiting for financeMaker-checker
Approval · financeMaker-checker

Post payout po_2077 to QuickBooks

Prepared by
Payouts flow
Amount
$31,800.00 net · fees $922.20
Rule
Payouts over $25,000 wait for finance
Expires
in 58 minutes, single use

Proven

Testing, reconciliation, logs, and evidence.

Every payout, matched to the books.

Each journal lands with its reference, and every run, approval and result joins the evidence chain, so a payout question takes seconds, not a month-end search.

Evidence · payouts

  • po_2041: QuickBooks journal JE-5530 posted on its own, balanced
  • po_2077: approved by finance at 07:12:40, under "Payouts over $25,000 wait for finance"
  • Fees and refunds recorded line by line

Example workflow, runnable in the sandbox. Names, amounts and times are illustrative.

Open by default

Use the apps you already run.

Same flow, same approvals, same evidence. Swap any step for another connector, or your own system with a REST or OpenAPI interface.

Book your next payout without a spreadsheet.

Install the template in your sandbox and watch test payouts post on their own, with the large one waiting for finance.