View all app connections
View all AI automations
View all chatbots
View all lead automations
View all booking automations
View all payment automations
View all workflows
View all Shopify
View all WooCommerce
View all HubSpot
View all Salesforce
View all Stripe
View all Google Sheets
View all Slack
View all dental practice
View all law firm
View all medical practice
View all real estate
View all restaurant and food
View all home services
View all construction
See all: get more leads
See all: get paid faster
See all: save admin time
See all: support customers
See all: book more appointments
See all: sell more online
See all: hire and onboard
View all AI automations
View all AI automations
View all AI automations
View all AI automations
View all AI automations
View all AI automations
View all AI automations

BoldBellowsEvery payout weighed, not waved through

Stop letting Xero call an eBay payout straight bank deposit revenue

A shallow connector calls the payout bank deposit revenue and moves on, which is exactly what breaks once a payout spans more than one currency or a refund lands in a payout weeks after the original sale. This build routes every settled payout through a dedicated clearing account, posting sales, fees, VAT, refunds and currency differences as their own coded entries — and holds a genuinely unreconcilable payout in an owned variance instead of forcing a number into the books.

View Pricing

From $745, paid once.
No monthly connector fee.

  • Every payout clears through one dedicated account
  • A cross-currency payout waits for a bookkeeper
  • A first clean payout is typically live inside two weeks
eBay to Xero automation by BoldBellows: a precision balance scale weighing eBay payout totals against Xero clearing-account postings, with fees, refunds and currency differences as calibrated weights
Payout weighed Cleared and posted LEDGER · THIS WEEK Payouts cleared9 Held for variance review1 Unbalanced entries0 Every entry traces to one payout

What keeps the ledger trustworthy

  • Anchored to real IDseBay payout and transaction IDs, mapped to Xero references
  • Coded the way Xero expectsa clearing account, not a bare bank deposit
  • Idempotency keys on every writea retry can never post the same entry twice
  • Variances get an ownera cross-currency payout names its own repair decision
  • A price you agree to onceproven against test scenarios before it's called done

01The straight-deposit trap

Revenue isn't the whole story of a payout

The moment a payout crosses currencies or carries a delayed refund, calling the whole thing revenue stops being a shortcut and starts being a liability at audit time. Every hour a bookkeeper spends untangling one deposit is an hour that shouldn't have been necessary in the first place.

"Xero showed a payout as pure revenue, but part of it was a currency conversion."

Without a clearing account, the currency difference had nowhere honest to land.

"A refund from last month's sale settled in this month's payout and threw off the close."

The sync had no way to connect a delayed refund back to its original sale.

"A retried sync posted the same VAT line into Xero twice."

Without an idempotency key, the retry just wrote the entry again.

A payout posted straight to revenue isn't reconciled, it's a guess waiting to be caught at audit. The clearing account is what actually proves the numbers match.

Same payouts, same eBay account. The difference is whether Xero receives a balanced set of entries, or one bank line that still needs explaining months later.

Before

Xero · straight bank deposit Composition: called revenue outright Retries: can post twice
  • A currency difference has nowhere honest to land
  • A delayed refund can throw off the wrong month
  • Without a replay check, a VAT line can end up posted twice

After

Payout PO-006579 Sales $4,050 · Fees -$310 · FX -$22 ✓ Routed through a dedicated clearing account ✓ Claimed by payout and transaction IDs ○ A cross-currency payout is held for review
  • Every currency difference lands somewhere explainable
  • A delayed refund reconciles to its own sale
  • An idempotency key stops a retry from doubling up

02How it works

The route a payout takes before Xero ever sees it

Picture a record on a turntable, passing three fixed stations in order: one checks it against the settlement rules, the next locks its identity to a payout and transaction pairing, the third builds out the clearing-account entries. A verification arm at the end either stamps the result or lifts it off to a repair queue.

