Farris, Rick

Examples of Artefacts include: (purchase or sales) invoices, credit notes, quick entries, corrective invoices, contact payments and opening balances. An artefact that requires payment can be a purchase invoice or a sales invoice and will be related to a Contact (either VENDOR or CUSTOMER ). Check out the "Key Concepts" section of the Tutorials & Guides to help you better understand the data relationships. The "Id" in your payload list you gave should enable you to retrieve and filter the payments which map to the voided transactions. Since you have (or can get) the Contact ID, Bank Account ID, Transaction ID, all you really need to know is that the payment was allocated or not. That is, was it a direct payment of an invoice, or was it a payment on account (and therefore unallocated). Look at the Contact Allocations to see if that is a better source for you in your workflow.

To clarify, you should be able to filter the contact payments by the list of trasaction_id values you build of your voided artefacts. Keep in mind to specify the payment type (whether the voided payment is a receipt or a payment). Hope this helps.

Hi Jim! If the payment was properly allocated, you should be able to find it through https://developer.sage.com/accounting/reference/payments/ and more specifically by the contact payments endpoint https://developer.sage.com/accounting/reference/payments/#tag/Contact-Payments. Let us know if this is what you were looking for.

Some additional information and background on this messaging is that it started on March 1st, 2021 as mentioned. The error message is confusing as the 3 fields listed include a line item quantity, when the unit price is allowed. The Artefact is a SALES INVOICE. I seem to remember that due_date might not be supported for any region in SBCA-Start (version) and am looking at a payload similar to the following that is causing the above Error code: 422 for the three attributes/fields mentioned in the error returned. Also, each line item has a quantity which can be inferred by the unit_price and net_amount, so the error message seems to be suggesting not to provide a quantity, either. I believe the discount_amount should probably be omitted if 0, but may also not be supported in the "Start" edition of Sage Business Cloud Accounting in the UK. I do note that goods and services are mixed in the following payload for the SALES INVOICE that is getting the error. The sample payload: { "sales_invoice": { "contact_id": "923c137cab894caa8b3ec9fcf1309d31", "date": "2021-03-31", "due_date": "2021-03-31", "invoice_number_prefix": "", "invoice_number": 403, "reference": "4540156044", "main_address": { "address_line_1": "C/O TEST\r", "address_line_2": "Accounts Payable Department\r", "city": "PO Box 0001\r", "region": "Glasgow\r", "postal_code": "G74 9FU" }, "invoice_lines": [ { "description": "TXU2 TEST PRODUCT", "ledger_account_id": "d2e342ce773b11ebb6a30662051ba57b", "unit_price": 392, "unit_price_includes_tax": false, "quantity": 1, "net_amount": 392, "discount_amount": 0, "tax_rate_id": "GB_STANDARD", "tax_amount": 78.4 }, { "description": "TX-2RL TEST PRODUCT2", "ledger_account_id": "d2e342ce773b11ebb6a30662051ba57b", "unit_price": 364, "unit_price_includes_tax": false, "quantity": 1, "net_amount": 364, "discount_amount": 0, "tax_rate_id": "GB_STANDARD", "tax_amount": 72.8 }, { "description": "SERVICES 01/02/21 to 28/02/21 = 28 days - invoice#403", "ledger_account_id": "d2e342ce773b11ebb6a30662051ba57b", "unit_price": 0, "unit_price_includes_tax": false, "quantity": 1, "net_amount": 0, "discount_amount": 0, "tax_rate_id": "GB_STANDARD", "tax_amount": 0 }, { "description": "ONGOING SERVICES", "ledger_account_id": "d2e342ce773b11ebb6a30662051ba57b", "unit_price": 0, "unit_price_includes_tax": false, "quantity": 1, "net_amount": 0, "discount_amount": 0, "tax_rate_id": "GB_STANDARD", "tax_amount": 0 } ] } } Lastly... Things got complicated in the UK post-brexit! So it's worth mentioning the discussions in the Developer Guides here: https://developer.sage.com/accounting/guides/brexit/sbca_api_brexit_guide/ Which points here to highlight the breaking changes that must be dealt with: https://developer.sage.com/accounting/guides/brexit/artefacts-breaking-changes-to-support-brexit-in-api-31/, specifically the "Required artefact parameters"

Hi Andrew! Firstly, have these invoices and payments been allocated? I presume so. From there you can get all reconciliations, or just those created since a certain date. See: https://developer.sage.com/accounting/reference/banking/#operation/getBankReconciliations If you need to create reconciliations via API, see: https://developer.sage.com/accounting/reference/banking/#operation/postBankReconciliations Perhaps this helps? Please let us know if I've misunderstood your context here or if you need further clarification.