PAYMENT MATCHING & REVIEW
Reconciliation
Import a genuine bank or PayPal transaction export, match it against server-verified PayPal captures, review every decision, and post approved entries to your internal ledger.
Live statements, payment evidence, approvals, ledger entries and audit events are saved to your authenticated Supabase workspace. No reviewer token is required.
Signed-in account: reviewer identity is recorded automatically from your authenticated session.
1. Import bank statement CSV
Upload an original CSV export from your bank or payment provider. No bank account connection is implied.
Accepted CSV columns and PayPal export guidance
transaction_id,amount,currency,reference,description,posted_atBank export: use the bank transaction ID, incoming amount, currency and the PayPal capture/order reference shown in the bank narration or reference field.
PayPal activity export: Transaction ID, Gross, Currency and Date are accepted; when no separate reference column exists, Transaction ID is used as the reference. Invoice ID or Custom Number is also accepted as a reference.
Use an original provider/bank export, not the public synthetic judge CSV. To test the public sample, first select “Try sample review” above, then import it in that separate sample workspace. Positive incoming amounts only. Transaction IDs are deduplicated. A PayPal activity export can confirm provider-side activity; it does not prove that funds settled in a bank account.
Accepted amount headers include amount, gross, credit and deposit amount. Accepted date headers include posted_at, transaction_date, date and booking_date. Keep the original source file for your records.FOR HACKATHON REVIEWERS
Judge testing kit
Choose one clearly separated test path: your private payment evidence or the public synthetic reviewer sample.
You are in your private workspace. Download your verified PayPal evidence here, or use an original bank/provider export.
Import your account evidence or original statement here, then run safe matching. For the public sample, click “Try sample review” first and import it there instead.
Exact reference, amount and currency matches remain pending until a human approves them. Exceptions are never auto-approved.
Important: PayPal capture evidence confirms provider-side activity; it is not proof of bank settlement. The public sample is synthetic and demo actions affect only the local demo session.
Your private workspace is not displayed until you select “Load my workspace”. Load it to view your statement rows, pending matches, exceptions, ledger entries and audit activity.
2. Match and review queue
Only your own completed, persisted PayPal captures with a server verification timestamp are eligible evidence. Reference may be the internal PayProof order reference or PayPal order/capture ID.
| BANK TRANSACTION | REFERENCE / DESCRIPTION | AMOUNT | STATUS | REVIEW REASON | ACTION |
|---|---|---|---|---|---|
| No statement rows yet. Import an actual bank or payment-provider CSV to begin. Synthetic judge samples belong in the separate sample review only. | |||||
3. Persistent workspace ledger
Approved entries saved to Supabase after explicit posting.
No entries posted yet.
4. Auditable activity
Import, matching, review, rejection and posting decisions.
No audit events yet.