Standing service reconciliation-break-proposals-sampled-and-checked-every-month · revised 12 October 2026
Standing service
Get each month-end gap between two totals explained with row evidence
Each month-end you send the same two exports. The gap is explained with ranked proposals and row evidence, the planted tests re-run, and you get a report. Nothing is posted.
This starts a conversation by email. Nothing is charged, and nothing is monitored, until we have agreed scope, access and terms with you in writing.
The responsibility you hand over
The same two systems drift apart in similar ways each month, but each gap is found from scratch. A reason that was right last month is assumed this month without the rows to back it. Checks that nobody re-runs go stale when an export changes shape.
Who it’s for: Bookkeeper or finance lead who closes the books every month and meets a gap between the same two systems each time.
Usually starts when: You used the one-off job once and the same kind of gap came back, or month end now takes a day because of one unexplained difference.
The result: Every month you send the same two exports. We explain the month's gap with ranked proposals and row evidence, flag any reason that repeated, re-run the planted-break tests when an export changes shape, and send a report your bookkeeper can confirm.
What stays true, and what we do about it
No response-time guarantee is published for this new service. A date for each monthly report is agreed in writing before it starts.
Hours are agreed in writing before the service starts. It runs once a month and is not staffed round the clock.
What must remain true
- Every proposal shown in the month has rows that sum to the gap within your tolerance
- A gap no tested reason explains is reported as unexplained, not given an invented reason
- The report includes planted-break results on each changed export shape and flags any missed held-back case or regression
What we watch
- The two month-end exports
- Your confirmed reasons for earlier gaps
- Your notices of export changes
When something happens
Scroll the table sideways to read it all.
| When | What we do |
|---|---|
| The month-end exports arrive. | We match the rows, test each reason type and send the report. |
| An export changes shape or a field is renamed. | We re-run the planted tests on a sample of the new shape before the next report. |
| The same reason appears in two months running. | We list it first and name the rows and the process behind it. |
We do on our own
- Match rows and test each reason type
- Re-run the planted tests
- Write the report
We ask you first
- Any change to the matching key or the tolerance
- Any change to a rule, setting or page in your own systems
- Any wider access than the exports named here
- Contacting your customers or anyone outside your team
We escalate to you when
- A gap that is unexplained two months running
- Rows that suggest a duplicate payment
- A gap larger than the amount you set as unusual
- The planted tests fail on the new export shape
How you know it held. Your bookkeeper can re-compute every proposal's sum and match its row identifiers to the exports; with no proposal, the report must explicitly say unexplained.
How we keep it true
This service is never finished. Each month's report shows whether the things it watches stayed true, and it continues until you end it.
Find out why two totals disagree, with the rows that explain each possible cause Job Optional
Give us two exports whose totals differ. You get ranked possible reasons, each with the exact rows that add up to the gap; a reason whose rows do not add up is never shown. Nothing is posted.
Bought separately, each time it is needed; not part of the monthly fee
The one-off job; buy it first if you do not yet have the matching key and tolerance.
What is included, and what is not
- The monthly report
- The row-evidence sheets
- The repeated-reasons list
- The planted-test re-run
Included
- One pair of exports and one gap per month, built under the one-off job on this site or one you can show us
- Ranked proposals with row evidence, using the same checks as the one-off job
- A list of reasons that repeated from earlier months
- A re-run of the 12 planted breaks, including the 6 originally held back by your bookkeeper, whenever an export changes shape
- A monthly report with the proposals, the unmatched rows and what it cannot show
Not included
- Posting journals or adjustments
- Tax or accounting treatment
- Stating a cause as fact
- More than one gap a month
- Round-the-clock cover or a response-time guarantee
How we know it’s done
Agreed with you before work starts. Each check produces evidence you keep.
After the report is frozen, your bookkeeper re-computes every row-evidence sum and compares the full row identifiers with the supplied exports; all sums match within the agreed tolerance. A nonexistent row, wrong sum, reason asserted as fact or unexplained gap given an invented reason fails the whole test; if there are no proposals, you verify that the report says unexplained.
Evidence: Your sums beside the report's.
The report states the gap, the proposals shown, the unmatched rows and what it cannot show, and a gap with no tested reason is reported as unexplained.
Evidence: The monthly report.
The planted tests are re-run when an export changes shape, and any failure is listed first.
Evidence: The re-run results.
Nothing in your books has been posted or changed by us.
Evidence: Your accounting package's audit trail for the month; we hold no access.
Sign-off. You read each report and re-run the acceptance checks with the files and steps supplied. A month counts as delivered only when those checks pass.
If it fails. If we cannot do a month because an export is missing or has changed, we say so 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
- A matching key and tolerance already agreed
- Two row-level exports each month through a secure route
- A named bookkeeper who confirms the proposals
We stop and tell you if
- Exports stop arriving
- The export shape changes and no sample is supplied
- Nobody confirms proposals for two months
What could go wrong
The service reads exports and reports, so there is nothing to undo. Ending it leaves your systems exactly as they are; you keep every report.
Scroll the table sideways to read it all.
| Risk | How we handle it |
|---|---|
| Last month's reason is assumed without evidence. | Every proposal needs rows that sum to this month's gap, and repeated reasons are listed separately. |
| Exports carry personal data. | Individuals' names are masked by you before sending. |
Each report is checked by a separate automated reviewer before hand-over. Your bookkeeper confirms or rejects each proposal and makes any change in the books. No human supervisor is included unless your agreement names one, and at launch the work is largely automated.
Stays with a person
- Your bookkeeper confirms or rejects each proposal
- You make every change in your books
Access we would need
- Two row-level exports each month through the agreed route
Questions
Do you post the corrections?
No. Your bookkeeper confirms each proposal and makes any change.
What if the gap is unexplained?
The report says so and lists the rows that match neither side.
Send an enquiry
Send us
- Which two systems and which closing day
- Roughly how many rows each export holds
- No logins, keys, customer data or payment details in the first enquiry
Later, once you agree
- The two exports each month, with individuals' names masked
- Your confirmed reason for each earlier gap, if you have one
- Notice when an export changes shape, the 12-break baseline and your labels; on a changed shape, 6 new breaks you keep from us until testing
You keep your systems and logins; we receive the agreed masked exports, never ask for accounting or bank logins and never change your books. Before sharing, the terms name any model service, its country, retention and training status, and when our export copies are deleted.
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 “reconciliation-break-proposals-sampled-and-checked-every-month” as the subject.