01
Collect
Pulls time entries, disbursements, order data, receipts, and billing notes into one controlled run.
Your team Keeping source systems available and naming the billing owner.
Workflow stack · Billing recovery
Billable work captured, issued, and watched.
Billing Recovery turns scattered time, disbursements, orders, approvals, and tax fields into a controlled billing run. Scellus captures the work, reconciles the pack, chases exceptions, and keeps ageing visible; your team keeps the commercial judgement.
- Included
- Billable capture
- Included
- Exception chase
- Included
- LHDN-ready issue
Stack readout · billing line to issued record
Built for finance, operations, and commercial teams in document-heavy businesses where billing depends on proof, approval, tax readiness, and repeatable recovery discipline.
Where billing leaks today
There is work done. There is no clean run.
-
Billable work is scattered.
Time, disbursements, orders, and approvals sit across inboxes, spreadsheets, portals, and notebooks.
-
The bill is rebuilt by memory.
Finance has to ask what happened, what was chargeable, and which supporting record proves the line.
-
Disbursements surface late.
Receipts, courier fees, search fees, expenses, and pass-through charges arrive after the bill has gone out.
-
Approvals hold the run.
One missing sign-off delays a whole batch, so invoices leave late and collections start cold.
-
Ageing is discovered after the fact.
The report is updated when month-end closes, not when a bill is issued or a collection risk appears.
-
e-Invoicing becomes a deadline scramble.
MyInvois fields, SST treatment, and rejection fixes are handled at submission time instead of during the run.
Operating truth
Billing is not invoicing.
Billing is the controlled path from billable source record to approved issue, accounting export, ageing update, and evidence trail. The invoice is only the last artifact.
The stack
Six blocks. One billing run.
Billing Recovery runs the full public block sequence. It starts by capturing chargeable records, reads and verifies the billable lines, chases gaps, pauses for judgement, then delivers issued bills, accounting exports, ageing movement, and audit trace.
- 01 Collect
- 02 Read
- 03 Verify
- 04 Chase
- 05 Review
- 06 Deliver
02
Read
Reads line items, fee descriptions, charges, dates, tax hints, and supporting evidence from the source record.
Your team Confirming rate cards, billing rules, and service descriptions.
03
Verify
Matches each line to source: time, order, claim, receipt, matter, project, or approved scope.
Your team Setting write-off thresholds and approval rules.
04
Chase
Routes missing approvals, unmatched disbursements, and held lines to the owner who can resolve them.
Your team Answering approval and classification questions.
05
Review
Hands over a clean draft pack with exceptions separated, source evidence attached, and sign-off ready.
Your team Final commercial judgement and release approval.
06
Deliver
Issues the approved bill, submits where e-Invoicing applies, exports to accounting, and updates ageing.
Your team Owning collections policy and client relationship calls.
What you receive
Not a prettier invoice. A billing record.
The output is the evidence that billable work was captured, approved, issued, exported, and watched through recovery.
-
A draft billing pack with billable lines matched to source records before the run closes.
-
An exception list covering missing approvals, incomplete disbursements, write-offs, and lines that do not reconcile.
-
Issued invoices or e-Invoice submissions prepared against the approved bill and current field rules.
-
A clean accounting export for your GL, billing platform, or finance workflow without a second manual pass.
-
Ageing movement, days-to-bill, days-to-receipt, rejection rate, and recovery risks reported on a defined cadence.
-
An audit trail linking bill, source record, approver, exception decision, submission state, and export.
The transition
What changes when Scellus runs billing recovery.
From memory to source record
Today
The bill is assembled from people remembering what happened and where the supporting record might be.
We handle
We build the run from source records, match every chargeable line, and hold anything that cannot be proven.
Your team
Confirms rate cards, billing policy, and commercial exceptions.
From month-end rush to daily control
Today
Finance discovers missing lines and approvals when the billing deadline is already close.
We handle
We chase gaps during the run, not after it, so the draft pack is ready before the billing window closes.
Your team
Approves the pack and releases the bills.
From issued late to ageing watched
Today
The invoice goes out late and the ageing report catches up only after collections has already slowed.
We handle
We issue, export, and update ageing on the operating cadence, with recovery risks surfaced early.
Your team
Owns collection tone, escalation policy, and client calls.
From e-Invoice scramble to prepared fields
Today
MyInvois submission, SST treatment, and rejection fixes happen at the end of the process.
We handle
We prepare field mapping, validation, and submission status as part of the billing run.
Your team
Approves tax positions and classification rules.
Division of labour
We run the evidence. You keep judgement.
Scellus handles Your team owns
Capture time, disbursements, orders, receipts, and billing notes
Keep source systems available and name the billing owner
Read billable fields and prepare line-item structure
Confirm rate cards, service descriptions, and billing rules
Match lines to source records and flag gaps
Set write-off thresholds and approval rules
Chase missing approvals and incomplete evidence
Answer exceptions that require judgement
Prepare draft packs, e-Invoice fields, exports, and ageing updates
Approve release and own collections policy
Maintain the audit trail and monthly recovery report
Own who can access billing and debtor records
Compliance and data
Billing data stays traceable while it moves.
Billing, debtor, tax, staff, client, and operating records stay under PDPA 2010 and the 2024 Amendment. The workflow names source system, access owner, approval rule, retention point, and audit handoff before data moves.
Where LHDN e-Invoicing applies, MyInvois field preparation, validation status, SST classification, and submission trace are handled as part of the billing run, not as a separate scramble.
Audit traceability is part of the deliverable: bill, source record, approver, exception decision, issue state, export, and ageing movement linked in one log.
Integrations
We meet the billing stack you already run.
Accounting and billing
- Xero, QuickBooks, MYOB, AutoCount, SQL Account
- Practice-management and billing platforms
- Custom GL, debtor, and management-account exports
- Billing tables, spreadsheets, and internal ledgers
Source records
- Time-capture tools and timesheets
- Orders, scopes, claims, and project records
- Receipts, disbursement evidence, and shared folders
- Email, Microsoft 365, and Google Workspace
Tax and delivery
- LHDN MyInvois field preparation and submission status
- SST classification and tax-code checks
- Client billing portals where present
- WhatsApp Business API for approval and chase where appropriate
Operating cadence
Capture, reconcile, then recover.
Daily
Capture and reconcile
New billable lines, disbursements, and source records are pulled into the run and matched before they go stale.
Billable work visible while it is still recoverable.Weekly
Exceptions and approvals
Held lines, missing evidence, write-offs, approval gaps, and classification questions are reviewed with a named owner.
The billing pack does not wait on inbox archaeology.Monthly
Issue, export, and report
Approved bills are issued, e-Invoice status is tracked, accounting exports are prepared, and ageing movement is reported.
Billing closes as an operating report, not a reconstruction.Indicative scope
Issued enough to collect. Logged enough to prove.
Build phase
Four to eight weeks
Source-system access, rate-card and rule capture, matching logic, approval routing, e-Invoice field mapping, accounting export, parallel run, and go-live.Operating retainer
Ongoing billing operations
Daily capture and match, exception handling, approval chasing, draft-pack assembly, e-Invoice preparation, export, ageing report, and rule reviews.Final scope, duration, and fee are confirmed at the Workflow Review against billing volume, source systems, approval rules, tax requirements, export format, and ageing profile.
What clients ask first
The questions that decide whether billing is under control.
-
We already have accounting software. What does this add?
- Accounting software posts the invoice once it exists. Billing Recovery assembles the billable lines, matches them to source, chases missing approvals, prepares the issue, exports cleanly, and keeps ageing visible.
-
Is this only for law firms?
- No. The workflow fits any document-heavy billing environment where charges, evidence, approvals, tax fields, and collection risk are spread across systems. Where legal billing rules apply, we include them in the rule book.
-
How does this support LHDN e-Invoicing?
- We prepare the approved bill for MyInvois fields, validation status, SST classification, and submission tracking where e-Invoicing applies. Your team owns the tax position and final approval.
-
How quickly does billing come under control?
- Typical builds reach a clean parallel run inside four to six weeks and full handover by week eight. The Workflow Review confirms the number against volume, systems, billing frequency, and approval rules.
Find out what billing recovery would take in your team.
Start with the records charges come from, the people who approve them, and the finance system they post to. We will map the capture, reconciliation, e-Invoice readiness, export, ageing, and the first workflow to operate.