Who this is for
A developer, operations lead or finance owner whose month-end or nightly job posts many invoices to Xero and finds some orders never arrived.
After a busy period the number of invoices in Xero is lower than the number of source orders, and the job log shows rate-limit errors or a run that stopped partway.
The result
A synthetic run of 150 orders, sent one call per order against a simulated allowance of 60 calls a minute so that it needs more than one minute of allowance, with a simulated rate-limit response and an interruption, finishes with every source order either created, already present or listed as held with a reason, and those three counts add up to 150; an order left in doubt by the interruption is held, not created again.
What is included
- One named job that posts invoices to one Xero organisation in bulk
- A request pacer that respects the documented concurrency and per-minute ceilings and the wait the response asks for
- Batching of creates where Xero supports it (Xero documents up to 50 invoices in one call), with each returned item's own status checked rather than the call status alone
- A durable checkpoint of the state of each source order so a stopped run resumes without repeating work, with any order left in doubt held for a person
- Tests with a simulated rate-limit responder: the pace test sends one call per order against a simulated allowance of 60 calls a minute, so 150 orders need more than one minute of allowance; the batch test sends batches of 10 with one invalid order; and a run on a Xero demo organisation within the limits
You receive
- The change as a pull request, with the pacing settings and the checkpoint design described
- A test log with the created, already-present and held counts per run and the request pace, redacted
- A held-order list format and a short note on how to release or retry held orders
What is not included
- Raising Xero limits or changing your Xero plan; the limits are Xero's
- Preventing duplicate invoices from retries beyond the checkpoint, which is a separate job
- Rewriting the job into a different architecture or adding a queue product
- Backfilling past months of missing invoices in your real organisation, unless agreed as its own project
- Bookkeeping, tax, audit or any accounting advice, including deciding how a transaction should be treated in your accounts
- Changing posted, reconciled or locked-period transactions: your accountant or account holder decides and performs those
- Live changes: your authorised account holder applies any agreed change and holds the production keys
What we need from you first
- The size of a busy run, how it is triggered, and the exact error text with names and amounts removed
- Whether the job runs in parallel and how many workers it uses
- What happens today after the job stops partway
- Do not send credentials, bank details, invoices, customer records or confidential code in the first enquiry
Never send passwords, keys, customer records or confidential code in the first enquiry. Secure handover is agreed after scoping.
How we check it is done
- A synthetic run of 150 orders, sent one call per order against a simulated allowance of 60 calls a minute so it needs more than one minute of allowance, with a simulated rate-limit response at call 60, ends with created + held + already-existing equal to 150.
- In the same run the request log shows no more than 60 calls in any minute and no more than 5 in flight at once, unless a lower ceiling was agreed in writing.
- A run stopped halfway and restarted creates only the orders still pending; no order the checkpoint records as created is created again, and an order that was in flight at the stop is held as in doubt.
- In a batch of 10 orders where one is invalid, that order appears in the held list with Xero's reason and the other nine are created and counted.
You inspect the named test evidence and sign off before payment. Your authorised account holder performs and verifies any live change, and decides what happens to records already posted.
When we would stop or decline
- The shortfall is caused by validation errors or a failed connection rather than rate limits
- The job must write to several Xero organisations at once with shared limits that need a wider design
- No stable order id exists and none can be agreed
Questions
Can you make Xero allow more calls?
No. The limits belong to Xero. The job paces the work and records what it could not do so nothing is lost silently.
Will the job fill the gaps in last month?
Not as part of this fixed scope. A past-month backfill is separately agreed and uses the same checkpoint approach.
What if the job also creates duplicates?
That is a separate failure with its own job. The two fit together, and the project that restores a broken sync covers both.
Price and terms
From £445 · untested offer price. Fixed after the quote is agreed (from £445); payment after the agreed checks pass and you sign off. No payment before sign-off.
This is a new service with no published client results. The price is a starting point we have not yet tested with buyers. Nothing is ordered or charged by the enquiry. The full specification is on the Synthetic Industry catalogue.