When a PayPal invoice is paid by bank transfer outside PayPal, verify the received transfer and record it as an external payment against the invoice. Record only the amount actually received. Do not wait for a PayPal transaction that never occurred, and do not mark the whole invoice paid if part of the balance remains due.
This guide is for freelancers and service businesses whose customer used bank details instead of the PayPal invoice checkout. It separates the bank receipt, the native PayPal invoice and any independent PayRequest record so one payment is not mistaken for several sales.
Identify Whether the Payment Happened Outside PayPal
“Paid from my bank” can describe two different routes. A customer may fund a PayPal checkout payment from a linked bank account, or send a separate transfer directly to your business bank account. The first route can still be a PayPal transaction; the second is an external receipt.
PayPal's invoice payment-method guidance lists bank accounts among Wallet funding methods and notes that checkout options vary by market. Ask which route the customer used, then verify it in your own records instead of deciding from the phrase “bank payment.”
If PayPal shows a transaction that is still pending, use the pending PayPal invoice guide. Do not add an external-payment record just to make a pending transaction look complete. If money arrived directly in your bank with no corresponding PayPal checkout payment, continue with external-payment recording.
If you discover both a completed PayPal payment and an external transfer for the same obligation, use the invoice paid twice workflow. That is a duplicate-receipt investigation, not the single external-payment case covered here.
Verify the Bank Receipt Before Changing Invoice Status
Match the invoice reference, customer, amount, currency and received date against your own bank record. A customer screenshot is useful for locating a transfer, but it does not establish that the money reached the correct account. Check whether the receipt is completed and whether it belongs to this invoice.
Keep a concise reconciliation note: invoice identifier, bank transaction reference, gross amount received, currency, received date and the person who matched it. Avoid copying a customer's entire statement or unrelated transactions into the invoice. A traceable reference is more useful than a large collection of screenshots.
Investigate differences before marking the invoice fully paid. An amount short of the invoice total can reflect a partial payment, a bank fee, a currency conversion or a mistake. Those possibilities do not all justify the same balance adjustment. Confirm what was agreed and what remains collectible.
For recurring clients, equal amounts can belong to different periods. Use the invoice number and service period together. Do not allocate this month's transfer to an older invoice merely because it is the first open row in a list.
Record the External Payment on the PayPal Invoice
Open the original invoice in PayPal and use the available payment-recording action from its details page. PayPal's current US invoice-management guidance says sellers can record offline payments, including partial payments, and see them with notes in invoice activity. Labels and availability can vary by account and market.
Enter the actual external method, date and amount offered by the form. Include a useful reference without sensitive bank details, then check the resulting activity and remaining amount. Recording receipt documents money already received; it does not initiate a bank transfer or move money into your PayPal balance.
PayPal's current invoicing reference distinguishes a full externally recorded balance from a partial one. Full external settlement can produce MARKED_AS_PAID, while a partial recorded amount leaves the invoice PARTIALLY_PAID. These are invoice states, not proof of a new PayPal processing transaction.
Do not cancel a valid sale simply because the customer used a different payment route. Archiving is a list-management action, and cancellation is different from recording settlement. Keep the invoice and payment evidence connected so the customer and your bookkeeping process can identify what was paid.
Reconcile a Partial Bank Transfer Without Erasing the Balance
Here is an original worked example for a fictional €600 service invoice. Assume the customer owes the full amount, has made no other payment, and first sends €200 directly to your bank. All amounts use the same currency and exclude any separate fee adjustment.
| Event | Verified receipt | Remaining invoice amount |
|---|---|---|
| Invoice issued | €0 | €600 |
| First external transfer received and recorded | €200 | €400 |
| Second external transfer received and recorded | €400 | €0 |
After the first receipt, the arithmetic is €600 − €200 = €400 due. Marking €600 as paid would erase a genuine outstanding balance. Recording the first €200 twice would also create the wrong result even though no money was refunded or moved.
After the second receipt, the two external records total €600 and the balance becomes zero. Before recording it, search for that bank transaction reference in your reconciliation notes. A repeated email about the same transfer is not another receipt.
If you entered an incorrect payment record, use the correction action supported by PayPal and verify the invoice again. Do not invent a refund when no money was returned. Keep an explanation of the correction so a later reviewer can distinguish a data-entry change from a financial movement.
Keep Any PayRequest Invoice Record Independent and Accurate
For future billing, PayRequest invoicing can keep the invoice and customer workflow together. If you already maintain a related invoice in PayRequest, reconcile it from the same verified receipt. A native PayPal invoice and a PayRequest invoice are separate records unless a verified integration explicitly connects them; this article does not claim automatic import or synchronization.
The PayRequest invoice view reviewed on 12 September 2026 supports manual status changes and records the old status, new status and supplied reason in an activity log. Its manual reminder check also refuses a reminder for an invoice confirmed as paid. These controls help record an established outcome; changing a status does not itself verify a bank transaction.
Use the paid status only when the invoice is fully settled. The reviewed manual status selector is not a partial-payment ledger. For an incomplete external payment, keep the actual amount and remaining balance in your reconciliation process instead of presenting the invoice as fully paid.
The customer billing portal provides a consistent place for customers to see their PayRequest billing records. Check the visible result after a status correction, while retaining the bank reference as receipt evidence. Do not assume that updating PayRequest also stops a reminder scheduled independently in PayPal or another system.
Close the Loop With the Customer and Your Reminder Queue
Once the full receipt is verified and recorded, review reminders in the system that issued the invoice. Check any separate email queue or bookkeeping workflow as well. The goal is to stop asking for the settled amount while preserving an accurate history of the sale.
A useful confirmation is: “We received your €600 bank transfer for invoice INV-600 on [date] and recorded it against that invoice. The remaining amount is €0. No further payment is required for this invoice.” For a partial receipt, state the received amount and the actual remaining balance instead.
For your next invoice, choose one primary billing record, put its reference in the payment instructions and define who matches external transfers. Start with PayRequest invoicing and review pricing: the Free plan has no monthly charge, with 2% per successful payment capped at €25 per transaction and provider fees separate. This general pricing statement does not determine fees for an external bank receipt or a manual status change.
Editorial note: AI assisted with this article and illustrative cover. PayRequest manual status and reminder behavior was reviewed in code; no payment, refund or invoice change was executed. The reconciliation example is an original operational model, not jurisdiction-specific accounting advice.