Backups and Data Checks
A recent clean copy, and proof the figures still reconcile.
The danger with an automated file is rarely a dramatic crash. It is the quiet error: a total that silently stops including the newest rows, a reference used twice, a figure that drifts a little and is not noticed until it reaches a customer or an invoice.
- Order ledger copiedDated copy written to the backups folder
- Reference counter copiedDated copy written alongside it
- Older restore points prunedRolling window kept, nothing older retained
- Totals recomputed from the linesChecked against the figure in the sheet
- References reconciledNo duplicates, no gaps, nothing stuck
From backup to verified audit, in four steps.
Before the working day, the files everything depends on are copied to a dated backup.
Each backup is fetched back and confirmed to exist. A storage service accepting a copy request is not the same as a file being saved.
A separate check re-derives the numbers independently: references reconciled, nothing stuck mid-process, totals recomputed from the lines.
If everything reconciles, the morning is silent. If anything is off, one itemised report goes out, graded by severity.
What changes after we deploy this.
If any of these describe your business, this workflow earns its keep.
When a shared workbook drives scheduling, pricing, or stock, it stops being a document and becomes infrastructure. Anything writing to it automatically needs both a recent clean copy and a check that the figures still add up.
An automation editing a file all day is exactly where a small, silent mistake compounds. Re-deriving the answers with different rules is the only way to catch an error the original logic would repeat.
A figure that drifts is cheap to fix on the morning it happens and expensive once it has been quoted, invoiced, or promised. This is about shortening that gap to hours.
An audit trail, kept for you.
Clean mornings are recorded as clean. You only hear about the mornings that need you, and the record shows both.
- Mon 06:04Silent, no report sentBackup verified, audit cleanDaily checkBackup verified, audit cleanMon 06:04Daily checkSilent, no report sent
- Tue 06:03Silent, no report sentBackup verified, audit cleanDaily checkBackup verified, audit cleanTue 06:03Daily checkSilent, no report sent
- Wed 06:05Graded red, reportedTotal excluded 4 newest rowsDaily checkTotal excluded 4 newest rowsWed 06:05Daily checkGraded red, reported
- Thu 06:04Graded orange, reportedReference 7710 appears twiceDaily checkReference 7710 appears twiceThu 06:04Daily checkGraded orange, reported
- Fri 06:06Silent, no report sentBackup verified, audit cleanDaily checkBackup verified, audit cleanFri 06:06Daily checkSilent, no report sent
We follow strict security practices including OAuth access control, AES-256 encryption, and full audit logs. Credentials are never stored in raw form.
- CASA Tier 2 verified
- OAuth access
- AES-256 encryption
- Audit logs
- GDPR
- CCPA
Want to know whether your figures actually reconcile?
We will run the checks over a copy of your data and tell you what agrees, and what does not.
It runs inside the tools you already use.
And 30+ others. If your tool is not listed, ask.
See every integrationThe questions we get before we build.
Still unsure? Ask us directly and we will answer before you commit to anything.
What does this actually protect against?
It gives you restore points for corruption, a bad automated edit, or an accidental deletion, and it detects inconsistencies in numbering, queues, duplicates, and totals before they pass unnoticed. It is worth being precise about the bound: backups held in the same cloud account protect against those failures, not against the loss of the whole account, which would need an off-platform copy.
Is this the same as checking that the automation is running?
No, and they are genuinely different jobs. Monitoring tells you whether something ran. This checks that the output is correct and recoverable, which is a question the running system cannot answer about itself.
Does it use AI?
No. The checks are deterministic arithmetic and reconciliation rules, so they give the same answer every time and can be relied on as a safety layer.
Why not just trust that the backup succeeded?
Because a cloud storage service reports success the moment it accepts the request, which is before the copy has finished. A backup that was never verified can quietly be a file that never appeared, which is why each one is fetched back and confirmed.
Will it create noise on a normal day?
No. If everything reconciles, nothing is sent. You only hear about exceptions, which is what makes the report worth reading when it does arrive.
How far back can we recover?
That is set to suit the operation, with a rolling window of dated restore points and older ones pruned automatically. Thirty days is a common starting point.
Other automations that complement this one.
Where Document Consistency Check keeps a document set consistent and Evidence and Audit Pack gathers the proof a process ran, this keeps the underlying files recoverable and their arithmetic honest. It exists because operational builds like Purchase Order Processing write to files a business genuinely depends on.
Want the numbers checked before you are?
Tell us which files your operation depends on. We will tell you what a verified backup and a daily reconciliation would look like for them.
Every workflow is a managed monthly service. No credit card, and we respond within one business day.