Money movement

Xero Supplier Payment on Account: Record and Allocate Advances

A supplier advance should remain visible until it is allocated or refunded—not disappear into a reconciled bank transaction. Here is how to manage that workflow in Xero, including cross-border payment checks.

Illustration of a supplier advance linked from a bank transaction to an invoice, with payment fees tracked separately.

To record a supplier payment on account in Xero, generally use a supplier prepayment when you deliberately pay before receiving a bill. Create the prepayment against the correct supplier contact, reconcile the bank movement, and allocate the credit when the bill arrives. If you accidentally paid more than an existing bill required, use the overpayment workflow instead.

The important distinction is between recording money leaving the bank and reducing the amount you owe a supplier. These are connected steps, but they are not interchangeable. For international suppliers, you must also establish what currency and amount the supplier actually received.

Prepayment, overpayment, or ordinary bill payment?

“Payment on account” is a business description, not a sufficiently precise transaction instruction. Before entering anything in Xero, establish whether a bill exists and why the money was sent.

SituationLikely workflowOperator check
Deposit paid before a bill existsSupplier prepaymentKeep credit linked to the supplier
Payment against an existing billFull or partial bill paymentMatch the existing transaction
More paid than the bill requiredBill payment plus overpaymentSeparate the excess amount
Annual service billed upfrontBill payment plus expense-period treatmentReview prepaid-expense accounting

Vintti’s guide to Xero prepayments describes using prepayments for advance payments and subsequently applying them to invoices or bills. By contrast, Northern Accountants’ overpayment guide explains the separate overpayment transaction workflow. Do not choose between them simply because both can leave a credit against a contact.

A supplier prepayment is also different from a prepaid expense. The former tracks an advance before the bill; the latter concerns when a cost belongs in the profit and loss account. Creating a Xero prepayment does not, by itself, spread an expense over future accounting periods.

How to record a supplier advance in Xero

The workflow below focuses on a deliberate advance before a bill exists. Screen labels, permissions, and available currency options can vary. Confirm the current options in your Xero organisation before posting, especially for foreign-currency transactions.

Check the supplier and supporting document

Search for an existing bill, payment, or prepayment first. A deposit request may already have been entered by another team member. Creating a second transaction would duplicate the accounting rather than resolve the payment.

Use the supplier’s established contact record. Retain the deposit request, purchase order or contract reference, payment currency, and purpose. Verify changed bank details independently before releasing funds; an accounting contact is not evidence that new payment instructions are genuine.

Create the prepayment from the bank transaction

When the outgoing payment appears in bank reconciliation, use the create-transaction workflow and select the Prepayment transaction type rather than treating it as an ordinary spend-money expense. Select the supplier contact and enter the relevant reference and transaction details.

Use the account and tax treatment approved for that transaction. Do not assume all deposits have identical VAT or GST treatment: jurisdiction, supporting documents, and the nature of the supply matter. Ask your accountant where treatment is unclear.

If the payment has already been recorded, match the bank line to that record instead of creating another prepayment. Recording or reconciling a transaction in Xero is not, by itself, an instruction to send money.

Verify both the bank match and the supplier credit

After reconciliation, confirm that the payment is visible against the intended supplier and that its unallocated amount is correct. Retain a reference connecting the accounting record to the bank or payout-provider transaction.

A reconciled bank line is not proof that the advance will be deducted from the next payment run. That requires the supplier credit to be identified and applied.

Allocate the advance when the bill arrives

Enter and approve the supplier bill through your normal process. Review the available prepayment credit and allocate the appropriate amount against the bill. Verify the remaining balance before scheduling payment.

Do not assume that matching supplier names or references guarantees automatic allocation. Check the result explicitly. If the bill uses a different contact or currency, investigate the mismatch rather than forcing the allocation through an unrelated adjustment.

What changes when the payment is an overpayment?

If a bill already exists and the supplier received too much, first account for the amount that settles the bill. Record the excess through the supplier overpayment workflow. In the relevant spend-money creation flow, this involves selecting Overpayment rather than an ordinary spend transaction.

Agree whether the supplier will return the excess or retain it against future bills. A promised refund is not yet a bank receipt, and a retained credit is not permission to ignore it during future payment runs.

Where a single bank debit covers a bill and an excess amount, the records matched during reconciliation should explain the entire debit without duplicating it.

The common mistake: coding a deposit only to an asset account

Posting an ordinary payment to a general-ledger account named “Prepayments” can produce an apparently sensible balance sheet while leaving no allocatable supplier prepayment credit. The bank reconciles, but the later bill can still appear fully payable.

This does not mean an asset account is always wrong. It means the account classification and the supplier allocation mechanism solve different problems. You need both appropriate accounting and a reliable way to deduct the advance.

