Taxi Passenger Invoices: Minimum Amount, Paper Mail, and Electronic Delivery
A finished taxi trip is not a receipt finance will accept. The rider has a completed order and nothing they can submit. The desk then builds a spreadsheet process, or promises paper and email paths the product was never set up to run. Ptaxi’s taxi dispatch software documents passenger invoicing from the wallet: select taxi trip orders, meet the minimum invoice amount, request paper or electronic delivery, and view invoice history.
This is not a new fare engine, and it is not a wallet-funding article. Taxi passenger wallet top-up and billing details already covered custom-amount top-up and the income-and-expense list. Invoice was a short pointer there. Today’s card is the invoice path itself.
Why a completed taxi trip is not yet a receipt
Dispatchers close the job. The passenger pays with a configured in-app method or account balance, or settles cash at the curb. None of that automatically produces an invoice finance can file.
The documented request sits in the passenger personal center, under My Wallet, next to top-up and billing details. The passenger selects taxi trip orders, applies for an invoice, and can view invoice history. That is the passenger-facing contract in the list.
Do not treat a trip receipt screenshot, a billing-details row, or a driver-written paper slip as the invoice feature. Billing details are a list of income and expense records. The invoice path is a request against selected taxi trip orders, and it can be blocked by a minimum amount.
The list names taxi trip orders as the selectable set. It does not say a canceled job, an unaccepted timeout, or a cash trip is included. Confirm which orders appear in the selector in a demo, and write down what you see. Do not brief “every paid trip is invoiceable” as a product fact.
What the passenger requests, and the minimum that can block it
The passenger action is straightforward. Select taxi trip orders. Request an invoice. Open invoice history later.
The gate is the minimum invoice amount set in the backend. Admin invoice management can set that minimum for passengers. If the selected orders do not meet it, the request should not be briefed as if it will always go through. The list does not publish the default amount. It does not say the minimum is computed from distance, waiting time, or a company-level override. Open invoice management in a demo and write down the value your build actually uses.
That is the first tradeoff to say out loud. A high minimum cuts down on tiny paper jobs the desk cannot staff. It also leaves a rider who took several short taxi trips stuck until the selected total clears the bar. A low minimum is easier for the passenger and creates more review work on the paper path. The list does not sell a packaged threshold.
Train staff to show the minimum before they promise invoicing on a sales call. A demo tenant with the minimum set above the test fare will look broken. That is a configuration issue, not a missing module.
Paper review and mail versus electronic email
Admin invoice management splits invoice types into paper and electronic. The two paths do not share the same staffing model.
For a paper invoice, the passenger selects orders and applies. Customer service reviews the request. After approval, the invoice is issued and mailed. That review step is the documented desk work. The list does not name the review fields, the mail carrier, or a turnaround time. Do not invent a two-day SLA or a printed letterhead template. In a demo, submit a paper request, open the admin invoice screen, approve it, and write down what the passenger history then shows.
For an electronic invoice, invoices are managed through a third party. After the passenger selects orders and applies, the invoice is sent automatically to the passenger’s email address. The list does not name the third-party vendor, the email-address source, or a retry when the mailbox bounces. Confirm in a demo which email is used, and what the passenger sees if no email is on the account. Do not brief a branded e-invoicing network, a tax-authority connection, or a credit-card statement as this feature.
The tradeoff is operational, not cosmetic. Paper gives the desk a chance to catch a bad selection before something goes in the mail. It also creates a queue that can stall when customer service is busy. Electronic delivery is faster and does not need that review, and it depends on a third party plus a working email address. The list does not document a fallback from electronic to paper, or a button that reprints a mailed invoice. Do not invent one.
Invoice records on the passenger profile, and invoice settings
On the admin passenger list, staff can open a passenger’s details and see invoice records, along with account information, login and registration logs, and related orders. That is the support path when a rider says a request is missing. It is not a second invoice engine.
Mention the neighboring actions only to keep them off this card. Staff can also top up a passenger, suspend or unsuspend the account, issue coupons, and send a push. Those are other tools. This walkthrough stays on invoice records.
System configuration includes invoice settings, alongside payment-method controls, withdrawal settings, and other switches. The list names invoice settings. It does not publish the fields inside that screen. Open it in a demo and copy what you actually see. Do not brief a tax-ID form, a default invoice title, or a company seal upload unless that demo screen shows it.
Do not turn this section into a finance-ledger training. Order accounts and the payment ledger are different admin screens, already out of scope here. The invoice card is the request, the minimum, the paper-versus-electronic split, and the records staff can open on the passenger.
What not to promise on taxi passenger invoices
Do not invent the default minimum amount. Confirm it in a demo.
Do not say every taxi order is eligible. The selector is documented as taxi trip orders that meet the minimum. Canceled, unpaid, or cash jobs need a look in the demo, not a claim in the proposal.
Do not import designated-driver or car-rental invoice wording as if it were this list. Paper review plus mail, and electronic delivery to email through a third party, are documented here. A pending/success/failed application queue is not what this taxi screen is described as. Keep that shape off the taxi brief.
Do not name bank cards, credit cards, or a card processor. Passenger payment should be briefed as configured in-app payment methods and account balance. Cash settlement, when it happens, is a curb payment with commission taken from the driver wallet. That is not the invoice feature.
Do not claim a tax-authority integration, an itemized statutory invoice layout, or a packaged “weekly invoice run.” The list does not describe those. Do not spend this page on wallet top-up or billing-details columns. Link the wallet post, then return to the request.
A short ops checklist before you brief the app
Keep this to one page.
- In the passenger app, open My Wallet. Find invoice request and invoice history, next to top-up and billing details. Select taxi trip orders and submit one test request that meets the minimum, and one that does not. Write down what the app does in each case.
- In admin invoice management, confirm staff can set the minimum invoice amount. Note the paper and electronic types.
- Submit a paper request. Confirm customer service can review it, and that approval is followed by mail issuance. Write down the statuses you see; do not brief invented labels.
- Submit an electronic request. Confirm it is sent to the passenger’s email through the third-party path. Note which email address was used, and what happens if that address is missing.
- On the admin passenger list, open the test passenger and find invoice records. Use that screen as the support lookup, not as a second request form.
- Open system configuration and find invoice settings. Copy the fields in front of you. Do not add settings the list does not name.
Close
Taxi invoicing is a wallet request against taxi trip orders, gated by a minimum amount, with two delivery paths that do not cost the same to staff. Paper invoices need a customer-service review and then go out by mail. Electronic invoices are issued through a third party and sent to the passenger’s email after the request.
If you run a taxi or dispatch company and finance keeps asking why a completed trip still is not a fileable invoice, walk this path in a taxi dispatch software demo. Bring a test passenger, a fare that clears your minimum, and one that does not. Then decide whether paper review, electronic email, or both belong in the launch brief. If you want a walkthrough on the same wallet’s top-up and billing list, use the passenger wallet post, and come back here for the invoice card. You can also contact Ptaxi when you want that demo scheduled.
Frequently asked questions
Can passengers invoice taxi trips from the app?
Yes. In My Wallet, the passenger can select taxi trip orders and request an invoice, then view invoice history. Invoicing has to meet the minimum invoice amount set in the backend. The list does not say every unpaid or canceled trip is eligible. Confirm which orders appear in the selector in a demo.
What is the difference between paper and electronic taxi invoices?
After the passenger selects orders and applies, a paper invoice is reviewed by customer service and then mailed. An electronic invoice is managed through a third party and, after the same kind of request, is sent automatically to the passenger’s email address. Do not brief a card-network billing product. Passenger payment on this line should be described as configured in-app payment methods and account balance.
Who sets the minimum invoice amount?
Admin invoice management lets staff set a minimum invoice amount for passengers. System configuration also includes invoice settings. The list does not publish a default amount, a per-company override, or a rule that the minimum is calculated automatically from trip distance.
Is this the same as the passenger wallet top-up and billing-details post?
No. Top-up and billing details already have their own walkthrough. Invoice request lives in the same wallet, but this article is the invoice card: the minimum amount, paper review and mail, electronic delivery to email, and invoice records on the passenger profile. Keep those rehearsals on separate cards.