A cross-currency payout re-enters here STAGE 1Payout read Checked against thesettlement rules STAGE 2Identity claimed Payout and transactionIDs matched STAGE 3Entries posted Split by sales,fees, VAT, refunds STAGE 4Result verified Stamped orsent to repair STAGE 1Payout read Against settlement rules STAGE 2Identity claimed Payout and txn matched STAGE 3Entries posted Split into their lines STAGE 4Result verified Stamped or repaired A cross-currency payout re-enters here
Every payout runs the full rotation once. Nothing gets a second pass through the same stage without a reason.

Why a payout has to route through a clearing account

  • An eBay notification is a nudge to go look, not the finished business record itself. If one arrives short on detail, the build pulls the payout fresh from the source rather than filling gaps with assumption.
  • eBay's Finances API keeps a payout figure and the amount actually deposited as separate numbers. A clearing account is the only place both of those figures can sit side by side without one having to disguise itself as the other.
  • Xero accepts an idempotency key precisely so a client unsure whether a request succeeded can retry safely. This build uses that key on every write, which is what keeps a retry from ever doubling an entry.

03Package by package

How the reconciliation build grows from Entry to Attestation

Entry gets a settled payout routed through the clearing account the day it lands. Add Variance, and a payout that spans currencies or carries a delayed refund stops and waits instead of posting wrong. Attestation goes further still, running its own recurring sweep so nothing sits unreconciled just because the live feed happened to miss it.

Settlement Reconciliation EntrySettlement Reconciliation VarianceSettlement Reconciliation Attestation

Ledger log PayoutCurrencySplitStatus PO-6501USD4 linesPosted PO-6506USD3 linesPosted PO-6509GBP4 linesPosted PO-6579USD+EURunclearHeld PO-6579Two currenciesReviewingVariance Cross-currency payout → held, not forced eBay ReadClaimedPostedVerified Ledger log PayoutStatus PO-6501Posted PO-6509Posted PO-6579Variance PO-6579Held Cross-currency → held for review eBay Read+ 3 more views

Settled-payout event filter Settlement Reconciliation Entry

Screens out anything that isn't genuinely settled yet, keeping a note of the reason each payout was let through.

Payout-transaction identity claim Settlement Reconciliation Entry

Pairs a posted entry with its source so tightly that the two can never quietly drift apart.

Cross-currency branching Settlement Reconciliation Variance

Catches a payout spanning currencies and holds it instead of forcing a single-currency guess.

Owned exception register Settlement Reconciliation Variance

Gives every held variance a specific bookkeeper accountable for closing it out.

Scheduled reconciliation Settlement Reconciliation Attestation

Checks in on eBay's records at set intervals of its own, independent of whether a sync run happened to fire.

Contract drift register Settlement Reconciliation Attestation

Notices the moment eBay or Xero redefines a field, before an entry quietly comes out wrong.

Mapping and decision notes Settlement Reconciliation Variance

Spells out the reasoning behind every account and code choice for future edits.

Thirty-day launch review Settlement Reconciliation Attestation

The ledger stays under close watch through your first full period close before sign-off.

PROGRAM HEALTH Payouts reconciled, this month Unbalanced entries Open count 0
Settlement Reconciliation Attestation adds this view — payouts reconciled climbing steadily while unbalanced entries hold flat at zero.

04Who it's for

Built for teams whose accounts have to genuinely balance

A marketplace ops lead who's tired of walking the accountant through the same payout figure monthly, a seller whose numbers rarely survive a close unchallenged, a bookkeeper who'd sooner start from coded entries than a mystery deposit, and an admin who wants a cross-currency case routed straight to one inbox.

Marketplace operations lead

Needs a payout's composition proven on demand, not reconstructed from memory each time finance asks.

Seller team

Every close means re-explaining the same discrepancy between what the bank shows and what actually happened.

Bookkeeper

Shouldn't have to work backward from a single figure to figure out what actually made it up.

Systems administrator

Wants a cross-currency payout assigned by name the instant it's flagged, not surfacing at month end.

05Compare

The gap between a bank feed and a real reconciliation

