Standing service recon-remittance-allocations-proposed-every-month · revised 12 October 2026
Standing service
Get proposed allocations for each month's customer payments, with unsure ones listed
Each month up to 100 customer receipts and remittance notices get proposed allocations to open invoices with quoted evidence, and an unsure list. A person applies them.
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
Customers change how they pay and what they write on remittances. A proposal method that worked on last month's mix of lump sums and short-pays can be wrong on this month's. The monthly job re-measures the "sure" tag on labelled receipts so it stays trustworthy.
Who it’s for: Credit controller or bookkeeper who allocates customer payments every month.
Usually starts when: Customer payments arrive every month, with lump sums and short-pays among them.
The result: Each month you receive proposed allocations with quoted evidence for up to 100 receipts, an unsure list, tie-out to the penny and a report from 20 receipts you label showing how many allocations tagged sure were correct (one wrong sure allocation withdraws the tag).
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 allocation for a receipt sums to the receipt to the penny
- Allocations tagged sure are correct on the monthly sample
What we watch
- The month's receipts and remittance notices, redacted
- The open-invoice export
When something happens
Scroll the table sideways to read it all.
| When | What we do |
|---|---|
| A month closes and receipts arrive. | We send proposals, the unsure list and the test report. |
| A "sure" allocation is wrong on the sample. | We stop using the sure tag, report it and re-learn before the next month. |
| Lump-sum payments rise sharply. | We say so and review the unsure share with you. Linked job: Remittance allocation proposals |
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.
Match what customers paid to your open invoices and get a proposed allocation to check Job Optional
For each bank receipt and remittance notice you get a proposed allocation to open invoices (full, part, short or unmatched) with the quoted evidence. Nothing is posted.
Bought separately, each time it is needed; not part of the monthly fee
What is included, and what is not
- Monthly allocation proposals
- Unsure list
- Test report
Included
- Up to 100 receipts and remittances a month plus the open-invoice export
- Proposed allocations with evidence and a sure or unsure tag
- A sample of 20 receipts labelled by you and scored
- Nothing applied or posted
Not included
- Applying any payment in your ledger
- Chasing customers
- 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 on 20 receipts you label, every allocation tagged sure is correct and one wrong stops the tag, and at least 15 of the 20 are tagged sure, or the sure share is reported at the top
Evidence: The labels beside the proposals
Sums tie out to the penny for every receipt
Evidence: The tie-out sheet
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 shift in how customers pay makes sure allocations wrong. | The sure tag is re-tested on 20 labelled receipts every month and withdrawn if one is wrong. |
| 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
Will it post payments?
No. A person applies every allocation.
What does unsure mean?
The evidence did not tie the receipt to invoices. Those are listed for you.
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 “recon-remittance-allocations-proposed-every-month” as the subject.