Hybrid billing and electronic invoicing
Every client charges differently, and the lab keeps bending the contract to fit the system. Public contracts ask for a measurement statement. The monthly client wants the advance installment. The one-off analysis bills only when the work order closes. Here all three models run side by side, and the invoice is born from what operations already delivered, not from someone re-keying.
Bill the way each contract demands.
Build the invoice from the work order line items (samples, parameters) or group by service. You do not bend the contract to fit the system; the system adapts to the contract.
The invoice comes from the contract or the work order, no gaps.
An installment contract generates the invoices in advance and links each completed work order to the available installment. Without a contract, the completed work order bills on the spot. No revenue left behind.
Issue the electronic invoice without leaving the system.
The customer electronic invoice (Brazilian NF-e) goes out using your A1 digital certificate, straight from here. No exporting XML, no re-keying in a separate issuer.
Measurement statement ready for public tenders.
Comes simple or with analytical parameters, the way public contracts usually require, with email delivery and batch generation.
A group with several entities bills from any of them.
More than one company? Bill from any of your registered CNPJs (Brazilian tax IDs), on the same screen, without switching systems.
The due date works itself out.
It is calculated from the contract rule (after approval, after issue, after collection or a fixed day of the month). Nobody has to remember to count days.
The analyzed sample shows up as an invoice line.
The parameter and sample type the lab ran drop into the invoice as a line, with the price from your catalog. What was done is what gets billed.
The client gets the invoice with the lab's identity.
Generate the document with your branding to attach, send or print. The bill arrives looking professional, not like a loose email.
Contract billing, the way the public sector asks for it
A government contract has its own billing rules, and that is where the spreadsheet usually bleeds. Here the measurement cycle lives inside the contract.
Measurement statement tied to the contract.
The statement comes from the contracted scope, simple or with parameters, so you do not rebuild the document every billing period.
Installment and work order talk to each other.
Each completed work order draws against the contract's available installment, so the advance does not bill the same service twice.
A due date that follows the tender rule.
After approval, after issue or a fixed day: the system calculates the date the way the contract asks, with no mental math.
Frequently asked questions
Can I bill different clients in different ways?
Yes. One client bills per completed work order, another per advance contract installment, another per measurement statement. All three models run at the same time, each contract with its own rule.
Does the electronic invoice really come out of the system?
Yes. The customer electronic invoice (NF-e) is issued with your A1 digital certificate, straight from here. No exporting XML to an outside issuer, no re-keying.
I have more than one tax ID. Can I choose which one bills?
You can. Bill from any registered tax ID on the same screen, without switching systems or keeping a separate record per company.
Do I have to calculate the due date by hand?
No. The due date comes from the contract rule: after approval, after issue, after collection or a fixed day of the month. Nobody counts days.
Stop running your LIMS and ERP as two systems.
See the work order become an invoice, the P&L update and the electronic invoice go out, live, with your lab's routine. Book a demo and find out how much time and revenue you leave on the table running two systems.