HELLO PEOPLE is an Australian Reckon integration company. We connect Reckon Accounts, Reckon Accounts Hosted and Reckon One to the systems around them, so supplier bills, sales and payments go in, and reports come out, without anybody retyping them.
Reckon has fewer built-in connection points than the cloud packages, so the first question is which Reckon you run and where the file lives. Then a fixed-price scope from a Perth team.
Built here. Your data stays here.
The problem
Reckon Accounts has served Australian businesses for years, and your bookkeeper knows it well. But it has fewer built-in connection points than Xero or MYOB, so the systems around it tend to hand over their data on paper, in email attachments, or in a spreadsheet somebody retypes.
What you already run
Chosen for the Reckon you run: the Reckon One API (its published connection point for other software) in the cloud, or file and database access for Reckon Accounts. Every record is checked before it posts, and anything unusual waits for a person.
Get a fixed-price scopeWhat changes
Five pieces of custom Reckon integration work, starting with the question that decides the rest: which Reckon you run.
Reckon is several products under one name. Reckon Accounts and Reckon Accounts Hosted come from the desktop line. Hosted runs the same software on a server somebody else looks after, reached through Citrix or a remote desktop session. Reckon One is the cloud product, with a different API entirely.
So the same request, such as getting invoices in from another system, is a different build on each. We settle which one you run before anything else.
On Reckon, the practical question is usually how data gets in at all, not how it posts once it is there. Supplier invoices are captured, checked, coded and posted, and sales from another system arrive as invoices rather than being keyed from a printout.
Most of this is rules rather than artificial intelligence: if this arrives, check that, then post it there. Rules are cheaper, faster and easy to audit.
In Reckon, payments are recorded and then reconciled against the bank statement. When a payment provider pays out in lumps, we split each lump back into the payments inside it, so the reconciliation is a check rather than a puzzle.
Each payment provider settles differently, which is why Stripe, Square, Tyro and others each have their own Reckon page.
Management reports that combine Reckon with job, sales or stock systems. Customer portals where clients see their invoices and statements without phoning the office.
How the figures are read depends on where the file lives and who hosts it. On Reckon One, a portal can read live through the API.
Many Reckon businesses are thinking about Xero or MYOB. If that move is coming, we build so the rules and checks can be pointed at the new system, rather than thrown away with Reckon.
If it is coming soon, we may suggest doing the move first. Building twice is the expensive option.
The Reckon edition and where the file lives decide the route. The route decides the price, and the price is fixed.
Reckon Accounts, Hosted or Reckon One, and who hosts the file. These two answers decide the route and most of the price.
Once the route is known, the scope is written and the price is fixed. If the scope changes, we re-quote rather than let it drift.
If a move to Xero or MYOB is already planned, we will tell you whether to integrate now or after. Building twice costs more.
Why HELLO PEOPLE
Connector tools are built for cloud software. Reckon One can suit them. Reckon Accounts on a desktop or a hosted server usually needs a route built for where the file actually lives.
| Concern | HELLO PEOPLE | Zapier / Make | n8n / self-hosted | MuleSoft / Boomi |
|---|---|---|---|---|
| Reckon Accounts on a desktop or hosted server | A route chosen for where the file lives | Usually needs a cloud connection | You work out file or database access | Custom build |
| Reckon One in the cloud | Built on the Reckon One API | Depends on the connector | You build against the API | Configurable, needs specialists |
| Checks before anything posts | Every record checked, exceptions held | Copies what it is given | You write the checks | Configurable, needs specialists |
| A planned move off Reckon | Rules built to be repointed | Rebuilt from scratch | Rebuilt from scratch | New connector project |
| 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, beginning with which Reckon you run, because the same request is a different build on each edition.
Reckon Accounts, Reckon Accounts Hosted, Reckon One or Reckon Elite. We confirm the edition and where the file lives.
The Reckon One API, or file and database access for the desktop line. The route is written into the scope, with its limits stated.
What arrives, what is checked, where it posts, and what waits for a person. Agreed with your bookkeeper as well as you.
Built and tested against a copy of your company file first. Your live Reckon is not written to until you have seen it behave.
Switched on from an agreed date, with the first weeks checked against what the bookkeeper would have entered.
Monthly support covers changes. If you later move to Xero or MYOB, the rules come with you.
Meet the person
Your Reckon Integration, handled by the founder from start to end.
Hello, I am Kasun, the founder of HELLO PEOPLE. My first career was in accounting, so I connect systems the way an accountant would: every record lands in the right place, and both sides agree.
I have run HELLO PEOPLE from Perth since 2007. Over 100 projects sit behind it, from accounting migrations and system integrations to custom software for small and medium businesses.
I have a solid accounting and IT background, with over 20 years of business experience covering every process a business runs on: sales, marketing, service delivery, inventory and warehousing, and compliance, across many industries. I hold accounting and IT professional qualifications and an MBA in Oil and Gas, and I am currently reading for a PhD in AI at Curtin University in Western Australia, focused on retrieval-augmented generation (RAG).
Small and boutique. The person who scopes your integration is the person who builds it, and the same person watches the first live syncs.
No ticket queue and no account manager in between. You hear back within one business day, usually sooner.
The integration is the start, not the end. When you need the next system, integration or report, you call the same person, who already knows your business.
Today
After
Scoped and quoted before you commit. Tested on a copy of your file, and you own the code.
Get a fixed-price scopeOn Reckon One, yes. It is the cloud product and has its own API, the published connection point other software uses. Reckon Accounts and Reckon Accounts Hosted come from the desktop line, and integrating with them usually means working with the company file or its database rather than a cloud API. Which one you run decides the build.
Which Reckon product you run, where the company file lives, and who hosts it. A Reckon integration consultant cannot scope anything sensible until those three are known, because each one points to a different route.
It changes how we reach the data. Hosted runs the same software on a server looked after by somebody else, reached through Citrix or a remote desktop session. What access that provider allows is part of the scope.
You need both. Your bookkeeper knows how the books should look. A Reckon integration company builds the thing that gets them there without typing. HELLO PEOPLE works with your bookkeeper, not around them.
Supplier bills captured, coded and posted, and payments from card providers matched before reconciliation. Both remove the most typing for the least risk.
A fixed price against a written scope, set once we know the product, where the file lives, and what has to move. We scope it before quoting and re-quote if the scope changes.
Sometimes. If the move is years away, an integration pays for itself before then, and the rules can be repointed at the new system. If it is months away, it is usually better to move first. See our Reckon to Xero and Reckon to MYOB pages.
Sending your details…
You can stay on this page while we send it.
The Reckon product and edition, where the file lives, and what gets typed in by hand today. We will come back with the route that fits 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