CAS Invoicing - Send Invoices to CAS and Record Response

[CarlyCotton]

User Story
After a ministry user approves a batch to be sent to CAS for invoicing, we need to send the invoices (and their detail records) to CAS via the API during the next available open window. This should also include any invoices we have previously received an error response for and a user has selected 'Retry'.

Acceptance Criteria

• Create process to send invoices to CAS via the API in the next available window

• Invoices to send to CAS: in an approved batch that have not already been sent;

• Update the status if response is error: Manual Intervention (to avoid retrying - any technical error should be retried)

• Save any Manual Intervention error messages received for the invoice (do not save any technical errors)

• Update Distribution Accounts to be used in TEST & STAGING (doesn't matter which award CR or DR each one goes to):

019.11215.18150.5185.1100000.000000.0000
019.11OCG.00000.1034.1100000.000000.0000
019.11110.18150.5001.1100000.000000.0000
019.11OCG.00000.4612.1100000.000000.0000
019.65OCG.00000.3990.6500000.000000.0000
019.11OCG.00000.3451.1100000.000000.0000
019.11OCG.00000.3463.1100000.000000.0000
019.11225.18150.5298.1100000.000000.0000
019.11215.18200.6508.1100000.000000.0000
019.11220.18632.7701.1100000.000000.0000

• Update Distribution Accounts to be used in DEV (doesn't matter which award CR or DR each one goes to):

019.11020.18150.5108.1100000.000000.0000
019.11020.18150.5185.1100000.000000.0000
019.11225.18150.5298.1100000.000000.0000
019.11OCG.00000.3451.1100000.000000.0000
019.11OCG.00000.3458.1100000.000000.0000
019.11OCG.00000.3463.1100000.000000.0000
019.11OCG.00000.3003.1100000.000000.0000
019.11020.18150.5010.1100000.000000.0000
019.11OCG.00000.1821.1100000.000000.0000
019.11OCG.00000.1046.1100000.000000.0000

Additional Context
CAS Files for Response Message and Payload Examples
-- carly to provide easier text for dist accts.

Technical

• Create release instructions to update sims.cas_distribution_accounts for DEV/TEST/STAGING assigning the provided values from the business.
• Call CAS endpoint under the existing CAS API service.
  • Set the invoice status to Sent when a successful HTTP status is returned.
  • Set the invoice status to Manual intervention when a BAD_REQUEST is returned following the same idea from CAS Supplier.
  • Other errors should leave the record status as pending to allow it to be retried.
• Create a scheduler to be executed three times a day with a hard limit to how many records will be selected following the same idea from the notifications.
  • Select all pending invoices under an approved batch.
  • Execute the CAS API calls with a limit of two max parallel operations (default configuration).
  • When a call fails, add an error to the process summary to allow the scheduler to retry.
• E2E tests for the new scheduler.
• Unit tests for the new API call following the ones already in place.