← Knowledge library

Finance & ZATCA

Reconcile payer remittance advice without inventing cash

Match payment-reconciliation lines to claims while keeping unmatched amounts in advice suspense.

Current source · source reviewed · 7 min read

Before you begin

1. Open Remittance

Read the advice ledger and cash ledger separately. The page shows arrival patterns including advice before cash, cash before advice, partial and combined receipts, explicit fees, reversals and returned payment.

Official local advice ingestion conserves900 SAR, comprising600reported paid and300adjustment, with one allocation and no bank/cash allocation. Zero recorded cash allocation is not proof of a zero real bank balance.
Compare advice conservation with absent bank evidence · 2026-10-18. Current audited MANSOQ application in an isolated local synthetic training environment. Official local advice ingestion conserves900 SAR, comprising600reported paid and300adjustment, with one allocation and no bank/cash allocation. Zero recorded cash allocation is not proof of a zero real bank balance.

2. Ingest the advice through canonical finance

Record the advice identity, total, received time, currency and line-level reported paid/adjustment amounts with match keys. The reconcile action deduplicates and reports matched and unmatched lines.

3. Review unmatched lines

Inspect suspense amount, unresolved amount fields and exceptions. Use the actual claim identifiers and evidence; do not attach a line to the nearest plausible claim.

4. Check balance identities

Read advice conservation independently of bank cash conservation. A received advice establishes what the payer reported, not what the provider’s bank received.

The demonstrated advice was created through the official local ingestion service with one explicit claim-number match: 600 SAR reported paid plus 300 SAR adjustment conserves a 900 SAR advice. Replaying the same request created no second allocation. No bank transaction or cash allocation was fabricated; a zero recorded cash allocation does not establish a zero real bank position.

The remittance-specific chain preserves600reported paid,300reported adjustment and the explicit claim_number match at precedence 10. Empty generic tariff candidates are unrelated to this remittance matching decision.
Read the remittance claim-match reason · 2026-10-18. Current audited MANSOQ application in an isolated local synthetic training environment. The remittance-specific chain preserves600reported paid,300reported adjustment and the explicit claim_number match at precedence 10. Empty generic tariff candidates are unrelated to this remittance matching decision.

Canonical route requirement

Legacy episode remittance posting is explicitly disabled. Use canonical RCM finance for advice, bank cash, settlement, reversals and payment notices.

Expected outcome

The system retains distinct advice allocations, matched lines and suspense. Confirm bank cash in the separate workflow before interpreting claim paid balances as realized receipts.

What the current screenshots demonstrate

These are current captures from an isolated Polyclinic training environment, using explicitly fictional insurance, response, authorization, remittance and policy fixtures. They demonstrate the displayed controls and scoped observations only. They do not establish live payer connectivity, a genuine insurer approval, regulatory qualification, production tax filing, a complete role/facility matrix or a cleared financial estimate.

Troubleshooting

The advice arrived but cash is unknown

Leave the bank position unknown and follow treasury’s bank-receipt workflow. Do not replace unknown cash with zero or mark the claim paid from advice alone.

Source evidence

References are pinned to the private MANSOQ source repository. Repository access is required to open these links.