In this section · 2 articles

Billing permissions and server settings

Every Billing permission and what it allows, the server settings that decide currency, numbering, rounding, due dates and seller details, the scheduled tasks, and what the health check reports.

Applies to
Billing 2.0 and later
Who can do this
Administrator, Platform owner
On this page

Billing has no settings panel. What a person can do comes from their permissions, and how documents are numbered, rounded and dated comes from your Laramin's server configuration.

Permissions

All keys start with feature.bill.. In the role editor they're in three groups. Give them with a role. See Give someone a role.

The role editor with the Billing group expanded, showing the Commercial Documents, Payments and Tax Rules resources and their action cells, including Download, Issue and Refund under Other actions.

Commercial Documents

ResourceActionsAllows
billing_accountlist, viewBilling Accounts: the list and each account's page.
orderlist, viewOrders.
invoicelist, viewInvoices.
invoiceissueThe Issue action on a draft invoice.
invoicedownloadDownloading an issued invoice as a PDF. Kept apart from view because a PDF leaves your Laramin.
credit_notelist, viewCredit Notes.
ledger_entrylist, viewLedger.

There's no permission to create, edit or delete any of these, because no one can. See How Billing keeps your money records.

In Billing 2.0.0 the Invoices screen has no Download PDF button. Someone with invoice.download opens the PDF through its address, /admin/billing/invoices/<reference>/pdf, using the invoice's Reference.

Payments

ResourceActionsAllows
paymentlist, viewPayments: the list and each payment's page.
paymentrefundThe Refund action.

Payments can't be created, edited or deleted on screen with any permission.

Tax Rules

ResourceActionsAllows
tax_rulelist, view, create, edit, delete, restore, removeTax Rules: adding, changing, deleting, restoring and removing rules for good.
tax_rule_itemlist, view, create, edit, delete, restore, removeTax Rule Items under a rule.

If you upgraded from a Payment Gateway version that still had tax rules or payments, the old feature.pg.tax_rule.*, feature.pg.tax_rule_item.* and feature.pg.payment.* permissions were renamed to these, so every role keeps what it had.

Roles

Billing brings no roles. Create one for your finance team and give it the permissions above. See Create a role.

Server settings

These are set in your Laramin's server configuration (its .env file) by whoever hosts it. They apply to every business. A change applies to documents created from then on: amounts already stored are never recalculated.

SettingWhat it doesDefault
BILLING_DEFAULT_CURRENCYThe currency of a billing account created without one. Add-ons that know the customer's currency pass it instead.USD
BILLING_INVOICE_PREFIXThe start of every invoice number.INV, as in INV-2026-000001
BILLING_CREDIT_NOTE_PREFIXThe start of every credit note number.CN
BILLING_INVOICE_PADDINGHow many digits the counter has, for invoices and credit notes. Widening it later continues the series.6
BILLING_PAYMENT_TERMS_DAYSThe due date of an issued invoice, in days after the issue date, when the add-on that raised it set none. 0 means due on receipt. null means invoices have no due date and never become overdue.30
BILLING_OVERDUE_GRACE_DAYSExtra days after the due date before an invoice is marked Overdue. The printed due date doesn't change.0
BILLING_ROUNDING_MODEHow a half is rounded in Billing: half_up or half_even. Unset, Billing follows your Laramin's money setting.Unset
BILLING_TAX_ROUNDING_SCOPEline rounds each line's tax and adds them up. document applies each rate once to the whole document and spreads the result across the lines. The two can differ by a paisa or a cent.line

Seller details

What an invoice says it's from. Each one left empty falls back to the Company Settings field shown, if there is one. See System and company settings.

SettingPrinted asFalls back to
BILLING_SELLER_LEGAL_NAMEThe seller's name under Bill FromCompany Name
BILLING_SELLER_TRADING_NAME"trading as" after the nameNothing
BILLING_SELLER_TAX_IDTax ID, for example your GSTINNothing
BILLING_SELLER_REGISTRATION_NUMBERReg. No.Nothing
BILLING_SELLER_ADDRESSThe addressBusiness Address
BILLING_SELLER_ZIPCODEThe postcodeThe company postcode
BILLING_SELLER_EMAILThe emailBusiness Email
BILLING_SELLER_PHONEKept with the invoice, not printed on the PDFThe company phone
BILLING_SELLER_WEBSITEKept with the invoice, not printed on the PDFNothing
BILLING_SELLER_COUNTRYThe country codeNothing

An invoice keeps the details it was issued with. Without a legal name or an address, the invoice still issues and a warning is written to the server log. Without a legal name, its PDF shows Seller details are not configured. under Bill From.

Careful: If you're registered for GST or VAT, set BILLING_SELLER_TAX_ID before you issue your first invoice. An issued invoice can't be changed to add it.

Invoice PDFs

PDFs are produced in English. Billing's screens are translated into more languages, but the PDF engine can only draw Latin, Greek and Cyrillic letters, so a PDF asked for in another language comes out in English.

Scheduled tasks

Billing adds three tasks to your Laramin's scheduled jobs. They run only while scheduled jobs run. Developer Tools › Scheduler shows when each job last ran. If they don't run, see Scheduled jobs don't run.

TaskRunsDoes
bill:reconcile-paymentsEvery 15 minutesAsks each provider what happened to payments that stopped moving, in case a gateway's notification never arrived.
bill:expire-paymentsHourlyCloses checkouts whose window has passed as Expired.
bill:mark-overdueDailyMarks issued and partly paid invoices whose due date, plus any grace days, has passed as Overdue.

Health check

Laramin checks every enabled add-on every five minutes, and Addon Management shows Billing as Unhealthy when one of these is true. See Add-on statuses.

Message starts withMeans
Billing is enabled but its tables do not existBilling's database changes haven't run.
The PaymentProcessor port is unbound, or Another module has bound PaymentProcessorPayments can't be taken, or another add-on is trying to record them. Contact your Laramin provider.
… provider reference(s) are shared by more than one paymentTwo payments carry the same provider reference, so the gateway's notifications for them can't be applied.
… callback(s) arrived on the legacy driver-only URLA gateway still sends notifications to its old address and you have more than one merchant account for it. Give the provider the account's own callback address from its Payment Gateway screen.
… payment(s) have been pending for over 24 hoursThe 15-minute task isn't resolving them. See A payment is stuck, or can't be refunded.
… payment(s) need attentionA payment can't move on by itself, most often because its gateway's add-on was removed.