Claim batches and remittances: how it works
Ready claims are sent to each insurer as one file: UAE claim XML (eClaimLink for Dubai, Shafafiya for Abu Dhabi) or the TPA spreadsheet. The insurer's remittance then pays and denies the lines; the money is posted and each claim moves on.
Lesson 4 of 9 · How it works
How it works
Make a batch per insurer from its ready claims; resubmitted claims carry only their denied lines and the resubmission comment.
Live mode sends the XML with the facility's own web-service login; simulated mode (the default) checks and records the file but sends nothing.
Spreadsheets and portals: download the file, upload or e-mail it yourself and mark the batch as sent with a reference.
Import the remittance (Remittance.Advice XML or a CSV with claim number and paid amount); a file imported twice is refused.
Money received is posted Bank / Insurance claims receivable; denied money stays open on the claim until it is resubmitted, written off or billed to the patient.
Where to find it
- Batches & submission
/admin/insurance/batches - Remittances
/admin/insurance/remittances
Settings that change it
- Insurance → Settings
/admin/insurance/settings
Checklist
Before you move on, check that you can:
- Open Batches & submission
- Make a batch per insurer from its ready claims; resubmitted claims carry only their denied lines and the…
- Live mode sends the XML with the facility's own web-service login; simulated mode (the default) checks and…
- Spreadsheets and portals: download the file, upload or e-mail it yourself and mark the batch as sent with a…
- Import the remittance (Remittance.Advice XML or a CSV with claim number and paid amount); a file imported…
Tips and common mistakes
- Have the regulator validate a test file before turning on production files: each regulator adds checks of its own.
- Simulated remittances let you walk the cycle; they are never posted to the ledger.