Anyone can wire a bank feed to a payout total in an afternoon. Proving that total is actually made of sales, fees, VAT, refunds and a currency conversion — and catching the one payout that genuinely spans two currencies — is what separates a feed from a reconciliation.

Comparing an unfiltered sync, a single Xero bank rule, and the BoldBellows settlement reconciliation build
The real differenceUnfiltered two-way syncA single Xero bank ruleBoldBellows build
What starts a writeEvery deposit, no filter appliedOnly what the rule's pattern happens to catchYesOne thing only: a genuinely settled payout
How it's matchedWhichever bank line looks closest in amountText in the description the rule was told to look forYesThe payout and transaction IDs, tied to Xero references
What the books getA single number, filed as revenueWhatever category the amount roughly suggestsYesSeparate, coded lines for sales, fees, VAT and refunds
When a payout spans currenciesPasses through unexaminedA scenario the rule's logic was never designed forYesCaught and set aside before it posts incorrectly

The cross-currency trap

Two currencies settle into a single deposit at once. Rather than pick an exchange rate and guess, cross-currency branching sets the payout aside for a bookkeeper to confirm.

The delayed-refund trap

A refund from one sale settles in a later, unrelated payout. The build traces it back to the original sale it belongs to, instead of letting it sit as an unexplained line in whichever payout it happened to arrive in.

PricingClear, one-off packages

Give Xero a payout it can actually reconcile

Each step up — Entry, then Variance, then Attestation — teaches the ledger to handle a stranger payout on its own. Make your selections below and the total on the right follows along live. Settlement Reconciliation Entry opens at $745.

View Pricing
Pricing

Build your eBay to Xero price

Pick a package, answer three short questions about event scope, identity and failure policy, and your price and turnaround move as you choose.


Choose your packageRequired

The three packages differ by how much settlement branching and self-checking the ledger carries.

One eBay account and one Xero organisation, routing a settled payout through a clearing account from day one.

  • One authorized eBay account, one Xero target
  • Settled-payout event filter
  • Payout and transaction identity claim
  • Duplicate-transaction replay defense
  • Ordinary and duplicate-path acceptance tests
  • Focused administrator handoff

Handles a payout spanning currencies or a refund settling in a later payout, with an owned exception state.

  • Everything in Settlement Reconciliation Entry
  • Two settlement-specific business-rule branches
  • One historical reconciliation pass
  • Owned exception register
  • Mapping and decision notes for future edits
  • Repair-state routing for a cross-currency payout

The ledger stays under a recurring check-and-alert cycle, even as your payout volume climbs.

  • Everything in Settlement Reconciliation Variance
  • Scheduled eBay-state reconciliation
  • Contract drift detection
  • Operational evidence register
  • Volume and timeout protection
  • Thirty-day launch review

Several eBay accounts, several legal entities, regulated retention, custom extensions or unsupported add-ons. Tell us the real scope and we will price it for your build.

Which payouts should actually post through the clearing account?Required

Lifecycle with reconciliation adds a sweep that catches a payout the live feed missed.

How should a Xero entry trace back to its eBay payout?Required

Conflict quarantine adds a queue for a match the rule can't confidently resolve on its own.

What happens when a Xero post fails?Required

Creating an operator case takes more setup than a stop, but nothing silently falls through.

How soon do you need it live?Required

Standard follows the schedule your other choices set. Pay to move up the queue and go live sooner.

Optional extrasOptional

Each one begins switched off. Turn on what your rollout needs, watch the total, switch it back off.

06The process

Rehearsing the reconciliation before a real payout runs through it

A first real payout is usually posted and ready for your review inside a couple of weeks once Settlement Reconciliation Entry is underway, needing nothing more than one eBay account and one Xero organisation to start. Variance takes longer to sign off, since proving it works means manufacturing a genuinely cross-currency payout and repeating the same test until the branch behaves identically every time, not once by luck. With Attestation, the extra time goes somewhere different altogether — we deliberately let a mapped account drift and then watch whether the scheduled cycle, not a person, is what catches it. If a cross-border promotion is coming up, say so early and we'll build that currency mix into the rehearsal rather than treating it as an edge case discovered live.

