> For the complete documentation index, see [llms.txt](https://help.alternativepayments.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.alternativepayments.io/integrations/accounting-integration-guides/one-time-payments-in-bank-deposits.md).

# One-Time Payments in Bank Deposits (Xero, Sage Intacct, QuickBooks Desktop and More)

A **one-time payment** is a payment a partner collects that is **not attached to an invoice**, such as a payment link or a POS terminal sale.

When Alternative Payments creates a bank deposit for a payout, one-time payments in that payout are added to the deposit as their own lines. The deposit total then matches the amount that landed in the bank.

This page covers these accounting platforms:

* Xero
* Sage Intacct
* QuickBooks Desktop
* Microsoft Dynamics 365 Business Central
* Oracle NetSuite
* Zoho Books
* FreshBooks

For QuickBooks Online, see [One-Time Payments in QuickBooks Online Deposits](https://help.alternativepayments.io/integrations/accounting-integration-guides/quickbooks-desktop/one-time-payments-in-quickbooks-online-deposits.md).

***

#### What a partner sees on the deposit

Each one-time payment adds a line to the payout's bank deposit:

* A **positive line** for the full payment amount, booked to the One-Time Payments account. It is labeled **One Time Payment**, or **POS Payment** for a POS terminal sale.
* A **negative line** for the fee on that payment, booked to the fees account, labeled the same way with **Fee** at the end.

One-time payments are never recorded as invoice payments, because there is no invoice behind them.

If a payout is posted as more than one deposit, each one-time payment line appears on only one of those deposits. The payout total across all of its deposits still matches the bank.

***

#### The One-Time Payments account

One-time payments are revenue, so they are booked to an **income account**.

**By default we create an income account called `Alternative Payments OTP`** the first time a partner receives a payout with a one-time payment. It is created once and reused after that.

**A partner can choose their own account instead.** On the [Integrations](https://app.alternativepayments.io/dashboard/integrations) page, the accounting integration's account settings include **Select account for one-time payments**. Only income accounts are offered. If the partner selects an account, we book to it and do not create ours.

***

#### Customer on the line

When the payer is a customer that is already synced to the partner's accounting platform, we attach that customer to the one-time payment line and its fee line.

On most platforms **a blank customer is normal**. It happens when:

* the payment was a guest checkout, which is not linked to a customer
* the payer exists in Alternative Payments but has not been synced to the accounting platform
* the payer couldn't be identified

Xero is the exception. See the next section.

***

#### Platform limits

{% tabs %}
{% tab title="Xero" %}
**Xero allows exactly one customer on each bank deposit.**

When a payout includes payments from more than one customer, we create **one Xero deposit per customer**. Each deposit's memo is numbered, for example `(1/3)`, `(2/3)`, `(3/3)`. Each one-time payment goes on the deposit for its own customer. A one-time payment from a customer with no invoices in that payout gets a deposit of its own.

**Every one-time payment in a Xero payout must have a customer.** If a one-time payment has no customer that is synced to Xero, Xero cannot accept the deposit, and the deposit for that payout fails. This most often happens with guest checkout payments.

**What the partner should do**

* To prevent it, make sure the payer is a customer synced to Xero before the payout is processed. For payment links, ask the payer to log in before paying, so the payment is tied to their customer record.
* If a deposit has already failed, record that payout's deposit by hand in Xero. Use the payout breakdown in the Alternative Payments dashboard for the amounts.
  {% endtab %}

{% tab title="Sage Intacct" %}
**Sage Intacct requires at least one invoice payment on every bank deposit.**

A one-time payment line does not count as an invoice payment. A payout that has invoice payments and one-time payments posts normally. A payout made up **only** of one-time payments cannot be posted to Sage Intacct, and the deposit for that payout fails.

This limit applies to Sage Intacct connections on the current version of the integration. Contact Support if you are not sure which version you are on.

**What the partner should do**

* Record that payout's deposit by hand in Sage Intacct. Use the payout breakdown in the Alternative Payments dashboard for the amounts.
* Retrying the same payout does not help. Sage Intacct rejects the same deposit every time.
  {% endtab %}

{% tab title="Other platforms" %}
QuickBooks Desktop, Microsoft Dynamics 365 Business Central, Oracle NetSuite, Zoho Books and FreshBooks accept one-time payment lines with or without a customer. A payout made up only of one-time payments posts as a normal deposit.
{% endtab %}
{% endtabs %}

***

#### Things worth pointing out

* Existing deposits are not changed. If a payer is synced as a customer after a payout was processed, that deposit keeps a blank customer.
* To see the fee for one specific payment, use the payout breakdown in the Alternative Payments dashboard.
* One-time payments always appear in the [Transactions](https://app.alternativepayments.io/dashboard/all-transactions) section of the Partner Dashboard, whether or not a deposit is created.

**Love our platform?** Check out our [Referral Program page](https://www.alternativepayments.io/referral-partners/)!


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.alternativepayments.io/integrations/accounting-integration-guides/one-time-payments-in-bank-deposits.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
