FlyAkeed
Supplier Reconciliation & Payment Settlements
Traacs spine × Supplier SOA × Payment proof · SAR · 2025–2026
Data as of 2026-07-14
Dashboard
Year
Quarter
Month
Supplier search (drill table)

Variance categories

Matched (|Δ|≤SAR 1) Over-settled (paid > cost) Under-settled (paid < cost) Unmatched Credit/Refund

Settlement coverage by supplier

settled vs Traacs cost without settlement evidence
Settled (period)Outstanding (all-period exposure − settled)

Supplier reconciliation — drill-through

Click a supplier to expand its booking lines. Settled / variance reflect the selected period; Exposure / Outstanding are all-period.

Supplier detail

Data-completeness tracker

Logic & KPI Definitions — Supplier Reconciliation & Payment Settlements

Sources & grain

  • Traacs (spine): Sales Raw Data - Hotels 2025 + 2026, one row per booking. Join key = Voucher No (HV/OHV). Cost = net payable; Selling Price = customer amount.
  • Settlement / payment voucher: per-supplier Allocation/PV*.csv — each PV lists every booking it settled (Doc.No = Traacs Voucher No), Matched & Outstanding + proof.
  • Supplier SOA: supplier statement (Belbeds; Expedia EPS) — billed position & aging.
  • Payment proof: bank transfer slip PDF, linked by PV number.

Time filter

Year / Quarter / Month filter the settlement lines by their booking Doc Date. Settled, variance and match counts recompute for the period; Exposure & Outstanding stay all-period (a standing AP position). SOA aging & Expedia EPS are statement-level and shown in full.

Matching hierarchy

  1. Exact Voucher No — conf 100 (hotel match 99–100%).
  2. Supplier invoice / EPS statement ref — conf 95 (Expedia).
  3. Amount ± SAR 1 + date ± 3d — conf 75.
  4. Name similarity + amount ± 2% — conf 60 → needs review.
  5. No match → Unmatched / Missing-in-Traacs / Missing-in-SOA.

Variance categories

CategoryRule
Matched|Settled − Traacs Cost| ≤ SAR 1
Over-settledSettled > Cost (leakage / cost understated)
Under-settledSettled < Cost (credit / discount / still owed)
UnmatchedSettlement line with no Traacs booking

KPI definitions

KPIDefinition
Settled (paid)Σ Matched amount across payment-voucher lines (period)
Traacs cost (matched)Σ Traacs Cost for those bookings
Net varianceSettled − Traacs cost
Over / Under-settledΣ positive / negative per-line variance
Match ratematched ÷ total settlement lines
ExposureΣ Traacs Cost for supplier (all bookings 2025–26)
OutstandingExposure − Settled = booked cost without settlement evidence in hand
CoverageSuppliers with any data ÷ Traacs universe (Hotels 111 · Cars 35)

Controls & exception handling

  • Exceptions log: every Over/Under-settled + Unmatched line → owner + status.
  • Review workflow: Preparer (Recon) → Reviewer (CoE/QA, Mshary) → Approver (Finance, Etman); 4-eyes on write-offs.
  • Segregation: booker cannot clear own exception.
  • Tolerance: auto-match ≤ SAR 1 / 0.5%.
  • Retention: 7-yr CTA / 5-yr general.
  • Completeness gate: "Reconciled" only when SOA + settlement + proof on file.

Data status (this build)

  • Live & reconciled: Belbeds, HotelBeds, TBO (settlement); Belbeds SOA; Expedia EPS three-way.
  • Awaiting data: 18 of 22 folders empty — incl. all Car suppliers.
  • FX: USD → SAR at realized Expedia slip rate 3.7695 (peg 3.75); original USD shown beside SAR.
Ref FA-OPS-RPT-2026-0002 · Prepared by Iqbal Basha. M · VP Operation and Sourcing · Traacs spine 2025+2026 · Generated 2026-07-14.
FlyAkeed Ref FA-OPS-RPT-2026-0002 · Operation & Sourcing · Prepared by Iqbal Basha. M · Generated 2026-07-14.