--- title: "Financial - Online Orders" url: "https://help.aurapos.com/en/article/financial-online-orders" language: "en" last_updated: "2026-10-26T13:39:05.855Z" --- # Financial - Online Orders See every online order that reached your store through your delivery and ordering partners, whether it was rung up successfully or failed. The report shows why an order failed and whether someone rang it up again by hand, so no order falls through the cracks. It is for store managers and franchisees. Updated Mon 26 Oct 2026 ## Running the report 1 Open **Reports** and choose **Online Orders** under **Financial**. 2 Set **Select your start date** and **end date**. Both start as today. Check that **Store** is the store you want. 3 Run the report. You get one page for each ordering partner, then four charts. Click an order to open its full details. **Tip**Run it every morning for yesterday, or once a week. Any order in red under **Failed online orders (automatically voided)** is an order your customer paid for or expects that never reached your till. Make sure each one was rung up by hand. ## Report options ### Select your start date The first trading day to include. The default is today. ### end date The last trading day to include. The default is today. The whole of this day is included, up to your close of trade. ### Store The store the report is run for. It is filled in for the store you are working in. **Close of trade**If your store's trading day ends after midnight, the report follows your trading day, not the calendar day. A footnote at the bottom of each page tells you when your trading day ends. Times on the report are your store's local time. ## The report at a glance BOB'S BURGERS  |  BOB'S BURGERS TIMES SQUARE Online orders report **Mon 19 Oct 2026** 00:00   to   **Sun 25 Oct 2026** 23:59 The two dates are the first and last trading day you asked for. Every order placed between them is included. 1. [Orders by partner](https://help.aurapos.com/en/article/financial-online-orders#orders): every order, grouped by ordering partner, then by whether it worked, then by status. 2. [Partner totals and recon](https://help.aurapos.com/en/article/financial-online-orders#totals): totals for each partner, and a check that every failed order was rung up by hand. 3. [Charts](https://help.aurapos.com/en/article/financial-online-orders#charts): four pie charts on the last page. 4. [Order details](https://help.aurapos.com/en/article/financial-online-orders#detail): click any order to see all of its information. ## Orders by partner Each ordering partner (the delivery or ordering company that sends you orders) starts on a new page. Inside a partner, orders are split into **Successfully rung up in Counter POS** and **Failed online orders (automatically voided)**, then by status, oldest first. | Date and time | Invoice # | Order # | Sales channel reference | Is paid | Paid online | Turnover (incl) | Special order found? | | --- | --- | --- | --- | --- | --- | --- | --- | | Quickbite 1 | | | | | | | | | Successfully rung up in Counter POS 2 | | | | | | | | | Status: Automatically accepted 3 | | | | | | | | | 19 Oct 26 12:41 4 | 3-10421 | 3-57 | Q-48211 | ✓ | ✓ | 185.00 | \- | | 19 Oct 26 18:05 | 3-10488 | 3-84 | Q-48307 | ✓ | ✓ | 242.50 | \- | | 20 Oct 26 19:32 | 3-10560 | 3-31 | Q-48395 | ✓ | ✓ | 312.00 | \- | | Automatically accepted subtotal: | | | | | | 739.50 | | | Status: Manually captured special orders | | | | | | | | | 20 Oct 26 20:15 | 3-10571 | 3-40 | Q-48402 | ✓ | | 130.50 | \- | | Manually captured special orders subtotal: | | | | | | 130.50 | | | Successfully rung up in Counter POS total: | | | | | | 870.00 | | | Failed online orders (automatically voided) | | | | | | | | | Status: Item not found | | | | | | | | | 20 Oct 26 20:02 5 | 3-10568 | 3-39 | Q-48402 | | ✓ | 130.50 | Yes | | Item not found subtotal: | | | | | | 130.50 | | | Status: No invoice generated | | | | | | | | | 21 Oct 26 13:10 | No Invoice | | Q-48471 | | | 96.00 | No | | No invoice generated subtotal: | | | | | | 96.00 | | | Failed online orders (automatically voided) total: 6 | | | | | | 226.50 | | ### 1 Partner The ordering partner the orders came from. Orders you typed in by hand as special orders are listed under the partner that the sales channel you used belongs to, so they sit on the same page as that partner's online orders. A sales channel that is not linked to an ordering partner is listed under its own name. ### 2 Successfully rung up, or failed **Successfully rung up in Counter POS** orders reached your till and count as sales. **Failed online orders (automatically voided)** holds every order that was not automatically accepted. These did not make it: the system cancelled them, so they are not sales. Each one has to be rung up by hand as a special order. ### 3 Status The status says what happened to the order. The statuses are explained in the list below the mock-up. ### 4 Click an order for its details Click the **Date and time**, the **Sales channel reference** or the **Turnover (incl)** to open that order's full details. Click the **Invoice #** to open the invoice in the Invoice Audit report. **Is paid** and **Paid online** are ticked when they apply. ### 5 Special order found? Only failed orders have an answer. A green row with **Yes** means someone has rung up a matching special order. A red row with **No** means nobody has yet, so the customer's order may never have been made. ### 6 Subtotals and totals Each status has a subtotal and each of the two groups has a total. Amounts include value-added tax (or your country's equivalent sales tax) and the delivery fee. ### The statuses Automatically accepted The store accepted the order and it was rung up at your counter by itself. This is the only status in the successful group. Manually captured special orders Orders a person rang up by hand as special orders, for example to replace a failed online order. An order the system accepted is never listed here as well. Manual processing The order is being captured by the store manually. Manually accepted The order was captured by the store manually and then accepted. Invalid items A menu item or discount on the order is not available to your store, or more than one percentage discount was sent. Duplicate order The partner's reference for the order had already been used for an earlier order, so no new order was created. Item not found The store could not find an item on the order. Expired The store did not accept the order within 2 minutes of receiving it. An order the store had acknowledged but not accepted gets 30 seconds more. Error at store The store received the order but had an error saving or printing it, so the order was not placed. A common reason is that the till's receipt printer was switched off or out of paper. Invalid request The order sent by the partner failed validation: its time, totals, taxes, payments or sales channel. Cancelled at store The store received the order but it was then cancelled. Outstanding and Acknowledged The order is still on its way: received by the system but not yet by the store, or received by the store but not yet accepted. You only see these for orders from the last few minutes. They sit in the failed group until the store accepts them. No invoice generated The order failed so early that no order was created at all. Only limited information is available, and the **Invoice #** shows as No Invoice. For any failed order, the order's details page has a message that explains what went wrong and what to do. ## Partner totals and recon After the orders for each partner you get a summary box and a recon box. Recon is short for reconciliation: checking that every failed order was matched by a special order. | Quickbite totals | | | --- | --- | | Successfully rung up in Counter POS | | | Turnover: | 870.00 1 | | \# Orders: | 4 | | Average: | 217.50 | | 60.0% of Quickbite orders were automatically accepted. 2 | | | Quickbite online orders recon | | | | | --- | --- | --- | --- | | | Failed | Manually captured | Balances 3 | | Turnover: | 226.50 | 130.50 | No | | \# Orders: | 2 | 1 | No | ### 1 Totals for the partner **Turnover** is the value of everything successfully rung up for the partner, **\# Orders** counts those orders and **Average** is the turnover divided by the number of orders. ### 2 Automatically accepted The share of the partner's online orders that went through without anyone stepping in. Special orders typed in by hand are left out of this share. ### 3 Balances The recon compares the value and the number of failed orders with the value and number of manually captured special orders. When they are equal, the **Balances** show **Yes** on a green background. When they differ, they show **No** on a red background and something was not rung up, or was rung up twice, or the amounts differ. In the example, two orders failed but only one special order was captured, so both balances show **No**. **Check the red rows**Look for failed orders with **Special order found?** set to **No**. Those are the orders still to be rung up. ## Charts The last page has four pie charts. They add up the value of all orders in the period, across every partner. Is paid How much of the turnover is settled at your till and how much is not. Transaction type The turnover split by type of order, for example delivery or collection. Integration result Orders successfully rung up in Counter POS compared with failed online orders. Sales channel The turnover split by the sales channel the orders were rung up on. ## Order details Click an order on the list to open the **Online orders detail report** for it. The header shows the **Reference** of the order. | Order information | | General information | | | --- | --- | --- | --- | | Date and time | Tue 20 Oct 26 20:02 | Grouping | Failed online orders (automatically voided) | | Invoice number | 3-10568 | Status | Item not found | | Order number | 3-39 | Partner | Quickbite | | Payment information (incl vat) | | Sales channel | Quickbite | | Net sales | 130.50 | Sales channel ref | Q-48402 | | \+ Delivery fee | 0.00 | Transaction type | Delivery | | \= Turnover | 130.50 | Till Id | 3 | | \+ Tip | 0.00 | Shift number | 3-117 | | \= Total Amount | 130.50 | Is paid / Paid online | No / Yes | **Message.** Under the panels, failed orders show a message explaining what went wrong and what to do, usually that the order must be rung up by hand as a special order with the partner's reference, on the right sales channel. If a matching special order exists the message adds: Good News: A matching manually captured special order was detected. The last page, **Data for nerds**, shows the raw order data as received. It is meant for AuraPOS support. Net sales The turnover less the delivery fee. Total Amount The turnover plus the tip. ## Watch the video A short walkthrough of the Online orders report: choosing your dates, reading the lists and checking that failed orders were rung up. [Report walkthrough video](https://www.youtube-nocookie.com/embed/FosXKaFuvIA?rel=0) Can't see the video? [Watch it on YouTube](https://www.youtube.com/watch?v=FosXKaFuvIA). ## Frequently asked questions An order failed and we rang it up by hand, but Special order found? still says No. Why? The report matches a failed order to a special order by the partner's order reference. The reference you capture on the special order must be the one the partner gave you, written exactly as the partner sent it. The special order must also fall inside the dates you chose. Why do the Balances show No? The recon compares the value and the number of failed orders with the value and number of manually captured special orders for that partner. If any failed order was not rung up, or a special order was captured twice, or the amounts differ, or a special order was rung up on a sales channel that is not linked to this partner, the balances show No. Look at the red rows under the failed orders to find the cause. An order shows Paid online ticked but Is paid is not. Why? Paid online tells you the customer paid the partner online. Is paid tells you the order on your till has been settled. A failed order was paid online but cancelled at your till, so Is paid stays empty until the special order is rung up and settled. Why do I see only one line for an order that the partner sent several times? When a partner tries an order several times, the report shows the latest attempt only, so one order is one line. Manually captured special orders are never merged with online orders. Why is the turnover different from my sales reports? Failed online orders were cancelled, so they are not sales. The turnover on this report also includes the delivery fee, and the special orders typed in by hand are included. Sales reports follow their own rules for what counts, so compare the same trading days and the same sales channels. What does the footnote about trading days mean? If your store closes trade after midnight, orders placed between midnight and your close of trade belong to the previous trading day. The footnote shows when your trading day ends. The times printed next to each order are your store's local time. Why does an order show No Invoice and nothing in the Order # column? The order failed before your till created an invoice for it. Only the limited information the partner sent is available. Ring it up by hand as a special order using the partner's reference. ## Glossary Automatically accepted An online order that was rung up at your counter without anyone stepping in. Automatically voided A failed online order that the system cancelled by itself. It is not a sale and has to be rung up by hand. Balances The recon check that shows Yes when the failed orders and the manually captured special orders match in value and in number. Failed online order An online order that did not reach your till successfully. Integration partner The delivery or ordering company that sends you online orders. Is paid The order on your till has been settled in full. Manually captured special order An order a person rang up by hand as a special order, often to replace a failed online order. Online order An order placed by a customer through an ordering partner and sent to your store. Paid online The customer paid for the order online, through the partner. Recon Short for reconciliation: checking that every failed order was matched by a special order. Sales channel The channel an order is rung up on, such as delivery or a partner's own channel. Sales channel reference The partner's reference for the order, used to match failed orders to special orders. Special order An order rung up at the till with a special order reference, for example the partner's order number. Special order found? Shows Yes when a matching special order exists for a failed order, and No when it does not. Trading day The business day that runs up to your close of trade, which can be after midnight. Turnover The value of an order including value-added tax (or your country's equivalent sales tax) and the delivery fee.