Understand billing, orders and credits

Distinguish an order from a check #

An order records a purchase or payment workflow. A check records an applicant’s progress. Paying for an order does not complete applicant details, identity review or the DBS process. Multiple checks may relate to purchased credits depending on the selected product.

Use the current order and checkout screens for amounts, taxes, fees and availability. Tutorial examples and chat are not a price quotation. Do not rely on an amount copied from an old conversation.

Organisation credits #

In prelaunch, adding checks uses isolated practice capacity rather than a paid checkout. Practice capacity is not a paid credit balance, and a simulated order does not demonstrate live charging. The credit and payment workflows below apply only where the workspace explicitly enables them.

Organisation credits can be purchased, reserved for a request and consumed according to the workflow. Availability depends on the pool status, check type, remaining quantity and expiry. A displayed historic purchase total is not necessarily the number available for a new request.

A supported AI check request reserves an existing eligible Basic credit only after explicit approval and a current availability check. If credit availability changes before approval, review a new proposal or return to Billing.

Review an invoice #

1. Open Billing in the intended account perspective.
2. Find the order or invoice by its reference and date.
3. Check the amount, currency and status.
4. Open the available invoice or order detail screen.
5. Use its download control where your permissions allow it.

An organisation member without billing permission may not see these records. An individual account shows its own purchases, not the organisation’s invoice history.

Payment problems and refunds #

Use the dedicated checkout for payment authorisation. Never paste card numbers, security codes or payment credentials into chat. If payment appears interrupted, inspect the existing order before starting another purchase.

Refunds require their supported workflow and eligibility review. AI can explain where to look but does not approve refunds or change payment outcomes. In the public demo, invoice and payment examples are synthetic and no money moves.

Detailed walkthrough #

1. Match the financial reference

Read the reference, date and amount together before opening a financial record. Two records can have similar values. Confirm the selected record belongs to the order or payment you intend to inspect; sample totals do not represent money taken.

2. Read the payment status

Check the status and any refund information alongside the amount in the detail view. A financial record describes payment activity; it does not establish that an application has been submitted to DBS. Use the related check separately to understand application progress.

3. Resolve a billing question

Keep the invoice or payment reference when asking about an unexpected amount. Read the items and recorded status before attempting another order. Never include card details in a support request. The tutorial only reads a fictional record and cannot issue a refund.

Practise this section #

Open Help & tutorials, select this guide and choose Start practice walkthrough. Read each highlighted component before continuing. Use Back to revisit an explanation and Retry if a sample has not loaded. The walkthrough uses fictional records; do not enter real applicant information.

Use Exit tutorial to leave and keep your place, then Resume walkthrough in this guide to continue. When returning from practice to a real workspace, review the actual record and your permissions before making a change. Tutorial completion does not perform the underlying task.

Before using this guide #

Open Billing for the organisation or Payments for your individual account. Have the order, invoice or payment reference available; never provide card credentials to the tutorial.

Worked example #

If two payments have the same amount, compare their dates and references before opening one. A recorded refund and the original order are financial history, separate from the current check stage.

Guided component walkthrough #

Each component has one short guided step. Read the explanation, then choose Next; Back revisits the previous component. The cursor only demonstrates useful navigation or an explicit action. Replay action repeats that demonstration, and Skip animation keeps the explanation. Use this written guide for feature details.

Main walkthrough

Billing

• Billing: Invoice, Date, Amount, Status, Refunded and Receipt, one row for every order your organisation has placed.
• Read the table headings: The headings tell you what each billing record value means. Read across one row rather than comparing values from different rows; this keeps the identity, status and other details associated with the correct record.
• Open the intended record: Use the open control on the intended billing record row to inspect its details. Check the row identity first. Opening details lets you read more information without assuming that the record needs a change.
• Match the financial reference: Read the reference, date and amount together before opening a financial record. Two records can have similar values. Confirm the selected record belongs to the order or payment you intend to inspect; sample totals do not represent money taken.
• Open an invoice: The opened invoice shows the order behind the selected billing row. Confirm its financial reference before reading the amount and payment state; opening these details does not take a payment.

Invoice details

• Invoice details: The record lists what was ordered and what it cost. This invoice is fictional; nothing has been charged.
• Read the payment status: Check the status and any refund information alongside the amount in the detail view. A financial record describes payment activity; it does not establish that an application has been submitted to DBS. Use the related check separately to understand application progress.
• Resolve a billing question: Keep the invoice or payment reference when asking about an unexpected amount. Read the items and recorded status before attempting another order. Never include card details in a support request. The tutorial only reads a fictional record and cannot issue a refund.

Individual walkthrough

Payments

• Payments: Your own payments, newest first, each with its reference, date and amount. Your organisation's orders are not shown here.
• Read the payment fields: Each payment card shows its description, receipt number and date, with amount and status beside them. Read these together to identify the payment before opening the receipt.
• Open the intended record: Use the open control on the intended payment card to inspect its receipt and details. Confirm the receipt number and amount first; opening the card does not request a refund or make a new payment.
• Match the financial reference: Read the reference, date and amount together before opening a financial record. Two records can have similar values. Confirm the selected record belongs to the order or payment you intend to inspect; sample totals do not represent money taken.
• Open a payment: The opened payment shows the record behind the selected card. Confirm the receipt number, amount and date before using its details to follow up a billing question.

Payment details

• Payment details: The record lists what was paid for and when. This payment is fictional; nothing has been charged.
• Read the payment status: Check the status and any refund information alongside the amount in the detail view. A financial record describes payment activity; it does not establish that an application has been submitted to DBS. Use the related check separately to understand application progress.
• Resolve a billing question: Keep the invoice or payment reference when asking about an unexpected amount. Read the items and recorded status before attempting another order. Never include card details in a support request. The tutorial only reads a fictional record and cannot issue a refund.

Related guides