HELLO PEOPLE is an Australian Stripe integration company. We connect Stripe to your accounting, online store, booking system or customer portal, so each payout is matched to the invoices it paid and the fees are booked where your accountant expects them.
The Stripe side is the easy half. The accounting side decides the job, so we look at how your books are set up before quoting a fixed price.
Built here. Your data stays here.
Each accounting system records a Stripe payout differently, so each has its own page. Click yours to see how it works there.
The problem
Every day or two, Stripe sends one amount to your bank. It covers dozens of customer payments, and the fees have already come out. Somebody in the office then works backwards from that bank line to the invoices behind it, and whatever will not tie out is left for next week.
Where payments start
Opens each payout, posts every payment against the invoice it paid, books the fees as an expense, records refunds and disputes on the day they happened, and lists anything it cannot match for a person.
Get a straight answerWhat changes
Four pieces of custom Stripe integration. Payout matching is where almost everyone starts.
The money Stripe sends your bank is a bundle: many customer payments, less the processing fees, arriving as one amount. We open each bundle and post every payment against the invoice it settled.
The fees are booked as an expense in their own right, so sales are reported at the full amount customers paid.
A refund, a customer dispute and a payment that fails after it looked successful each reach your books differently. Each one is posted to the right account on the date it happened.
A payment already recorded that later fails is reversed with a clear trail. It is never deleted, because a deleted record is the one your accountant asks about.
If customers pay you monthly through Stripe, each renewal becomes a sale in accounting against the right customer and the right income account.
Failed renewals are listed for follow up rather than surfacing at year end as a gap nobody can explain.
Taking a payment is only half the job. When a customer pays a booking, a deposit or an invoice through a portal on your website, the payment is posted back against the right record so the booking, the job and the ledger all agree.
Where Stripe payments are split between parties through Stripe Connect, each transfer is recorded as its own movement rather than lumped in with sales.
The price depends on how you take payments and how your books are set up. Both are clear after one conversation, and the quote is fixed.
How your accounts are set up decides most of the work. We look at that before quoting, and it costs nothing to ask.
Where an existing connector already does what your accounts need, we tell you. We only quote a custom build when it genuinely will not.
One price covers the build, testing on a real month of payouts, and go-live. Support plans cover changes on either side.
Why HELLO PEOPLE
Sometimes, and we will say so when it will. Where it falls short is usually the same few places: fees, refunds, disputes and payments with no invoice.
| Concern | HELLO PEOPLE | Zapier / Make | n8n / self-hosted | MuleSoft / Boomi |
|---|---|---|---|---|
| A payout covering many payments | Split back to each invoice | Often posted as one amount | You write the matching | Configurable, needs specialists |
| Processing fees | Booked as their own expense | Depends on the connector | You write the rule | Configurable, needs specialists |
| Refunds and disputes | Posted on the date they happened | Often left for month end | You handle each case | Configured per case |
| Payments with no invoice | Held and listed for a person | Posted somewhere or skipped | You decide in code | Configurable, needs specialists |
| Ongoing cost | One-off build plus optional support | Charged per task, every month | Hosting and upkeep are yours | Enterprise licence |
| Who you talk to | The person who built it | Chat support | Community forum | Enterprise support desk |
An Australian business running on five disconnected platforms, accounting, CRM, field-service, eCommerce, and reporting, was spending hours each day re-keying the same data. We connected the systems through their APIs so contacts, invoices, orders and payments flow automatically. Errors are visible and recoverable.
Read the full case studySix steps. Before go-live, a past month of your Stripe payouts is replayed and compared with what was recorded by hand.
Online checkout, invoices, subscriptions, a booking system or a portal. Each one leaves a different trail in Stripe.
Which accounts sales, fees and refunds should land in, and how your accountant wants to see them. This decides the design.
The Stripe side is the straightforward half. Most of the build is the rules that match payouts to invoices and handle what does not match.
A past month of your payouts is run through and compared with what your bookkeeper recorded by hand.
The integration starts from an agreed payout, so nothing is posted twice and nothing is missed.
Stripe and your accounting system both change over time. Support plans keep the matching right as they do.
Today
After
Scoped and quoted before you commit. You own the code and the credentials.
Get a straight answerNot the Stripe side. The Stripe API, the published connection point other software uses, is the straightforward half. The hard part is the accounting: a payout arrives as one amount, already less fees, covering many payments. A build that records the payout as income loses both the fees and the detail of which invoices were paid.
How your books are set up, and whether an existing connector already posts Stripe the way your accountant needs. A Stripe integration consultant should tell you when it does. If it does not, the scope starts from how payouts, fees and refunds should land.
You can hire either. What matters is that whoever builds it understands the accounting as well as the code, tests it on a real month of payouts, and is still around to support it. HELLO PEOPLE is a Stripe integration company that does all three, with fixed prices.
Access to Stripe with the right permissions, access to your accounting system, and an hour with whoever reconciles Stripe today. Their spreadsheet is usually the best specification there is.
It is quoted as a fixed price against a written scope, once we have seen how you take payments and how your books are set up. Payout matching for one accounting system is a smaller job than subscriptions, disputes and a customer portal together.
Yes. Each accounting system records payments differently, so each pairing has its own page. Start from the list in the catalogue above, or see every payment pairing.
It is held and listed for a person. It is never posted to a guess, and never left out of the payout total.
Sending your details…
You can stay on this page while we send it.
Where Stripe payments start, which accounting system they need to reach, and who reconciles them today. We will come back with what it takes and a fixed price.
Prefer a quick chat? Call 0425 531 127. We answer the phone in Perth.
Thanks for reaching out. We will get back to you within one business day.
See what else we do