If a deposit was recorded incorrectly, review the existing transaction before adding anything else. Consider closed periods and filed tax returns before correcting or reclassifying it. The goal is one accurate cash movement with a traceable supplier balance—not a second payment record.

International advances need a settlement check

For cross-border payments, distinguish the amount debited from your bank, the amount instructed in the payment currency, and the amount credited to the supplier. FX conversion and fees can make those figures differ.

Your advance record should retain:

  • Supplier and purchase reference: the contact, order, and reason for the advance.
  • Currency and principal: the agreed deposit currency and amount, separately from identifiable fees.
  • Payment evidence: the provider reference, status, and available delivery confirmation.
  • Supplier confirmation: the amount the supplier recognises as credit against the order.
  • Accounting linkage: the Xero transaction reference and eventual bill allocation.

For the wider fee-allocation problem, see our guide to paying international supplier invoices in full. A bank charge should not silently become an unexplained reduction in the supplier’s deposit.

Also verify that your Xero subscription and transaction workflow support the currencies involved. Do not assume that a prepayment in one currency can be allocated directly to a bill in another. Have your accountant review unsupported allocation scenarios and any foreign-exchange treatment.

Hypothetical example: an overseas production deposit

A manufacturer requests a deposit in its invoice currency before production. Your business pays from a different-currency bank account, and the payment provider charges a separate fee.

Record the supplier advance and the fee according to their respective accounting treatment. Obtain confirmation of the deposit credited to the order. When the final bill arrives, check whether it shows the full order value or only the remaining balance: deducting the deposit again from an already-net bill would understate the payable.

Allocate the advance where appropriate, reconcile the resulting balance with the supplier, and release only the verified remainder.

Checklist before the next payment run

  • Check for unallocated advances and overpayments before approving supplier balances.
  • Confirm that the bill, advance, and payment instruction refer to the same supplier and purchase.
  • Verify whether the final invoice is gross or already net of the deposit.
  • Investigate currency differences, deductions, and returned payments separately.
  • Give each unresolved advance an owner and a follow-up date.
  • Review the actual report used for payment approval; do not assume every report includes unallocated credits.
  • Prevent a second release while an earlier transfer is still being investigated.

For larger supplier portfolios, make the advance check a release condition rather than a reminder. In evaluating AP automation, ask how the workflow exposes unapplied credits before payment approval and preserves references through reconciliation.

Close the advance, not just the bank line

A sound Xero supplier payment on account workflow ends when the advance is allocated, refunded, or otherwise resolved with supporting evidence. Bank reconciliation is an intermediate milestone.

Start by reviewing open supplier advances and assigning responsibility for each unresolved balance. If international payment execution sits outside Xero, evaluate Payouts.com’s payout automation alongside your accounting workflow, with particular attention to how payment references, settlement evidence, and exceptions will return to the finance team. Confirm the required integration and transaction coverage before implementation.

Created with AI assistance. Sources are linked in the article; this content is general information, not legal, tax, or financial advice.

Discussion

