Send claims automatically with a job queue
Claims that are created automatically, on posting or by a job queue, don't go to the bank until someone chooses Perform Operations. The RdN Perform Operations job queue does that for you. It runs operation suggestions on the claim batches, sends all pending operations to the bank and closes batches with nothing left waiting. If claims are created automatically, this is the most important job queue in Banking.
Scenario
Dæmi ehf. creates claims when sales invoices are posted. The collection officer wants new claims, updates and cancellations to go to the bank every day without opening the claim batches.
Before you start
- Claims are created and sent manually with Perform Operations without errors.
- A bank user is registered for the user who runs the job queue.
- You have permission to change RdN Claim Setup and create job queue entries.
Walkthrough
- Open RdN Claim Setup and go to the Job Queue - Claim Operations FastTab. By default the job queue only handles open claim batches. To include closed batches, turn on Allow Claim Suggestions on Closed Claims. With Get Claim Suggestions On Claims Dating Back To: you limit them to batches created on or after that date.
- Open Job Queue Entries and create an entry that runs codeunit 10041507 (RdN Perform Operations).
- If the job queue should only handle automatic claim batches, set the parameter
AUTO_ONLY. Automatic batches are created on posting or by the RdN Create Claims JOB job queue. You then send manual batches with Perform Operations. - Choose a recurrence, for example daily in the afternoon, and set the entry to Ready. If RdN Create Claims JOB creates the claims, schedule this job queue to run after it.
Result
In each run the job queue goes through the claim batches and does this for each of them:
- Runs operation suggestions on claims that aren't paid, cancelled or in secondary or legal collection. Claims that have changed get Operation Alter or Cancel.
- Sends all pending operations to the bank, including new claims with Operation Create. The claims appear in the customers' online banks.
- Closes the batch when no claim in it is waiting to be created.
What can go wrong
- The job queue entry is in error. Open it and read the error. Usually new claims couldn't be sent, for example because the bank user isn't registered. Fix the cause; the next run sends the claims.
- An update or cancellation didn't reach the bank, but the job queue entry isn't in error. Errors in those don't stop the job queue. Open the claim and choose Perform Operations to see the error.
- A claim wasn't sent. Check whether the batch is closed and
Allow Claim Suggestions on Closed Claims is off, or whether the parameter
AUTO_ONLYis set and the batch is manual. - A suggestion you cancelled is sent anyway. The job queue runs the suggestions again and sends them
without review. Create batches you want to review first manually, set
AUTO_ONLYand send those batches with Perform Operations.
All messages are in Help.