Your settlement worksheet Which Xero accounts each posting line maps to Which organisation the entries should post into Who owns a currency variance when it opens How far back a historical backfill should reach Built from how your books actually close Build summary Test set: 14 payouts run Payouts posted 14 Currency variances caught 2 Unbalanced entries 0 Ready for handoff
  1. Walk your bookkeeper through the mapping

    Every account this build could ever post to gets picked in that session, line by line, with nothing left ambiguous.

  2. Design the clearing entries and routing

    You approve exactly how a payout splits into entries and what a currency variance should trigger.

  3. Build against your real organisation

    The event boundary, the payout-and-transaction pairing and the idempotency handling stop being a design on paper and start running against your live Xero setup.

  4. Deliberately break it first

    A test payout is engineered to span two currencies at once, purely to watch the branch catch it before a real one ever gets the chance.

  5. Hand off on a working payout, not a promise

    Once a genuine payout has cleared and your bookkeeper has signed off on how it split, the build is yours to run without us.

Three things to have ready

  • Sign-off from whoever administers the eBay side of the account.
  • Adviser-level access to the target Xero organisation.
  • A recent payout report, ideally one that includes more than one currency.

07Security and ownership

A clearing entry is as far as this build reaches.

What comes in is payout and transaction detail from eBay; what goes out is a clearing entry into the one Xero organisation you name. Whatever you already run for bank reconciliation, and any account you didn't sign off on, simply isn't part of this build's world.

Scoped strictly to settlement posting

There are exactly two things this build does: read payout detail from eBay, and post the resulting entries into Xero. Invoicing, contacts and anything else in your organisation stay completely off limits.

A signed-off account map, nothing beyond it

Every account this build could ever touch was chosen with your bookkeeper's sign-off before launch, and that list doesn't grow on its own afterward.

Credentials stay off every posted entry

Every key that authorizes a write is vaulted well outside anything a viewer of the books would ever open — no entry, comment or attachment carries one.

An idempotency key travels with every write

Each request carries its own idempotency key, so Xero itself refuses a duplicate before the build even needs to check.

An audit trail without the sensitive detail

Tracing a posting back to its source only ever requires the payout ID, what it turned into and when — never a copy of the underlying order or card data.

The whole build transfers, not just access to it

Every mapping decision, every exception rule and a full runbook documenting both become yours outright at close — there's nothing about running this that still needs us in the loop.

08In their words

What BoldBellows clients say

Verified reviews from teams who use BoldBellows automations every day, from marketplace operations to sales and customer follow-up, for this eBay to Xero route.

AI Translation & Localisation

When we expanded abroad we needed fast, accurate translations. BoldBellows built an AI translation system that turns our content into several languages instantly.

The translations read naturally and suit each culture. We now serve customers in five new countries without hiring translators. BoldBellows helped us go global.

Kenji NakamuraVerifiedOsaka, Japan

AI Chatbot & Customer Support

BoldBellows built an AI support chatbot for our online boutique, and it has changed how we run the business. We used to have two full-time staff answering the same questions all day. Now the AI handles order tracking, product recommendations and even refund requests on its own.

What surprised me most is how natural it sounds. Customers compliment the ‘agent’ without realizing it’s AI. Our support workload dropped by 75% and customer satisfaction went up dramatically.

Maria GonzálezVerifiedMadrid, Spain

AI Customer Journey Automation

We wanted a smoother path from first contact to purchase. BoldBellows built an AI system that guides each customer there automatically.

It sends personalized messages, recommends products and follows up at just the right moment. Customer retention has improved dramatically.

Nadia HassanVerifiedCairo, Egypt

AI Workflow Automation for Agencies

Running a digital agency with many clients was overwhelming. BoldBellows built one automation dashboard that tracks tasks, sends updates and creates client reports automatically.

