Salla and Zid accounting mapping: orders are not one journal event

Map independent event families

• Order creation and changes: maintain the commercial order and line-item snapshot.
• Payment-status events: record collection evidence or customer advances according to the underlying facts.
• Delivery or fulfilment: evaluate revenue recognition and inventory movement.
• Cancellation, refund and return: distinguish payment reversal, commercial return, credit note and physical inventory return.
• Settlement: reconcile gross collections, platform or gateway deductions and the actual bank deposit.

Required identifiers

• Provider store and order IDs.
• Webhook event ID or deterministic idempotency key.
• Payment, shipment, return and refund identifiers when present.
• Jabr document, journal entry and ZATCA identifiers created from the event.
• Settlement and bank transaction identifiers used for reconciliation.

Controls before posting

• Reject duplicate delivery and payment events without creating duplicate entries.
• Do not create an invoice solely because an order exists.
• Require product/account mapping before inventory or revenue posting.
• Prevent the storefront and payment gateway from both recording the same collection.
• Leave unknown fees, foreign currency and unexplained settlement differences for review; never plug the difference.

Migration and replay

Choose a cutover timestamp, import the opening subledger position, then replay only events after the cutover. Reconcile orders, receivables or advances, inventory, provider clearing and bank deposits before enabling scheduled synchronization.