Read-only payout reconciliation

Know exactly
where the
payout went.

Upload your payment and bank exports. PayoutProof reconstructs the payout, verifies the numbers, and shows you only what still does not reconcile.

Nothing gets written back to your books.

ONE PAYOUT. EVERY MOVEMENT.ILLUSTRATIVE DEMO
stripe_payout_0921.csvREAD ONLY
bank_september.csvREAD ONLY

PAYOUT RECONCILIATION

Payout #43928

STRIPE / SEP 14–20USD
Gross sales
+$24,380.00
Refunds
−$1,240.00
Stripe fees
−$917.65
Chargeback
−$380.00
Reserve release
+$0.00
EXPECTED PAYOUT✓ CODE VERIFIED
$21,842.35
BANK DEPOSIT
$21,806.35
UNEXPLAINED
−$36.00
! 1 ITEM REQUIRES REVIEW

Possible cause: a reserve adjustment appears in the payment export but could not be matched on the bank side.

AI INTERPRETS · CODE VERIFIES
VERIFY, DON'T POST.

Your accounting stack stays. The guesswork goes.

01 / The problem

Sales are not the payout.
The payout is not always the deposit.

COMMERCE

Gross sales

$24,380.00

PAYMENT PLATFORM

Payout

$21,842.35

BANK

Deposit

$21,806.35

−$2,537.65EXPLAINED BY WHAT?
−$36.00WHY IS THIS STILL MISSING?

Illustrative figures throughout. The difference is easy to see. The work is proving why.

The monthly investigation

The last few dollars
can take most of the time.

TODAY / TOO MANY PLACES TO LOOK

  1. 01Open Stripe
  2. 02Export payout CSV
  3. 03Open Shopify
  4. 04Open bank
  5. 05Open QuickBooks
  6. 06Compare dates
  7. 07Compare transaction IDs
  8. 08Check fees
  9. 09Check refunds
  10. 10Find the exception

“Was this refund in the next payout?”
“Is the cutoff date different?”

WITH PAYOUTPROOF

01

Upload

02

Verify

03

Review exceptions

Same source data.
A much shorter question list.

Checked — not changed

Not another
bookkeeping
automation tool.

PayoutProof does not post.
It checks.

Keep the accounting process you already trust. Use PayoutProof as an independent verification layer for the payouts that need to be explained.

ACCOUNTING AUTOMATION

Sync. Post. Categorize.
Create entries. Write to books.

“Let us write the data correctly.”
PAYOUTPROOF

Read. Match. Verify. Explain.

“Let us verify that the numbers make sense.”ZERO WRITE ACCESS

02 / How it works

From two exports
to one reconciliation proof.

01

Upload

Bring the files you already use

Start with payment-platform and bank/accounting exports. No accounting migration and no new source of truth.

↳ stripe_payout.csv
↳ bank.csv
2 FILES READYREAD ONLY
02

Verify

Reconstruct the payout

Deterministically rebuild the expected payout from sales, refunds, fees, disputes, reserves, and adjustments.

SALES+$24,380.00
REFUNDS−$1,240.00
FEES−$917.65
CHARGEBACK−$380.00
✓ CODE VERIFIED$21,842.35
03

Review

Look only at what does not reconcile

Successful payouts get out of the way. Exceptions stay visible with the evidence needed to understand them.

47 PAYOUTS CHECKED
44✓ RECONCILED
3! REQUIRE ATTENTION
Review 3 exceptions →

03 / Exception first

Do not review
47 payouts.
Review the 3
that failed.

The useful screen is not the one with every transaction. It is the one where everything already explained has disappeared.

HIDE WHAT IS EXPLAINED.
SHOW WHAT IS NOT.

SEPTEMBER / PAYOUT REVIEWDEMO
47CHECKED
44✓ RECONCILED
3! NEED YOU
EXCEPTIONS ONLY
01#4218$12,437.28✓ RECONCILED
02#4219$8,904.11✓ RECONCILED
03#4222−$36.00! REVIEW REQUIRED
04#4223$6,318.40✓ RECONCILED
05#4237−$88.00! REVIEW REQUIRED
06#4238$4,118.92✓ RECONCILED
07#4241+$54.20! REVIEW REQUIRED
44 explained. 3 need a human.

04 / The proof

Every payout
gets a reason.

Not just a total that almost matches. A traceable breakdown of the money that moved — and the part that still needs an answer.

01

The movements.Every component, in one place.

02

The comparison.Expected payout against the bank.

03

The open question.A possible cause. For you to review.

EXAMPLE PROOF / DEMO DATA

PAYOUT RECONCILIATION

Payout #43928

Sales
+$24,380.00
Refunds
−$1,240.00
Processing fees
−$917.65
Chargeback
−$380.00
Reserve release
+$0.00
EXPECTED PAYOUT
$21,842.35
BANK DEPOSIT
$21,806.35
UNEXPLAINED
−$36.00

↳ POSSIBLE CAUSE

Reserve adjustment appears in the payment export but could not be matched to bank-side records.

AI-generated explanation — review before acting.
AI INTERPRETSCODE VERIFIES ✓

Built for financial arithmetic

AI can explain the mismatch.
It should not invent the math.

01 / DETERMINISTIC CORE

Code

Amounts · Dates · IDs · Matches
Tolerances · Joins · Payout boundaries

24,380.00 − 1,240.00 − 917.65 − 380.00
= 21,842.35
✓ VERIFIES
02 / INTERPRETATION LAYER

AI

Column mapping · Unknown labels
Human-readable explanations

“The bank deposit is $36 below the expected payout. A reserve adjustment may explain the difference.”
↳ INTERPRETS