Clients love the transparency and we love the time we get back. Productivity is up, and project delays have dropped to almost zero.

Samuel BoatengVerifiedAccra, Ghana

AI Voice Assistant

BoldBellows built a custom AI voice assistant for our customer hotline. It answers questions, books appointments and handles simple requests.

Customers love how fast it is, and our call-centre workload dropped dramatically. One of the smartest upgrades we’ve made.

Hannah JohnsonVerifiedChicago, USA

AI Video & Voice Automation

We publish product videos every week, and BoldBellows introduced us to AI video automation. The system writes the script, voices it and produces the finished video in minutes.

The quality is remarkable: professional voiceovers, clean visuals and smooth editing. Production time went from three days to under 30 minutes, and we scaled our video marketing without adding cost.

Lucas SteinerVerifiedMunich, Germany

AI Accounting & Invoice Automation

BoldBellows automated our whole invoicing process: creating invoices, sending reminders and tracking payments.

Late payments dropped sharply, and our accounting team finally has time for strategy instead of repetitive admin. Worth every penny.

Ravi PatelVerifiedNew Delhi, India

AI Social Comment & DM Automation

We get thousands of comments and messages every week. BoldBellows built an AI system that replies instantly, filters spam and surfaces the important ones.

Engagement is up and our page looks active around the clock. It’s like having a full social media team that never stops.

Sofia DimitrovVerifiedSofia, Bulgaria

AI Content & Social Media Automation

Our marketing agency couldn’t keep up with content. BoldBellows set up an AI content engine that writes blog posts and captions and even designs our social media creatives.

It spots trends and suggests topics for us, so we stay ahead of competitors. We now produce three times the content with the same team, and engagement has soared. They didn’t just automate our workflow, they lifted our whole brand.

Daniel BrooksVerifiedToronto, Canada

09FAQ

What tends to come up during setup

Still unsure? We reply in plain English.

Our accountant set up a bank rule for this years ago — isn't that enough?

A bank rule only sees what the feed shows it, which is a single flattened number — it can't recover the sales, fees, VAT and refunds that number was actually made of, and it has no concept of a payout spanning more than one currency. Getting that detail means reading the payout where it's still intact, on eBay's side.

Is there any risk of it writing somewhere in our chart of accounts we haven't signed off on?

None. The account list this build is allowed to touch is fixed during setup and reviewed by your bookkeeper — writing to anything outside it isn't a permission the build has to begin with.

What about payouts that settled before this was set up?

Name the window you want covered and the historical settlement backfill applies the same reconciliation logic retroactively across it, keeping its output on its own dedicated track, well clear of anything already posted in your live books.

Is what we pay for Xero itself wrapped into this number somewhere?

No — separate billing, always. The price here pays for the build itself, once. Your Xero licence fee and whatever eBay deducts as seller fees carry on exactly as before, untouched by this arrangement.

What's the plan if eBay or Xero quietly changes a field this relies on?

The build watches its own dependencies through a standing drift check, so a broken assumption gets flagged automatically rather than showing up first as an odd number in the books. A handoff document also lists exactly what the build relies on across both platforms, in case you ever need to investigate yourself.

If the connection drops mid-sync, could a VAT line end up duplicated?

Two separate safeguards, really. Xero itself rejects a duplicate outright when it sees a request repeat its idempotency key, and before that ever comes up, the build has already looked up the payout's identity and found the existing entry to update instead. Related searches this service covers include sync ebay orders to xero, ebay xero integration and ebay xero accounting sync.

Next stepLet the numbers explain themselves for once

Let Xero see what a payout was really made of

Share one payout your bookkeeper had to piece together manually, along with the Xero organisation you'd want it posted into, and we can turn that alone into a fixed number. Settlement Reconciliation Entry starts at $745.

  • From $745, paid once
  • Sales, fees, VAT and refunds all stay separately coded
  • A payout spanning currencies waits for a real answer
  • The whole build transfers, not just access to it