Restore a broken invoice sync, proven on a synthetic trading month

The result you are buying

How the work fits together

The project is complete when every fix named in the written proposal has been accepted by you, the synthetic trading-month test passes, and anything left is listed in writing. You accept the repaired sync on the strength of the test, not each internal step.

1. Replace hard-coded account codes in a finance sync with a checked mapping table Job Each time it fires

   Up to 25 source categories map to active ledger accounts through one reviewed table, and an unmapped or archived account is held with its name instead of posting to a default.

   If lines post to the wrong account or runs fail on an archived account

   Posting must be right before duplicates and gaps can be judged, so it goes first when it is on the agreed list.

2. Stop a retried automation from creating a second invoice in Xero or QuickBooks Online Job Each time it fires

   Replaying, retrying or double-running one named invoice automation leaves exactly one invoice per source order in a test accounting file, and an unknown outcome is held for a person.

   If a retry or re-run creates a second invoice

   Each order must create one invoice before counts are compared; it goes after the mapping fix when both are on the agreed list.

   After: Account code mapping table

3. Make a bulk Xero invoice run finish every order, or list exactly which ones it held Job Optional

   A synthetic run of 150 orders against a simulated limit of 60 calls a minute, with a simulated 429 and an interruption, ends with every order created, already present or held, and counts that add up.

   If the sync writes to Xero and drops orders

   Offered with it when gaps appear on busy runs.

   After: Stop duplicate invoices on retry

4. Make a customer sync reuse the right Xero contact instead of creating near-duplicates Job Optional

   Replaying a synthetic customer list through one named sync creates each customer once in a Xero demo organisation, and a changed email or name updates the same contact.

   If the sync writes to Xero and splits customers

   Offered with it when contacts are duplicated.

5. Stop QuickBooks Online invoice updates from failing with a Stale Object Error Job Optional

   Two quick edits to one synthetic QuickBooks Online invoice from a sync and a person both land as agreed, and a stale update is re-read once and then held, not looped or lost.

   If the sync updates QuickBooks Online invoices

   Offered with it when updates fail with stale-object errors.

6. Make foreign-currency orders create invoices in the right currency, with the right rate Job Optional

   Synthetic orders in the base currency, a two-decimal currency and a zero-decimal currency create invoices with the order currency and amount, and no default or inverted rate is stored.

   If orders arrive in several currencies

   Offered with it when currencies or rates are wrong.

How an engagement works

The price covers the agreed list only. Failures you add later are quoted separately, and failures that turn out to be bigger jobs are re-scoped with you.

How it starts

1. You describe the sync and the failures you have seen, using invented examples.

2. We read the description, propose the failure list, the order of repair and a fixed price.

3. You agree the list, price and terms in writing. Nothing starts before then.

4. We apply and test each fix on a demo or sandbox target and send it for your acceptance.

5. We run the synthetic trading-month test and send the final summary.

What is included, and what is not

• The failure list with the agreed order of repair
• A pull request for each accepted fix, with its test evidence
• The synthetic trading-month test log with counts, and a final summary of what was fixed, what is held and what needs a bigger job

How we know it’s done

Agreed with you before work starts. Each check produces evidence you keep.

1. Every fix named in the proposal is accepted by you or removed from the list in writing.

   Evidence: The final summary with your acceptance or removal recorded for each fix.

2. A synthetic trading month run through the repaired sync on the test file creates every source order exactly once, and created plus already-present plus held equals the source count.

   Evidence: The three counts and the order list from the test log.

3. Every created line posts to an active account that the written proposal names for its category, and no line posts to an account the proposal does not name.

   Evidence: A per-line account listing from the test file, set beside the proposal's category-to-account list.

4. Each accepted fix still passes its own acceptance checks when the whole sync runs together.

   Evidence: The combined test log mapped to each fix's checks.

When it fits, and when we stop

What could go wrong

Every fix is a separate pull request that your team merges, so any one can be reverted on its own. If the project stops, accepted fixes stay accepted and the rest is handed back with notes. Nothing in your live accounting records is changed by this project.

Scroll the table sideways to read it all.

Each change is reviewed separately from the work that produced it, and you accept every fix. No human supervisor is included unless your proposal names one. At launch the work is largely automated, and we say so.

Stays with a person

• You accept each fix
• You merge, switch over and deploy on your own gates
• Your accountant decides what happens to posted records

Access we would need

• Read access to the sync code or definition through the agreed route
• A demo or sandbox target created by you

Questions

Related

Send an enquiry