ABN Invoice

Invoice collections · manual review

Payment Processor Balance Bridge Review

Bridge a processor account from opening balance through net activity and payouts to closing balance. Keep this separate from invoice revenue or bank cash.

Try the invoice tool now ↗

The existing invoice tool is separate. Start without signing in; free output has branding and usage limits. This review is not a new automatic billing, bank-sync or membership feature.

What decision does this help with?

Expected closing equals opening plus signed net activity minus signed payout deductions. Reported closing minus expected closing is the unexplained difference. Use amounts from one complete report window.

Start with filled fictional records

Use internal codes instead of personal or bank details. Entries are reviewed locally in this page and are not uploaded, saved to an account or written into a draft. Keep a separate copy before leaving.

Account code | Opening | Net activity excluding payouts | Payouts deducted | Reported closing

Choose Review to inspect the entered example.

Fictional worked case · not customer evidence

Expected result and how to read it

Opening500 plus net activity1200 minus payouts1000 gives expected closing700. Reported690 leaves an unexplained difference of -10.

Before using the result

  1. Choose a review date and source scope where requested. Preserve original invoices and agreements; a pasted row is not evidence by itself.
  2. Use one consistent currency, unit and amount basis. Correct a source conflict before copying a result to another record.
  3. Read every flagged or excluded record. A blank record is not assumed to be a verified zero. Editing inputs clears the prior result and disables its download.
  4. Download the review for your own working papers if useful. The CSV is a manual review file, not an invoice or an accounting-system import format.

All figures must use the same account, currency, timezone, period and pending/available scope. Payouts must be excluded from net activity or they are counted twice. A zero difference is only arithmetic consistency.

Prepare only verified new work

Resolve differences in your original records first. Open the existing invoice tool only when the next charge has been independently checked. Re-invoicing an already issued balance would duplicate the request for payment.

Try the invoice tool now ↗

Questions before acting

Does a match prove payment, approval or a valid invoice?

No. The result compares only entered facts under the displayed method. Verify original records and any agreement before taking action. It creates no invoice, receipt, approval or new right to charge.

Can I use this for regular customer reviews?

All figures must use the same account, currency, timezone, period and pending/available scope. Payouts must be excluded from net activity or they are counted twice. A zero difference is only arithmetic consistency.

Source and independent method

The source below provides context for the workflow. The worked examples and comparison method on this page are independent manual aids, not a source-endorsed feature or a claim about another product’s current capabilities.

Read the original source

Reviewed 19 October 2026. A manual review file is not an invoice or a receipt.