Overview
bLIS generates B2B invoices for completed laboratory work. Billing is based on ordered tests, panels, and fees on an accession — not on payment collection inside the product. Each billing cycle produces:- One invoice per billed client organization that has pending charges
- Optionally, a master invoice (Excel) that aggregates every line item across those clients
How billing works
- When you order tests or panels on an accession, bLIS creates billable instructions for those items (and fees such as STAT when applicable).
- After the accession reaches final status and has no open holds, those instructions become pending line items.
- On a schedule configured for your deployment, a billing run invoices every pending line item.
- Prices are looked up at invoice time and snapshotted onto each line item. Later catalog price changes do not alter invoices that have already been issued.
When work becomes billable
An instruction appears as a pending charge only when all of the following are true:
Cancelled accessions do not become final, so their instructions are not billed.
Pending charges accumulate until the next billing run. Finalizing an accession does not create an invoice by itself.
Who is billed
For each line item, bLIS chooses a single billing client:- Invoice override client on the test specification, if configured — that client is always billed for that test
- Else the accession Bill to organization, if set
- Else the accession primary client
How invoices are separated
Within a billing run, invoices are separated by billed client only.- The billable unit is an instruction (an ordered test, panel, or fee) — not the accession as a whole
- All pending line items for the same billed client go on one invoice, including charges from many accessions
- Each instruction is its own line item (with the accession ID shown for reference)
- There is no automatic split by accession, date range, receiving lab, or panel within a run
How pricing is determined
bLIS resolves the price for each pending line item when the billing run (or invoice preview) runs:
An Invoice override client changes who receives the invoice line, not which client’s price list is used.
For panel orders billed per accession, you typically get one line item for the panel at the panel price — not a separate charge for every constituent test.
Once an invoice is generated, line item prices are fixed on that invoice.
Billing mode
Tests and panels have a billing mode that controls how many charges are created when the work is ordered:
Reflex and other result-triggered orders are not fanned out per sample, even if the target test is configured to bill per sample.
STAT fee
When an accession priority is set to STAT, bLIS adds a STAT processing fee instruction. Clearing STAT removes that fee (if it has not already been invoiced). The amount uses the billed client’s STAT fee override when one is set (the Bill to client, if present). Leave the override blank to use the lab-wide STAT fee. Set the override to0 to waive the fee — no STAT line appears on the invoice.
Split billing
Split billing does not divide the dollar amount across clients, and it does not create additional invoices. It flags responsibility on the invoice:- On an accession, you can name organizations in split billing. Those appear in the invoice Split with column.
- On a client, you can configure a default split-billing organization. When that client is the primary client, pending line items can be flagged accordingly.
If a different organization should pay, use Bill to (or a test Invoice override client). Use split billing only when you need the invoice to show a shared-responsibility flag.
Excluding charges
You can keep work out of invoicing in several ways:
After an instruction has been invoiced, you cannot change its billed amount in bLIS. Adjust eligibility before the billing run.
What appears on an invoice
Client invoices typically include:- Invoice number and date
- Billed client (invoice to)
- Line items with accession, subject identifiers (shown as Donor ID, UNOS ID, and Alternate ID), description, optional sample custom fields configured for invoices, Split with, date, and price
- Invoice total (sum of line item prices)
Formats
Your lab sets the default org invoice format in admin billing settings. Master invoices are always Excel.
Master invoices and notifications
When master invoicing is enabled, each billing run also produces a master invoice: one Excel file with every line item from the run, including which client was billed. This is meant for internal finance review alongside the per-client invoices. Notification behavior depends on your lab settings:Key fields
Related
Accessions
Accessions must reach final status before their charges can be invoiced.
Holds
Open holds keep an accession’s charges out of invoicing.
Test specifications
Configure prices, billing mode, and invoice override clients.
Reports
Reporting finalization relates to when an accession can become final.