We’re a small VAT-registered trading company that books all purchases, supplier payments and sales invoices through the API, and we’re moving from the legacy XML/JSON API to REST ahead of the June 2027 switch-off. Overall it’s been a good experience, but there are some gaps that block a full migration. All points below are checked against the current spec at /api-docs/v2.
Issues found in use
- No way to attach a document to a purchase.
POST /documents/receiptonly uploads to the Receipt Hub. Sales invoices have/documents/sales, andGET /purchaseshas ahas_receiptsfilter, but there’s no equivalent of the legacydocument/uploadwithPurchaseId. This is our biggest blocker. - Silent breaking change that lost data. The purchase field
suppplier_reference(triple “p”) worked in September; by October it had been renamedsupplier_reference. The old name was silently ignored rather than rejected, so aPUT /purchases/{id}succeeded but wiped our supplier reference to null. The spec marksPurchasesPutRequestasadditionalProperties: false, so unknown fields should be rejected. A changelog or versioning for breaking changes would really help. PUT /purchases/{id}replaces all item lines. Changing one field means resending every line, and all line IDs are regenerated. A PATCH, or line-level updates, would be safer.- Supplier payments can’t be edited. Changing a payment date needs
DELETE+POST. APUT /supplier_payments/{id}(even just date/notes) would help. - Can’t filter supplier payments by purchase.
GET /supplier_paymentshas nopurchase_idfilter, so finding the payment for one purchase means paging through all of them.
Gaps in the spec
- No purchase credit notes. Sales credit notes are supported (void/refund/hold), but there’s no endpoint to raise a credit note against a purchase, so we still do it in the UI.
- Bank transactions can’t be tagged or matched.
POST /bank_accounts/{id}/transactionscreates untagged transactions only, with no PUT/DELETE. There’s no way to tag a transaction, correct its date, or match a transfer between two of our own accounts. Matching card repayments is a manual UI step every time. - Bank accounts can’t be renamed.
/bank_accountshas GET/POST only. /reports/vat-obligationsrequireshmrc_account_id, but no endpoint returns it, so the report can’t be used from the API alone. There’s also no way to view filed VAT returns.- No edit (PUT) for client payments, journals, inventory or projects.
- Spec errors:
/documents/receipt,/documents/salesand/documents/generaldon’t define their request parameters or body.supplier_referenceis described as “Search by supplier reference” inPurchasesPostRequestandPurchasesPutRequest, where it’s a field being set, not a search.- The VAT code list says
nisogsinPurchasesPostRequest/PurchasesPutRequestbutnigoodsinPurchaseOrderPutRequest.
Legacy API outage (FYI)
- Legacy API seems to be down currently. Every legacy API call fails with “Cannot load the schema for the namespace ‘https://api.quickfile.co.uk’ – The remote server returned an error: (404) Not Found.” REST kept working, which let us carry on, but anyone still on legacy would have been stuck.
What works well
POST /purchaseswith an embeddedpaymentworked first time: the payment auto-allocates and the response includes the receipt number.- Redating a supplier payment with
DELETE+POST /supplier_paymentsis reliable. DELETE /client_payments/{id}returns a clear error when the payment is locked in a filed VAT return. The legacypayment/deletefails silently in that case.
Thanks!