ISP Renewal: Match Every Service ID Before You Accept the Proposal
The carrier proposal says you have 42 services. Your invoice says 47. The network diagram shows 39. The site list includes two offices that closed last year.
Which number are you renewing?
Do not solve that question by accepting the carrier’s spreadsheet as the inventory. A proposal can price what the provider believes is active. It cannot confirm which circuit reaches which site, what the business still needs, which services are duplicated, or whether a requested disconnect ever reached the final bill.
Before you renew business internet, match every billed service to a location, technical purpose, owner, and contract decision. If a field is missing, the service is not ready for another term.
Build one service-level renewal file
Start with the signed agreement, every active order form, the latest proposal, at least several recent invoices, the carrier’s service inventory, your site list, network diagrams, IP records, firewall or SD-WAN configuration, open orders, and prior disconnect confirmations.
Create one row for every billed or proposed service. Do not group circuits into a regional total because they share a product name.
Capture these fields:
| Field | What to record |
|---|---|
| Provider service ID | The carrier’s identifier for the active service |
| Customer circuit ID | The label used in your network, monitoring, or asset system |
| Billing account and invoice line | Where the recurring charge appears |
| Service address | The actual installed location, including suite or building detail |
| Demarcation | The handoff room, floor, rack, or other usable location detail |
| Product and bandwidth | DIA, broadband, ethernet, wavelength, fixed wireless, managed router, static IP block, or another service |
| Business role | Primary, backup, voice, guest, payment, warehouse, cloud access, temporary project, or another defined purpose |
| Technical dependency | Firewall port, SD-WAN edge, public IP, VPN, allowlist, DNS, voice, monitoring, or routing dependency |
| Contract record | Order, term, renewal date, notice requirement, and commitment |
| Monthly charge | Recurring service, equipment, management, and related fees |
| Decision | Keep, correct, disconnect, reassign, replace, or investigate |
| Owner and due date | The person responsible for closing the decision |
The account total tells finance what the company pays. This file tells IT and procurement what the company is buying.
Match identifiers before you compare prices
A single circuit can carry several identifiers. The carrier may use a service ID, circuit ID, billing product ID, order number, location code, and customer account number. Your team may call the same service “Dallas primary” or label it with a firewall interface.
Do not assume similar names mean the records match. Prove the relationship.
For every row, trace the provider service ID to the invoice line, installed address, demarcation, network device, monitoring record, and signed order. If the carrier uses an underlying access provider, capture that provider’s circuit reference too.
This work catches problems that a price comparison misses:
- Two invoice lines may describe the same installed service.
- One circuit may be active but absent from the renewal proposal.
- A proposal may use an old address after an office move.
- A disconnected service may still appear on an invoice.
- A live backup path may be mislabeled as an unneeded circuit.
- A managed router, IP block, or construction charge may sit under a different service ID from the transport it supports.
You are not looking for a prettier spreadsheet. You are building a chain from contract to bill to location to network use.
Walk the exceptions instead of guessing
Any row that does not reconcile belongs in an exception queue. Give it an owner and a deadline.
A carrier representative can explain its records, but the provider should not be the only party deciding whether a service exists or matters. Have the site contact, network team, finance, and procurement confirm the physical, technical, billing, and contract records.
When remote evidence is weak, test or inspect the site. A carrier portal showing “active” does not prove that your equipment still uses the handoff. A monitoring system showing no traffic does not automatically prove the circuit is safe to disconnect. It may be a standby path that only carries traffic during failover.
Use simple exception states:
Missing from carrier records: Your network shows a service that the proposal or inventory does not list.
Missing from company records: The carrier bills a service that IT cannot map to a site or device.
Identifier conflict: The invoice, proposal, order, and technical record appear to describe the same service but use details that do not agree.
Status conflict: A service marked disconnected, pending, or inactive still appears active elsewhere.
Purpose unknown: The service exists, but nobody can confirm the workflow or continuity need it supports.
Do not bury these rows at the bottom of the renewal file. Put the unresolved quantity, monthly charge, location, and risk in front of the renewal approver.
Separate the service decision from the provider decision
First decide which services the business needs. Then decide whether the incumbent carrier, an alternative provider, or a different design should supply them.
Mix those decisions and the carrier’s current inventory becomes the requirement by default.
Give every service one disposition:
- Keep: The location, purpose, technical dependency, owner, price, and term are confirmed.
- Correct: The service is needed, but the address, speed, identifier, billing, equipment, support, or contract record is wrong.
- Disconnect: The service is no longer needed, and its technical and contract dependencies have been cleared.
- Reassign: The service remains useful, but the location, cost center, role, or owner must change.
- Replace: The need remains, but another provider, access type, capacity, or architecture fits better.
- Investigate: Material records still conflict, so the approver does not have enough evidence.
If two services are meant to provide continuity, confirm their primary and backup roles. Then use the internet circuit diversity buying guide to test whether they share a carrier, last mile, building entrance, equipment, or power dependency.
Inventory proof and diversity proof are different. You need both when the business is paying for resilience.
Clear the dependencies before disconnecting anything
An unused-looking circuit can still carry a public IP block, VPN tunnel, voice route, security sensor, payment device, guest network, vendor connection, or emergency failover path.
Before approving a disconnect, check:
- Current interface state and traffic history over a period that fits the business.
- Firewall, router, and SD-WAN configuration tied to the service.
- Public IP addresses, DNS records, vendor allowlists, certificates, and VPN peers.
- Voice, alarm, elevator, payment, camera, building, or operational services at the location.
- Monitoring, alerting, and support records.
- Equipment return, inside wiring, construction, and early termination obligations.
- The replacement service’s installation, acceptance, and tested failover status.
Do not issue the disconnect because the replacement order was accepted. Keep the old service until the new one is installed, documented, tested, and accepted.
If the carrier relationship is already tied up in a billing dispute or deadline, run a two-track telecom renewal plan. Protect continuity and competitive options while the disputed charges follow their own evidence path.
Rebuild the proposal from the approved inventory
Once the rows are reconciled, send the provider an approved service schedule. Ask for a revised proposal that maps every proposed item back to that schedule.
The proposal should make it possible to answer:
- Which current service ID is being renewed, changed, or replaced?
- Which new service ID or order will result from the change?
- What location and demarcation does it serve?
- What recurring and one-time charges apply?
- Which equipment, IP, support, or managed services are included?
- What term, commitment, notice, and price change applies to that specific service?
- Which current services must remain active during migration?
- Which services will be disconnected, by whom, and on what evidence?
Check the math from the rows up. The proposal total should equal the approved services and charges. If the total only works after an unexplained credit or a quantity that nobody can reproduce, the proposal is not ready.
Price the current billed estate, the cleaned proposal, and the steady-state cost after temporary credits end. Include installation overlap, equipment, construction, support, applicable taxes and surcharges, and internal migration work.
A lower unit rate can still produce a worse renewal if it attaches a longer term to services you never confirmed.
Put the inventory schedule into the approval record
NIST Cybersecurity Framework 2.0 gives this work a useful control anchor. Its Asset Management category calls for inventories of managed services and supplier-provided services, priority based on criticality and business impact, and service management throughout the life cycle.
That is exactly the discipline a connectivity renewal needs. The inventory is not a one-time finance exercise. It should stay usable through installs, changes, moves, outages, renewals, and disconnects.
Attach the approved service schedule to the renewal record. Have legal or procurement confirm which document controls if the proposal, schedule, order form, and master agreement disagree.
After signature, assign owners for:
- Confirming new service IDs and billing start dates
- Updating network diagrams and monitoring labels
- Recording installed demarcation and equipment
- Verifying the first invoice against the signed schedule
- Tracking old-service disconnects through the final bill
- Reviewing inventory after site, network, or provider changes
A disconnect request is not completion evidence. Close the row when the service is out of use, technical dependencies are cleared, required equipment is handled, the carrier confirms the action, and the charge disappears as expected.
Make the approver see the uncertainty
The renewal decision should show more than the proposed monthly total.
Give the approver:
- Count and monthly cost by keep, correct, disconnect, reassign, replace, and investigate
- Material identifier, address, status, and billing conflicts
- Circuits that support critical or backup workflows
- Services waiting on a replacement installation or migration
- Unresolved contract, notice, or termination questions
- Current cost, cleaned cost, and steady-state proposed cost
- Named owners and dates for every remaining exception
Renew as proposed when the schedule is reconciled, the services still fit, dependencies are known, the proposal maps cleanly to the approved rows, and the contract supports the required changes.
Renew with written corrections when the provider still fits but identifiers, billing, service descriptions, migration steps, or disconnect treatment need to change.
Use a short bridge or competitive review when the deadline is close and material services remain unmatched. Do not convert unknown inventory into a long commitment because the proposal expires Friday.
The renewal starts with one blunt question: can you trace every proposed service to something the company can locate, explain, and approve?
If the answer is no, you are negotiating from the carrier’s records instead of your own.
If your business internet agreement is approaching renewal, request a Contract and Spend Risk Review. Bring the agreement, proposal, invoices, carrier inventory, site list, network records, open orders, and disconnect history. Catch Advisors will help you decide what to keep, correct, disconnect, replace, or compare before you sign.