Automated reporting is the weekly sales sheet, the month-end debtors list or the job-cost report produced by the system instead of a person. The figures are pulled from your sales, job and accounts software, reconciled and checked, then sent to each reader at the time you set. Ozwebnet writes it from scratch in Adelaide, South Australia, for businesses across Australia — one fixed quote staged against milestones, and the source code handed over with the IP assigned to you.
DETAIL OF SHEET 06 — DATA PLATFORMS →
The weekly or month-end report that someone assembles by hand — export from Xero, export from simPRO, paste into a spreadsheet, fix the totals, email it — is produced instead by a system on a schedule. The system reads the period's figures from each source, applies the same matching rules every time, checks that the totals agree with the systems they came from, and delivers the finished report as a PDF or spreadsheet to its readers. If a check fails, the report is held and someone is told, rather than a wrong report going out.
We take the spreadsheet as it is built now — every column, total, exception and footnote — and record where each figure comes from and who receives it, so the automated report matches the one people already read.
At the start of the week, on the first of the month or the day after period close, the system reads the period's figures from Xero, MYOB, simPRO, ServiceM8, Cin7 or your own database — or from your data warehouse where one exists. No one exports anything.
The figures are matched by the rules set at specification — invoice to job, job to sale, payment to invoice — and the totals compared with the systems they came from. A report does not leave until its numbers agree.
A source that did not answer, a period with missing entries, a total far from last period's: the report is held, the person responsible is told exactly what to fix, and a report that failed its checks does not go out under your name.
The owner's one-page summary, the branch manager's page, the accountant's spreadsheet — each reader receives the version for their role, by email, into a shared folder or to a portal, as a PDF, a spreadsheet or both.
Each report that went out is kept with its date, its figures and its readers, so last March's numbers can be found and re-sent, and any past period can be run again from the same screen when a question comes up.
When a column is added, a branch opens or a matching rule changes, it is changed once in the report definition and every future run and every reader gets it. Nobody hunts through spreadsheet formulas.
TYPICAL SCOPE FOR THIS KIND OF SYSTEM — YOUR EXACT SCOPE IS FIXED IN WRITING AT THE SPECIFICATION STAGE.
Not sure which? Ten minutes on 1300 699 321 tells you — Mon–Fri 9–5 ACST.
One fixed quote, set in writing at the specification stage (02 Blueprint) and staged against the five milestones below. Each milestone ends with a working system; stop at any milestone and keep what has been built.
SEE THE FIVE STAGES ANIMATED →We watch the report being built by hand once, and note every source, formula, exception and reader along the way.
The report layout, its sources, its matching rules, its checks and its schedule are specified in writing; the fixed quote is set here, staged against milestones.
Built one report at a time; each milestone ends with a report that runs and arrives on its own.
The automated report is run beside the hand-built one for the same period until the two agree, then tested before launch.
The reports go live on their schedule, and you receive the source code with the IP assigned to you.
Yes. We take the spreadsheet as it is built now — every column, total and exception — record where each figure comes from, and the system produces the same report on the schedule you set, pulling from Xero, MYOB, simPRO, ServiceM8, Cin7 or your own database.
The report is held. The totals are checked against the systems they came from and against the last period; if a check fails, the person responsible is told what to fix and the report stays held until it is fixed.
One fixed quote, set in writing before the build and staged against milestones.
Yes — source code delivered, IP assigned to you.
Yes — Adelaide first, Australia-wide. The reports are written in Adelaide and run against your systems wherever your office is.
Call, or answer a few short questions — what you run, what breaks, when you need it working — and we reply within one business day. The quote is fixed in writing before any build starts.
