How Expense Rebilling Status Works

Every logged expense carries one of three rebill statuses — unbilled, rebilled, or non-rebillable — and that single field is what determines whether an expense is still available to attach to a client invoice. This article covers what each status means, how an expense actually gets attached to an invoice as a reimbursable line item, and why an expense can't accidentally end up billed twice.

The Three Statuses

Every expense starts as unbilled the moment you log it — this is the default, and it means the expense hasn't been attached to any invoice yet and is available to be. Rebilled means the expense has already been added to a specific invoice as a line item; it carries a timestamp recording exactly when that happened. Non-rebillable is a status you set manually for expenses that were never meant to be passed on to a client at all — internal costs, overhead, anything you're tracking for your own records but don't intend to invoice for.

How an Expense Actually Becomes an Invoice Line Item

Rebilling isn't a background process — it happens the moment you select one or more unbilled expenses and attach them to a specific invoice. When you do, each selected expense is converted into a line item on that invoice: quantity of one, rate equal to the expense amount, and a description built from the vendor name, the category, and the expense date, so the client sees exactly what they're being asked to reimburse rather than an unlabeled dollar figure. The invoice's subtotal, tax, and total are recalculated immediately to include these new items, in the same transaction that updates the expenses — there's no separate step where the invoice total lags behind what was just added.

Why the Same Expense Can't Get Billed Twice

When expenses are selected for rebilling, the system only considers ones that are either completely unattached to any invoice or already attached to the specific invoice you're currently working on — not expenses tied to a different invoice entirely. In the same transaction that adds the line items, each expense's rebill_status flips to rebilled, its rebilled_at timestamp is set, and its invoice_group_id is recorded. Because that update happens as part of one atomic transaction alongside the invoice change, an expense can't end up rebilled on the invoice's side while still showing as unbilled and available elsewhere — the two changes succeed or fail together.

What Happens If You Try to Rebill an Already-Rebilled Expense to a Different Invoice

Once an expense's invoice_group_id points to Invoice A, it's excluded from the pool of expenses eligible to be added to Invoice B. The filter used when selecting expenses to rebill explicitly checks for either no invoice attached or the invoice you're currently working with — an expense already spoken for by a different invoice simply won't come back as an eligible result, so there's no accidental double-billing to catch after the fact; it's structurally excluded from the start.

Reversing a Rebill

If you need to remove a reimbursable expense from an invoice — the invoice was voided, or the expense shouldn't have been included — that's a manual correction on both sides. The line item needs to be removed from the invoice, and the expense's status needs to be reset (typically back to unbilled) so it becomes eligible for billing again. The system doesn't automatically detect that a line item was deleted from an invoice and un-rebill the corresponding expense on its own; that link, once made, has to be manually undone if the billing changes.

Frequently Asked Questions

Can I attach a non-rebillable expense to an invoice anyway? The status is meant to reflect your own categorization of the expense, not a hard system lock — but the rebilling flow is built around selecting from unbilled expenses. Marking something non-rebillable is really a way to keep it out of your own view of "what's still available to bill," rather than a mechanism the system enforces against you overriding it deliberately elsewhere.

Does rebilling an expense affect the amount stored on the expense record itself? No. The expense's own amount field doesn't change — what changes is that a line item matching that amount gets added to the invoice, and the expense's status and linkage fields get updated to reflect where it went.

If I split one expense across two invoices, does that work automatically? No — rebilling attaches the full expense amount as a single line item on one invoice. Splitting a cost across multiple invoices would need to be handled by logging it as separate expense entries in the first place, each rebilled independently, rather than splitting one expense record after the fact.