Recent Tickets
| Date | Passenger / Group | PNR | Supplier | Due | Status |
|---|
Supplier Balances
Client Outstanding / Remaining Balance₨ 0
| Client Name | PNR | Ticket Sale | Received | Remaining | Payment Status | Slip Number(s) |
|---|
| Type | Party / PNR | Original | Received/Paid | Balance | Follow-up | Status | Action |
|---|
| ID | Date | Passenger | PNR | Agent / Party | Route | Sale | Paid | Balance | Status | Action |
|---|
Customer / Travel Agent List
| Customer / Agent | Phone | Tickets | Total Sale | Paid | Balance | Status | Action |
|---|
Search any passenger or PNR to see who owns the booking, how it
arrived, and who must be contacted after a flight change or
cancellation.
| Passenger / PNR | Booking Owner | Source | Contact | Flight | Update Status | Last Contact | Action |
|---|
| Date | Supplier | Slip No. | Payment Type / Allocation | Method | Note | Created By | Amount | Action |
|---|
| Ticket Date | Supplier | PNR | Passenger / Group | Purchase | Matched Payment | Remaining | Status | Matched Slip(s) |
|---|
Unmatched Payments / Supplier Advance
| Date | Supplier | Slip | Payment | Matched | Unmatched / Advance | Action |
|---|
Refund requests are maintained manually and stay separate from the Supplier Ledger. Applying a refund only records when/how the airline was contacted. A refund affects no supplier ledger balance automatically; adjustment is manual and optional.
| Date | Supplier | PNR | Passenger | Slip No. | Request Status | Applied Detail | Refund Amount | Adjusted Against | Refund Used | Fresh Payment | Customer Status | Action |
|---|
Profit = Sale Amount − Purchase Amount. Tickets with no Sale
Amount, Refund Pending or Refunded status are excluded from
recognized profit.
| Date | Passenger | PNR | Supplier | Purchase | Sale | Profit / Loss | Margin | Status |
|---|
| Time/Date | Type | Reference | Details | Cash In | Cash Out |
|---|
Recent Daily Closings
| Date | Opening | Cash In | Cash Out | Expected | Actual | Difference | Closed By |
|---|
| Departure | Time Left | Passenger | PNR | Route | Supplier | Status | Actions |
|---|
Admin compares the supplier's monthly statement with the system
ledger. A matched record can be verified and locked.
Mismatch Diagnostics
Reconciliation History
| Month | Supplier | System Balance | Statement Balance | Difference | Status | Locked By | Note |
|---|
Outstanding supplier debits are settled against the oldest items
first (FIFO). Use this report to see what is payable, receivable,
overdue and why.
Recommended Payment Plan
Outstanding Item Detail
| Priority | Supplier | Date | Age | Bucket | Reference | Reason | Original Debit | Outstanding |
|---|
Admin-only journal. Entries are never deleted; a wrong entry must
be reversed. Lock a completed supplier month to prevent back-dated
changes.
Journal History
| Date | Supplier | Type | Voucher | Reason | Debit | Credit | Status | Action |
|---|
Supplier Smart Control Panel — All Supplier Work in One Place
Click any supplier to open its account. Add payments and payment slips only inside that supplier account. Existing tickets, payments and historical data remain unchanged.
AL AMAL TRAVELS
Supplier Ledger Statement
Simple staff workflow: Smart Ticket Entry automatically creates the supplier row. Click Add Payment on that same ticket row, enter payment details, attach slip and Save. Passenger / PNR never need to be entered again.
Pending Reconciliation Dashboard
Work from the pending list first. Unlinked and partially linked payments stay here until reconciled. Linking is reference-only and never changes the supplier ledger balance.
| Date | Slip / Ref | Payment | Linked | Remaining | Status | Action |
|---|
Simple Ticket-wise Supplier Ledger — Newest First
Rows come automatically from Smart Ticket Entry. Passenger, PNR and purchase amount are read-only here. Add supplier payment directly on the same ticket row.
| Date | PNR | Passenger / Route | Purchase | Paid | Balance | Status | Slip / Payment |
|---|
| Date | Voucher # | Ref. # | Narration | Traveling Date | Debit | Credit | Balance |
|---|
| Date & Time | User | Action | Record | Details / Old → New |
|---|
Admin-only security record showing who accessed the system, when
they logged in or out, and the total session duration.
| User | Role | Login Time | Logout Time | Duration | Status |
|---|
ITEMS IN BIN0
RETENTION7 Days
NEXT AUTO CLEANUP—
| Deleted | Type | Record | Details | Expires | Action |
|---|
Live Backup Restored
Backup source: AL_AMAL_LEDGER_BACKUP_2026-09-08.json • 100 tickets • 85 supplier transactions • 24 customer receipts. Existing cloud records are preserved; only missing records are merged.
Weekly Email Backup
Schedule: Every Sunday at 10:00 PM Pakistan time. This requires the Netlify scheduled function and email service environment variables included with this build.
EMAIL TOalamaltravels.tourism786@gmail.com
LAST EMAIL BACKUPNever / not reported
LAST STATUSNot configured
Important: a browser-only HTML file cannot send an email by itself while the computer is closed. The scheduled Netlify function must be deployed and configured.
Download Backup
Save all tickets, payments and refunds in one backup file.
Restore Backup
Select a previously downloaded JSON backup.
Important
This system saves data in this browser. Take a backup regularly, especially before changing computer or clearing browser data.