These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Electricity Billing System
- Who it's for
- Shared service accounting
Shared service accounting
A shared service team can keep organizations, team membership and counterparties distinct while reviewing banking instructions. Each instruction belongs to one organization, and the reviewer must act within that scope. A central analyst can work operation exceptions without changing the original approval.
How Electricity Billing System is set up for you
Instruction owner
Assign a preparer to each document and keep its organization, counterparty and amount visible during review.
Independent decision
Ask a reviewer to decide on the revision that was actually submitted and retain the reason.
Provider evidence
Keep external identifiers, statements and confirmations linked to the original instruction.
Exception owner
Give an analyst the unmatched movements and uncertain operation receipts to investigate.
A shared service team can keep organizations, team membership and counterparties distinct while reviewing banking instructions. Each instruction belongs to one organization, and the reviewer must act within that scope. A central analyst can work operation exceptions without changing the original approval.
Start with one organization, a small set of eligible counterparties and provider-held accounts, and a recent instruction that has a real provider response. Register the relevant team members and their roles. The preparer should record the instruction, its debit and credit lines and its supporting file. The reviewer should inspect the frozen revision before approving it. Follow the provider response into the receipt record and compare a movement against an account snapshot.
Run a second case with a delayed provider response or a mismatch between the applied amount and confirmed occurrence date. Leave the exception visible while the analyst checks the source event. This gives the team a concrete way to agree who investigates, which evidence resolves the item and when the document can be marked confirmed. Keep existing provider and ledger connections in the setup plan; the team should verify their returned references in the pilot.
[Plan implementation](/electricity-billing-system/implementation) around those cases and [review permissions](/electricity-billing-system/roles) before broad access.
Features to start with
Roles on the team
- Auditor
- Read authorized evidence and reports in a scoped, read-only audit view. No record writes and no action execution.
- App Administrator
- Maintain organization configuration and membership. Administrative membership does not confer approval, financial or execution authority and cannot grant an independent reviewer entitlement.
- Accounting Preparer
- Prepare assigned operational records and execute eligible reviewed actions. Own organization and draft scope only; accepted, posted and provider evidence is read-only; guarded workflows authorize every transition.
- Accounting Reviewer
- Review eligible document revisions independently and reconcile operational evidence. Approve or reject through guarded actions only; no unrestricted editing of protected or executed records; a reviewer cannot approve their own submission.
- Operations Analyst
- Works unresolved operation and reconciliation evidence without gaining document approval authority.
Set up Electricity Billing System your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.