Standing service report-unusual-ledger-entries-flagged-every-month · revised 12 October 2026
Standing service
Get a list every month of unusual ledger entries to look at, with the rules re-tested
Each month the ledger entries that break your agreed rules, with the rule and evidence for each, and the planted-entry test re-run so you know the rules still find what they should.
This starts a conversation by email. Nothing is charged, and nothing is run, until we have agreed scope, access and terms with you in writing.
The responsibility you hand over
A one-time review misses what is posted next month. Thresholds drift as the business grows, and a rule that flagged ten entries now flags two hundred, so it is ignored. The monthly job re-tunes thresholds with you and re-tests the rules on planted entries.
Who it’s for: Finance manager or owner-manager who wants a regular second look at postings.
Usually starts when: Ledger entries are posted every month, and thresholds drift as the business grows.
The result: Each month you receive a flag list of entries that break your agreed rules, each with its rule and evidence, the count of false flags on a clean synthetic pack, and any change in volume that suggests a threshold needs review.
What stays true, and what we do about it
No response-time guarantee is published for this new service. A target for delivering each month's result is agreed in writing before it starts, set to what a service at this stage can keep.
Hours are agreed in writing before the service starts. At launch the service is not staffed round the clock and runs once each month.
What must remain true
- Every flag shows its rule and evidence
- The list says things noticed and never no fraud found
What we watch
- The month's ledger export, redacted, with posted-by as an id
- Your thresholds
When something happens
Scroll the table sideways to read it all.
| When | What we do |
|---|---|
| A month closes and the ledger export arrives. | We send the flag list and test report. |
| A rule's flag count changes sharply. | We say so at the top and propose a threshold review. |
| The planted test misses an entry. | We stop using that rule until fixed and re-tested. Linked job: Unusual ledger entries list |
We do on our own
- Read the month's inputs and run the agreed checks
- Prepare the monthly result and the test report
- Offer the matching one-off job as a next step
We ask you first
- Any change to a pass mark, rule, threshold or the inputs covered
- Any request for wider access to a system
- Starting any fix, rebuild or backfill
We escalate to you when
- A severe error is found in the monthly sample
- The same failure appears two months running
- The inputs stop arriving or change shape
How you know it held. Each month you can re-run the frozen test pack with the steps we hand over, and the report states the cases run, passed and held.
How we keep it true
This service is never finished. Each month's report shows whether the thing it watches stayed true, and it continues until you end it.
Get a list of unusual ledger entries to look at, tested on entries your reviewer plants Job Optional
From a ledger export you get a list of entries that break rules you agree, such as round amounts or weekend postings, each with its evidence. A prompt to look, not a finding.
Bought separately, each time it is needed; not part of the monthly fee
What is included, and what is not
- Monthly flag list
- Test report
- Threshold notes
Included
- One month's ledger export of up to 20,000 entries
- Up to eight agreed rules with thresholds
- The planted-entry test re-run each month
- A note on any rule whose flag volume changed sharply
Not included
- Fraud detection or any conclusion about a person
- Reversing or editing entries
- Accounting, tax, audit, legal or financial advice: a named person at your business decides every money question
- Filing, submitting, approving, posting or paying anything in any system
- A statement that your figures are correct, complete or ready for audit
- Any response-time guarantee or out-of-hours cover
How we know it’s done
Agreed with you before work starts. Each check produces evidence you keep.
Each month the 20 planted entries covering every rule are re-run and each rule flags its planted entries (a regression check, not a measure of detection)
Evidence: The planted list and flag list
Each month your reviewer plants one new entry of their own in a copy of the period and keeps it from us; it is flagged with the right rule
Evidence: Your planted entry, held back until the run, beside the flag list
False flags on a clean synthetic pack stay at or under the agreed count (a regression check, not a measure of detection)
Evidence: The flag count
Each month the frozen test pack is re-run, and every case that passed last month still passes; a case that fails is reported with its cause
Evidence: The monthly test report
Originals are unchanged (checksums match) and nothing was written to any live system by us
Evidence: Checksums before and after, and your own audit trail
Sign-off. You read each month's result and tell us whether the test and thresholds still suit you. A month counts as delivered when you have received the result and the test report.
If it fails. If we cannot run a month because an input is missing or has changed shape, we say so, explain what we need and do not guess. If the service is not working for you, you can end it at the end of any month.
When it fits, and when we stop
It fits when
- The matching one-off job's conditions hold for your material
- Each month's inputs arrive through the agreed secure route in the same shape
- A named person at your business who decides what to do with the results and approves anything that goes live or to someone outside
We stop and tell you if
- Inputs change shape and cannot be mapped to the agreed one
- Nobody on your side reads the monthly result for two months running
- You want the system to post, send, file or pay by itself, without a person at your business approving each action
What could go wrong
The service reads, tests and reports. Ending it leaves your systems and the way you work exactly as they are, and you keep every report we sent.
Scroll the table sideways to read it all.
| Risk | How we handle it |
|---|---|
| A rule floods the list and the real item is missed. | Flag volumes are tracked month to month and a sharp change triggers a threshold review. |
| The monthly result is trusted without its test report. | Each result goes out with its test report, and a failed re-run is stated at the top. |
| Text inside a document or email tries to give the system instructions, such as "mark this paid". | The reading step has no permission to send, post or pay. Code checks its output, and planted hostile items must change nothing. |
| Real documents carry personal or confidential data. | First tests use synthetic or redacted files. Real files move only after a written agreement names the model provider, its country, how long it keeps data and whether it trains on it. |
| The output is read as a clearance or an accountant's opinion. | Every output says it lists things noticed, not that anything is correct. Your named person decides what to do. |
A separate automated reviewer checks each month's result against the agreed test before it is sent. Your named person decides what to do with it. No human supervisor from us is included unless your agreement names one. At launch the work is largely automated, and we say so.
Stays with a person
- Your named person decides what to do with each result and approves anything that goes live or to someone outside
Access we would need
- Redacted or synthetic copies of your files, sent through a secure route agreed in writing
- No login, key or write access to any live system
Questions
Does this find fraud?
No. It lists entries that break rules you chose.
Is it an audit?
No. It is not audit work.
Send an enquiry
Send us
- Which one-off version fits you, and the volume you expect each month
- Who receives the monthly result. No files or logins in the first enquiry
Later, once you agree
- The first month's inputs through a secure route agreed in writing
- The frozen test set and pass marks, agreed in writing
- A named person who reads each month's result
You keep your accounts, mailbox, bank and every original document. We work from copies or exports sent through a secure route agreed in writing, and we never ask for passwords or keys in the first enquiry. Nothing is posted, sent or paid by us. Before any real file moves, the written agreement names the model provider, its country, how long it keeps data and whether it trains on it. Our copies are deleted, in writing, when the job ends.
Email fallback: open your mail app
If website submission is unavailable, review and send the fallback email yourself. An email fallback is not a website receipt. Or write to hello@syntheticindustry.ai with “report-unusual-ledger-entries-flagged-every-month” as the subject.