Car Rental Store Finance: Order Accounts, Income Detail, and the Payment Ledger
A store manager who cannot see this week’s income will invent a spreadsheet. A platform finance lead who cannot tie a refund to a store will invent a chat thread. Ptaxi’s car rental software documents two admin views for that work, both under financial management. Order accounts compile financial data for each store and let staff open that store’s related order-income information, then drill into each order. The payment ledger records expense, income, top-up, and other transaction flow for users and stores, line by line.
Those are reports and records. They are not a bank connection, a payout button, or a tax-filing product.
The tradeoff is ordinary. If you leave these views unused, each store will keep a private workbook, and no two workbooks will use the same columns. If you oversell the screens as a live bank feed, finance will expect a nightly match to cash that the list does not describe. Train the fields you can open. Write any reconciliation rule as your procedure after you have watched a real store week in the build.
Order accounts are a store income view
Order accounts do two jobs, and you should keep them in that order. First, they compile financial data for each store. Second, they let you look at the related order-income information for a given store, including a details page for each order.
The compiled store row is already specific. It includes operating city, store name, store phone, passenger payment, store income, tax, coupon discount, platform commission, refund amount, completed order count, and an action to open details.
Read that list as a settlement snapshot, not as a live cash position. Passenger payment and store income are both on the row, so a store’s take is not assumed to equal what the renter paid. Coupon discount, platform commission, tax, and refund amount are recorded there as well, which is why a promoted booking or a refunded job can look different from a full-price completed rental. The earlier note on coupons and commission already covers how checkout discounts and commission rates can be configured. This article does not retell that configuration. It only points at the amounts this report stores after the fact.
Completed order count sits on the same row. It is a volume figure next to money figures. Do not turn it into a utilization rate or a fleet-availability score. The list does not add those.
The list also does not say how often the row refreshes, whether you can export it, or how the tax figure is calculated. In a demo, open a store you know, read every column, and write down what a refunded or couponed job does to the totals. Then stop.
The details page is income per order
From that store row, the details action opens a page where staff can view income for each order. The documented fields are order number, order time, passenger, order amount, store income, and order type.
This is the place to answer “which job made up that store total?,” not the place to re-price the rental. Order amount and store income both appear, so a single job can show what was charged and what the store was recorded as earning. Order type is a field; the list does not publish a type catalog here. Confirm the type labels in the build, and do not invent them in a sales script.
If a renter is arguing about a fee, this income detail is still not the exception-order file. Exception orders and appeals are a different queue, already described in exception orders and appeals. You may use an order number from this page to find the job. Do not brief order accounts as the dispute tool.
The payment ledger is the line-by-line record
The payment ledger records every transaction flow for users and stores — expense, income, top-up, and other recorded movements. Each line includes affiliated store, order number, username, transaction amount, transaction type, order type, title, transaction status, payment method, and transaction time.
That is a different question from the store income summary. Order accounts tell you how a store’s order income looks. The ledger tells you what individual movements were recorded, including top-ups that may not appear as store order income. Train staff to start from the question they actually have. “What did this store earn on completed rentals?” belongs on order accounts. “What was this payment, in this status, by this method, at this time?” belongs on the ledger.
Payment method is a field on the line. Transaction status is a field on the same line. Name them as fields. Do not turn payment method into a list of networks, and do not turn transaction status into a promise that the line is already reconciled to a bank statement. The list does not name a card scheme, and it does not describe a bank import.
Title and transaction type are also recorded. Use them to tell movements apart in a walkthrough, but do not invent a complete type dictionary beyond the documented examples of expense, income, and top-up. If your finance team needs a mapping to their own chart of accounts, that mapping is yours to write after you have seen the values in the build.
Neighboring finance queues to keep separate
The same financial-management menu also includes invoice management and deposit records. Keep both off this briefing except to say what they are not.
Invoice management shows invoice application information, including pending, successful, and failed applications. That is a different finance queue. This article is not an invoicing guide.
Deposit records track whether store and user deposits were paid and refunded. Vehicle deposits, violation deposits, and deposit refund already have their own write-ups, including vehicle and violation deposits and return inspection and deposit refund. Do not retell those flows here. A ledger line may mention an order that also has a deposit; that does not make the ledger the deposit-refund tool.
Platform commission configuration, including different rates with and without a coupon, plus tax in that configuration row, is likewise a setup task, not this report. Look at the recorded commission and tax amounts on the store income view. Change rates on the commission screen, not by editing the report.
What not to promise from these two screens
Do not promise real-time bank reconciliation, an automatic payout to the store, or a named card network. Do not sell the tax field as tax-filing software; it is a recorded tax amount on the store income view. Do not claim a statutory calculator, a filing calendar, or an export that satisfies an accountant’s software unless you have seen that export in the build — and the list does not describe one. Do not treat order accounts and the payment ledger as the same screen. Do not use this article to re-teach deposit refund, coupon setup, or exception-order handling. Do not invent payment-method brand names.
A short finance checklist before you brief a store
Keep this to one page.
- In admin financial management, open order accounts. Pick one store and read the full row: city, name, phone, passenger payment, store income, tax, coupon discount, platform commission, refund amount, and completed order count.
- Open details and walk at least one order. Confirm order number, order time, passenger, order amount, store income, and order type.
- Compare a full-price job with a couponed or refunded job, if you have both. Talk about the recorded amounts, not a formula you invented.
- Open the payment ledger. Find the same order number, then read transaction amount, type, status, payment method, and transaction time.
- Show one top-up or other non-order movement if the ledger has one, so staff see that the ledger is wider than store order income.
- Point at invoice management as a separate queue for pending, successful, or failed invoice applications. Do not run an invoicing drill in this session.
- Leave deposit refund and commission configuration on their own training cards.
If a script starts promising a bank sync or a tax filing, cut it back to the store row, the order detail, and the ledger line you can actually open.
Close
Store finance questions in car rental usually come in two forms. What did this store earn on its orders, including tax, commission, discounts, refunds, and completed volume? And what individual expense, income, or top-up movements were recorded, in what status, by what method, at what time? Ptaxi’s admin financial management gives you those two views: order accounts with a per-order income detail, and the payment ledger.
That is enough to stop a shadow spreadsheet, if you train the fields as they are. It is not enough to sell a bank feed, an automatic payout, or a tax product. Look at order accounts and the payment ledger in Ptaxi’s car rental software. If you want a walkthrough, ask for a demo and bring one store’s week, including a refund or a discounted job if you have one, then open the store row, the order detail, and the matching ledger lines.
Frequently asked questions
What does the store order-accounts report include?
Order accounts compile financial data for each store and let staff view that store’s related order-income information. The store row includes operating city, store name, store phone, passenger payment, store income, tax, coupon discount, platform commission, refund amount, completed order count, and a details action. The details page shows income for each order: order number, order time, passenger, order amount, store income, and order type. The list does not describe a bank feed or a tax-filing export.
How is the payment ledger different from order accounts?
The payment ledger records each transaction for users and stores — expense, income, top-up, and other recorded flow — with affiliated store, order number, username, transaction amount, transaction type, order type, title, transaction status, payment method, and transaction time. Order accounts summarize store income from orders. The ledger is the line-by-line record. Do not train them as the same screen.
Does the tax field mean this module files taxes for the store?
No. Tax is a recorded field on the store income view. It is not a tax-filing product, a return wizard, or a statutory calculator the list describes. If you need to know how the figure is computed, confirm it in a demo and write your own finance procedure. Do not sell this report as tax software.
Can this ledger reconcile to a bank account or pay the store automatically?
The list does not say that. Payment method is a field on each ledger line, and transaction status is a field on the same line. That is not real-time bank reconciliation, an automatic payout, or a named card network. Invoice management is also a different finance queue, covering invoice applications that are pending, successful, or failed.