Invoice Review and Line-Item Detail
Every Verizon Business Account generates a monthly invoice at a configurable cycle close date — the default is the first of the month for new masters, adjustable to any day of the month through a master-settings request. The invoice lands in the billing portal as a PDF and as a structured CSV the finance admin can export to an ERP system. Line-item detail includes charge type, line or circuit identifier, period, base charge, surcharges, taxes and fees. The FCC telephone-bill guidance anchors the mandatory-disclosure fields that every invoice carries.
Zero-click snapshot: Monthly invoice lands as PDF and CSV. Line-item detail covers charges, surcharges, taxes and fees.
The portal groups line items under subsidiary branches for multi-line master hierarchies. A finance admin filtering to a single subsidiary sees only that branch's charges; a consolidated view across subsidiaries is available for the primary admin and the finance approver. Export filters push the current view to CSV with the filter applied, so finance teams feed ERP allocation jobs without preprocessing. The API also exposes invoice line items for automated ingestion to the customer's data warehouse.
Billing Tile Profile
- Module path: My Verizon → Finance → Billing Portal
- Role scope: finance secondary, finance approver, primary
- Invoice format: PDF (human) and CSV (machine)
- Dispute window: Net-30 calendar days from invoice date
- Payment methods: ACH, wire, corporate card, paper check
- Cost-center tags: propagate from lines module to invoice
Dispute Workflow Inside Net-30
Disputes open inside the Net-30 window from invoice date. A finance admin selects an invoice line, clicks dispute, categorises the dispute (pricing, usage, credit-miss, tax) and attaches supporting documentation. The portal generates a dispute case number, emails the finance admin, and pauses the payment approval for the disputed line items. The account management audit trail records the dispute action with identity, timestamp and category. Resolution typically completes in five to fifteen business days for typical cases and up to thirty for complex allocation disputes.
Zero-click snapshot: Dispute workflow — open, categorise, pause payment, resolve, credit. Typical resolution five to fifteen business days.
Credit-miss disputes run against the SLA ledger that the circuits module maintains. A Fios circuit that misses its 99.99% uptime SLA accrues a credit entitlement; the finance admin who notices an unapplied credit files a credit-miss dispute pointing at the ledger entry. Resolution applies the credit against the current cycle and, if the disputed cycle already paid, generates a refund or carries the credit forward at the finance team's election.
Tax-Exempt Certificates and State Jurisdictions
Tax exemption is the most common newly-incorporated customer adjustment. A freshly enrolled master sees regular tax rates on the first invoice until the resale or tax-exempt certificate uploads. The certificates module accepts PDF, JPG and PNG uploads; the system checks basic formatting and writes the file hash to the audit trail. Certificates apply retroactively to the current billing cycle — uploading on invoice-day-25 still exempts taxes on that cycle's invoice, which spares the finance admin a dispute round-trip.
State-by-state multi-certificate uploads handle customers with operations across multiple tax jurisdictions. A retail master with stores in twelve states uploads twelve separate certificates and the system applies each certificate to the lines whose service address matches the issuing state. Certificate renewal is tracked against the certificate's stated expiration date; the portal sends an email reminder 60 days before expiration so the finance admin can upload the new certificate without interruption.
Cost-Center Allocation and Subsidiary Branches
Cost-center allocation is the layer that connects line lifecycle to finance accounting. A line tagged with cost-center R-301 propagates that tag into the invoice line item and the CSV export. The tagging taxonomy is the customer's own — Verizon Business accepts any string up to 64 characters as a tag. Multi-tag assignments split a line's charges across two or more cost centers by a configurable percentage, useful for shared-resource accounting on fleet wireless. Tag taxonomy can import from an ERP system once the primary admin enables the integration.
Subsidiary branches in a multi-line master hierarchy carry their own default cost-center prefix and their own invoice view. A regional supervisor who holds a regional secondary scope sees only their branch's invoices and can tag lines within the branch. Consolidated invoices for the primary admin roll up every branch with the tags preserved, so finance teams run a single reconciliation across all subsidiaries without exporting thirty separate PDFs.
Payment Methods, Approval SLAs and the Portal Grid
Payment methods are configurable per master in the billing-settings module. ACH pull from a business checking account is the default because it carries no interchange margin and settles within two business days. Wire transfer is accepted for multi-cycle credit positions where the finance team prefers manual control. Corporate credit card is accepted up to Mid-Market tier volume; Platinum and Diamond masters typically move off card to avoid the percentage fee. Legacy paper-check remittance is accepted through a lockbox address for envelope accounts that predate digital migration.
The portal grid summarises the operational SLAs for the primary payment and dispute actions. Each row answers how long the action takes and which payment method the workflow supports. Approval chains on finance secondaries follow the same two-step reviewer-approver pattern documented in the account management reference, with a primary-admin escalation for invoices above the configurable threshold.
| Action | SLA | Supported Method |
|---|---|---|
| Invoice generation | Cycle close + 2 business days | PDF and CSV delivery |
| Dispute opening | Within Net-30 of invoice date | Any invoice line item |
| Payment by ACH pull | Settle in 2 business days | Business checking account |
| Payment by wire | Settle in 1 business day | Remit to lockbox routing |
| Payment by corporate card | Settle same day | Up to Mid-Market tier |
Escalation Paths for Billing Exceptions
Most disputes resolve inside the portal without human escalation. For the cases that do escalate, Platinum and Diamond tier masters reach a named finance-team liaison through the connect-team directory. The liaison owns the dispute case from open to close and coordinates with the customer's finance admin on complex allocation questions. Urgent billing exceptions that cascade to service suspension risk reach 24/7 support at 1-877-333-7117 so operations continue while the billing question resolves in the background.
The billing portal aligns with the FTC privacy framework for customer-payment data handling. ACH account numbers are tokenised at first entry and the portal never displays the raw number after save; card PANs follow PCI-DSS tokenisation rules. The audit trail records every payment-method change with identity, timestamp and masked value so the customer's internal audit team reconstructs the payment-method history without exposing the raw credentials.