Integrations and source ownership

• Meter reading system. Bring meter, period and consumption into meter runs for preparers to submit. Readings stay owned by the meter reading system.

• Payment provider and bank. Import receipts with their provider event identifier so duplicates are recognised, then verify them.

• General ledger or ERP. If the corporate ledger lives elsewhere, send posted journals from here using their operation keys.

• Operations and SCADA. Supply monitoring and leak detection stay in operations systems; agree how leak estimates reach billing as separate adjustments.

Each connection needs an agreed source of truth, a field mapping, an event identifier and a retry policy. Keep credentials in the approved secret store with the smallest scope that works. A repeated delivery must not create a second run, receipt or posting. Rejected records wait with their original identifier and a visible reason.

Reconcile imported readings and receipts with their source each day during the pilot. Test a duplicate payment file, a missing reading and a revoked credential before turning on schedules. Availability depends on each provider’s interface, commercial access and configuration.

Use the implementation plan to agree integration acceptance criteria.