Reckon Customer Portal
without leaving the system you already trust.
Invoices outstanding and paid, statements on demand and payment history too, on a login you own. Your customers get the self-service the bigger firms offer without you having to leave Reckon to give it to them.
How the portal reaches your data depends on where the file lives, so that is the first thing we settle. Fixed-price scope, an Australian team, support after launch.
Covers Reckon Accounts, Reckon Accounts Hosted and Reckon One.
- No per-user fee Portal logins do not cost Reckon seats
- 18+ yrs Building business software
- Fixed Price scopes, no surprises
- You own it Code, docs and credentials
Built here. Your data stays here.
- No offshore development. Everything is written by our own team in Australia. Nothing is subcontracted overseas.
- Your data stays onshore. Hosted in Australia, on infrastructure you own, under Australian law.
- Every state, not just ours. Perth, Melbourne, Sydney, Brisbane, Adelaide and everywhere between.
What your customers see
What your customers see in a Reckon portal
Every screen reads live from Reckon, so the figures match because they come from Reckon rather than from a copy somebody refreshes.
- Invoices outstanding and paid
- Statements on demand rather than on request
- Payment history against each account
- Pay now, posted back correctly
- Documents and correspondence
Who logs in
Editions covered
What people ask us for
Start with the job your Reckon portal has to do
The same portal gets asked for in six different ways depending on where you are up to. Select any one to read how we approach it.
One place, one view
Your customers should not need three logins
Reckon holds part of the picture. The rest is in the job system, the CRM, the payment gateway and wherever your documents live. A portal that only reads Reckon hands your customer a fragment and sends them back to the phone for the rest.
We join them. One login, designed to your brand, showing a complete account view built from every system that has a piece of it.
- Your job or field service system, for job status and completed work
- Your CRM, so the contact and the account are one record
- Payment gateways, so paying in the portal reconciles in Reckon
- Document storage, for anything attached to the account
- Your website or app, so the login is part of your brand rather than beside it
How it works now
Every question lands on your desk
- Customers ring or email to ask the same questions
- Somebody exports from Reckon and sends it out
- Chasing takes a person the best part of a day a week
- No record of who was told what, or when
After
Customers look it up, straight from Reckon
- Available any time, straight from Reckon
- Nothing rekeyed, because it is read rather than copied
- Anything they submit posted back where you want it
- An audit trail of who saw what and when
Scoped and quoted before you commit. You own the code, the documentation and the credentials at the end of it.
Get a fixed-price scopeQuestions owners ask about a Reckon portal
Is this the Reckon login?
No. The Reckon login is where you and your staff work. This is a separate portal you own, for your customers, that reads and writes your Reckon data. Your customers never get access to Reckon itself.
What can customers actually see?
Typically invoices outstanding and paid, statements on demand rather than on request, payment history against each account. What they cannot see is anything else, because the portal only ever requests the records belonging to that contact.
What is the hardest part of Reckon portal work?
Reckon Accounts and Reckon Accounts Hosted are desktop-lineage products, and how a portal reaches the data depends on where the file lives and who hosts it. Reckon One is the cloud product with a different API entirely. The portal is the same idea in each case and a different build underneath, so which edition you are on is settled before we quote.
Do we need a licence for every portal user?
No. The portal reads through the API under one connection, so the number of customers logging in does not change what you pay Reckon. That is usually the reason a custom portal costs less than the alternative once you have more than a handful of users.
Will it slow Reckon down or put our data at risk?
The portal reads through the API rather than touching your system directly, so day-to-day use is unaffected. Writes are limited to what you approve, and everything is logged so you can see what changed and when.
How long does it take?
A straightforward portal over Reckon is usually weeks rather than months. We scope it and quote fixed-price before starting.
Sending your details…
You can stay on this page while we send it.
Tell us what your customers keep ringing about
Which Reckon edition you are on, roughly how many customers would use it, and what they most often ring about. We will come back with a straight answer and a fixed-price scope.
Prefer a quick chat? Call 0425 531 127. We answer the phone in Perth.