39 comments
  • Diego Berg ·

    The advice to verify both the bank match and the supplier credit after reconciliation is something we learned the hard way. We had three prepayments that reconciled perfectly but never showed up as available credits when the bills came in because they were tagged to the wrong contact variant in Xero. Now we have a checklist that requires the AP clerk to screenshot the supplier credit balance immediately after reconciling.

    Reply
    • Lucas Holm ·

      We've had the same issue, and it's worse when you have international subsidiaries of the same supplier set up as separate contacts. The prepayment sits on 'Supplier Ltd - UK' but the bill comes in under 'Supplier Ltd - Singapore' and no one notices until month-end reconciliation.

    • Felix Costa ·

      We had the same contact variant problem, especially with suppliers who had multiple entities or changed legal names. Now we enforce a policy that any new contact record has to be approved by AP and checked against existing records before it can receive a payment. Still doesn't catch everything but it's reduced duplicate prepayments significantly.

  • Noah Khan ·

    The part about not confusing the account classification with the supplier allocation mechanism is crucial. I've seen too many controllers think they've done their job by getting the balance sheet right, but then AP is still scheduling duplicate payments because there's no supplier credit visible in the contact record.

    Reply
    • Elsa Sato ·

      Exactly. We had this happen with a retainer payment where finance posted it to a prepaid asset account for the balance sheet, but the supplier contact showed zero credit. Three months later AP issued a second check for the same engagement because nobody connected the two records. Now we require the prepayment transaction type for anything going to that supplier, regardless of the GL treatment.

    • Idris Yamamoto ·

      We had this exact scenario with quarterly hosting fees. Balance sheet was clean, but the supplier kept appearing in our payment run at full invoice value because the prepayment credit wasn't linked. Had to unreconcile and redo it properly as a prepayment transaction type.

  • Kwame Silva ·

    The workflow distinction between overpayment and prepayment is helpful, but what's your recommended approach when you discover the mistake weeks later and the bank feed is already reconciled? We had a case where someone coded a supplier advance as a regular bill payment, and by the time AP caught it we'd already closed the month and filed VAT. Reversing it cleanly without reopening the period turned into a mess.

    Reply
    • Elena Mbeki ·

      If the bank feed is already reconciled, you'll need to delete the incorrect reconciliation first, then create the prepayment transaction and re-match it. Xero won't let you reclassify a reconciled transaction from a bill payment to a prepayment without breaking the original match. Just make sure you're not inside a locked period before you start unwinding it.

    • Kofi Ali ·

      If the bank feed is already reconciled to the wrong transaction type, you'll need to unreconcile it first, delete or void the incorrect transaction (depending on whether it's in a locked period), then reconcile correctly as a prepayment. The tricky part is if it crossed a filed VAT return—then you might need to leave the original and use a journal to reclassify, but honestly that gets messy and I'd loop in your accountant before doing anything.

  • Aarav Rahman ·

    The table at the top is the most useful thing I've seen on this topic. We had three different people entering the same deposit three different ways because 'payment on account' can mean any of those scenarios depending on who requested it and when the PO was cut.

    Reply
    • Lena Mensah ·

      We ended up adding a required 'reason code' field in our payment approval workflow that forces the requester to pick from those exact scenarios before the payment gets queued. Cut down on duplicate entries and made reconciliation way faster.

    • Hiroshi Romano ·

      We solved this by adding a mandatory dropdown field in our payment request form that maps directly to those four scenarios. Forces the requester to classify it before it even hits AP, which cuts down on the guesswork during reconciliation.

  • Grace Cohen ·

    The warning about posting to a prepayments asset account without creating the supplier credit is painfully relevant. We had three months of duplicate vendor payments before an invoice-level audit caught it—the GL looked fine but the AP aging was completely wrong because none of those advances were actually linked to supplier records for allocation.

    Reply
    • Andre Andersson ·

      We had a version of this where the reconciliation team and AP team weren't syncing on who owned prepayment allocation. Bank statements looked perfect, but we nearly paid the same invoices twice because nobody was checking the supplier credits before payment runs. Now we require a prepayment review step before closing each month.

    • Ingrid Osei ·

      We caught the same thing during a year-end reconciliation. The frustrating part is that Xero lets you reconcile the transaction perfectly fine without the supplier credit existing, so there's no warning at the point where the mistake happens. Now we require AP to verify the unallocated prepayment shows on the contact record before marking the bank rec as done.

  • Mateo Weber ·

    The reminder to check whether a bill already exists before choosing the transaction type is basic but incredibly easy to skip when you're processing a high volume of payments. We've had instances where AP created a prepayment while someone in procurement had already entered the bill, resulting in a duplicate liability that didn't surface until reconciliation.

    Reply
    • Camila Sharma ·

      We implemented a simple shared status field in our project management tool that AP checks before creating any prepayment. Not elegant, but it stopped the duplicates. The real fix would be forcing prepayments and bills to go through a single intake queue, but we don't have the headcount for that.

    • Nia Kowalski ·

      We had the exact same duplication issue. Now we enforce a rule that only AP can create prepayments or overpayments, and procurement flags expected advances in the PO notes field so AP knows to look for them during reconciliation.

  • Kenji Rossi ·

    The warning about reconciled bank lines not being proof of automatic deduction is worth printing and taping to every AP desk. We discovered three months of duplicate payments to a recurring vendor because the prepayment credits were sitting there reconciled but never actually applied to the bills—our payment run just kept treating each invoice as fully due.

    Reply
    • Sanjay Park ·

      We had a similar problem but in reverse—prepayments were being auto-allocated by someone who didn't realize part of the credit was meant to cover a different PO entirely. Now we require a match confirmation step before any allocation goes through, even if the supplier name matches perfectly.

    • Yuki Becker ·

      We built a quarterly reconciliation routine specifically for this after finding similar issues. The part that helps is pulling a report of all supplier contacts with unallocated credits and cross-checking it against outstanding bills. It's manual but catches exactly what you described before it becomes a multi-month problem.

  • Wei Chowdhury ·

    The point about verifying changed bank details independently before releasing funds hits home. We almost got caught by a spoofed email that looked like it came from a long-standing supplier with 'updated payment instructions.' Now we require voice verification on a known number before updating any bank account in the contact record, which has saved us twice this year.

    Reply
    • Viktor Ivanov ·

      We do the same thing now, plus we flag any contact record change in our approval queue. The scary part is how easily those requests can slip through when you're processing high volumes. One additional layer we added is requiring dual sign-off on any payment over a threshold to a supplier whose bank details changed in the last 90 days.

    • Amina Adeyemi ·

      We do the same thing now, plus we flag any contact record change in our approval queue. The extra friction is worth it because AP fraud attempts have gotten so sophisticated that even careful people can miss the signs when they're busy.

  • Ravi Aziz ·

    The section on foreign currency transactions is critical but feels incomplete. When you create a prepayment in GBP but the supplier actually received EUR (after your bank converted it), how do you handle the inevitable mismatch when the bill arrives in EUR? Do you absorb the FX difference as a realized gain/loss at allocation, or does Xero force you to write off the difference separately?

    Reply
    • Leila Nakamura ·

      This is exactly why you need to create the prepayment in the currency the supplier actually received, not the currency that left your bank account. The article mentions establishing what the supplier received before recording anything—that's the key. If your GBP leaves and EUR arrives, the prepayment should be in EUR at the amount they confirmed receiving. Your FX loss sits in the bank reconciliation as a separate line item or fee, not buried in the supplier record.

    • Jonas Johansson ·

      You record the prepayment in the supplier's billing currency (EUR in your example), not your bank account currency. The FX conversion happens at reconciliation when you match the GBP bank outflow to the EUR prepayment—Xero posts the difference to your unrealized gains/losses account automatically. The bill then allocates cleanly because both it and the prepayment are in EUR.

  • Julia Patel ·

    The cross-border check is critical and rarely discussed in Xero guides. We had a prepayment recorded at invoice amount in GBP, but the supplier only received about 92% after intermediary fees, and when their invoice arrived it was denominated in EUR. Took us three reconciliation cycles to figure out why the allocation kept failing and why we kept showing an outstanding payable.

    Reply
    • Clara Larsson ·

      We handle this by recording the prepayment at the actual amount received by the supplier, not what left our bank. Requires manual calculation and we document it in the reference field, but it prevents exactly that reconciliation nightmare when the invoice arrives. The FX loss and intermediary fees go through a separate line item on the same bank transaction.

    • Malik Muller ·

      We handle this by recording the prepayment at the actual amount received by the supplier, not the amount we debited. The FX spread and intermediary fees get coded to a separate bank charges account at the time of reconciliation. That way when the EUR invoice arrives, the prepayment amount already reflects what they actually got and the allocation matches cleanly.

  • Mia Reyes ·

    The distinction between prepayment and prepaid expense finally makes sense to me. We've been treating annual SaaS vendor invoices as prepayments in Xero when we should have been amortizing them properly. Anybody have a good workflow for the expense-period treatment mentioned at the end of that table?

    Reply
    • Theo Santos ·

      We use the manual journal approach at month-end to shift the unexpired portion into a prepaid expense balance-sheet account, then reverse the corresponding slice each month. It's clunky but at least gives us the P&L timing right. Would love to hear if anyone has automated this with tracking categories or similar.

    • Fatima Petrov ·

      We use the manual journal approach at month-end to shift the unexpired portion into a prepaid expense account, then reverse it monthly over the contract period. It's separate from the supplier prepayment workflow—the prepayment clears when the bill hits, but the expense amortization is a different set of entries entirely.

  • Priya Moreau ·

    We ran into exactly this problem last quarter with a Chinese manufacturer. Created the prepayment in USD, they received CNY after conversion fees, then their invoice came through in CNY at a different rate. Xero wouldn't auto-match and AP just forced it through a write-off account. The cross-border currency point here is critical but I wish the article went deeper on multi-currency allocation mechanics.

    Reply
    • Daniel Dubois ·

      That currency mismatch scenario is exactly why the article emphasizes establishing what the supplier actually received. The FX gain/loss should go through the proper revaluation account rather than a write-off, otherwise your treasury reconciliation will never balance properly. Did you end up creating the prepayment in CNY from the start after that?

    • Ethan Lindqvist ·

      This is a good example of why the supplier-received amount matters so much. If the prepayment had been created in CNY from the start (even if your bank sent USD), the later allocation would have been cleaner. The write-off route just hides the FX tracking problem until audit asks where those variances came from.

  • Sara Tanaka ·

    "A reconciled bank line is not proof that the advance will be deducted from the next payment run" - learned this the hard way when we doubled up on a supplier payment because the prepayment credit wasn't linked to the contact properly. Now we have a checklist step specifically to verify the supplier credit balance before releasing any payment batch.

    Reply
    • Sofia Diaz ·

      Same issue here. The part that caught us was when the prepayment was created in USD but the contact had separate AUD bills flowing through at the same time. Xero won't auto-match across currencies, so the credit just sat there while AP kept scheduling full payments. Now we flag multi-currency suppliers during the advance approval stage.

    • Dmitri Haddad ·

      We added the same thing after a similar incident. The workflow check that really helped us was requiring a screenshot of the supplier prepayment balance before finalizing any payment batch over $10k. Catches mismatches before the wire goes out.

Run your entire money cycle on one ledger

Global payouts, AP/AR automation, and AI agents with their own wallets and spend limits.

Get started