Catering transaction: capture is not submission
A quote, cover estimate or advance-payment discussion is not proof of fiscal submission. Confirm the supported client-billing and settlement sequence; do not assume deposits automatically create fiscal invoices.
Cost recipes per portion, record event/client orders, bill clients and review credit collections, supplier purchases and expenses alongside sales.
Confirm setup before real-time submission
Configure the business fiscal details, item/tax classifications and enabled, initialized eTIMS settings. Only real-time submission mode submits through the settlement path. Manual mode or disabled/uninitialized settings must not be described as automatic submission.
KRA distinguishes system-to-system solution types including online OSCU and VSCU. This page describes the DineHQ product workflow, not a certification claim, eligibility decision or tax advice. Confirm your registration and obligations with KRA or a qualified adviser.
Pending, failed and confirmed are different states
A paid bill does not prove a successful fiscal submission. Connectivity or provider errors can leave a pending/retry or failed state. Inspect the sale's fiscal status, check configuration and the error, and use the supported retry/resubmit action where available.
Do not label a pending receipt as confirmed, invent a QR code or repeatedly create a new sale to resolve a fiscal failure. Reprint after successful submission to include the returned fiscal details. Offline order recording cannot guarantee online fiscal confirmation.
Check your actual operating workflow
Do not assume a specialist event planner, equipment-hire scheduler or deposit-to-fiscal-invoice automation. Confirm any advance-payment workflow before relying on it.
- Confirm cover count, portions and client billing terms.
- Re-cost recipes using current supplier prices.
- Record client bills and collections without confusing unpaid credit with cash.
- Record event labour and transport; compare the worksheet with actual costs.