AI interprets. Code verifies.

Read only by design

Check the books.
Don't let another tool
rewrite them.

PayoutProof is designed as a verification layer. Your existing accounting process remains the system you operate.

STRIPE EXPORTSHOPIFY EXPORTBANK CSVQBO EXPORT
READ-ONLY VERIFICATION LAYER

PayoutProof

READ VERIFY REPORT

NO WRITE BACK

YOUR BOOKS STAY YOUR BOOKS.

Small scope. Clear purpose.

Everything needed to check.
Nothing that posts.

02

Exception-first review

Hide reconciled payouts. Focus on the discrepancies that still need human attention.

44 CLOSED → 3 NEED YOU
03

Human-readable explanations

Translate an unexplained delta into a concise description of what may have caused it.

04

Read-only workflow

Verify data without adding another system that posts transactions into your books.

05

Payout-level evidence

Keep the totals, transaction components, and exception context together.

06

Existing workflow first

Start from the exports already used in the monthly close. Keep your accounting stack.

05 / Built for people who already reconcile

A verification layer
for real month-end work.

01

E-commerce bookkeepers

Review payouts across multiple client books without changing the accounting workflows those clients already rely on.

Illustrative workflow, not a multi-client workspace promise.
02

Monthly close

Turn payout reconciliation from a multi-file investigation into a short exception list before closing the month.

03

Automation audit

Use an independent check when your existing accounting workflow already moves data automatically but you still want to verify the result.

04

Client explanation

Turn a confusing payout discrepancy into a clean explanation you can review before discussing the books with a client.

Less investigation. More explanation.

The reconciliation workflow,
before and after.

01 / MANUAL

  1. Export payment data
  2. Open bank
  3. Open accounting
  4. Compare totals
  5. Check fees
  6. Check refunds
  7. Check dates
  8. Find mismatch
  9. Explain mismatch
  10. Repeat

02 / PAYOUTPROOF

  1. Upload
  2. Verify
  3. Review exceptions
  4. Done
CHECKED — NOT CHANGED

Reconciliation should end with an explanation,
not another spreadsheet.

Inside the product / Concept preview

One payout.
The whole explanation.

PayoutProof.SEPTEMBER CLOSE / 47 PAYOUTS↳ READ ONLY

RECONCILIATION / USD

Payout #43922

Sales
+$20,144.20
Refunds
−$620.00
Fees
−$1,008.37
Chargeback
−$88.00
EXPECTED
$18,427.83
BANK
$18,391.83
DIFFERENCE
−$36.00

✓ DETERMINISTIC CALCULATION

PAYMENT EXPORT + BANK EXPORT → RECONCILIATION PROOFNOTHING WRITTEN BACK.

For bookkeepers

One client has
one payout problem.
A bookkeeper has twenty.

PayoutProof is designed around professionals who already have a working accounting process and repeatedly perform the same verification across e-commerce clients.

YOUR MONTH-END MENTAL LOAD
CLIENT 01✓ EXPLAINED
CLIENT 02✓ EXPLAINED
CLIENT 03! REVIEW
CLIENT 04✓ EXPLAINED
CLIENT 05✓ EXPLAINED

CONCEPTUAL WORKFLOW
NOT A MULTI-CLIENT WORKSPACE PREVIEW

06 / Early access

Verification should
cost less than
the investigation.

One focused tool. A clearer month-end.

THE PROOF, NOT ANOTHER PLATFORM.
EXPECTED$21,842.35
BANK$21,806.35
TO EXPLAIN−$36.00 ↗
PROFESSIONALEARLY ACCESS
$49/month

Early pricing hypothesis for e-commerce bookkeepers and accounting professionals.

  • ✓ Payout reconciliation
  • ✓ Exception review
  • ✓ Reconciliation explanations
  • ✓ Read-only workflow
Get Early Access Plan scope may evolve during early product validation.
VERIFY, DON'T POST.

The PayoutProof philosophy

You already have
accounting software.
You need proof that
the payout makes sense.

The accounting system can remain exactly where it is. PayoutProof exists between the raw payment data and your confidence in the final number — verifying the arithmetic, explaining the discrepancy, and leaving the books untouched.

DATA → MATCH → VERIFY → EXPLAIN

NO WRITE BACK

07 / A few clear answers

Good questions.
Straight answers.

No accounting migration.
No mystery arithmetic.

01Is PayoutProof bookkeeping software?

No. PayoutProof is designed as a reconciliation checker. It explains how a payout was formed and surfaces the items that still need review rather than managing the full bookkeeping process.

02Does PayoutProof write to QuickBooks or Xero?

The product concept is read-only. It is designed to verify exported accounting or bank-side data rather than posting transactions back into the books.

03Does AI calculate the payout?

The intended model is deterministic reconciliation for financial calculations. AI can help interpret data structures or explain a discrepancy, but the arithmetic itself is verified by code.

04What files does it use?

The initial concept focuses on payment-platform exports such as Stripe or Shopify Payments together with bank or accounting-side exports. Exact format support should not be assumed beyond the formats implemented in the product.

05Does it replace A2X, Synder, or my accounting system?

No. PayoutProof is positioned as a verification layer rather than an accounting-sync or bookkeeping replacement.

06What happens when a payout reconciles correctly?

The exception-first workflow is designed to move successful payouts out of the way so attention can stay on the small number of discrepancies that still need investigation.

Month end / Nothing left unexplained

Explain the difference.
Then move on.

Verify the payout, find the exceptions,
and leave your books untouched.

Get Early Access

EARLY ACCESS / IN PREPARATION

Registration is not open yet. This is a product preview; no payment or financial files are collected here.

We don't touch your books.
We show you where the money went.